Drive Letter Conflict (Windows Operating Systems)
As mentioned in the ‘
System Requirements
’ section of this manual (on page 3), the DTL+
requires two consecutive drive letters AFTER the last physical disk that appears before the
‘gap’ in drive letter assignments (see
Figure 10.5
.) This does NOT pertain to network shares
because they are specific to user-profiles and not the system hardware profile itself, thus
appearing available to the OS.
What this means is, Windows may assign the DTL+ a drive letter that’s already in use by a
network share or Universal Naming Convention (UNC) path, causing a drive letter conflict. If
this happens, please consult your administrator or helpdesk department on changing drive
letter assignments in Windows Disk Management (administrator privileges required.)
Figure 10.5 – My Computer
In this example, the DTL+ uses drive F:, which is the first available drive letter after drive E:
(the last physical disk before the drive letter gap.) Because letter G: is a network share and
not part of the hardware profile, the DTL+ may attempt to use it as its second drive letter,
causing a conflict.
If there are no network shares on your system and the DTL+ still won’t load, it is possible that a
card reader, removable disk, or other previously-installed device is holding on to a drive-letter
assignment and still causing a conflict.
Please note that Drive Letter Management, or DLM, has improved significantly in Windows XP
SP3, Vista, and 7, so you may not come across this issue, but if you are unable to resolve the
conflict, please contact Kingston’s Technical Support Department for further assistance.
© 2011 Kingston Technology Corporation. All rights reserved. All registered trademarks and trademarks are the property of their respective owners.
Document No. 48008071-001.A02
DataTraveler
®
Page 22 of 22
