This really isn't a simple question. First, is the app running as a service, or is the machine left with a "user" logged on? I presume you are talking about the app running on an NT server...
If the app is running as a user, the problem is trivial, put a net use command in that user's logon script.
If the app is running as a service, (and nobody is logged on when it is running), the plot thickens. There is NO CLEAN answer that I know of. There are some NT registry hacks to run an application at startup. This app can be a script. Alternately, you can run a script from the windows AT command (or the easier WINAT, inf the resource kit).
The main issue will be making sure the same "username" is running all of the processes, because of possible conflicts in permissions. Attached are a couple of clippings from TechNet, which MAY work. I haven't tried them.
Good luck
Will Harper, MCSE
-----Original Message----- From: Jaye Mathisen [SMTP:mrcpu@internetcds.com] Sent: Thursday, April 08, 1999 3:53 PM To: toasters@mathworks.com Subject: Ridiculously easy question...
I'm just starting to use CIFS, and everything works fine, except one minor problem...
I would like NT (4.0SP4, if it matters), to attach a drive on system startup, rather than having to be logged in...
For various reasons, I cannot use UNC paths in my application, so I need to map the drive when the system boots, with a username and password...
Is this possible?
My filer is running 4.3.4, but I think I'm going to upgrade tonight to 5.2.1...