problem accessing 2nd CD-ROM drive

[clayton]

I'm no longer able to use 2 CD-ROM drives on my system -
the same configuration was previously working fine for
the past year+. On my secondary IDE channel I have a
standard CD-ROM drive as master and a Sony CD-R drive as
slave (the problem exists no matter which is master, and
with any combination of 2 CD drives - the above, or 2
standard CD-ROM drives). The BIOS always correctly
identifies both, but in Windows (XP Pro) it will only
read from the master drive - if I put a disk in the slave
drive and try to read it, nothing happens, I can't eject
it (or have to wait 30-40 secs), and it usually causes
Explorer to stop responding (when I bring up the task
manager - if I end task it, the disk will usually eject,
and the system returns to normal). This sometimes happens
with both drives.

I've tried this with 40 & 80 strand cables (does it
matter on a CD drive?), and also on the secondary IDE
channel on my Maxtor PCI ATA133 card (this is a fairly
recent addition, but there has been no problem with it
for at least a month). I have 2 WD 20GB drives on my
master channel, the CD drive(s) on the secondary channel,
and a removeable drive bay with a Maxtor 40GB drive (for
backup) on the PCI card. My motherboard is an MSI
845EMax, with a P4 1.5 GHz processor.

Thanks for any help on this - I've never experienced
problems like this.

-Clayton

 

[Rich Barry]

XP Service Pack 1 hoses CD-ROM and floppy-disk access

By Brian Livingston

Microsoft's launch of its new Windows Server 2003 line is just taking place
as I write this, and my readers are starting to send fascinating tips about
its secrets. But while I'm compiling a new batch of articles on that
subject, the most interesting gotcha I've heard of this week involves
Windows XP with Service Pack 1 installed.

Jeffery Davidson, manager of information systems for the ATP Oil & Gas
Corporation, sent in the following well-documented tale. Have a listen:

· "Last week, my company purchased two new Panasonic Toughbook
laptops for some of our field personnel. I configured them with Windows XP
and Office XP, made sure that all of the patches and drivers were installed,
including XP Service Pack 1a, added all of the third-party software they
needed, and sent them out to the users.

"The users both came back yesterday and complained that they couldn't get
the floppy drives to work. After duplicating the problem, I spoke to
Panasonic's tech support, who told me that this was a problem with the SP1
installation. He referred me to Microsoft's Knowledge Base article 811839 --
'An I/O Device Error May Occur When You Access the Floppy Disk Drive in
Windows XP Service Pack 1.'

"Apparently, the problem is caused by Windows dynamically changing the
computer processor power state to a deeper idle state (from the C2 state to
the C3 state).

"To fix the problem. the article referred me to another KB article,
811840 -- 'How to Change the PromoteLimit Value for the Transition from C2
to C3 Power States.' This fix involved editing two strings of four bytes in
six binary keys in the registry, increasing the time that must elapse from
100 milliseconds to 500 milliseconds before Windows XP promotes the
processor from a C2 to a C3 power state.

"When I changed the registry, the two laptops were able to access their
floppy drives successfully.

"All well and good. Here's where I started to get concerned. Late last week,
one user who had a Compaq EVO D510 desktop machine suddenly started
experiencing severe endless loop crashes. Unable to repair the problem, I
decided to wipe the drive and reinstall Windows XP.

Initially, I was unable to restore the system from Compaq's restore disks.
The technical support folks at Compaq decided the problem was a bad restore
disk. I was able to manually install XP, and then manually install the
hardware drives from the corrupt disk.

"After the installation, I again installed ancillary programs and downloaded
patches, including XP Service Pack 1a. After SP1 was installed, I began to
experience problems with the CD-ROM drive intermittently not reading data
from the different CD-ROMs I was trying to install from.

"The error message I would get was 'An I/O error has occurred while
installing a file. This is usually caused by bad installation media or a
corrupt installation file.' I could either abort or retry. However, retrying
did nothing but repeat the error message.

"I decided to search the Microsoft knowledge base for 'I/O Errors' and
promptly saw the same KB articles I used yesterday to fix the laptops. I
decided to try the same thing on this desktop, even though I hadn't
experienced problems with the floppy drive.

"Surprisingly enough, it worked. But that's what bothers me. Why is XP SP1
causing these problems with different kinds of I/O operations? This has now
occurred on three out of the 60-odd machines I'm responsible for, so it's
widespread enough to want Microsoft to come up with a better solution than
manually editing several binary strings in the registry. For that matter,
I'd tell them myself, but they don't have a great feedback system, as you
probably know."