Closed jstolarek closed 4 years ago
Doesn't happen with standalone DOSBox.
Hm. Are you sure? https://www.vogons.org/viewtopic.php?t=33618
Edit: If you're using the exodos set, I think the batch or conf files of exodos might be installing the workaround TSR prior to running the game. This would explain why you don't see it there. Try running it in "really" stand-alone dosbox, without making use of the exodos launcher conf or bat files.
Edit 2: Also, it's always useful to test the more modern dosbox core (listed as "DOSBox-core" in the RA updater). If you're on a platform where it's available, of course.
Are you sure?
It doesn't happen with the DOSBox that I have, which is v0.74-2. I have no idea what exodos is. I'm on Debian Buster and using a package from official repo. I just tested on dosbox-staging v0.75 and interestingly the problem happens there as well. But the thread you linked to is right - it only happens with version 1.4 of the game. Version 1.3 works as expected.
it's always useful to test the more modern dosbox core (listed as "DOSBox-core" in the RA updater)
Wait, I thought that DOSBox-SVN is more modern?
Closing, since this does not seem to be a problem of the core itself.
Wait, I thought that DOSBox-SVN is more modern?
Nope. It does keep in sync with upstream dosbox (thus the "svn" in the name), but new features are added to DOSBox-core. DOSBox-svn is kind of a "legacy" or "compatibility" core, while DOSBox-core is has been split from it and has received a rewrite of many parts of the code, and additions of features that don't exist in upstream dosbox.
Running Prince of Persia in DOSBox-SVN results in screen being flooded with text "JoyX: 64 JoyY: 64 Btn: 0":
This makes the game unplayable. Doesn't happen with standalone DOSBox. The core is running with default options and the input is set to Keyboard + Mouse.