Eject CDR does not unmount?

R

Russ Sprouse

When I eject a CDR, shouldn't WinXP be smart enough
to "forget" the CDR that was in the drive? When I put in
another CDR, it still shows the name of the previous CDR.

Anybody know how to fix this?

-- Russ
 
V

V Green

Russ Sprouse said:
When I eject a CDR, shouldn't WinXP be smart enough
to "forget" the CDR that was in the drive? When I put in
another CDR, it still shows the name of the previous CDR.

Anybody know how to fix this?

-- Russ

I think if you disable Autorun for an optical drive,
this will happen, as XP no longer checks the drive
every 1 sec or so.

Is this applicable to your situation?

Will also happen if your burning software is
up and running at the time you notice the
behavior-it turns autorun off as well.
 
G

Guest

I do have Autorun disabled. I'll try that, thanks.

But it seems to me, XP ought to be smart enough to know
that if you eject a removable disk, that disk is no
longer mounted. It is acting like a Microsoft
product. ;^)

-- Russ
 
S

Steve N.

V said:
I think if you disable Autorun for an optical drive,
this will happen, as XP no longer checks the drive
every 1 sec or so.

You may be correct about the Autorun effecting this behaviour, however
Autorun does not check the drive every second or so but only when the
tray is opened and closed.

Steve
 
V

V Green

Steve N. said:
You may be correct about the Autorun effecting this behaviour, however
Autorun does not check the drive every second or so but only when the
tray is opened and closed.

Steve

OK, if you wanna split hairs with me...

"Autorun" actually refers to a FILE with that name
on a CD or some other types of removable media
that, if found, automatically
gets executed as soon as it is found after said media
is inserted and the filesystem is mounted and active.

The service that performs this function is generically
referred to as "autoplay" or "autorun", even though
the actual service is probably the removable storage manager.

And, unless XP is different from other versions of NT
that preceded it, it absolutely DOES poll the drive
about every 1 - 1.5 sec. to see if the media's been changed.

It does NOT rely on the drive itself to report media
changes, as some of them don't.

If this behavior is verifiably different in XP from
W2K (which is where I last checked on it) please
enlighten me and post some links to your source,
as I don't want to be the provider of incorrect information ;-)
 
S

Steve N.

V said:
OK, if you wanna split hairs with me...

"Autorun" actually refers to a FILE with that name
on a CD or some other types of removable media
that, if found, automatically
gets executed as soon as it is found after said media
is inserted and the filesystem is mounted and active.

The service that performs this function is generically
referred to as "autoplay" or "autorun", even though
the actual service is probably the removable storage manager.

And, unless XP is different from other versions of NT
that preceded it, it absolutely DOES poll the drive
about every 1 - 1.5 sec. to see if the media's been changed.

It does NOT rely on the drive itself to report media
changes, as some of them don't.

If this behavior is verifiably different in XP from
W2K (which is where I last checked on it) please
enlighten me and post some links to your source,
as I don't want to be the provider of incorrect information ;-)

Yes, you are correct, autorun refers to autorun.inf on a CD as you
described. Thanks. I am not afraid of being corrected either :) What I
meant was auto-insert notification.

Still, I have never observed any peiodic polling of a CDROM drive in any
version of Windows, regardless of auto-insert notification settings on
the drive. What I have observed is that when a CD is put in the drive
Windows checks the drive and reads the disc info from it (disc type and
volume name, if applicable), which can be ovserved if My Computer is
open, a disc inserted and the disc name and/or disc type is updated in
the My Computer window. The only times I have seen this not happen was
when there was a problem with the drive itself, the cabling, or jumper
settings on the drive, and that was usually also accompanied by
difficulty reading the disc contents in general. I suppse a driver issue
could also account for it, but that I have not seen.

I apologize if you think I was trying to correct you for any other
reason than trying to get at accurate information, and if you can supply
documentation show that Windows XP does indeed poll optical drive
periodically I would be very interested in reading it, as I don't think
I want my systems wasting time checking a CDROM drive every 1 - 1.5 seconds.

Steve
 
V

V Green

Steve N. said:
Yes, you are correct, autorun refers to autorun.inf on a CD as you
described. Thanks. I am not afraid of being corrected either :) What I
meant was auto-insert notification.

