[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Bug-wget] VBScript and Task Manager
From: |
D'Amato, Paul J. |
Subject: |
Re: [Bug-wget] VBScript and Task Manager |
Date: |
Wed, 16 Apr 2014 18:13:23 +0000 |
Thank you Alex for your response.
I modified the run WshShell.Run command as suggested. Thank you!
I confirmed that the CurrentDirectory is what I expect. It is the location of
the script and the wget executable.
I was able to get wget to run from the task scheduler outside of the vbscript.
I was able to do this utilizing the "Start In" option.
I applied this to the vbscript task and the task completed!
Thanks to everyone on the wget bug team for your assistance.
Paul
-----Original Message-----
From: address@hidden [mailto:address@hidden
Sent: Wednesday, April 16, 2014 12:02 PM
To: D'Amato, Paul J.
Cc: address@hidden
Subject: Re: Re: [Bug-wget] VBScript and Task Manager
Greetings, D'Amato, Paul J
1st You didn't need loop for waiting download. It can cause error because wget
create file immediately. WshShell.Run has WaitOnReturn parametr. So You can try
something like "WshShell.Run runWget , 0, True"
2nd Possible variant - please check value of WshShell.CurrentDirectory
property. When You lauch script manually, it start from it directory. Sheduler
lauch script from some system directory. You can or assign value to
WshShell.CurrentDirectory (WshShell.CurrentDirectory = currentDirectory) or
(may be better) use "-P" wget option.
Best regards, Alex
The information in this e-mail is intended only for the person to whom it is
addressed. If you believe this e-mail was sent to you in error and the e-mail
contains patient information, please contact the Partners Compliance HelpLine at
http://www.partners.org/complianceline . If the e-mail was sent to you in error
but does not contain patient information, please contact the sender and properly
dispose of the e-mail.