3 replies to this topic

[pscEx]

Inside a cmd window the command

"C:\Dokumente und Einstellungen\Peter\Desktop\WinBuilder_01\Tools\upx.exe" -t "C:\Dokumente und Einstellungen\Peter\Desktop\WinBuilder_01\Projects\Standard\Target\i386\system32\shell32.dll" >upxx.txt 2>&1

brings the correct contents of upxx.txt

Ultimate Packer for eXecutables
Copyright © 1996,1997,1998,1999,2000,2001,2002,2003,2004,2005,2006
UPX 2.02w Markus Oberhumer, Laszlo Molnar & John Reiser Aug 13th 2006

testing C:\Dokumente und Einstellungen\Peter\Desktop\WinBuilder_01\Projects\Standard\Target\i386\system32\shell32.dll [OK]

Tested 1 file.

The script line

ShellExecute,"Open","#$q%Tools%\upx.exe#$q","-t #$q%pFileBox1%#$q >#$q%Tools%\upxx.txt#$q 2>&1"

shows the correct log

#05 [Success] Shellexecute: [Open] using: ["%BaseDir%\Tools\upx.exe"] with parameters: [-t "%BaseDir%\Projects\Standard\Target\i386\system32\shell32.dll" >"%BaseDir%\Tools\upxx.txt" 2>&1]

but brings an error
[attachment=425:attachment]
and upxx.txt is not generated.

My coding error or WinBuilder issue?

Peter

[Brito]

Hi Peter, I've tested both on console and on winbuilder and haven't found a solution..

Modified the command to use cmd.exe instead:

ShellExecute,Open,cmd.exe,"/c #$q%Tools%\upx.exe#$q -t #$q%Tools%\upx.exe#$q>#$q%Tools%\upxx.txt#$q"

This should be enough to test upx.exe itself and check the result - still didn't worked..


When you type "cmd /?" there are a few conditions wich should be respected, look on the end of the first page of instrutctions, not sure if this is the reason, but might help to understand this.

One thing is special chars like "&" wich need sometimes to be written as "&&" to be properly handled.

[pscEx]

Hi Peter, I've tested both on console and on winbuilder and haven't found a solution..

Modified the command to use cmd.exe instead:

ShellExecute,Open,cmd.exe,"/c #$q%Tools%\upx.exe#$q -t #$q%Tools%\upx.exe#$q>#$q%Tools%\upxx.txt#$q"

This should be enough to test upx.exe itself and check the result - still didn't worked..
When you type "cmd /?" there are a few conditions wich should be respected, look on the end of the first page of instrutctions, not sure if this is the reason, but might help to understand this.

One thing is special chars like "&" wich need sometimes to be written as "&&" to be properly handled.

Well built trap
If you try a different script which has an 'execute' button (e.g. autoLocalization) the access violation occurs, too!

So maybe it is a brother of the 'cannot focus' issue.

Peter

[Brito]

So maybe it is a brother of the 'cannot focus' issue.

It might very well be..