Trouble with @COMSPEC.

[iXX]

Hi!

I have trouble with this command to work (running command line utility):
 

RunWait(@COMSPEC & ' /c ' & '"C:\Program Files (x86)\ReHash\ReHash.exe" -None -SHA256 -Out:NoSpaces "D:\Bla Bla\File.Bin" > D:\BLE\aa.txt', "", @SW_HIDE)

In Windows cmd.exe, this works:

C:>"C:Program Files (x86)ReHashReHash.exe" -None -SHA256 -Out:NoSpaces "D:Bla BlaFile.Bin" > D:BLEaa.txt

I believe this is the same, syntax should be OK, so why it dont work??

Thanks for Your time!

 

[BrewManNH]

First, change /c to /k to keep the console window open, second lose the @SW_HIDE until you find out what your error is. Third, change the RunWait to ConsoleWrite and just have it print out the command you're using to see if it is identical to the manually entered line.

[Gianni]

also, try to run your command directly (without cmd) like this:

RunWait('"C:\Program Files (x86)\ReHash\ReHash.exe" -None -SHA256 -Out:NoSpaces "D:\Bla Bla\File.Bin" > D:\BLE\aa.txt', "", @SW_HIDE)

[orbs]

 

also, try to run your command directly (without cmd) like this:

RunWait('"C:\Program Files (x86)\ReHash\ReHash.exe" -None -SHA256 -Out:NoSpaces "D:\Bla Bla\File.Bin" > D:\BLE\aa.txt', "", @SW_HIDE)

 

@PincoPanco, the use of comspec is required for the output redirection (or at-least that's what my tests indicate).

@iXX, in addition to what BrewManNH suggests, it would be helpful if you can tell what is the indication for failure:

- do you get an error message?

- what is the return value of RunWait()?

- what is the value @error?

[Gianni]

maybe something to do with the "File System Redirection"
Take a look >here and >here

[BrewManNH]

It probably has something to do with the environment that the script is running in, as PincoPanco said, but hiding everything like that runwait command does, means no one will know. Which is why I always tell people having these issues is to never run hidden or with /c until they get it running.

[iXX]

So I tested:

- Change  @ComSpec from ' /c ' to ' /k '    ->    no change.

+ Remove @SW_HIDE    ->    console window opens and there something like "Program not name of in or out command, program or bat" (my bad translate to english, i hope you understand it).

- Then I change to ConsoleWrite:

ConsoleWrite(@ComSpec & ' /k ' & '"C:\Program Files (x86)\ReHash\ReHash.exe" -None -SHA256 -Out:NoSpaces "D:\Bla Bla\File.Bin" > D:\BLE\aa.txt')

Here is out:

>"C:Program Files (x86)AutoItSciTE..autoit3.exe" /ErrorStdOut "D:AU3hash.au3"
C:\Windows\System32\cmd.exe /k "C:Program Files (x86)ReHashReHash.exe" -None -SHA256 -Out:NoSpaces "D:Bla BlaFile.Bin" > D:BLEaa.txt>Exit code: 0    Time: 0.210

 

It looks identical.

 

- Running without @ComSpec as PincoPanco suggests    ->    no luck.

- Running my original code is without error message (exit code 0).

- The return value of my original code is 1, the @Error is 0.

- With @ComSpec ' /k ' the return value is  -1073741510, @Error is 0.

- Only working "solution" I found = make a .BAT file with this content:

 

"C:Program Files (x86)ReHashReHash.exe" -None -SHA256 -Out:NoSpaces "D:Bla BlaFile.Bin" > D:BLEaa.txt

... and RunWait("ThisBATfile").  It is solution like pig!

- With File System Redirection I am not familiar, need study.

 

If someone want to try this, the utility can be downloaded here: http://rehash.sourceforge.net/

[Gianni]

try using quotes in this way and it should work:

RunWait(@COMSPEC & ' /c ""C:\Program Files (x86)\ReHash\ReHash.exe" -None -SHA256 -Out:NoSpaces D:\Bla Bla\File.Bin > D:\BLE\aa.txt"', "", @SW_HIDE)

[iXX]

 

try using quotes in this way and it should work:

RunWait(@COMSPEC & ' /c ""C:\Program Files (x86)\ReHash\ReHash.exe" -None -SHA256 -Out:NoSpaces D:\Bla Bla\File.Bin > D:\BLE\aa.txt"', "", @SW_HIDE)

Dont work, BUT!  I add two more quotes to "D:Bla BlaFile.Bin" - because there is a space in the path, AND IT WORKS!!

RunWait(@COMSPEC & ' /c ""C:\Program Files (x86)\ReHash\ReHash.exe" -None -SHA256 -Out:NoSpaces "D:\Bla Bla\File.Bin" > D:\BLE\aa.txt"', "", @SW_HIDE)

THANKS A LOT for help!

SOLVED.

[Gianni]

... ah right!  also are needed quotes around source and destination filenames if there are spaces in the path ....