Here's my last stab at it...in no particular order...
You said earlier that you tinkered with the BIOS...to get it to
display the cdrw drive properly. Why did you do this?...after 2 years
with that drive?
Go to NEC's site...download the latest firmware for that drive and
install it.
Well, I've done the next round of experiments, and I'm still at
a loss. Based on suggestions from this thread (and other places),
I tried the following:
1. Switched the IDE data cable to CD-RW drive. Result: no
change - CD-RW drive still fails on power up even with
a different cable.
To check drives and controllers...
Take out that 2nd drive. Make SURE you change the jumpers on the
drive on the primary controller. Then put that 2nd drive on the
secondary controller...again making sure you set the jumpers properly.
Then boot into the CMOS only...don't let it boot into the operating
system. You should see both drives as master on their particular
controller. If you do, you don't have a problem with the mb,
controllers, or IDE drives.
One potential problem that you and Albert both have in common...
You've got more than 1 partition booting up. If something happens to
one of the partitions, the drive letters get changed...and that OFTEN
confuses the hell out of Windows. To get around this, you should
always letter your optical drives at the end of the alphabet. I use R
for the rom's and W for the writers.
Also, see if your BIOS has the option to delay the booting of the
drives. If it does, set one or both back a few seconds.
Here's what I think might be happening...
The 2nd IDE drive (older drive?) doesn't always boot up quickly enough
when its cold. So its not recognized on boot...and its normally the D
drive. When it doesn't boot properly, your cdrw then becomes the D
drive...and confuses Windows...which is not hard to do! lol
2. Disconnected 2nd HDD (to see if a power issue). Result:
no change - CD-RW drive still fails on power up.
Put it in as slave on the primary. Make sure you change the jumpers
on both drives. See what happens. Then put the 2nd IDE as the master
on the secondary. See what happens.
REMEMBER...you've got TWO issues here...the BIOS...and the operating
system. See how all this works in BOTH areas...BIOS and then
operating system.
I think these rule out a faulty IDE cable and possible power issues.
I was hoping the CD-RW drive would fail (blinking LED, open/close
button not working) on #3, and that would pretty much indict
the drive. However, since the drive _seemed_ to work when the
IDE data cable was detached, it's looking more like a IDE
controller (motherboard) problem.
Only the power seemed to work...and the POWER is not your problem.
Your problem is a data/IDE problem.
Check the controllers per above.
Now that things are put back together, the symptoms have changed
somewhat. Now the drive never works, even after restarts (warm).
Restarts used to make the CD-RW drive work OK.
So, two further questions:
1. Does it still look like a CD-RW drive problem? (I.e., should
I just go out and buy a new one?)
Possibly. But watch the CMOS boot. If the cdrw is recognized in a
boot, the data and the power for the drive...and the
controller...would seem to be working properly.
Make sure you have the controllers set up properly in the BIOS.
'Auto' is usually the best setting.
2. I'm still curious as to why any peripheral (CD-RW or otherwise)
would ever report different PNP Device IDs (part of which is
what the BIOS is displaying - the "_NEC NR-7700A" when things
work or the "NEC CDROM DRIVE: IDE" when things fail) and/or
firmware versions (the "1.23" when things work or the "2.0"
when things fail. Anybody have any insight into this? A
couple of postings in this thread confirmed seeing similar
identification discrepancies, but it still seems strange that
a peripheral's firmware would ever report two different values
for its identity.
That's what I didn't understand...from your initial post. When did
this start happening? That's unusual. That's why I suggest you get
the latest firmware upgrade and flash it.
Any software upgrades/installs lately...that may have caused the
problem. Norton? If yer runnin' realtime anti-virus protection, turn
it off for this drive.
Also, have you looked into your Event Viewer?
Can you try the drive in another machine?
Good luck, Mike...let us know.
Have a nice week...
Trent©
NUDITY...birth control for folks over 50!