Removing CD from drive causing bsod

  • Thread starter Thread starter Frank Morise
  • Start date Start date
F

Frank Morise

Thankfully, very little seems to crash my 3 year old install of w2k.

One consistent, if avoidable blue screener, is when I have a CD in the drive,
list it's directory contents or view a file (usually in Total Commander (aka Windows
Commander)), and remove the CD without first changing the directory listing to something
else.

Apparently , when the op sys goes to look for the cd again , and finds nothing,
it can't handle it. Is this a flaw that can be patched somehow or like the doc said, if
it hurts when you lift your arm, don't lift it.
 
Frank Morise said:
Thankfully, very little seems to crash my 3 year old install of w2k.

One consistent, if avoidable blue screener, is when I have a CD in the drive,
list it's directory contents or view a file (usually in Total Commander (aka Windows
Commander)), and remove the CD without first changing the directory listing to something
else.

Apparently , when the op sys goes to look for the cd again , and finds nothing,
it can't handle it. Is this a flaw that can be patched somehow or like the doc said, if
it hurts when you lift your arm, don't lift it.
Click to expand...

This may be an issue with Total Commander; do you get the same response when
you use Windows Explorer to do this?
On all my workstations (at least my home PC and the 3 workstations I just
tested here at work) if I have a folder open or similar on a CD (or any
removable drive, including mapped network shares) and I remove that drive
from use (i.e., ejecting a CD or disconnecting a mapped share) then the
folder window simply closes, with no error.
 
I haven't had a chance to test it yet with Explorer. Have you tried to actually open
a file in a text editor or play an mp3, THEN remove the disk while the file is still
active and open? I believe this is the circumstance that causes the bsod.
 
Frank Morise said:
I haven't had a chance to test it yet with Explorer. Have you tried to actually open
a file in a text editor or play an mp3, THEN remove the disk while the file is still
active and open? I believe this is the circumstance that causes the bsod.
Click to expand...

Opening a text file in Notepad from a network share or CD, then removing
said device, gives me no error unless I try to save, at which point I get a
long delay (as Windows looks for the destination, I presume) and then a
"Location not found" error, and the default save location is now "My
Documents."

An MP3 would be completely different. I didn't test this, because I know
I'll get an error :) Where a text file would be opened and completely
cached into memory, an MP3 will be "streamed" from its location, i.e. it
will be read little by little as the program asks for it. If I'm 1/2 way
through an MP3 and I disconnect the source, it obviously cannot continue to
play because the data is no longer available. Whereas this might not cause
a BSOD, it would most certainly generate some sort of negative response.

Which leads me to the question: is the file you're trying to use some sort
of database or is it a large file that needs to read from the source
regularly? Or does this happen with any file you open from CD?
 
Back
Top