(Solved) Running WinRAR from AutoIt

[melmitts707]

Yes, I am going to feel really stupid after I find out why it don't work...

Running Windows 10 Pro, from the command line I enter

          WinRAR a -r- E:\UserID\DataBackup\BackupData.rar D:\UserID\Data\*

It works fine

From my AutoIt script I enter:

          RunWait("WinRAR a -r- E:\UserID\DataBackup\BackupData.rar D:\UserID\Data\*")

It doesn't work. No errors reported, the script finishes running but no file created

If I try using ShellExecuteWait I get multiple popup error messages.

Any guidance or words of wisdom about what I am missing an or doing wrong?

Thanks

Mel

 

Edited January 14, 2016 by melmitts707

[TheDcoder]

To run DOS (console) commands, try RunWait(@ComSpec & " /c " & 'commandName', "", @SW_HIDE)    ; don't forget " " before "/c"

Remarks in the Documentation for RunWait

Edited January 13, 2016 by TheDcoder

[water]

Welcome to AutoIt and the forum!

The help file is a great ressource
RunWait expects "The full path of the program".

[melmitts707]

I said I would feel stupid... I was using a different file compression program that didn't require the full path but apparently WinRAR does. Anyway, it works perfectly by including the program's full path.

Thanks to all for the help

Mel

[AdmiralAlkex]

You are saying that as if WinRAR is the weird one. In fact most applications DON'T add themselves to the PATH environment variable. Open a cmd window and run path and see for yourself.

[melmitts707]

I wasn't saying that WinRAR is weird, I was saying the other compression program (pacl) did not require it so I didn't think about or even try to run the WinRAR program with the full path when I should have. I know most programs must be ran with full path or added to the system PATH command. I just went temporarily brain dead...