C0deHunter wrote on 2021-11-06, 17:51:

Hello all, My LiteON IDE CD-ROM drive that used to appear correctly fine under Windows 8SE, all of a sudden has the yellow excla […]
Show full quote

Hello all,
My LiteON IDE CD-ROM drive that used to appear correctly fine under Windows 8SE, all of a sudden has the yellow exclamation mark and no matter how many times (or with different drivers) I update, it fixes it temporarily when the Windows session is active, but I when I reset or turn the system OFF, the yellow exclamation mark reappears.

Also worth noting that this IDE CD-ROM drive is detected correctly by the system BIOS, also under MS-DOS 7.1 (I have multiple boot OS)

Please let me know how should I fix this.

Thanks!

What does Device Manager state the problem is? Usually you get a summary when you double-click on the device entry.

"This device is either not present, not working properly, or does not have all the drivers installed.
"Error CODE 10
Try upgrading the device drivers for this device"

It recommends to update the driver, and when I do, it does it again upon the next reset.

Does the CDROM work OK booting to DOS 7?
Have you changed anything in the Windows Config.sys or Autoexec.bat ?
Loading a DOS CDROM driver can conflict with the Windows Protected mode driver (is why Windows install rems the MSCDEX line out of auto bat)

Check also for things like a soundcard CDROM IDE interface spontaneously re-enabling itself or something if you've got it plugged into a motherboard port.

(BTW that can happen on some cards that don't have the header installed even.)

Horun wrote on 2021-11-06, 20:31:

Does the CDROM work OK booting to DOS 7?
Have you changed anything in the Windows Config.sys or Autoexec.bat ?
Loading a DOS CDROM driver can conflict with the Windows Protected mode driver (is why Windows install rems the MSCDEX line out of auto bat)

Yes
No

OK, let me explain further:
I am using System Commander 2000, and have an option to boot from the following OS:

DOS 7.1
Win98SE
Windows ME
Windows 2000 Professional

This IDE CD-ROM is recognized under DOS, WinME and Windows 2000. It is only under Win98SE that has issue with it, and this is something that just happened recently, as it was working even under Win98SE since last year that I have installed the OS.

UPDATES:

1) I re-installed Win98SE, and it is still not recognized (the Intel BX INF drivers installs the primary fifo and secondary fifo drivers, but the yellow exclamation still remains.

2) I swapped this IDE CD-ROM with another good one that I know it works, and I still get the yellow exclamation.

3) Tested this newly swapped CD-ROM under DOS, WinME and Win2K, and it works with no issue.

This is driving me nuts...

OK, I found the culprit:

It was the size of the CF card installed on Secondary IDE: previously I had a 32GB Industrial CF card as my gaming 'hard-drive', and I did not have this yellow exclamation.

Recently, I cloned this drive to a bigger, 64GB Industrial CF (exact same make and model, Transcend), and I get this yellow exclamation mark on it.

Again it is only in Win98SE, as WinME/Win2K/DOS has no issues detecting this 64GB CF card.

Essentially this larger drive (set as master), makes the secondary slave drive (my IDE CD-ROM) undetectable under Windows 98SE.

C0deHunter wrote on 2021-11-07, 01:48:

OK, I found the culprit: […]
Show full quote

OK, I found the culprit:

It was the size of the CF card installed on Secondary IDE: previously I had a 32GB Industrial CF card as my gaming 'hard-drive', and I did not have this yellow exclamation.

Recently, I cloned this drive to a bigger, 64GB Industrial CF (exact same make and model, Transcend), and I get this yellow exclamation mark on it.

Again it is only in Win98SE, as WinME/Win2K/DOS has no issues detecting this 64GB CF card.

Essentially this larger drive, make the secondary slave drive (IDE CD-ROM) undetectable under Windows 98SE.

Well ! You never mentioned you made some changes and also never mentioned you also had a CF card. From your first post sounded like things were exact same as a year ago....just a CDROM 🤣
😁 Glad you figured it out.

Thank you! Still I wanted to learn why a larger drive would created this issue.

I don't think it's the size of the CF card. I'd rather assume it has something to do with the card's controller.