Meanwhile, feast your eyes on these terrific screenshots.
![Image](https://i.imgur.com/5kM5B42.png)
![Image](https://i.imgur.com/jILcxOC.png)
![Image](https://i.imgur.com/kTEl7pr.png)
If you do, let me know how it goes: I'm aiming for low-end computers and all I have to test the code is DosBOX since I no longer have the legit hardware. I'll probably get back to it, mostly to iron out the bugs and use the PIT instead of the TIMER for time slices (I just released a "WIP demo" of a Breakout clone that uses the PIT chipset and it's overall much smoother: https://qbmikehawk.neocities.org/games/cody/ )
That's kind of good news: Panda still uses some ASM code and CALL ABSOLUTE to get the mouse input, while Minesweeper DUO uses CALL INTERRUPTX. I replaced that part of the code and I'm eager to see where it's gonna crash next.
Cody shouldn't try to initialize the sound card when it is first launched, so that's weird; it may try to initialize the sound card even if "sound" is set to FALSE if it thinks a sound card might be available. However, if "lodma" is set to -1 or "baseport" is set to "0xFFFFFFFF", it shouldn't... Try setting "numpages" to 0 and see if that works.
I tried again setting the pages to zero. Sound off and set the controller to "KEYBOARD" from "MOUSE" (not sure if that's right). Still didn't start unfortunately.MikeHawk wrote: ↑Wed Apr 29, 2020 5:07 pm Cody shouldn't try to initialize the sound card when it is first launched, so that's weird; it may try to initialize the sound card even if "sound" is set to FALSE if it thinks a sound card might be available. However, if "lodma" is set to -1 or "baseport" is set to "0xFFFFFFFF", it shouldn't... Try setting "numpages" to 0 and see if that works.
Sound card is a Sound Blaster 16. Works on other things. Still no sound from MSDUO or PANDA though.
The Panda patched version worked!!
Thanks for the help Erik! I'm fairly certain removing the overdrive chip won't be necessary... last patch fixed a stupid mistake where I was reading a string out of bounds; I should probably focus on the sound system, mode Y and the keyboard handler. Both Cody and MSDuo have an EMS component, but since MSDuo works on your system and I didn't modify it too much in Cody, I can probably rule that out...
If I play the sounds slowly and let the previous sound finish completely before hitting space bar and triggering the next sound clip to be played, it doesn't crash. I sat there for a bit slowly tapping and it worked fine. If I press space too quickly while a previous sound is playing it will usually freeze the application after the two overlapping clips finish (Requiring a soft reset with CTRL+ALT+DEL).Segment: 9C11
Length: 16103