Sometimes when I turn my computer on and it scans for all of my devices it says that my CD-Writer is ATAPI Incompatible and asks me to "Hit F1 to resume". Once it has booted up it then doesn't read any discs properly.
However this only happens about 50% of the time so I don't have a clue what it could be. In fact I don't even know what the error message means. Could anyone give me any help?
Thanks in advance.
That's odd, but I've seen strager things when dealing with atapi.
Can you give anymore info? How are your drives set up? What drives are installed on which cable and as master or slave? Does this happen under specific circumstances. For example, does it only happen after a warm reboot?
My CD - writer is the slave on my secondary IDE cable with my CD-ROM as the master.
Can't really tell if it only occurs at specific times, only that it tends to happen in spurts. So for a few boots it will happen and then for a few it won't. It had cleared up and then my PC started reading an incorrect amount of RAM. So I took the case off, pushed some power and IDE wires out the way and pressed my RAM sticks in. The RAM problem resolved but the ATAPI problem immediately came back. I thought it might be a cable connection problem but it will sometimes come and go without me even opening up the case and doing anything.
I am really stumped.
Actually, that kind of makes sense. The ram problem triggered the bios setup program and probably changed some settings related to your cd drives or the secondary ide port. Something to check, although most cdroms and cdrws are SUPPOSED to be udma capable, an awful lot of them aren't. Try entering bios and manually setting the secondary ide port to pio mode 4. Another possibility is that the dmi pool got rearranged and your getting resource conflicts.
Not sure what the error message means. Could just be that when whatever it is messes up, the cdrw doesn't respond to commands and your system spits out that message.
When the cdrw flakes out does it mess up the cdrom too?
99.9% chance this won't help but have u checked your CMOS battery?
You might possibly need to install an aspi manager for
your cdr drive. Programs like CDR-Win, Nero, NTI--just about
all of them need an aspi manager to work. The good news is
a Nero aspi manager will work with Fireburner or CDR-Win--
sometimes even better than the aspi managers those sites provide for their customers. (Golden Hawk's aspi manager would
not work for me under Win XP Pro, but Nero's will. So go figure.)
So your problem's fix just might require you to download and
install an aspi manager from somewhere that works on your
setup.
rick barclay
No. Wait. Don't hang up!
This is America calling!
It only happens sometimes when you boot?
That could point to a degradation in the capability of your drive to respond to the bios's autodetect routine. If you know or can acquire the proper values, hard setting them might be a worthwhile option.
Doubt if an aspi manager would help. Whatever is going wrong is happening during bios autodetect, long before the os starts to load.
Could be a failing cdrw drive, but I question that because of the history of the problem. Cmos battery is a possibility. Something else to try, unplug and reconnect all the ide cable connectors, including the connection to the motherboard. Sometimes the pins can oxydize and go intermittant. The cable itself could be going bad. If you have a spare try swapping it out. Make certain to get them plugged back correctly.
Last edited by kevinalm; 11-02-2002 at 11:20 AM.
