Why doesn't Windows recognize a USB device plugged into another port? (2004)

Re:Why doesn't Windows recognize a USB device plugged into a... by Dylan16807 on Friday June 26, 2015 @03:54PM (#9787326)

Windows doesn't delay writes to a non-fixed drive by default, so the blinking light works fine.

A new write is possible but unlikely if the user is done with the drive, and again shouldn't cause major damage.

[ Parent | on HN ]

Re:Why doesn't Windows recognize a USB device plugged into a... by justin66 on Friday June 26, 2015 @07:21PM (#9788308)

File locking is still a thing.

The blinking light does precisely what it advertises. That's never really been the issue.

Damage certainly is unlikely if the thing is pulled while mounted. I wouldn't design the UI around that, though.

[ Parent | on HN ]

Re:Why doesn't Windows recognize a USB device plugged into a... by Dylan16807 on Saturday June 27, 2015 @05:08AM (#9789571)

An unplugged drive doesn't need locks, and if a program puts a file into an inconsistent state and leaves it there because it has a lock? Have they ever heard of crashing or power outages?

[ Parent | on HN ]

Re:Why doesn't Windows recognize a USB device plugged into a... by justin66 on Saturday June 27, 2015 @01:28PM (#9790836)

You want "them" to use files more safely so that you can implement a less safe means of mounting and unmounting devices? I'm grateful Microsoft (and others) do not think that way.

[ Parent | on HN ]

Re:Why doesn't Windows recognize a USB device plugged into a... by Dylan16807 on Saturday June 27, 2015 @03:46PM (#9791313)

If a program crashes when idle I don't want corrupt data. If I leave a program open in the background and I lose power or my video card driver takes down the system I don't want corrupt data.

I can somewhat excuse losing data if things go wrong during a save. At any other time it should be robust enough that my data is safe.

This is not just about unplugging drives, this is a general sanity measure.

[ Parent | on HN ]