this post was submitted on 19 Dec 2025
993 points (99.3% liked)
Funny
12657 readers
1425 users here now
General rules:
- Be kind.
- All posts must make an attempt to be funny.
- Obey the general sh.itjust.works instance rules.
- No politics or political figures. There are plenty of other politics communities to choose from.
- Don't post anything grotesque or potentially illegal. Examples include pornography, gore, animal cruelty, inappropriate jokes involving kids, etc.
Exceptions may be made at the discretion of the mods.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I was adding a second drive to a Windows desktop the other day and was tempted to assign it
A:. I just couldn't do it, though. It felt like I was violating some unspoken rule.Knowing Windows there's some legacy piece of code that checks if there's a floppy in drive A: and assigning a drive to it makes the OS fail to boot or something.
Some dumbass at my workplace assigned a network folder to D:, and made it a department standard (along with 20 other network folders assigned their own drive letters) and so now you can't access external drives if you restart the computer with one plugged in.
Because windows assigns D:\ to the flash drive before user initialization, and then overwrites it with the network drive when they log in, which breaks both for that session.
..………. Fuck.
I wonder how UEFI treats it; diskette drives were kind of sacred in the old BIOS days. How modern Windows handles it is anyone's guess, I'm sure it's been rewritten by Copilot by now.
I 100% assumed the same thing. Lol