Sometimes windows detects the USB stick but doesn’t assign it a drive letter. You can open up disk management and manually assign one.
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.
Thanks for the explanation!
It still does look funny though.
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.
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.
Could be like Linux where a lot of drivers are in the kernel and it doesn’t need to add drivers every time you plug something in
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
Just check it with lsusb on Linux and you’ll see the device and vendor id stays the same, independent of the port - else no udev rules would work
Don’t know though what ever the fuck windows is doing…
That’s very unlikely to happen. Once the driver is installed via Windows update it doesn’t magically uninstall itself.
“There’s a problem with your USB storage device”
*Continues to work just fine, just as if there is no problem*
“You need to format your USB drive” when there’s a perfectly usable FAT partition, which just happens to not be the first partition on the drive
Its because you didnt eject beforehand and theres orphaned inodes or data blocks
Except I always eject…
“That’s what she said” *laugh track*
“You need to manually eject your USB drive before you remove it” - statements dreamed up by the utterly deranged
Also, half the time when you try to eject it, it says “device busy” even though I’m not transferring files. Well, best of luck with that bud, I’m busy too yank
had that under linux too, because there’s still buffer to be written; but under linux i can at least check /proc/sys/vm/dirty_bytes to see how long it will take.
That’s because some program still accesses it
Could be just your file browser (“explorer”) that has a window open with the content of that device, or maybe some program has a hiccup and didn’t free it’s file pointer
No, it’s because I use it on linux and windows can tell. Windows hates me for my freedom.
Oh right that.
Sorry its been a while since I’ve used windows
They hate us because they ain’t us.
In the worst-case scenario, yes… but the wording on the Windows dialog literally says, “There is a problem with your device and you should scan it” and then when you do, “Your device is ready to use, no problems were found.” This, after it was ejected and got the safe removal notification. 🤷♂️
The file system was not unmounted cleanly so the dirty bit is 1 -> windows tells you to check the drive. This clears the dirty bit even if nothing was wrong.
deleted by creator
*laughs in ext4
laughs in btrfs and xfs
Laughs in ISO 9660 on disc.
☠️ in IBM 12-row/80-column punched card format
Fortran Watfor?
ext is just so simple yet beauti- and useful