I have a Gigabyte EX58-UD4 motherboard with optimized BIOS default settings loaded. Here's the various IDE connections that show up during POST:

IDE Channel 0 Master: (SSD1 model)
IDE Channel 0 Master: (SSD2 model)
IDE Channel 0 Master: (SSD3 model)

Detecting IDE drives...
IDE Channel 4 Master: TEAC DV-W516GA C4S6
IDE Channel 4 Slave : None
IDE Channel 5 Master: None
IDE Channel 5 Slave : None

In the Integrated Peripherals settings, on top of the optimized defaults, I further disabled any unnecessary devices, so now the settings are:

ICH SATA Control Mode     : IDE
SATA Port0-3 Native Mode  : Disabled
Onboard SATA/IDE Device   : Enabled
Onboard SATA/IDE Ctrl Mode: IDE

Serial port, LAN, 1398, onboard audio, USB controller: all are disabled.

Now what happens in this case is: when I select "Start Windows 98 Setup from CD-ROM", the whole thing fails at the first step where it tries to load CD-ROM driver (OAKCDROM/OEMCD001 I think) - it just says no CD drives found. But if I connect a SATA CD drive to a different SATA port, so that it shows up during POST as

IDE Channel 2 Master: ATAPI CD-ROM (I don't recall the exact model name)

then this drive does get detected and setup resumes. Why is this a problem? Because this same behavior happens in DOS - no matter what CD driver I use (VIDE-CDD, GSCD, OAKCDROM, etc.) with the motherboard's IDE connection - the IDE CD drive isn't detected but the SATA CD drive is. The latter is missing some very important functionalities - the front audio 3.5 mm jack and the audio out connector on the rear. So I really want to make the IDE CD drive work in DOS, but I've had no luck. Even tried out a couple of different IDE CD drives apart from the TEAC, but same result.

If anyone knows why this happens and how this can be resolved, I'd be very grateful for any pointers.

Solved the issue - I searched and found UDVD2.SYS - that's the one which is able to detect the CD drive without any issues. Used the /H and /D flags while invoking this driver in config.sys

Nice, maybe try xdvd2.sys too (newer). 2018-16-12 version: https://web.archive.org/web/20181020053006/http://optimizr.dyndns.org/dos/drivers.html

Oeps, link is 2018-10 now, will make no difference in case of xdvd2.sys

Edited March 13Mar 13 by deomsh
Addition

20 hours ago, sk9392 said:

IDE Channel 2

That is the source of problem with original driver. You have to connect your CD-ROM exactly to SATA ports 0-3 (ATA channels 0-1) that only can work in Legacy Mode on this chipset. And on SATA controller and PATA device it is possible too with help of the PATA-SATA converter, but not on addidional PATA controller port on the motherboard as it works in PCI Native Mode always.

On 3/14/2026 at 3:13 AM, SweetLow said:

That is the source of problem with original driver. You have to connect your CD-ROM exactly to SATA ports 0-3 (ATA channels 0-1) that only can work in Legacy Mode on this chipset. And on SATA controller and PATA device it is possible too with help of the PATA-SATA converter, but not on addidional PATA controller port on the motherboard as it works in PCI Native Mode always.

That actually did it! Now the Win98 install CD actually runs from the SATA CD drive (I connected it to SATA port 3), but strangely Win98 itself doesn't show that CD drive (either in explorer or Device Manager) even though the Win98 setup does recognize the drive. I'm not sure why this happens... If the setup detects the drive, shouldn't the OS? I have RLoew's SATA controller drivers installed.

13 minutes ago, sk9392 said:

If the setup detects the drive, shouldn't the OS? I have RLoew's SATA controller drivers installed.

Please be specific: which RLoew drivers, mention filenames.

Edited March 27Mar 27 by deomsh

55 minutes ago, deomsh said:

Please be specific: which RLoew drivers, mention filenames.

Sure, there are 2 "Primary SATA Controller" devices listed and 2 "Secondary SATA Controller" devices. For the "Primary SATA Controller" and "Secondary SATA Controller", the driver files are C:\WINDOWS\SYSTEM\IOSUBSYS\ESDI_506.pdr and C:\WINDOWS\SYSTEM\VMM32\IOS.vxd. Driver date for both is given as 3-4-2009. Driver Provider: "RLoew". Manufacturer: (SATA hard disk drivers).

Additionally there are three "Standard Dual PCI SATA Controller" devices listed as well. The driver file for these is "C:\WINDOWS\SYSTEM\VMM32.VXD (CONFIGMG.vxd)". Manufacturer: "(R. Loew / Microsoft hard disk drivers)". Driver provider: "RLoew". Date: 11-2-2015.

Finally two more listed: "Primary IDE controller (single fifo)". The driver files are the same as those for "Primary SATA controller", but the driver provider is Microsoft, manufacturer is "(Standard hard disk drivers)" and the driver is dated 1999. And there's "Secondary IDE controller (single fifo)". Same files, driver provider and manufacturer as Primary IDE controller device, but the driver date is 7-11-2025.

Out of all these, only the "Secondary IDE controller (single fifo)" device shows an exclamation mark (device is either not present, not working properly, or does not have all the drivers installed).

I hope that's comprehensive but if you need any more info, please let me know

Thanks for the info.

If you have used RLoew's SATAPTCH to patch your version of ESDI_506.PDR you should be 'good'. Otherwise better use original/ updated ESDI_506.PDR and patch again from command-line.

About Setup: I assume you run Setup from MS-DOS command-line, so Setup is the using the Dos drivers, until Windows 'takes over'.

If your Hard drive is SATA too, check if your CD-drivers are mentioned in CONFIG.SYS/ AUTOEXEC.BAT, with REM before is okay, even better. Sometimes Win9x needs these names as a 'hint' to 'find' a CD-ROM, even they are not loaded. Especially MSCDEX shouldn't be loaded before starting Windows of course.

Edited March 27Mar 27 by deomsh
Better reading of post before

Thanks @deomsh. I solved the issue by simply going into safe mode and removing the 3 "Standard Dual PCI SATA Controller" devices in Device Manager. After that rebooted into Win98, it installed some drivers and the CD drive was visible again

Happy to hear, lucky you  

After I responded to your post, my idea's where going in such a direction too.