We have some computers that get thumb drives plugged into them on a weekly basis. Every computer on the network has a drive mapped to F: and the thumb drives need to be set to G: for the program that accesses them to work properly. The problem is that Windows doesn't notice that F: is already taken by the mapped drive and usually tries to set the thumb drive to F:. Since there are several different thumb drives that get used as the G: drive, and Windows isn't particularly reliable for remembering the drive letter to begin with, this causes frequent problems. Is there any way to tell Windows what the first available drive letter is so I can avoid this?
Software/Hardware used:
ASKED:
November 22, 2006 10:13 AM
UPDATED:
November 27, 2006 9:49 AM
Thanks for the link to the code (which I’ll probably use later) but unfortunately it doesn’t solve the problem. Those scripts see the used drive letters correctly, so if Windows were using that same information it would be setting the thumb drives to G:. Since Windows is trying to use F: instead, I have to conclude that it’s looking at other information somewhere else (that doesn’t include mapped drives). Eventually it won’t be a problem as I intend to be using different network drives and getting rid of the F: mapping, but that’s at least a few months off and I don’t want to have to deal with the thumb drive problem until then.