Closed dajhorn closed 2 years ago
I can confirm the issue. But I wonder the expected behavior for this - apparently you cannot run 32-bit program on a 8088 CPU. Perhaps some kind of error messages should be shown in such cases?
A nice enhancement here would be a modal dialog that says "the emulation crashed" with a clean non-zero exit.
BTW, this UI lockup happens in Linux builds too, and the only way to close the DOSBox-X window is with kill -9
.
I looked into it and found it was due to an infinite loop. If that loop is fixed, you will be returned to the prompt after trying to run UNZIP with a message that it requires a 386.
Code of Conduct & Contributing Guidelines
Have you checked that no other similar bug report(s) already exists?
What operating system(s) this bug have occurred on?
Windows 10 21H2
What version(s) of DOSBox-X have this bug?
0.83.19 SDL1
Describe the bug
DOSBox-X instantly hangs if a 32-bit application is started on the 8086 or 80186 emulation.
Expected behavior
DOSBox-X remains responsive even if the emulation crashes.
Steps to reproduce the behaviour
unzip
from the Z: drive.Used configuration
Emulator log
No response
Additional context
unzip
is convenient because it is bundled with DOSBox-X, but this happens with every 32-bit application that I've tried.