#486 Hyperoid - Freezes and mouse and keyboard become unresponsive
Having a weird problem with DOSBox.
I had Windows 3.1 set up on Windows 10, which worked fine, and I was able to play all my old favourite Windows 3.1 games :).
I moved this directory over to my new Lubuntu 18.04 setup. Windows 3.1 works fine. I have sound and I have MIDI; however when I try to run Hyperoid (which worked fine in my Windows 10 setup):
- DOSBox slows to a crawl
- Screen updates perhaps twice a minute (adjusting CPU settings does not help at all)
- The Windows 3.1 mouse cursor disappears
- Keyboard is extremely unresponsive to Ctrl-F9 (terminate) and Ctrl-F10 (escape mouse); however if I keep bashing, occasionally it will pick it up.
- CPU core is maxed out, even when the clock speed is set very low (e.g. 3000 cycles).
I've tried:
- Using the nosound option
- Using auto cpu settings
- Using simple fixed CPU settings, and adjusting clock speed all the way up to 20000 cycles (makes no difference)
- With and without MIDI
However it does not seem to make a difference.
Because the core is maxed out, it suggests the problem lies outside the emulation sandbox.
Apart from the CPU settings and MIDI being set-up, my DOSBox configuration is the default one.
Windows 3.1 has these drivers installed:
- Sound Blaster 16 (v3.57.14)
- S3 864 1.41B5 (800x600 256 colors SF)
Win32s is also installed.
On the host side, it's a Toshiba laptop. One particular thing to note is that the NVidia graphics card is configured to pass through from my integrated Intel graphics card. This did cause me some grief on Windows 10 before. It's probably unrelated, but it's an unusual configuration, so it's probably worth mentioning.
Lubuntu has recently switched back to PulseAudio; however I don't think sound is the issue (because I have the same problem even when I use the nosound configuration); however it was the first thing I suspected.
I'm all out of ideas. Any suggestions would be much appreciated.
Seems to be a graphics issue. If I use VGA instead of the 'S3 864 1.41B5 (800x600 256 colors SF)' drivers, the problem goes away.
Last edit: Chris Wyatt 2018-08-06