XP Home, Drives don't "hook up hard" at logon

[Guest +Bob+]

I have a laptop with XP-Home. When I log on, it does not "hit" the

network drives to check and see if they are there. The same problem

occurs returning from Standby - network drives are always hosed.

 

The only way to get them to hook up, or know if they are even

available, is to go into Windows Explorer and manually click on each

connection (drive). Then they hook up. FYI - they will all show as

"disconnected network drive" until I click on them.

 

In fact, even if the Windows 2.3K server is down (that the shared

drives are on), I won't know it until I go into Explorer and try to

manually connect. There are no notifications in XP-Home (unlike

win2k).

 

This has been true since I bought this laptop (several years) but the

problem seems to have accentuated with the addition of a wireless

netcard, which seems to connect a little later in the logon process to

the router. The result is that trying to use most programs (without

manually and carefully going through Explorer) causes programs that

access the drives to fail in various ways, some with more lasting

results. If I remember to go Explorer first, it is fine.

 

I wrote a program that opens a small text file on each drive and tried

running that at logon. Unfortunately I can let it run all day and it

will not cause the hookup to occur. Manually going through Explorer is

the only known solution I have.

 

It's not a server problem per se - all my win2k clients work

flawlessly. They also notify you if any drive does not hook up, a nice

feature XP Home seems to lack (Another MS innovation, can't have those

error messages confusing the dumbed down public!)

 

I know XP-Home networking has a certain lamosity factor in the

networking area, but this one is wearing on me! I'd use any solution

that simply hacks out the need to manually go through Explorer,

whether it's some automated way to force that specific MS "hit the

drive hard" feature to run, or a way to get XP to do it for me

automatically (and properly).

 

Thanks,

[Guest Bob I]

Re: XP Home, Drives don't "hook up hard" at logon

 

At logon all the drives should be mapped at that point, not prior. Write

a startup CMD file for that with the first line clearing all mapping.

 

NET USE * /D

then follow with the desired mapping

 

+Bob+ wrote:

> I have a laptop with XP-Home. When I log on, it does not "hit" the

> network drives to check and see if they are there. The same problem

> occurs returning from Standby - network drives are always hosed.

>

> The only way to get them to hook up, or know if they are even

> available, is to go into Windows Explorer and manually click on each

> connection (drive). Then they hook up. FYI - they will all show as

> "disconnected network drive" until I click on them.

>

> In fact, even if the Windows 2.3K server is down (that the shared

> drives are on), I won't know it until I go into Explorer and try to

> manually connect. There are no notifications in XP-Home (unlike

> win2k).

>

> This has been true since I bought this laptop (several years) but the

> problem seems to have accentuated with the addition of a wireless

> netcard, which seems to connect a little later in the logon process to

> the router. The result is that trying to use most programs (without

> manually and carefully going through Explorer) causes programs that

> access the drives to fail in various ways, some with more lasting

> results. If I remember to go Explorer first, it is fine.

>

> I wrote a program that opens a small text file on each drive and tried

> running that at logon. Unfortunately I can let it run all day and it

> will not cause the hookup to occur. Manually going through Explorer is

> the only known solution I have.

>

> It's not a server problem per se - all my win2k clients work

> flawlessly. They also notify you if any drive does not hook up, a nice

> feature XP Home seems to lack (Another MS innovation, can't have those

> error messages confusing the dumbed down public!)

>

> I know XP-Home networking has a certain lamosity factor in the

> networking area, but this one is wearing on me! I'd use any solution

> that simply hacks out the need to manually go through Explorer,

> whether it's some automated way to force that specific MS "hit the

> drive hard" feature to run, or a way to get XP to do it for me

> automatically (and properly).

>

> Thanks,

>

[Guest +Bob+]

Re: XP Home, Drives don't "hook up hard" at logon

 

On Thu, 19 Jul 2007 10:44:43 -0500, Bob I <birelan@yahoo.com> wrote:

>At logon all the drives should be mapped at that point, not prior. Write

>a startup CMD file for that with the first line clearing all mapping.

>

>NET USE * /D

>then follow with the desired mapping

 

Thanks Bob, I will give the "manual" mapping a shot.

[Guest Bob I]

Re: XP Home, Drives don't "hook up hard" at logon

 

 

 

+Bob+ wrote:

> On Thu, 19 Jul 2007 10:44:43 -0500, Bob I <birelan@yahoo.com> wrote:

>

>

>>At logon all the drives should be mapped at that point, not prior. Write

>>a startup CMD file for that with the first line clearing all mapping.

>>

>>NET USE * /D

>>then follow with the desired mapping

>

>

> Thanks Bob, I will give the "manual" mapping a shot.

>

 

Your welcome, mapping it though the cmd file is quick and if needed can

be run anytime you wish.

[Guest +Bob+]

Re: XP Home, Drives don't "hook up hard" at logon

 

On Fri, 20 Jul 2007 09:38:37 -0500, Bob I <birelan@yahoo.com> wrote:

>

>

>+Bob+ wrote:

>

>> On Thu, 19 Jul 2007 10:44:43 -0500, Bob I <birelan@yahoo.com> wrote:

>>

>>

>>>At logon all the drives should be mapped at that point, not prior. Write

>>>a startup CMD file for that with the first line clearing all mapping.

>>>

>>>NET USE * /D

>>>then follow with the desired mapping

>>

>>

>> Thanks Bob, I will give the "manual" mapping a shot.

>>

>

>Your welcome, mapping it though the cmd file is quick and if needed can

>be run anytime you wish.

 

 

Thanks again Bob I, this did it for me.

[Guest Bob I]

Re: XP Home, Drives don't "hook up hard" at logon

 

 

 

+Bob+ wrote:

> On Fri, 20 Jul 2007 09:38:37 -0500, Bob I <birelan@yahoo.com> wrote:

>

>

>>

>>+Bob+ wrote:

>>

>>

>>>On Thu, 19 Jul 2007 10:44:43 -0500, Bob I <birelan@yahoo.com> wrote:

>>>

>>>

>>>

>>>>At logon all the drives should be mapped at that point, not prior. Write

>>>>a startup CMD file for that with the first line clearing all mapping.

>>>>

>>>>NET USE * /D

>>>>then follow with the desired mapping

>>>

>>>

>>>Thanks Bob, I will give the "manual" mapping a shot.

>>>

>>

>>Your welcome, mapping it though the cmd file is quick and if needed can

>>be run anytime you wish.

>

>

>

> Thanks again Bob I, this did it for me.

 

You're welcome, please have a good day.