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.
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.
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