Open enderdrag64 opened 1 year ago
It doesn't seem to reproduce the issue here on Linux, even if I break the sound configuration by changing sound card resources, in which case I just get a sort of in-game "console" following a message about sound configuration.
Seems to boot fine here with x64 VS SDL1 build,
Based on the replies I was curious if it might've been a platform dependent issue so I tried again on another computer. The one I tried on before was a Windows desktop on a second-gen Ryzen processor.
This time I tested on an old Windows 10 laptop with an Intel processor. It still crashed but I got a slightly different error this time: I copied the exact same config over for this
Are you using 3Dfx acceleration with the game or software rendering?
I'm using the 3Dfx mode and I'm not seeing any issues.
Yes I'm using 3dfx acceleration. I tested with both nglide and dgvoodoo
Maybe there is something about dynamic core (core=auto might switch to dynamic when the game starts).
Try running with core=normal
I could reproduce the error using the Windows 32-bit version of DosBox-X in order to play Redguard on Linux using dgVoodoo2 and DXVK enabled from Lutris.
It happens when the system RAM setting are the default 16 MB l, but when changed to 64 (the game requires that large amount of RAM or it fail with an error) the error do not happen and the game starts normally.
Might be the same as the issue in https://github.com/joncampbell123/dosbox-x/issues/3779. That also involved an "illegal descriptor" error and was triggered by 16 MB not being enough memory for the game.
Describe the bug
Whenever rgfx.exe gets to the "Loading sound" phase, dosbox crashes with the error message "Illegal descriptor type 0 for int 21"
I found this issue in both the 05.01 and 09.01 builds.
Steps to reproduce the behaviour
Launch rgfx.exe with dosbox-x. I performed this test using both nglide and dgvoodoo2 for glide emulation, both win32 and win64 builds of dosbox-x. Both combinations had this crash
Expected behavior
The game would load and dosbox-x would not crash.
What operating system(s) this bug have occurred on?
Windows 10 22H2
What version(s) of DOSBox-X have this bug?
2023.09.01 vsbuild and mingw, 2023.05.01 vsbuild and mingw
Used configuration
Output log
Additional information
No response
Have you checked that no similar bug report(s) exist?
Code of Conduct & Contributing Guidelines