Mapping To Hard Drive

[timlab1955]

Okay, this is one for the techie (if you dare (LOL)). When my computer boots, it automaticly tries to map to my external hard drive through my wifi. Of course it can't and it states can't do it. But after a few seconds/minutes I can go to computers, click on it (red X) and it brings it up for the rest of the time or until I reboot the computer. How can I solve this? Thanks.

 

[MilesAhead]

When you map a drive to a letter in Explorer there's a box that's checked by default that says automatically reconnect at logon. Disconnect the drive. Map it manually. Uncheck the box before mapping.

I usually do .cmd files with net use statements to map drives since I only have a 2 PC network and the "other" PC is often not running.

cmd file might be something like:
@echo off
net use X: \\PCName\folder

I have a folder in my PATH that has a bunch of .cmd files and .exe that don't need installation dumped in there. Also have a command prompt pinned to taskbar. You can open a command prompt and type MyNetUse.cmd or have a shortcut for the batch file.

 

[timlab1955]

I figure if I leave the default (check auto) it would, but it seems like it needs a cup of coffee or something before it logs on. I have no clue where I would be a cmd file to make this auto? Got a hint for me?

 

[Fred Garvin]

Tim, if you right click on Computer, select disconnect network drive. You should see your external drive listed in the mapped drives to remove it.

 

[MilesAhead]

Here's an example to connect shared folder named SharedFolder on computer named MYPC as drive X:

(type the next 3 lines in Notepad)
@echo off
ping -n 20 127.0.0.1 > nul
net use X: \\MYPC\SharedFolder

Do File=>Save As and save it as MAP.CMD in Windows\System32 folder.
Drag a shortcut to it into your StartUp folder. (Type shell:startup in search line in Start button to get the StartUp folder)

The Ping command makes it wait about 20 seconds(or whatever number you put after the 'n'). That should give the other end of the network time to be active.

Google "net use" for more info on net use command.

 

[DeaconFrost]

You have two options:

1. Wait patiently, since you are connecting through Wi-Fi, or start using a wired connection.
2. See if your wireless card has a driver/app that lets you connect before login, such as the Intel ProSet.

I'm making an assumption here that you don't work in a corporate environment with mapped netwok drives (or you do and use a wired system). WiFi usually takes a lot longer to connect, and if not set up properly, won't connect until after a user logs in...and that's why your drives fail to be accessible right away. My user account maps 4 drives automatically, and if I am on Wi-Fi in my office, they will not connect at all. I run a script from my desktop to remap them, and all is well.

 

[timlab1955]

Your right I don't work in a corporate environment. In fact, I'm retired and watch over 4 dogs, 1 cat and 1 horse. But it got me interested and I'm wondering how it can be done. And yes I'm on wifi 99.9% of the time. As for the software to connect to the drive, I have found a program with my wifi called Intel ProSet Wireless, but really don't have any clue about how to give it that time to connect. Can you assist? Thank you.

 

[DeaconFrost]

I don't recall off the top of my head, but in the settings or advanced settings, there's a check box to enable the Wi-Fi connection to connect before you login. If you can find that, your drives should map properly once you do actually log in.