I'm new here, and I see from the archive that this is a perennial subject, but I haven't trawled enough yet to know if the answer to my particular problem is in there somewhere. I have this .bat (names changed to protect the innocent):
if exist q:\grep.exe goto qok net use q: /delete net use q: \\IPADDRESS\SHARE /user:USERNAME PASSWORD :qok c:\perl\bin\perl c:\pins\econ.pl This is all fine on my workstation, either kicked off manually or from the Windows Scheduler, and also fine if run manually on the server that is the intended host. But it doesn't work on the server from the scheduler. I've verified that the net use is working and that the Perl script does actually get started. I can't work out if it's having trouble with the fact the drive is mapped, or if it's because the mapping is set up with a different username/pw to the one the .bat runs under (mine, not SYSTEM). The c: in the line that calls the Perl was only put in to rule out another possible source of the problem, they don't seem necessary in the 3 ways of running it that work. Should I try doing the net stuff from inside the script, in a system(....); statement? NB The people running this server still have Perl back at 5.6 _______________________________________________ ActivePerl mailing list [EMAIL PROTECTED] To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