Still, I have never observed any peiodic polling of a CDROM drive in any
version of Windows, regardless of auto-insert notification settings on
the drive. What I have observed is that when a CD is put in the drive
Windows checks the drive and reads the disc info from it (disc type and
volume name, if applicable), which can be ovserved if My Computer is
open, a disc inserted and the disc name and/or disc type is updated in
the My Computer window. The only times I have seen this not happen was
when there was a problem with the drive itself, the cabling, or jumper
settings on the drive, and that was usually also accompanied by
difficulty reading the disc contents in general. I suppse a driver issue
could also account for it, but that I have not seen.

I apologize if you think I was trying to correct you for any other
reason than trying to get at accurate information, and if you can supply
documentation show that Windows XP does indeed poll optical drive
periodically I would be very interested in reading it, as I don't think
I want my systems wasting time checking a CDROM drive every 1 - 1.5 seconds.

Steve

OK, did a little research and perhaps found the answer
to the OP's question:

http://support.microsoft.com/?kbid=817357

but was actually looking for stuff re: the polling
activity.

Found this:

"This behavior can occur if the Auto Insert Notification option is
enabled in Device Manager. If this option is enabled, Windows checks
for the presence of a CD-ROM in the CD-ROM drive every few
seconds. Most CD-ROM drives return an answer directly, but some
drives blink the drive light before returning an answer. This behavior
can occur with IDE, SCSI, and proprietary CD-ROM drives. "

from:

http://support.microsoft.com/default.aspx?scid=kb;en-us;138598

I can attest to the accuracy of the statement, as many optical
drives I have had would blink their status light as described. My
current drives don't.

I know that this is an old reference, but the same thing was
still going on as of W2K as I had an exchange with another
user about a year ago who was running an extremely
computationally intensive real-time app that would "burp"
every few seconds...when I suggested that
he disable AIN, the problem went away.

So, it would suggest that AIN was still polling the drive...

Perhaps XP has a different methodology, I haven't noticed.
It may instead use the methods detailed here:

http://support.microsoft.com/default.aspx?scid=kb;en-us;163503

which would do away with drive polling---
 
S

Steve N.

V said:
OK, did a little research and perhaps found the answer
to the OP's question:

http://support.microsoft.com/?kbid=817357

but was actually looking for stuff re: the polling
activity.

Found this:

"This behavior can occur if the Auto Insert Notification option is
enabled in Device Manager. If this option is enabled, Windows checks
for the presence of a CD-ROM in the CD-ROM drive every few
seconds. Most CD-ROM drives return an answer directly, but some
drives blink the drive light before returning an answer. This behavior
can occur with IDE, SCSI, and proprietary CD-ROM drives. "

from:

http://support.microsoft.com/default.aspx?scid=kb;en-us;138598

I can attest to the accuracy of the statement, as many optical
drives I have had would blink their status light as described. My
current drives don't.

I know that this is an old reference, but the same thing was
still going on as of W2K as I had an exchange with another
user about a year ago who was running an extremely
computationally intensive real-time app that would "burp"
every few seconds...when I suggested that
he disable AIN, the problem went away.

So, it would suggest that AIN was still polling the drive...

Perhaps XP has a different methodology, I haven't noticed.
It may instead use the methods detailed here:

http://support.microsoft.com/default.aspx?scid=kb;en-us;163503

which would do away with drive polling---

Thanks a lot. Learn something new every day (on a good day). Guess I'm
not too old of a dog yet :)

Steve
 
G

Guest

Russ Sprouse said:
When I eject a CDR, shouldn't WinXP be smart enough
to "forget" the CDR that was in the drive? When I put in
another CDR, it still shows the name of the previous CDR.

Anybody know how to fix this?

-- Russ
Oh, ya btw, i dun tink it is hardware prob. coz laz time me too got da same
prob..all i did was formatt my hdd and reinstall winxp pro sp0.. it got to do
sumtin wit software/registry missing.. try to search at
http://www.freshdevices.com/index.html..try the fresh diagnose or fresh ui..
i tink it may help..reply if tt helps.. GoooOoD LuCk !! bYeZ!!!
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top