I have a client with a strange problem...
He has two Dell PCs running WinXP Home that are sharing
data across a wireless network. Since Computer "A" has a
DOS program that requires data on Computer "B", I created
a batch file to connect the required drive letters during
startup.
This has been working fine until recently. Now, when the
batch file attempts to connect the drives during startup,
Computer "B" is not found, so the mapping fails. When I
investigated the problem, I found out that the batch file
is attempting to map the drives before the network
connection is available. After Computer "A" is fully
started, I can run the batch file with no problems.
Is there some way within WinXP that I can force programs
in Startup to wait until the system is fully running?
This problem appears to me to be a WinXP issue. My client
would prefer to blame Dell, but I don't think they are the
cause of the problem. Any help would be appreciated!
jcdecker
johncdecker@hotmail.com