I can use the DosBox' Game Blaster emulation with all games all tried, but Creative's own utilities don't seem to recognize it.
Any takers for fixing that? I'd be willing to send out the Game Blaster program disk.
Why do it needs fixing? You said it worked with all the games you have tried.
DOSBox 60 seconds guide | How to ask questions
_________________
Lenovo M58p | Core 2 Quad Q8400 @ 2.66 GHz | Radeon R7 240 | LG HL-DT-ST DVDRAM GH40N | Fedora 32
You know, I sort of expected an imbecilic answer like that. 😵
I'd take it.
I find it interresting to see what the creative utilitities try to do.
If you want, please send the files to the email addres of the crew.
Water flows down the stream
How to ask questions the smart way!
Most likely, there is some undocumented command that is used by those tools. There was exactly the same problem with Sound Blaster utilities, now fixed.
Indeed. gameblaster.cpp only seems to emulate ports 0x220-0x223.
TESTCARD.EXE writes 0x5A to 0x227 and then expects 0x22A to return 0x5A.
CMSDRV.COM writes 0xA0 to 0x227 and expects 0x22B to return 0xA0. It also writes 0x1B to 0x228 and later expects some unknown result in 0x224; return 0x1B seems to work fine. Failing the first test makes CMSDRV claim there's no card there, failing the second makes it not play any music.
The very first version of the Sound Blaster Developer's disk also documents a third way of checking for a CMS: Writing 0xC6 to 0x226 and expecting 0xC6 from 0x22A, then writing 0x39 to 0x226 and expecting 0x39 from 0x22A. This seems to be for bare CMS only.
I suspect that any port read/write from 0x224 to 0x22f just returns/sets a latched value, though I have no real card to test this.
Edit: The CMSDRV.COM 3.20B from the Sound Blaster 1.0/1.5 does work nicely in DosBox. (However, Sound Blaster 2.0's TEST-SBC.EXE does not find the optional CMS chips.)
The CMSDRV 3.10 from the original Game Blaster on the other hand can't find the card.
