Bill, The script I'm using does not contain the %SnifferDrive% variable. The date of the snfupd.cmd file is 10/31/2004 and the date of the zip (Bill_Landry_snfupd.zip) is 12/9/2004.
I'll replace the script with the current version over the weekend when I have some time and see if it resolves the issues. George -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Landry William Sent: Wednesday, June 15, 2005 11:03 PM To: [email protected] Subject: RE: [sniffer] Auto Sniffer Updates Did you happen to comment out or not change either of the following variables in your script to point to the correct drive\directory paths?: SET SnifferDrive=c: SET SnifferDir="c:\imail\declude\sniffer" Which cause the calls to these variables later in the script's execution to fail: %SnifferDrive% cd %SnifferDir% If IMail cannot change to the proper script drive\directory location, then that would cause the script's failure to run, and would account for why you would need to execute a second batch file to get to the correct script file location. Bill -----Original Message----- From: Glenn \ WCNet [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 15, 2005 2:31 PM To: [email protected] Subject: Re: [sniffer] Auto Sniffer Updates Well blow me down. That did the trick, least-wise it does for triggering by a test message! I'll know for sure when the next notification arrives. Thanks!!! G.Z. ----- Original Message ----- From: "George Kulman" <[EMAIL PROTECTED]> To: <[email protected]> Sent: Wednesday, June 15, 2005 4:06 PM Subject: RE: [sniffer] Auto Sniffer Updates You might want to try the following which resolved this problem for me (a while ago) 1. The IMail program alias is: c:\Sniffer\snfupd.bat 2. I created a .bat file which is: echo off cd\ c:\sniffer snfupd.cmd All of my Sniffer programs and files are in the c:\sniffer folder (directory) which isn't required but happens to be the way I chose to do it. George -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Brad Morgan Sent: Wednesday, June 15, 2005 4:54 PM To: [email protected] Subject: RE: [sniffer] Auto Sniffer Updates > That is what I'm using. I tried editing the .cmd file to do away > with the variables and hard-wire my parameters into it. It works > either way (before or after eliminating the variables) when executed > manually. It does not work via Program Alias -- my .snf file does > not change when an update notification arrives. > Procedure: I send a test message to the update address. I get back > a copy of the test message, and a "S n i f f e r update" notice > indicating that an update occurred . . but, in fact, an update > does NOT occur, the .snf file is still date/time stamped the same > (I'm not using the -N option on WGET at this point, so a download > should always occur). My guess would be either a permissions problem or a path problem. Verify that the account that runs the program alias has permissions to all of the data locations and verify that you are not relying on the PATH environment variable which may be different in each context. Regards, Brad Morgan IT Manager Horizon Interactive Inc. This E-Mail came from the Message Sniffer mailing list. For information and (un)subscription instructions go to http://www.sortmonster.com/MessageSniffer/Help/Help.html This E-Mail came from the Message Sniffer mailing list. For information and (un)subscription instructions go to http://www.sortmonster.com/MessageSniffer/Help/Help.html This E-Mail came from the Message Sniffer mailing list. For information and (un)subscription instructions go to http://www.sortmonster.com/MessageSniffer/Help/Help.html ---------------------------------------------------------------------------- --- This message and any included attachments are from Siemens Medical Solutions USA, Inc. and are intended only for the addressee(s). The information contained herein may include trade secrets or privileged or otherwise confidential information. Unauthorized review, forwarding, printing, copying, distributing, or using such information is strictly prohibited and may be unlawful. If you received this message in error, or have reason to believe you are not authorized to receive it, please promptly delete this message and notify the sender by e-mail with a copy to [EMAIL PROTECTED] Thank you This E-Mail came from the Message Sniffer mailing list. For information and (un)subscription instructions go to http://www.sortmonster.com/MessageSniffer/Help/Help.html This E-Mail came from the Message Sniffer mailing list. For information and (un)subscription instructions go to http://www.sortmonster.com/MessageSniffer/Help/Help.html
