TruHak Posted September 1, 2010 Posted September 1, 2010 I have scripts that I use to install new versions of software each year and each year they seem to work with some minor path tweaks. However, this year I cannot get one command to fire off. The path is good because I can execute it from START>RUN, but under RunWait, ProcessWait, or ProcessWaitClose the executable won't execute. Here is the command line... RunWait(@ComSpec & '/c \\deploy1\install\licensed\sc\autodesk\Inv2011\Inv2011',@MyDocumentsDir,@SW_HIDE) Suggestions?
TruHak Posted September 1, 2010 Author Posted September 1, 2010 Correction on the path: RunWait(@ComSpec & '/c \\deploy1\install\licensed\sc\autodesk\Inv2011\Inv2011.lnk',@MyDocumentsDir,@SW_HIDE)
Beege Posted September 1, 2010 Posted September 1, 2010 (edited) Is the file in My documents? if so you try:RunWait(@MyDocumentsDir & '\deploy1\install\licensed\sc\autodesk\Inv2011\Inv2011.lnk','',@SW_HIDE) Edited September 1, 2010 by Beege Assembly Code: fasmg . fasm . BmpSearch . Au3 Syntax Highlighter . Bounce Multithreading Example . IDispatchASMUDFs: Explorer Frame . ITaskBarList . Scrolling Line Graph . Tray Icon Bar Graph . Explorer Listview . Wiimote . WinSnap . Flicker Free Labels . iTunesPrograms: Ftp Explorer . Snipster . Network Meter . Resistance Calculator
TruHak Posted September 1, 2010 Author Posted September 1, 2010 No, the path points to a remote installation folder.
BrewManNH Posted September 1, 2010 Posted September 1, 2010 Are you sure it doesn't run? Because you have the window hidden it might be running and you're missing it. Also, you're running a shortcut, does that shortcut point to a valid location on the computer you're running the script from? If it's pointing to a file on the server, and the shortcut doesn't use a UNC path to point to that location, for example uses C:\Somefile.exe, instead of \\deploy1\install\licensed\sc\autodesk\Inv2011\Somefile.exe then it won't work either because it's looking for Somefile.exe on the computer you're running the script from. If I posted any code, assume that code was written using the latest release version unless stated otherwise. Also, if it doesn't work on XP I can't help with that because I don't have access to XP, and I'm not going to.Give a programmer the correct code and he can do his work for a day. Teach a programmer to debug and he can do his work for a lifetime - by Chirag GudeHow to ask questions the smart way! I hereby grant any person the right to use any code I post, that I am the original author of, on the autoitscript.com forums, unless I've specifically stated otherwise in the code or the thread post. If you do use my code all I ask, as a courtesy, is to make note of where you got it from. Back up and restore Windows user files _Array.au3 - Modified array functions that include support for 2D arrays. - ColorChooser - An add-on for SciTE that pops up a color dialog so you can select and paste a color code into a script. - Customizable Splashscreen GUI w/Progress Bar - Create a custom "splash screen" GUI with a progress bar and custom label. - _FileGetProperty - Retrieve the properties of a file - SciTE Toolbar - A toolbar demo for use with the SciTE editor - GUIRegisterMsg demo - Demo script to show how to use the Windows messages to interact with controls and your GUI. - Latin Square password generator
TruHak Posted September 1, 2010 Author Posted September 1, 2010 Thanks for the input from all. Through more trial and error, I stumbled upon a syntax that is working and pass it along in case anyone cares. I have used the following for several years: RunWait(@ComSpec & '/c \\deploy1\install\licensed\sc\autodesk\Inv2011\Inv2011.lnk',@MyDocumentsDir,@SW_HIDE) I changed to: RunWait(@ComSpec & " /c" & '\\deploy1\install\licensed\sc\autodesk\Inv2011\Inv2011.lnk',"",@SW_HIDE) The key is the space between the first " and the /c". I take that space out and it does not kick the link off. I add the space and the it fires up every time.
BrewManNH Posted September 1, 2010 Posted September 1, 2010 (edited) Without the space before the /c the command line reads like this C:\Windows\System32\cmd.exe/c and Windows interprets that like you're trying to find the file "c" in the "C:\Windows\System32\cmd.exe" folder and there's a really good possibility that you don't have a file called c in a folder called cmd.exe on the system. Edited September 1, 2010 by BrewManNH If I posted any code, assume that code was written using the latest release version unless stated otherwise. Also, if it doesn't work on XP I can't help with that because I don't have access to XP, and I'm not going to.Give a programmer the correct code and he can do his work for a day. Teach a programmer to debug and he can do his work for a lifetime - by Chirag GudeHow to ask questions the smart way! I hereby grant any person the right to use any code I post, that I am the original author of, on the autoitscript.com forums, unless I've specifically stated otherwise in the code or the thread post. If you do use my code all I ask, as a courtesy, is to make note of where you got it from. Back up and restore Windows user files _Array.au3 - Modified array functions that include support for 2D arrays. - ColorChooser - An add-on for SciTE that pops up a color dialog so you can select and paste a color code into a script. - Customizable Splashscreen GUI w/Progress Bar - Create a custom "splash screen" GUI with a progress bar and custom label. - _FileGetProperty - Retrieve the properties of a file - SciTE Toolbar - A toolbar demo for use with the SciTE editor - GUIRegisterMsg demo - Demo script to show how to use the Windows messages to interact with controls and your GUI. - Latin Square password generator
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