FAT32, exFAT, and NTFS
FAT32, exFAT, and NTFS
37 comments
-
-
"There's a problem with your USB storage device"
Continues to work just fine, just as if there is no problem
-
Its because you didnt eject beforehand and theres orphaned inodes or data blocks
-
"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
-
No, it's because I use it on linux and windows can tell. Windows hates me for my freedom.
-
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. 🤷♂️
-
Except I always eject...
-
-
-
"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
-
-
*laughs in ext4
-
ext is just so simple yet beauti- and useful
-
@30p87 @SnotFlickerman until you are out of inodes...
-
-
Sometimes windows detects the USB stick but doesn't assign it a drive letter. You can open up disk management and manually assign one.
37 comments
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.
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.
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
That's very unlikely to happen. Once the driver is installed via Windows update it doesn't magically uninstall itself.