rootx Posted August 21, 2017 Posted August 21, 2017 I need help to understand why the run function does not work, but if i use it directly inside cmd shell the command works. $where is the name of the jpg file ShellExecute(@ComSpec ," /k C:\Users\root\Desktop\test\exiftool.exe -p $FileName "&'"'&$where&'"'&" > "&'"'&@ScriptDir&"\out.txt"&'"',@ScriptDir);<----- work Run("C:\Users\root\Desktop\test\exiftool.exe -p $FileName "&$where&" > "&@ScriptDir&"\out.txt",@ScriptDir);<--- doesn't work I would use the run command! Thx
water Posted August 21, 2017 Posted August 21, 2017 What is the Return Value and the value of @error after calling Run? My UDFs and Tutorials: Spoiler UDFs: Active Directory (NEW 2024-07-28 - Version 1.6.3.0) - Download - General Help & Support - Example Scripts - Wiki ExcelChart (2017-07-21 - Version 0.4.0.1) - Download - General Help & Support - Example Scripts OutlookEX (2021-11-16 - Version 1.7.0.0) - Download - General Help & Support - Example Scripts - Wiki OutlookEX_GUI (2021-04-13 - Version 1.4.0.0) - Download Outlook Tools (2019-07-22 - Version 0.6.0.0) - Download - General Help & Support - Wiki PowerPoint (2021-08-31 - Version 1.5.0.0) - Download - General Help & Support - Example Scripts - Wiki Task Scheduler (2022-07-28 - Version 1.6.0.1) - Download - General Help & Support - Wiki Standard UDFs: Excel - Example Scripts - Wiki Word - Wiki Tutorials: ADO - Wiki WebDriver - Wiki
jchd Posted August 21, 2017 Posted August 21, 2017 What gives this? Run('C:\Users\root\Desktop\test\exiftool.exe -p $FileName "' & $where & '" > "&@ScriptDir&"\out.txt', @ScriptDir); Your version has issues with whitespace(s) in $where and/or @Scriptdir. This wonderful site allows debugging and testing regular expressions (many flavors available). An absolute must have in your bookmarks.Another excellent RegExp tutorial. Don't forget downloading your copy of up-to-date pcretest.exe and pcregrep.exe hereRegExp tutorial: enough to get startedPCRE v8.33 regexp documentation latest available release and currently implemented in AutoIt beta. SQLitespeed is another feature-rich premier SQLite manager (includes import/export). Well worth a try.SQLite Expert (freeware Personal Edition or payware Pro version) is a very useful SQLite database manager.An excellent eBook covering almost every aspect of SQLite3: a must-read for anyone doing serious work.SQL tutorial (covers "generic" SQL, but most of it applies to SQLite as well)A work-in-progress SQLite3 tutorial. Don't miss other LxyzTHW pages!SQLite official website with full documentation (may be newer than the SQLite library that comes standard with AutoIt)
Skysnake Posted August 21, 2017 Posted August 21, 2017 Put something like this into your script to see what it is using? Consolewrite("$where [" & $where &"] " & @CRLF ) Consolewrite("@scriptdir [" & $scriptdir &"] " & @CRLF ) Show the output? Skysnake Why is the snake in the sky?
Deye Posted August 21, 2017 Posted August 21, 2017 (edited) The run command doesn't look right to me, perhaps try : Run("C:\Users\root\Desktop\test\exiftool.exe -p " & $FileName & $where & " > " & @ScriptDir & "\out.txt", @ScriptDir) Edit: ohh, I see that is an internal variable, then please ignore my post .. Edited August 21, 2017 by Deye
rootx Posted August 21, 2017 Author Posted August 21, 2017 I read on the help... and now work... But why? Global $_ExePath = @ScriptDir & "\exiftool.exe" $where = "C:\Users\root\Desktop\test\1.jpg" $pid = Run(@ComSpec & " /c " & $_ExePath & " -p $FileName "&$where&" > "&@ScriptDir&"\out.txt",@ScriptDir) ConsoleWrite($_ExePath & " -p $FileName "&$where&" > "&@ScriptDir&"\out.txt"&@CRLF)
TurionAltec Posted August 22, 2017 Posted August 22, 2017 Calling "@comspec " calls cmd.exe command prompt to run the command. That is only required to call internal cmd commands such as "dir". In your case you are using a redirection to a file, "> "&@ScriptDir&"\out.txt The ">" operator is processed by cmd.exe. To Get AutoIt to handle the redirection will require the use of "StdoutRead" command. The following is untested, but a combination of the example in the StdoutRead help file, and your example. #include <AutoItConstants.au3> $iPID=Run($_ExePath & " -p $FileName "&$where, $sFilePath, @SW_HIDE, $STDOUT_CHILD) ProcessWaitClose($iPID) Local $sOutput = StdoutRead($iPID) ConsoleWrite("Output is: "&@CRLF&$sOutput&@CRLF) If you require your results in a file, @comspec is the easiest. If you are looking to manipulate the result immediatly in your script, you want StdoutRead / StderrRead.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now