I've made a couple of batch files that I run from laptops using WinXP. I had to put a drive mapping command in them because, apparently, dropping down to the OS from within Universe makes a new shell environment. Recreate your mapped drive with the NET USE command in your batch file. My process isn't perfect but before I do the NET USE command, I use the following method to branch around if the drive letter already exists:
if exist z:\nul then goto z.is.there net use x: \\127.0.0.1\sharename password /user:DOMANE\USERID /persistent:no :z.is.there Be sure to put in the valid DOMAIN\USERID and password. Then set the server IP and sharename and you should be good to go. Biggest issue this doesn't handle is if the z: is pointing to a different location than what you're wanting. Methods for ensuring that is a topic for a different discussion. HTH's BobW -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ray Buchner Sent: Thursday, March 23, 2006 7:40 AM To: u2-users@listserver.u2ug.org Subject: [U2] UV 10 and Windows 2003 Mapped Drives I have some simple DOS batch processes executed from Universe Proc's that are failing now that I moved Universe 10 to a Windows 2003 server. An example would be this seemingly simple one... copy d:\accounts\sklar\EDI.EXPORT\810.TXT Z:\Imports Z:\ Is a mapped drive to another 2003 server called ECOMM_PA1 When at a DOS command prompt (In windows) I can hit Z: and it connects perfectly. I can also execute the above copy command within the batch process perfectly. However, when I am in Universe and shell-out to DOS, I cannot hit this mapped drive Z: It gives the following error message... C:\>Z: The system cannot find the drive specified. I have triple checked all permissions on each side to no avail. I have also tried using a UNC path to ECOMM_PA1 which also failed. Does anyone have any ideas? -Ray ------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
