IRQ problem w/Windows 95 boot

[Powder]

Lost access to my CD-ROM drive -- BIOS boot-up shows hardware & driver; no conflict in device driver (CDROM on IRQ15). However, during Windows boot-up, during autoexec.bat sequence, the AZTPNP.EXE file shows CD-ROM I/O:000, IRQ:00. I'm thinking this would be the source of the problem. (Manufacturer insists CD-ROM is bad... I doubt this since also had a problem w/floppy drive & got it back, no thanks to manufacturer!)

Any ideas for resolving this??

[JonYoung]

Which version of win95 are you using? I'm using osr1 and I've found that it has a few problems with IRQ. Also, how did you get the floppy back, maybe the same method will work? This is a little odd, because as far as I know there is no IRQ 00, so check the control panel, you might see 'this item is not using any resources because it is disabled or has a problem', in which case the IRQ is a symptom, not a problem.

------------------
Percussive maintenance, it may not work but it sure feels good...

[Powder]

I'm using Windows 4.00.095 B; IRQ 00 is reserved for the system timer... no resource problems i.d'd in the device manager. I have tried the same techniques to get my CD-ROM back as I did for the floppy (check connections, remove device & let the system recognize it again, check line entries in autoexec.bat & config.sys -- they are loaded as they should be).

It's that AZPNP line that seems to direct the system to the wrong IRQ. The CD-ROM shows on my system as an audio CD, instead of the data disc that is loaded. When I try to boot from the master restore diskette (w/the master CD in the drive), I either get no response from the CD-ROM OR (on one occassion) got the message "CDR103: CDROM not High Sierra or ISO-0660 format reading drive Q" (drive Q=CD-ROM).

Still welcoming all ideas!!

[JonYoung]

Ok, a couple more ideas...
That tagline (AZTPNP.exe) suggests plug and play involvement here... the sticky fingers of the PNP bios fiddling with your resources. check the settings for that, and for the system board extension if you have one, in case one of them has gone bonkers.
Also, it might not be the IRQ necessarily, have you checked the I/O allocation? the cd-rom might be clashing on the memory blocks it's using rather than the interrupts.
As to the problems recognising cds, what happens if you put an audio cd in, and does the drive ever work, or is this more than an unreliability problem?

------------------
Percussive maintenance, it may not work but it sure feels good...

[PostCode]

Try REming out the line in the autoexec.bat file that pretains to the cdrom drive. It may be ghosting the drive. Hope this helps.

------------------
Eric's BIOS Post Codes (http://www.webenet.net/~ntuser)