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.
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.
About 15 years ago there was a company I did some work for (I was at an MSP at the time) who wanted to virtualize certain systems. Great. No problem. Except those systems needed to read floppies. Ok, I can pass it through. Except they wanted to get away from floppies. Great, let’s get you a newer system from a different vendor because this one went out of business when NT4 was still the big dog. Nope, too much money and the process would change.
So I had to reregister every DLL by hand because the installation didn’t work on Server 2008 r2. And every few months it would have to be done again because one of the guys thought himself a genius and kept messing up the janky ass workflow we put together to download info from thumb drives to a virtual floppy.
So plug in the drive, janky ass script creates a virtual floppy in drive A of the server, and manually (eventually I just wrote a script because I didn’t want to get that call on a Saturday) register each DLL every so often. And they’d rather pay the company I worked for several hundred dollars a month than pay a couple of grand one time that would have paid for itself in less than a year.
lol … I had this kind of argument with my wife for years.
She kept buying the smallest bottles of dish washing liquid for years … if it was smaller, to her it was much cheaper. I kept telling her that the price for the small bottle was more expensive per liter of liquid compared to buying it all in bulk.
I kept telling her that if you just bought one giant bottle for the best price when it went on sale, you’d end up buying more liquid and saving money over time. I’d buy a big huge bottle every year or so and it would last us months, then she’d revert to buying small bottles again.
Eventually, she realized that it was cheaper in the long run to buying big bottles … mostly because when you bought one giant bottle, you’d forget the problem altogether for about six months or even a year.
I know an OAP who pays two lots of $59 a month for two mobile phones. ‘you get more calls that way’. But it’s a big data plan - even the smallest phone plans have unlimited calls. Heck, one is a flip phone with no data. Can’t convince her she only needs to pay $23 each though.
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.
I 100% assumed the same thing. Lol
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.
It’s a code of honour at this point … no one uses A: in respect for all those drives that died for our sins
About 15 years ago there was a company I did some work for (I was at an MSP at the time) who wanted to virtualize certain systems. Great. No problem. Except those systems needed to read floppies. Ok, I can pass it through. Except they wanted to get away from floppies. Great, let’s get you a newer system from a different vendor because this one went out of business when NT4 was still the big dog. Nope, too much money and the process would change.
So I had to reregister every DLL by hand because the installation didn’t work on Server 2008 r2. And every few months it would have to be done again because one of the guys thought himself a genius and kept messing up the janky ass workflow we put together to download info from thumb drives to a virtual floppy.
So plug in the drive, janky ass script creates a virtual floppy in drive A of the server, and manually (eventually I just wrote a script because I didn’t want to get that call on a Saturday) register each DLL every so often. And they’d rather pay the company I worked for several hundred dollars a month than pay a couple of grand one time that would have paid for itself in less than a year.
lol … I had this kind of argument with my wife for years.
She kept buying the smallest bottles of dish washing liquid for years … if it was smaller, to her it was much cheaper. I kept telling her that the price for the small bottle was more expensive per liter of liquid compared to buying it all in bulk.
I kept telling her that if you just bought one giant bottle for the best price when it went on sale, you’d end up buying more liquid and saving money over time. I’d buy a big huge bottle every year or so and it would last us months, then she’d revert to buying small bottles again.
Eventually, she realized that it was cheaper in the long run to buying big bottles … mostly because when you bought one giant bottle, you’d forget the problem altogether for about six months or even a year.
I know an OAP who pays two lots of $59 a month for two mobile phones. ‘you get more calls that way’. But it’s a big data plan - even the smallest phone plans have unlimited calls. Heck, one is a flip phone with no data. Can’t convince her she only needs to pay $23 each though.
Oh thumb drive to virtual floppy sounds like when I had to work on old cnc machines that had a few modern upgrades
I keep my storage hard drive assigned to B so the optical drive is still D.
You monster.
I assigned my 18TB HDD to A because my second drive is B and my main drive is C, so I have to complete the pattern or my brain will explode.
Make it G: violate unspoken rules.
If you have never assigned a drive to F: or G:, how can you even say you lived?