I've got a shortcut to a program that resides on a network drive (M:)
If I double-click the shortcut without the M: drive mapped, Windows (95 or NT, it does the same on both) somehow remembers where the program originally came from, and maps a DIFFERENT drive letter (F:) to the original UNC. It also modifies the shortcut and permanently changes the drive letter in the "Target" field. It looks like it grabs the first open drive letter.
My problem arises when this happens in a different office, across our WAN. Instead of their M: being mapped locally, the shortcut decides its going to find its long-lost home, and maps back to Minneapolis. This makes the program run very slowly from Washington DC.
So, my question is, how can I prevent Windows from remapping its own drive letter? Or at least make it map to the one I want?
You can duplicate this problem with any .EXE file. Just create a shortcut to an EXE on a network drive, then disconnect the drive & try to run the shortcut. After you run the program, check Explorer & you'll see a new drive mapping. Check the shortcut properties & you'll see the new drive letter there, too.