Windows is great because if you plug your mouse into one USB port then maybe you move the mouse to another, it completely forgets that mouse ever existed and is like “setting up device!”
No it wasn’t just win95 but also IBM DOS and BIOS.
Keyboard not found, press F2 to continue asks the users to either plug in a keyboard and the press F2 on that one to continue or press F2 on an unrecognised keyboard so that the OS could pick it up.
It would then reload the driver’s for the PS/2 keyboard and continue as normal.
well technically… USB initialization isn’t that simple, when you change which port it’s plugged into, it’s numerated under that new memory space, so from the computers perspective, it’s a different number, it’s a different device.
Usually you have a vendor and a device id to identify the connected device on the bus
You’re right though, that in every different port it will get its own memory allocated an so on (at least I also believe that), but that’s no reason to not identify the already known device
there are a couple IDs in the device manager, if you look closely you will see where it changes, and then search the registry for that string and you will find how crazy Windows can be with USB hardware. Actually stripping out those ID’s is a huge pain. I only know because of having to make legacy hardware work for work
it was worse with USB1 and old drivers wouldn’t unload so then when you unplugged them and plugged them back in, sometimes they wouldn’t work unless you rebooted. Windows is stupid
Windows is great because if you plug your mouse into one USB port then maybe you move the mouse to another, it completely forgets that mouse ever existed and is like “setting up device!”
Bro, you know what this is.
It sure is great. If I remember correctly, there was a Windows 95 error saying “keyboard not found, press F2 to continue.”
No it wasn’t just win95 but also IBM DOS and BIOS.
Keyboard not found, press F2 to continue asks the users to either plug in a keyboard and the press F2 on that one to continue or press F2 on an unrecognised keyboard so that the OS could pick it up.
It would then reload the driver’s for the PS/2 keyboard and continue as normal.
well technically… USB initialization isn’t that simple, when you change which port it’s plugged into, it’s numerated under that new memory space, so from the computers perspective, it’s a different number, it’s a different device.
Usually you have a vendor and a device id to identify the connected device on the bus
You’re right though, that in every different port it will get its own memory allocated an so on (at least I also believe that), but that’s no reason to not identify the already known device
there are a couple IDs in the device manager, if you look closely you will see where it changes, and then search the registry for that string and you will find how crazy Windows can be with USB hardware. Actually stripping out those ID’s is a huge pain. I only know because of having to make legacy hardware work for work
it was worse with USB1 and old drivers wouldn’t unload so then when you unplugged them and plugged them back in, sometimes they wouldn’t work unless you rebooted. Windows is stupid
Is that just obfuscated on other platforms (like MacOS)? I don’t think I’ve ever had a Mac get “confused” by a device by changing its port.
the other OS’s don’t store the configuration in the registry, that’s the main difference
I see.
So Windows just needs to git gud.
Git gut by using a sane POSIX architecture just like any other OS out there.
That’s very unlikely to happen. Once the driver is installed via Windows update it doesn’t magically uninstall itself.