Why should recognizing each CD hamstring XP for 10 seconds?

[Guest]

Does it seem unreasonable to anyone else that Windows XP should freeze itself
(and me, the user) for 10 seconds or so every time a new CD is inserted into
a drive? I mean ... this is an interrupt-driven, multitasking, secure,
real-time-capable operating system, right? So why can't programs and the
user interface continue unimpeded when one puts in a new disk? Why should
the whole user interface thread come to a screeching halt, just to monitor a
CD drive?

Microsoft went to the trouble of creating a special cursor (the arrow with
the CD attached) to let us know what is going on; why couldn't they have just
put that effort into moving the CD recognition code into its own thread?

This flaw is a real irritant when doing a lot of CD and DVD reading and
writing.

 

[Robert Moir]

Does it seem unreasonable to anyone else that Windows XP should
freeze itself (and me, the user) for 10 seconds or so every time a
new CD is inserted into a drive? I mean ... this is an
interrupt-driven, multitasking, secure, real-time-capable operating
system, right? So why can't programs and the user interface continue
unimpeded when one puts in a new disk? Why should the whole user
interface thread come to a screeching halt, just to monitor a CD
drive?

Well given that my system doesn't behave in that way, and that its Windows
XP SP2 just like everyone else's, one of us has some kind of system fault or
issue thats changing the way XP behaves.

 

[Malke]

Does it seem unreasonable to anyone else that Windows XP should freeze
itself (and me, the user) for 10 seconds or so every time a new CD is
inserted into
a drive? I mean ... this is an interrupt-driven, multitasking,
secure,
real-time-capable operating system, right? So why can't programs and
the
user interface continue unimpeded when one puts in a new disk? Why
should the whole user interface thread come to a screeching halt, just
to monitor a CD drive?

Microsoft went to the trouble of creating a special cursor (the arrow
with the CD attached) to let us know what is going on; why couldn't
they have just put that effort into moving the CD recognition code
into its own thread?

This flaw is a real irritant when doing a lot of CD and DVD reading
and writing.

Actually, you have something wrong on your system. This is not normal
behavior and I haven't seen it on any of my 5 XP SP2 systems (Pro and
Home) or on any of my very many clients' machines. You need to
troubleshoot your system. Since you didn't tell us anything about your
computer's hardware, it is not possible to give you focused advice.

Old optical drives? Old, weak, and/or inadequate power supply? Huge
number of background programs running? Viruses/malware taking up system
resources? Not enough RAM? Slow processor? Etc. Etc.

Malke

 

[Guest]

Nothing antiquated about my Windows XP Pro SP2 system ... all Microsoft
updates installed, Pentium 2.6 GHz HT, 1 GB RAM, 2 SATA disk drives, 2 PATA
disks, 4 optical drives (newest is 3 months old), 450 watt power supply, no
other programs running, Norton AntiVirus reporting system clean, ...

But in Windows Explorer, or Nero Burning ROM, about 5-10 seconds after
inserting a new CD or DVD (blank or written or commercially pressed), the
program stops responding to mouse clicks or keys like DELETE ... for up to
about 10 seconds.

I'll try this on some other systems, but my recollection is that this
happens on ALL Windows XP systems.

Rainer

 

[Malke]

Nothing antiquated about my Windows XP Pro SP2 system ... all
Microsoft updates installed, Pentium 2.6 GHz HT, 1 GB RAM, 2 SATA disk
drives, 2 PATA disks, 4 optical drives (newest is 3 months old), 450
watt power supply, no
other programs running, Norton AntiVirus reporting system clean, ...

But in Windows Explorer, or Nero Burning ROM, about 5-10 seconds after
inserting a new CD or DVD (blank or written or commercially pressed),
the program stops responding to mouse clicks or keys like DELETE ...
for up to about 10 seconds.

I'll try this on some other systems, but my recollection is that this
happens on ALL Windows XP systems.

As Mr. Moir and I have told you, this is not normal behavior on XP
systems. I would definitely think about upgrading your power supply to
a better one as that could be the cause of your issue. Also, as I've
said, you could have far too many processes/programs and/or malware
running in the background. Having a gig of RAM would not help in that
instance.

If you want focused help, then please see these links for the kind of
information you need to supply:

http://www.dts-l.org/goodpost.htm


Malke

 

[R. McCarty]

Along with Malke's suggestion - I'd turn off Autoplay for the Optical drive
and also check the AutoPlay handlers that are loaded. It could also be
that the optical has thrown read errors and the controller has stepped
back it's operating mode from DMA to PIO. Could also be improper
Master/Slave/Cable Select jumpering.....Whatever the cause, it's not a
proper XP operating condition when mounting optical media.

 

[frodo]

But in Windows Explorer, or Nero Burning ROM, about 5-10 seconds after
inserting a new CD or DVD (blank or written or commercially pressed), the
program stops responding to mouse clicks or keys like DELETE ... for up to
about 10 seconds.

Just so you don't think you're being beaten up, I have seen this sort of
thing before, in Nero and Explore both. On systems that are modern, like
yours. With AutoPlay disabled. So, you're not the only one.

[you said "the program" appears to freeze, not the whole system -- right?]

I have often wondered WHY myself -- it is annoying. Basically the system
is mounting the drive, and during that time there are some low level
system things that get locked. Depending on how the application is
written, it may "pend" on that system resource (ie, wait pending its
availability). The situation is better or worse depending on how fast the
drive's firmware recognizes the disc -- today's drives have to recognize
lots of different disc types, and it can take a while. Combo drives tend
to be slowest, and blank media are slower too. XP is at the mercy of that
firmware and the driver that talks to it, so different maker's drives may
be more prown to this sort of delay.

You can make Explorer a bit more responsive if you turn on its
multithreaded options:

------cut-----
Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer]
"DesktopProcess"=dword:00000001
"SeparateProcess"=dword:00000001

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\BrowseNewProcess]
"BrowseNewProcess"="yes"
-----cut-----

the first two lines are for Windows Explorer, the later for Internet
Explorer. As for Nero, Nero is as Nero does...

 

[(PeteCresswell)]

Does it seem unreasonable to anyone else that Windows XP should freeze itself
(and me, the user) for 10 seconds or so every time a new CD is inserted into
a drive?

Yes - and I have the same reaction about XP supposedly at least having the
appearance of being a multi-tasking system.