Hi, Paul - and all.
I probably should have added that I seldom write to SD cards. My only use
of them, almost, is to transfer photos from my digital camera to my
computer. I do much more reading from them than writing to them, so the
cache is seldom a consideration.
My first post was not to advocate yanking, but to point out the option in
"Policies", which is hidden so well that few users are aware of it.
RC
--
R. C. White, CPA
San Marcos, TX
(e-mail address removed)
Microsoft Windows MVP (2002-2010)
Windows Live Mail 2011 (Build 15.4.3508.1109) in Win7 Ultimate x64 SP1
"Paul" wrote in message
SC said:
Even though I have my cards set up as R.C. does, I still do a Safely
Remove before yanking them out. I know it's not supposed to make any
difference and that it's supposedly safe to just pull them without the
extra step, but I have had cases where what I had copied to the card was
corrupt and unusable, and I'm not talking about large 1GB+ files. Not
often, but enough to piss me off when I went to use it later and it didn't
work. For the extra 3 or 4 seconds it takes, I would use the Safely Remove
anyhow.
My experience, over many years, is the notion of "cache flushing"
is a flaky subject. There have been problems in the past, that
were fixed with bailing wire and binder twine. And that didn't serve
to build my confidence. Especially when some of the flush
commands are emitted non-blocking, and there is a race condition
between the storage device flushing its cache, and the OS turning
off the computer power :-(
So I don't know about you guys, but I'll use Safely Remove for
anything capable of supporting that feature. I don't trust
software (OS) designers enough otherwise.
This isn't a very good example, but in Linux, with a floppy drive,
you can write a file to the floppy, wait two minutes, see no activity.
Now, if you don't "unmount" the floppy using a command, and then
pull out the floppy, you'll be missing some writes! You can wait
forever, and the stupid cache has pending writes inside it.
So as far as I'm concerned, being clever and saying "SD doesn't cache
and I can play fast and loose", holds no profit for me. There is
just too much that can go wrong (memorize giant table of OS versus
device type versus removal safety).
Paul