Drive Letter Conflict (Windows Operating Systems) - Kingston Technology DataTraveler Vault Privacy Anleitungen

Drive Letter Conflict (Windows Operating Systems)

As mentioned in the 'System Requirements' section of this manual (on page 3), the DTVP
requires two consecutive drive letters AFTER the last physical disk that appears before the
'gap' in drive letter assignments (see .) This does NOT pertain to network shares
Figure 11.5
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 DTVP 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 11.5 – My Computer
In this example, the DTVP 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 DTVP may attempt to use it as its second drive letter, causing
a conflict.
If there are no network shares on your system and the DTVP 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.
®
Document No. 48000012-001.A02 DataTraveler Vault - Privacy Page 27 of 29