When loading up Windows 3.1 with "Creative Labs SoundBlaster 1.5" driver installed (SNDBLST2.DRV), the following message box pops up:
"A configuration or hardware problem has occurred. Use the Drivers option in the Control Panel to re-configure the Sound Blaster driver."
Entire listing of my emulated C: drive
Here's what the driver configuration screen shows inside of Windows 3.1. The settings match the port and IRQ my dosbox config:
The reason I know that r4009 introduced it is I imported the trunk into a git repo and used "git bisect" to find the first bad commit.
My setup had been working perfectly up until recently.
Also, I'm absolutely sure it isn't due to something in the internal state of the C: drive, since I keep it in a git repo, and before each test during the bisect, I would bring the repo back to a pristine state.
To aid testing, I can give you access to the git repo that represents my C: drive, if you need it.
Last edit: h3xx 2017-06-08
Thanks for the report. Should be fixed now.
Sorry, ignore my post.
All is well.
Last edit: James-F 2017-06-17
Confirmed fixed. Booted up existing windows 3.1 and greeted by TADA.WAV.
Thank you very much!