-
Notifications
You must be signed in to change notification settings - Fork 383
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PC-98 MEM command requires a very specific DOS version #5060
Labels
Comments
Now that you mention it, at the root of my DOSBox-X PC-98 configuration I copied MEM.EXE from a MS-DOS 6.20 bootdisk several years ago. I'll remove it and try again. Apologies for blaming your version of MEM.EXE. |
It works. |
Closed
2 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
A PC-98 version of MEM.EXE was added, which is nice, but it will only run if the DOS version is set to a very specific value (version 6.20).
Steps to reproduce the behaviour
Start DOSBox-X with machine=pc98.
Type mem.
Observe complaint about DOS version in Japanese.
VER SET 3 30.
Observe complaint about DOS version in Japanese.
VER SET 3 0.
Observe complaint about DOS version in Japanese.
VER SET 6 20.
Program displays memory list.
Expected behavior
Like the IBM PC MEM version from FreeDOS, I expect it to be able to list memory regardless of DOS version, within reasonable limits of course. I don't expect MEM to reliably list memory with a DOS version less than 3.0 but I do expect it to be more flexible than this.
#5059
What operating system(s) this bug have occurred on?
Linux x86_64
What version(s) of DOSBox-X have this bug?
Latest build
Used configuration
Output log
No response
Additional information
A link was given to the source code of MEM: https://github.com/lpproj/mem.nec/
If I am able to compile it from source, I can remove the version check. Then use the various PC-98 boot disks to see how well it works on any version of DOS other than 6.20.
Have you checked that no similar bug report(s) exist?
Code of Conduct & Contributing Guidelines
The text was updated successfully, but these errors were encountered: