Once DOS support is working, copy the folder containing cwcdos.exe to c:\ , uninstall the vxd drivers, install the wdm drivers and
Execute cwcdos.exe from its directory when needed (or put it in autoexec.bat) .

If you need more detailed help along the way, feel free to ask .

Thanks! Also, I installed the drivers from a folder on the desktop, and it tells me to restart my computer. When this happens, Windows tells me it found new hardware, and it looks for drivers, but doesn’t find them.

If it asks for the path to the drivers, point it toward the folder where you ran setup.exe from .

Otherwise, you can update drivers from device manager and pointing to the folder where you ran setup.exe from

Okay, thanks!

CWCDOS still doesn’t find a SoundFusion chip.

BliggyBlop wrote on 2020-04-26, 18:53:

CWCDOS still doesn’t find a SoundFusion chip.

Does running
cwcdos /v
show anything more ?

Interesting:

I do not know why it's not detecting it . Maybe a BIOS setting .

Do you have any other soundcards (preferably ISA , if the board has ISA slots ) ?

Yes, but not installed. I tried to install it once, but the process went haywire, and I gave up. It’s an Ensoniq ES1370.

Not the best choice for DOS either .
It it worked the CS4280 would probably be more compatible .

Does your board have ISA slots ?

No.

OK, I will try to dig up my CS4630 this evening, and attempt to replicate the issue you are experiencing .
I have an Asus P3B-F based Windows 98SE machine I should be able to use as a testbed .

If that fails, we could give the ES1370 a shot . It will require EMM386.EXE to be loaded so it may limit compatibility with some games .

Incidentally, PCI sound card compatibility under DOS is not fantastic. The best PCI cards for DOS are the Yamaha YMY724/YMF744/YMF754 series, ESS Solo-1 and CMI8738 . If you happen to spot one .

Ok, I have scoured the bowels of the Internet and am quite confident that your motherboard is either a Trigem Anaheim-2 or Anaheim-2a with a CS4280 .

I found what I believe are the original drivers provided by Trigem here http://www.elhvb.com/mobokive/archive/Trigem/ … s/Sound/Cs4280/

I have analyzed the three Windows 9.x driver sets provided and all three have DOS drivers, but only two different versions of cwcdos.exe exist. Interestingly, they are both version 2.80 , but have different sizes, dates and checksums .

Anyway, long story short . I have prepared two cwcdos driver sets along with their dependencies for you to try .

Just unzip each of them and try running cwcdos.exe /v from the unzipped directory under DOS. Let me know the results .

Olddos says:

* Found PCI Bios.
* A SoundFusion chip was not found,

Newdos says:

* Found PCI Bios.
* BA0/BA1 not configured correctly.
* A SoundFusion chip was not found.

Newdos says the same thing as the drivers you gave me before.

This is really strange .

As far as I can tell BA0/BA1 refers to PCI registers .
Other than maybe a video card, do you have any PCI devices slotted in the motherboard ?
In another thread, someone mentioned the issue might be related to a BIOS setting . Would you be willing to RESET your CMOS settings to factory defaults ?

I finally tested out both versions of cwcdos.exe on my P3B-F motherboard with a CS4630 based-card and both detected the card . I was not able to get them to not detect the card .

At this point, if resetting BIOS CMOS settings does not fix it, I really do not know what to try next, except maybe a BIOS update, if one is available . If your motherboard is an Anaheim-2, there are some BIOS available, but nothing in the README (which I had to run through Google translate) purports to fix this kind of issue .

Maybe it's time to disable this one in the BIOS and try that ES1370 instead, or consider getting another PCI sound card with better DOS support, such as Yamaha YMF724/YMF744/YMF754 or ESS ES1938 based one . Hopefully, whatever the issue is with the onboard CS4280, it will not extend to other cards .

One has to wonder if somehow this motherboard has a "crippled" version of the SoundFusion, which has no DOS extension.

I imagine that if there was a crippled variant, it would have had different PCI device id . Then again, maybe not .
The issue could also be due to some BIOS bug/incompatibiity that went relatively unnoticed considering that this system was released during the waning days of DOS .

The programming guide mentions an optional EEPROM, maybe there's an issue with that or maybe it is required for DOS compatibility .

https://www.alsa-project.org/files/pub/manual … _audio_spec.pdf