Re: External Drives
- From: "Timothy Drouillard" <hdrdtd@xxxxxxxxxxx>
- Date: Thu, 23 Apr 2009 15:36:12 -0400
WRT Internal card readers, if you're just inserting and removing cards from
the reader, then no you'don't haver to use the 'Safe To Disconnect' app in
your tray.
Using the app on a card reader disconnects the READER itself, and not the
cards you're plugging into it.
"BillW50" <BillW50@xxxxxxx> wrote in message
news:gsqd9b$ajl$1@xxxxxxxxxxxxxxxxxxxxxx
In news:75bc10F12oqt1U1@xxxxxxxxxxxxxxxxxx,
Phred typed on Thu, 23 Apr 2009 14:27:16 GMT:
In article <gso7lc$c14$1@xxxxxxxxxxxxxxxxxxx>, Ben Myers
<ben_myers@xxxxxxxxxxx> wrote:
BillW50 wrote:
In news:djvtu4hf9eilkfh6mlrgk470lrf7r1rf1o@xxxxxxx,
RnR typed on Wed, 22 Apr 2009 06:51:36 -0500:
Just wondering if usb external drives should have the usb service
stopped before unplugging the usb connection like other usb
peripherals? I never did it before but having a thumb drive fail
on me recently made me rethink this.
If I use remove with a built in card reader or my PC Card to USB,
they won't detect anything plugged into them later until a reboot.
And that is an interesting and anomalous result! ... Ben Myers
I've noticed a similar effect with one of those external USB
"multi-readers" (the ones that show up as several drives when plugged
in) running on a PC under Win XP Home.
When you finally work out which drive the bloody card is actually in,
it works okay. But when you finish the job and "stop" that drive, the
whole reader is disconnected and seems to require a reboot to get it
back. :-(
I noticed this happens on any card reader (multiple or not) and Cardbus to
USB cards on any computer running Windows XP Home. I don't know about
other systems, but I have Windows 2000 and 98SE here I could try the same
with.
On a related topic concerning USB drives (whether thumb drives or
external HDDs) I have found an annoyance when copying files from a
Windows XP Pro system running NTFS to the USB device as FAT32.
If the original file name is in standard 8.3 format the transfer
results in all uppercase names when read under Windows ME. For
examples, a file originally named "thisdata.dat" will appear as
"THISDATA.DAT" and "ab090423.txt" becomes "AB090423.TXT". (Names
originally in mixed case are not changed: "ThisData.dat" stays that.)
Of course, under current Windows operating systems this might be
regarded as just a cosmetic problem. However, it does create a bit of
a glitch when one is visually scanning a list of file names looking
for a particular file, or for an interlopper. (And it *is* untidy. :-)
Perhaps someone out there knows of an optional properties setting that
can prevent this sort of thing from happening?
Cheers, Phred.
I think I know the answer to this one. As 8.3 only supports uppercase only
(well on FAT formats anyway). I am talking about the ASCII characters in
the directory (folder). Although earlier versions of Windows will normally
show the first letter in cap and the rest in lowercase for in 8.3 format.
If it doesn't follow this rule, then it isn't really an 8.3 filename is my
belief on a FAT format.
Now here I am guessing... As I think NTFS doesn't really have a 8.3
filename support. So everything is stored in long filename. It doesn't
have to support it since it doesn't have to be compatible with
FAT12/16/32. When you transfer to FAT12/16/32, it sees it as 8.3 and
adjusts accordingly. Which means all caps.
--
Bill
Asus EEE PC 701G4 ~ 2GB RAM ~ 16GB-SDHC
Windows XP SP2
.
- Follow-Ups:
- Re: External Drives
- From: BillW50
- Re: External Drives
- References:
- OT: External Drives
- From: RnR
- Re: External Drives
- From: BillW50
- Re: External Drives
- From: Ben Myers
- Re: External Drives
- From: Phred
- Re: External Drives
- From: BillW50
- OT: External Drives
- Prev by Date: Re: External Drives
- Next by Date: Re: External Drives
- Previous by thread: Re: External Drives
- Next by thread: Re: External Drives
- Index(es):
Relevant Pages
|
