VOGONS


First post, by Wraith

User metadata
Rank Newbie
Rank
Newbie

I'm currently in retro-gaming mode. 😀

I've successfully gotten Pool Of Radiance, Curse of the Azure Bonds, and Secret of the Silver Blades working. However, the newest one, Pools Of Darkness, crashes whenever I use anything other than no sound. The initial game starts with full sound but it's the VACE program that has internal sound. Once that's past, the following error pops up from DOSBox:

Exit to error: CPU:GRP5: Illegal Call 7

That's the IRQ that the sound blaster is configured for. However, I've tried changing the IRQ to default (5), tried a different address (A220,A230,etc), and I've tried configuring it to use just PC Speaker, but the same thing happens. When launching it straight out of XP, I get an NTVDM CPU error. Obviously it's something to do with DOS sound, but I can't figure out how to do this and playing silent just sucks. Has anyone run into this and have a fix? I'd be eternally grateful if I could kick Gothmenes' butt one more time. 😁

Reply 1 of 8, by ykhwong

User metadata
Rank Oldbie
Rank
Oldbie

I have also the problem in two games, FS3 and Dual Succession 2.
CPU:GRP5:Illegal call 7

Reply 2 of 8, by eL_PuSHeR

User metadata
Rank l33t++
Rank
l33t++

Seems like a common GPF (General Protection Fault) to me. Nothing to do with SoundBlaster IRQ.

Intel i7 5960X
Gigabye GA-X99-Gaming 5
8 GB DDR4 (2100)
8 GB GeForce GTX 1070 G1 Gaming (Gigabyte)

Reply 3 of 8, by HunterZ

User metadata
Rank l33t++
Rank
l33t++

Try using different core= settings and try using a CVS build of DOSBox (see the development forum for info). Try various cycles settings (go as low as 500 cycles or less - you never know). Try all 4 combinations of EMS and XMS disabled and enabled. Try lowering the amount of emulated RAM to only a couple of megabytes, or raising it to the maximum that DOSBox supports.

Reply 4 of 8, by wd

User metadata
Rank DOSBox Author
Rank
DOSBox Author

Neither soundblaster nor GPF 😉
This happens when code is executed that looks like 0xff 0xff...

So it might be any bug you like with the effect of executing data.

Playing around with the dosbox.conf switches as HunterZ might
help, also try loadfix before starting the game.

Reply 5 of 8, by Wraith

User metadata
Rank Newbie
Rank
Newbie

I appreciate all of the suggestions Hunter, but no dice on any of them. Even tried the CVS builds as you suggested. The only thing that produced any kind of a noticeable difference is when I set the core to full. That changes the error from the one stated above to "Illegal opcode", but it still dies a quick death. 🙁

Reply 6 of 8, by Wraith

User metadata
Rank Newbie
Rank
Newbie

What's the loadfix that you refer to WD?

Reply 7 of 8, by ykhwong

User metadata
Rank Oldbie
Rank
Oldbie

loadfix.com - it's an exterior command in z:\

Reply 8 of 8, by Wraith

User metadata
Rank Newbie
Rank
Newbie

Tried that too, or at least, I ran it and got 64kb allocated. Still the same result. 🙁