The Windows A: drive is used for the operating system and the programs that are installed on it. The Windows B: drive is used for the data that is stored on it.
The C: drive is the default installation location for Windows, if you have a CD/DVD drive on your machine it’s likely the D: drive, and any additional drives fall in line after that. What about the A: and B: drives?
Image by Michael Holley.
Today’s Question & Answer session comes to us courtesy of SuperUser—a subdivision of Stack Exchange, a community-drive grouping of Q&A web sites.
The Question
If you’re a geek of a certain vintage—we won’t start naming years—the answer to this question is patently obvious to you. For younger geeks, however, the A: and B: drive have always been mysteriously unaccounted for on their computers.
SuperUser reader Linker3000 poses the question:
What and where, indeed? Thankfully we have some seasoned geeks to answer the query.
So your second drive is D:, your DVD is E: and if you put in a USB stick it becomes F: and the following drive G:. And so on and so forth.
But then, what and where are A: and B:?
The Answers
Image by AJ Batac.
Veteran geek Adam Davis offers an in-depth look at the missing drive letters:
SuperUser contributor Nick chimes in with an interesting anecdote building off of the third paragraph of Adam’s answer dealing with letter assignments:
By the time hard drives became cheap, the “expensive” computers typically had two floppy drives (one to boot and run common programs, one to save data and run specific programs). And so it was common for the motherboard hardware to support two floppy drives at fixed system addresses. Since it was built into the hardware, it was thought that building the same requirement into the OS was acceptable, and any hard drives added to the machine would start with disk C: and so forth.
During the transition from 5.25″ disks (which were actually, physically floppy) to 3.5″ disks (which were encased in a harder plastic shell) it was common to have both drives in one system, and again it was supported on the motherboard with hardware, and in the OS at fixed addresses. As very few systems ran out of drive letters, it was not thought to be important to consider making those drives reassignable in the OS until much later when drives were abstracted along with addresses due to the plug’n’play standard.
A lot of software was developed since that time, and unfortunately much of it expected to see long-term storage on the C: drive. This includes the BIOS software that boots the computer. You can still attach two floppy drives, boot into DOS 6.1, and use it as you would have in the early 90’s, with floppy drives A and B.
So largely the reason for starting the hard drive at C is for backwards compatibility. While the OS has abstracted data storage to some degree, it still treats A and B differently, in such a way that allows them to be removed from the system without altering the OS, caching them differently, and due to early viruses treating their boot sector with more caution than the hard drive’s boot sector.
So much for being rebellious indeed—if you want to live on the edge you can assign a data drive to A: and B:, but not a boot drive.
“You can assign the letters C through Z to each drive on your computer. A and B are usually reserved for floppy disk drives, but if your computer does not have floppy disk drives, you can assign A and B to volumes.”
So when I built a new computer recently with two internal drives, one for the OS and one for data, I thought, hey!, I’ll make my data drive “A”. I felt all rebellious until I discovered that Windows will not index drives lettered A or B. :(
Took me quite a while to figure out what the problem was, but I found some other people who suffered the same issue when they used A or B for a [primary] drive. As soon as I assigned that drive a different letter, windows indexed the drive. So much for being rebellious.
Have something to add to the explanation? Sound off in the the comments. Want to read more answers from other tech-savvy Stack Exchange users? Check out the full discussion thread here.