SI
SI
discoversearch

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor.  We ask that you disable ad blocking while on Silicon Investor in the best interests of our community.  If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.
Pastimes : Computer Learning -- Ignore unavailable to you. Want to Upgrade?


To: Sexton O Blake who wrote (74466)3/7/2011 8:59:10 AM
From: PMS Witch2 Recommendations  Read Replies (1) | Respond to of 110626
 
Windows keeps track of your system's disks, volumes, partitions, and drive letters in the Registry.

HKEY_LOCAL_MACHINE\SYSTEM\MountedDevices

When Windows boots, drive letters are assigned to volumes. Beginning with NT, users can change which letters are used. Because this information is not available at boot time, some other method is necessary to locate the data Windows needs.

On my system, where I have volumes both with and without drive letters, executing BCDedit reveals that if a letter is available, it's used in the Boot Configuration Database. Volumes without letters appear differently.

Example1: device vhd=[V:]\Taffy.VHD

Example2: device partition=\Device\HarddiskVolume8

Example3: device partition=W:

Checking my Registry reveals the LBAs where the volumes begin, the Drive Signature, and assigned letter in the same key. (A separate key for each volume.)

Why Microsoft does this, I do not know.

But . . .

On a system with removable media, it is possible to "lose track" and overwrite valuable data accidentally. If the system checks Disk Signatures before writing, this disaster can be prevented. I see no reason why this should apply to fixed media, beyond applying a "one solution fits all" approach.

Cheers, PW.