[QUOTE=megamaced]
WOW, an old 486/Windows 3.11 query! 
What CD-ROM driver are you using? You should use Microsoft’s generic DOS driver: MSCDEX
MSCDEX–Examples
Loading and enabling a single CD-ROM device driver
This example shows the relevant CONFIG.SYS and AUTOEXEC.BAT commands for a
computer with one CD-ROM drive.
The CONFIG.SYS file contains the following DEVICE command:
device=c:\devices\cdromdrv.sys /d:mscd000
This command loads the device driver CDROMDRV.SYS, which came with the
CD-ROM drive. The AUTOEXEC.BAT file contains the following MSCDEX command:
c:\dos\mscdex /d:mscd000 /l:g
This command enables the device driver that has the driver signature
MSCD000. The /E switch specifies that the driver be allowed to use expanded
memory, if available. The /L:G switch assigns the drive letter G to the
CD-ROM drive.
[/QUOTE]
Thanks for replying. This thing doesn’t like any driver I try, or perhaps there could be something wrong with the autoexec.bat or config.sys
I have 3 drivers installed and have tried all 3:
usdide.sys (I have a US Drives CD-ROM)
oakcdrom.sys
atapicd.sys
The mscdex file was loaded with the MS-DOS 6.22 install, so I’m pretty sure I have the correct file version.
My autoexec.bat had the following command:
c:\cdromdrv\mscdex /v /d:cd003 /m:10
I deleted the /v
I edited the /m:10 to what your suggested, /l:g
I also tried /l:d
Does the drive assignment matter (d or g) or can /m:10 be used as well in it’s place? The atapi floppy disk created this /m parameter. The other 2 drivers I downloaded, so I don’t have a driver install floppy for those 2. Atapi also used REM === command lines, one on top and one on bottom of the c:\cdromdrv command line, but i deleted those 2 REM lines.
As far as the config.sys file is concerned, it currently looks like this:
Device=c:\cdromdrv\usdide.sys /d:cd003
Of course I’ve tried the other 2 drivers in the place of usdide.sys
I’ve also, in both files, tried reassigning the signature to what you had listed: /d:mscd000 and also /d:cd000 and /d:cd006 (edited both files when changing the /d command)
I saw that you mentioned an expanded memory /E switch, but I don’t know where to put this line. I do have expanded memory in place.
Having gone through all that, could it be a jumper problem? I didn’t change anything on the back of the CD-ROM when I started on this, as the CD-ROM did work on a previous Windows 95 install a few years ago. I have tried different jumper settings in the mean time, and I think I just left it as Master, since that seems to work on other machines. Originally it didn’t have a jumper back there.
So no matter what I’ve tried so far, with oakcdrom.sys it says “no drives found, aborting installation”. The other 2 say “no interface card found” and "device driver not found ‘cd003’ et al.
At least I know the power is on, as the CD-ROM drive light comes on and the door opens and closes.
One thing I do know is the old Award BIOS IDE configuation screen doesn’t recognize the CD-ROM drive. My newer machine does recognize it as the Secondary Master. Unfortunately, Award offers no BIOS update, and the ones I have tried to seek out through a 3rd party want like $70 or something like that. Wish I had a Hewlett-Packard BIOS 
There’s gotta be a way to get this to work, as I know it did in the past (under a Windows 95 platform).
Thanks.