Is my PC crazy? Or is it just me......

[SmiZ]

Ok just wondering if anything similar has happened to anyone else.

I had just finished burning about six CDs in a row and put in a seventh and started it burning. I run a dual boot win2k / millenium setup and have an 8x8x24 IDE yamaha burner. All of these discs were burned with cdrwin 3.8A. The seventh disc started burning, and just after the TOC had been written, the program gave me the error: "Write command failed, device does not exist" Windows 2000 had come up with an error box saying I had unplugged a device improperly. When I checked windows explorer, both my regular CD rom and my burner weren't listed anymore. (both on secondary IDE channel) I hadn't touched or bumped the tower, and had been doing the exact same operations for a couple of hours.

I rebooted (warm) the machine and in POST, the secondary IDE channel was still not recognized. I then turned the power off and back on and only then were the two drives finally recognized by BIOS and windows. This is the second time I have seen this exact same situation on this machine.

What the hell is going on??

 

[MCS]

Yes this has happened to me before!!

I am not saying this is what your problem is but for me I had a slightly dodgy power connection to the back of the CD-ROM.

I suggest you open her up and have a "twiddle" with all the connections.

 

[SmiZ]

I've checked the power connections and didn't notice they were loose or anything out of the ordinary, but as I have two drives on the secondary channel, would both have to come uplugged to give this error?

Just seemed really strange to me as the tower hadn't been moved or touched in weeks. Must be gremlins or something.

 

[Edski]

Put them on your Primary IDE as slave to your hard drive and see if they show up in Windows

 

[SmiZ]

They show up now, and they are still on the secondary channel. What I don't understand is why they all of a sudden 'disappeared'? How does this happen? All I have to do to fix it is turn the PC off and back on. (cold reboot) The machine had been up for probably a week or two, so why does this happen every so often out of nowhere?