If you can, please provide the contents of your AUTOEXEC.BAT and CONFIG.SYS files, which will show what is loading when the computer boots. You should be able to use the EDIT tool (e.g. EDIT AUTOEXEC.BAT) to bring up the file contents of each.

Also, does your system already have an IDE CD drive installed as well as the LMSI drive?

Thanks for the reply. I have a Mitsumi IDE cd drive off the header on the motherboard. I have no lmsi drive installed because I don’t have one. Upon more reading I think this card may have come in a kit with a specific lmsi cd drive. I feel like that’s where the conflict is. The card doesn’t seem to like my ide drive and seems like it’s looking for the lmsi one maybe ? Also I think the drivers I am using are for the version of the PAS with the onboard SCSI interface as I can’t find the exact drivers for my PAS. maybe another issue being caused there. Will send pictures of autoexec / config tonight when i get back to it.

That Digbie2 chip on your PAS16 only wakes up when you load the driver for it AND create a device for it in config.sys. Only then it can cause conflicts when using the same device name or letter. So I think the problem lays elsewhere.

Have you moved the IRQ jumper yet to rule out an IRQ conflict?

Coincidence, my PAS16 LMSI is on its way. I happen to have a LMSI drive and controller card. (CM260 + CM206)

When I get back to the computer tonight and post a pic of the Autoexec/config maybe it will tell someone more that knows exactly what they are looking at. I myself not being that guy haha. I tried the jumper in all three spots with no change. Also that very interesting that your gonna be setting that all up soon would like to hear how you make out.

The version of MSCDEX that comes with the PAS16 drivers is from a time before DOS 6.22 (1991) and could be causing the Incorrect DOS version message. It probably overwrote the DOS 6.22 file during the installation.

If you download the newer version (https://www.allbootdisks.com/disk_files/Dos6.22/MSCDEX.EXE) see if you can replace the file that's currently on your system. If that's the problem you won't need to edit anything.

Interesting I will give that download a shot for sure and here are the Autoexec and config.

**First 2 pics are pages 2 and 1 of config.sys
3rd pic auto exec

The installer has added in the SCSI driver so you can remove the last line in config.sys which is trying to load tslcdr.sys (or just type REM before device). However as it’s not loading the driver this line isn’t harmful to leave in.

Autoexec looks fine and it does look like MSCDEX is causing the incorrect DOS error. If you replace it with the version I linked see if that fixes the problem.

I’ll give this a shot I’ll get back to you. but now I have another problem I’m getting a “mvsound.sys not loaded” error when I try to load any of the music programs that came with pas16 software and in game setup menus when selecting my sound card. this was working before I don’t think I messed with anything since I am working with a fresh install of dos since my previous run at it. I see the mvsound.sys file amongst the files I copied over initially with the drivers. Do I just need to copy that over to somewhere ?

mvsound.sys should be in C:\ as that’s where config.sys is pointing to. If it’s not in the root directory it should be copied there. It should be there if it’s trying to load the CD driver from the same directory though … run MEM /c /p to see if it has loaded.

The mvsound.sys problem was an issue with the config.sys it was going under conventional memory option only instead of expanded memory + cdrom option so I changed that. That fixed the sound card. The later version of MSCDEX fixed the optical drive and the wrong dos version error ! Then removing the command line for THE SCSI cd driver took away the WARNING SCSI DEVICED NOT DETECTED. I’m good to go thank you so much for your help.

Good to hear, cheers!

Awesome, glad it's all working now!