You may want to try some modern DOS drivers:
http://optimizr.dyndns.org/dos/drivers.html

Are you referring to UDVD2.SYS? I just tried that and it says "No drive to use" when trying to load UDVD2.SYS.

The Oak and Acer generic CD-ROM drivers allow changing the I/O port address and the IRQ, however, it is expecting the I/O port to only be 3 characters long.

DEVICE=VIDE-CDD.SYS /D:MSCD001 /P:xxx,yy
where xxx = I/O port address in HEX and yy=interrupt in DEC.

The readme gives examples with I/O port 1F0 with IRQ 14; I/O port 170 with IRQ 15; 1E8 with IRQ 12; 168 with IRQ 10. My Promise Ultra 100 TX2 card is on IRQ 11, and according to Windows 95, it uses I/O port address of 6000-6007, 6100-6103, 6200-6207, 6300-6303, and 6400-640F. Can MS-DOS 6.22 use addresses this high? I'm starting to think maybe not.

In config.sys, I setup,
DEVICE=VIDE-CDD.SYS /D:MSCD001 /P:6000,11 /P:6100,11 /P:6200,11 /P:6300,11 /P:6400,11

however, when using the Oak variant of VIDE-CDD.SYS, I get an error saying that it could not find the CD-ROM and when I use the newer Acer variant of VIDE-CDD.SYS, I get an error stating 'illegal request'.

I also tried CDROMGOD, which is a boot disk that allows you to select 1 of 40 different CD-ROM drivers. I tried about 15 and none of them could find the CD-ROM when connected to the Promise Ultra 100 TX2.

The promise site has 3 different firmwares (BIOS) for the card. (One is for the WD version.)

I've had some Promise cards the were picky/weird as to Master/Slave/CS jumper settings on the drive.
I don't remember exactly but was something like.
Drive was wired (cabled) as Master but it wouldn't work with the drive jumpered as Master.
Without changing the cable I moved jumper to Slave or CS (which is what I don't remember) and it worked fine.
Same card/wiring but different HDD had to be jumpered as Master to work.
.

PCBONEZ: You're back 'eh? I thought you had left the forum for good.

I have experienced very similar occurrences with Promise cards to what you describe. There are some quirks with some hardware, some cable and jumper configurations which I haven't bothered to narrow down. I have merely figured out what worked, and sent with that, then left it alone. I suspect you did the same. For the particular case in hand, the Promise identifies the HDD and CD-ROM just fine and it works just fine in Windows. I have come to the conclusion that there is no solution to problem I face. I vaguely remember another user experiencing this. I think it was elianda, but I cannot say for certain.

My solution to the OP problem was more of a retreat - I hooked the CD-ROM drive up to the onboard PIO-3 IDE port and left the HDD connected to the Promise card. I can now use the CD-ROM in DOS, but it is in PIO-3 mode instead of the UDMA3 mode offered by the Promise. If someone determines a solution to this issue, please post back. Normally, you don't need to use the CD-ROM in DOS unless some program wants to verify authenticity from the CD-ROM drive.

feipoa wrote:

PCBONEZ: You're back 'eh? I thought you had left the forum for good.

Howdy back.
Anymore I only do the forum thing when I need an economical vacation from real life.
Or I threw my back out again, I'm stuck in a chair and bored as sh*t.
I'll be here a short while then I'll go *poof* for a long while.
.

I look for the poor man's great escape several times per day! My reality bites.