XP Home Edition "net map" script fails sometimes

[Bob Romus]

I have a network map script consisting of a command line
batch file with several commands like "net use F:
\\fileserver\Public". The map script resides on a another
read-only/guest access share on the same server. A shorcut
to this map script (\\fileserver\login\net_map.bat) is
created on the Startup folder on the WindowsXP HE client.
The problem is that sometimes no drives not mapped at all
and sometimes all the drives are mapped. I tried to put
the shortcut to the script either in the "all users"
or "current user" startup folder but with no luck. It
seems that Win98 SE clients don't exhibit this behaviour.
Any ideas why this is happenning?

[Mike Holmes]

Hi Bob
I think this problem might be one that i have experienced. On Windows
Xp the connection with the network seems to be slow in stating up. I
also have a script that runs from the startup folder and I've never
had any problem with it on Win98 machines. However when I added some
WinXP machines I began to get the odd message from users saying they
could not access the netwrk drives. Experimenting a bit I discovered
that if you logon immediatily the logon window appears the mapping
fails, if yoou leave the login window a couple of mintues the mapping
works OK. I do not have a technical solution to this problme but I
have found that a simple workaround in my login script seems to work -
if a mapping fails I get the script to wait 5 seconds and then try
again before giving up. This seems to have done the trick.
cheers
Mike

On Fri, 9 Jan 2004 01:35:47 -0800, "Bob Romus"
> wrote:

>I have a network map script consisting of a command line
>batch file with several commands like "net use F:
>\\fileserver\Public". The map script resides on a another
>read-only/guest access share on the same server. A shorcut
>to this map script (\\fileserver\login\net_map.bat) is
>created on the Startup folder on the WindowsXP HE client.
>The problem is that sometimes no drives not mapped at all
>and sometimes all the drives are mapped. I tried to put
>the shortcut to the script either in the "all users"
>or "current user" startup folder but with no luck. It
>seems that Win98 SE clients don't exhibit this behaviour.
>Any ideas why this is happenning?

[Bob Romus]

Thx for such a quick reply! I had a guess it could be
something like that and I have been searching for a way to
introduce a delay (though without testing first for a
failed connection). I have found it but implies the
existence of the CHOICE command which XP doesn't seem to
support anymore.I also don't exactly know how to test for
a failed connection. Can you asist me with some example or
link? My e-mail address is and
sometimes I'm online with Yahoo ID FLORINL67 or MSN ID
. Thanks a lot for your time, Bob

>-----Original Message-----
>Hi Bob
>I think this problem might be one that i have
experienced. On Windows
>Xp the connection with the network seems to be slow in
stating up. I
>also have a script that runs from the startup folder and
I've never
>had any problem with it on Win98 machines. However when I
added some
>WinXP machines I began to get the odd message from users
saying they
>could not access the netwrk drives. Experimenting a bit I
discovered
>that if you logon immediatily the logon window appears
the mapping
>fails, if yoou leave the login window a couple of mintues
the mapping
>works OK. I do not have a technical solution to this
problme but I
>have found that a simple workaround in my login script
seems to work -
>if a mapping fails I get the script to wait 5 seconds and
then try
>again before giving up. This seems to have done the trick.
>cheers
>Mike
>
>On Fri, 9 Jan 2004 01:35:47 -0800, "Bob Romus"
> wrote:
>
>>I have a network map script consisting of a command line
>>batch file with several commands like "net use F:
>>\\fileserver\Public". The map script resides on a
another
>>read-only/guest access share on the same server. A
shorcut
>>to this map script (\\fileserver\login\net_map.bat) is
>>created on the Startup folder on the WindowsXP HE
client.
>>The problem is that sometimes no drives not mapped at
all
>>and sometimes all the drives are mapped. I tried to put
>>the shortcut to the script either in the "all users"
>>or "current user" startup folder but with no luck. It
>>seems that Win98 SE clients don't exhibit this
behaviour.
>>Any ideas why this is happenning?
>
>.
>