Closed rderooy closed 2 years ago
Issue is resolved with https://github.com/joncampbell123/dosbox-x/commit/05d65bfacdc7e81972c6c214224e07c4e7c3072f
I think I'm hitting this issue again in Dosbox-x release 2023.10.06, installed via Debian packages.
Dosbox-x crashes during Windows 98 SE Italian setup, but before reaching the graphical environment.
Log messages look very similar to the ones above:
LOG: DEBUG: INT 2Fh Windows 286/386 DOSX init broadcast issued (ES:BX=0000:0000 DS:SI=0000:0000 CX=0000 DX=0001 DI=030a(aka version 3.10))
LOG: [286 DOS extender]
LOG:
LOG: 681753340 ERROR BIOS:INT16:Unhandled call 6F
LOG: 681756511 ERROR CPU:Illegal Unhandled Interrupt Called 68
LOG: DOSBox-X has switched to max cycles, because of the setting: cycles=auto.
If the game runs too fast, try a fixed cycles amount in DOSBox-X's options.
LOG: 681845111 ERROR CPU:Illegal Unhandled Interrupt Called 5C
LOG: INT 15h mouse initialized to 3-byte protocol
LOG: INT 15h mouse reset
LOG: INT 15h reporting mouse device ID 0x00
*** stack smashing detected ***: terminated
I'm not sure if I should open a new issue or if it's ok to comment here.
@lucrus73 Your said issue differs from the original one posted here. I think this is common with issue #4482, which maybe solved in the fixes after the October release. Refer to the said issue for more details and further discussions.
Describe the bug
As mentioned on discord. Running Win98SE SETUP from the internal DOS causes a general protection fault while setup is preparing to copy files.
This is a new issue, and doing a git bisect, turns up this commit.
Steps to reproduce the behaviour
Run Win98SE SETUP.EXE
Expected behavior
No response
What operating system(s) this bug have occurred on?
Fedora 36
What version(s) of DOSBox-X have this bug?
latest git
Used configuration