Came up with a solution, still working on making it perfect.
unmapped the drives that I had.

Created a new network location. used the same shares as I did before using
\\computer\share\ and then named the share according to the names I gave the
drive mapping. (used to be "I:\" now it's "I; drive")

doesn't give me errors when I boot, and I can read and write to the shares
as before. Biggest drawback so far is that I can't get disk usage stats like
bytes free space.

Sturmey


"sturmey" wrote:

If you do not check the "reconnect at login" box, it doesn't keep the mapping
after a reboot. This was not the solution.

It has to be a registry entry, I seem to remember seeing something like it a
few years ago, but I can't find it.

Sturmey

"sturmey" wrote:

That could work. Doesn't it delete the mapping though when I log out? I seem
to remember that happening in previous versions of Windows.

I'll try it and find out.
Sturmey

"Tom Allen" wrote:


"sturmey" wrote in message
...
Sorry. Not a viable solution.

I use the drives, but some of them are mapped to shares on other
computers
that aren't alwas on. Also two of the drives are mapped to a file
server
through openVPN which only comes up after I've logged in. (OpenVPN
allows me
to connect both inside and outside the firewall).

I need to have the drives mapped, I don't need to know if windows was
able
to auto connect at log in.


Delete the mapping and recreate it without 'reconnect at login' ticked ?

Tom