CP/M — Drive letters predate the IBM PC
## MS-DOS and Windows Around the time the MS-DOS operating system was being developed for the 16-bit 8086, hard disk units were becoming small and cheap enough to be fitted to higher-end IBM PCs. MS-DOS followed CP/M's convention of using drive letter assignment. By default, MS-DOS reserved A: and B: for attached floppy units. Drives C: and onwards were assigned for Hard Disk Drives (HDDs). This is why the Windows system is always located on C:. Unlike floppy drives, hard drives are always partitioned. This enabled multiple file systems to be stored on the much larger HDD. It was also necessary for the Master Boot Record (MBR) boot process. This is where the confusion started. The C: drive now referenced a file system on the first HDD, not the device itself. Nobody noticed initially, because it was very unusual to have more than one file system on a HDD. In other words, the C: drive apparently referenced the HDD, as well as the single file system on it. Hard disks got bigger and MS-DOS gained a graphical shell (Win 3x and Win 9x) and then was replaced by Windows NT. NTFS became the dominant file system and it became increasingly common to have more than one file system on a disk. For example, both the C: drive and the D: drive could be found on the same disk. Windows 3 from 20 years ago; the confusion was already baked into the pixels. ## RAID Adds to the Confusion RAID made the situation even more confusing, as it enabled a file system to be stored across multiple disks. The graphic designers of Windows, all too happy to further exacerbate this confusion, used a picture of a disk to denote a drive. If that wasn't bad enough, the drive nomenclature and iconography was extended to virtual objects such as network shared storage and file-backed drives, such as Macrium backups. On Windows operating systems with an NT kernel (i.e., every release since Windows 2000) the drive letter is only an alias for the mounted volume identifier. Windows will attempt to persist the same letter between reboots. If you're backing up using Macrium Reflect, the [Macrium rescue environment](https://www.macrium.com/blog/the-macrium-rescue-environment-cca57a4ebc61) will, if possible, replicate this. However, there are times when this is not possible. Windows will not assign the same drive letter to two volumes. This is the case even if they're identical, such as after a clone operation. You can read more about this in our [dedicated knowledge base article](https://knowledgebase.macrium.com/display/KNOW72/Drive+letters+assigned+to+restored+or+cloned+partitions).As IT budgets tighten, it’s time for a back to basics approach
Forget cyber security: Cyber resilience is what really matters today