Talk:USB mass storage device class
|This is the talk page for discussing improvements to the USB mass storage device class article.
This is not a forum for general discussion of the article's subject.
|WikiProject Computing / Hardware||(Rated C-class, Mid-importance)|
Mac OS 8.5.1 Driver Question
xbox 360, playstation 3, etc. mass storage
I don't know about the others, but the Xbox 360 only works with the fat32 file system, unlike the other operating systems.
Does it matter if you unplug a USB mass storage device without "Safely removing hardware" or the like? What happens if you unplug one during a file transfer? I've never noticed any problems, but these kinds of problems are subtle — Omegatron 03:30, 10 December 2006 (UTC)
It does not matter if you remove it without "Safely removing hardware". Also if you unplug one during a file transfer the file will become corrupted, although I am not sure if it corrupts the original file. I definitely do not recommend unpluging it during a file transfer. 184.108.40.206 11:10, 26 June 2007 (UTC)
- well, i unplug one after playing maple (i install it into my thumbdrive) and the next time i plug it in, the file is gone! the folder says it's empty, including my phone's backup! someone please help. Ragnaroknike 15:21, 28 July 2007 (UTC)
You definitely need to use "Safely remove hardware". The operating system mantains a cache, and if you remove the stick before telling windows to flush it (via safely remove hardware) you can corrupt the entire filesystem. —Preceding unsigned comment added by 220.127.116.11 (talk) 16:25, 6 July 2008 (UTC)
- Windows 2000/XP uses Write Behind caching on removable media for some odd reason. Pulling the usb cable or even pulling the card out of the reader before making it "safe" is a very bad idea. It is in my experience Windows will write "most" of the data immediately, but last bits won't be written in much as a few minutes sometimes. Safeing it will cause the write cache to immediately and completely flush. Windows 98 doesn't use Write Behind caching on removable media by default and is generally safe the pull the usb after you "think" the data is written. 18.104.22.168 (talk) 12:42, 26 July 2008 (UTC)
Is the scale to the right of the first image correct, seems like a long device to me. Judging by the Quarter used in the previous versions of the image, the length should be just above 80mm instead of 100mm. Bergsten (talk) 12:40, 17 November 2007 (UTC)
Limits ? Technical details ?
No backport to Linux kernel 2.2
The "Unix-like" section incorrectly states that "a backport to [Linux] kernel 2.2 has also been made". "Neither USB-Storage nor High Speed USB are supported in the 2.2 line of kernels." - According to www.linux-usb.org. Although some general USB functionality was back-ported to Linux 2.2.18+ ; I believe that to be the source of confusion. Madman420 (talk) 02:45, 12 May 2009 (UTC)
- There is a usb-storage driver since 2.2.18: http://lxr.linux.no/#linux-old+v2.2.18/drivers/usb/usb-storage.c
- I've added it as a reference. --scgtrp (talk) 03:18, 2 February 2011 (UTC)
Error in article regarding AutoRun
Malware and inherent vulnerability
Since Windows's AutoRun feature works indiscriminately on any removable media, USB storage devices became
- It does not use AutoPlay, but it continues to use autorun. Some malicious programs change autorun.inf so that double-clicking the drive, or right-clicking and selecting open causes it to run a copy of itself on the drive, which then performs the expected action.--22.214.171.124 (talk) 13:43, 19 December 2011 (UTC)
Having used various external USB drives on various PCs / operating systems I have *always* found them unreliable on large, long-running data transfers. By large / long-running I typically mean using something like rsync to synchronise changed data between disks, either both USB on the same computer, or both USB on different computers across ethernet or one USB external and one internal (IDE or SATA).
Without exception, various error messages and 'hangs' start to occur after a while and either the rsync fails on lots of files or else the transfer rate slows down enormously because of OS delays while waiting for time-outs or 'resetting' hardware.
I never experience such problems with two internal IDE drives.
The conclusion is that there is something unreliable about implementations of USB when used for large / long-running transfers. Whether it is inherent in the USB protocol, or ubiquitous across operating systems' implementations (Windows 2K / XP / 7; various Linux) the effect is the same - USB is not reliable for large / long-running data transfers.
Why is this protocol problem never addressed in USB reviews? Or discussed in articles about the protocol? Such failures with primary, internal disks would be intolerable. — Preceding unsigned comment added by 126.96.36.199 (talk) 07:57, 12 June 2011 (UTC)
A forum member at msfn.org using the handle Maximus Decim has packaged the USB Mass Storage drivers from Windows Me into an installer for Windows 98 Second Edition English version. Other forum members have made versions for other language versions of 98 SE. 188.8.131.52 (talk) 03:23, 6 February 2011 (UTC)
- Why is there a reference and external links to Linux drivers but it is a sin to add either type for Windows 98SE drivers? I want clarification of why one O/S is important but another is not?
- A link to the Maximum Decim Generic USB Mass Storage Device Drivers should be included in this article, because Microsoft no longer support the operating system, nor did they include generic support.
- • Sbmeirow • Talk • 17:46, 19 December 2011 (UTC)
Linux USB info
https://www.technovelty.org/linux/what-actually-happens-when-you-plug-in-a-usb-device.html — Preceding unsigned comment added by Sbmeirow (talk • contribs) 04:22, June 20, 2014