Mark Ingalls

Has anyone else experienced an Access Violation in powershell.exe after docking
/ undocking a laptop? I don't have an exact repro, but here are some of
the things I have configured that others may not have (I haven't determined
whether or not these items have a direct impact on the problem at hand):

1. Redirected 'My Documents' folder to a network drive
2. 'My Documents' folder made available offline
3. When docked, my laptop has both a wired and wireless connection to the
same subnet (wired connection is higher in binding order)
4. When I launch powershell, I'm placed in my u:\ (redirected mydocs) by
default.
5. Powershell Community Extensions installed
6. MoW's TabCompletion installed

If the current directory is a network drive and I undock my laptop, nearly
any action (even 'cd c:\temp') results in an Access Violation and powershell
needs to be shutdown. The same thing happens if a network drive is the current
directory and I dock my laptop. I haven't completely tested this with all
network drives, but since I'm placed in U:\ at powershell startup and I spend
most of my time there, I'm often see this problem.

I've hesitated to post this, as my company has some pretty strange desktop
/ laptop configurations (including ZenWorks from Novell) and I don't know
what all they have excluded from the standard Windows XP installation.

If anyone else has noticed (or specifically NOT noticed) this, please let
me know and I'll post this to connect as necessary.

Thanks,
Mark