-
Notifications
You must be signed in to change notification settings - Fork 381
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
"change current floppy image" doesn't work after booting a freedos(98) hdd image #5251
Comments
I don't have any difficulties in installing Night Slave. Edit: I used genuine MS-DOS 6.2. FreeDOS doesn't work. |
I tried preparing a hdi with ms-dos installed using np21w, boot that in dosbox-x, then night slave hdinst will indeed work. btw: I had to strip config.sys and autoexec.bat installed by default to a minimum, otherwise it stucks in various stages. |
Yeah, you're right. I can't prepare a HDD image on DOSBox-X. |
Thanks for the confirmation. While I do understand this is a niche in a niche, but I think we should probably update the wiki to reflect this? |
Describe the bug
update: it's likely a dosbox-x - freedos(98) incompatibility issue.
title updated to reflect this, previous title:
Steps to reproduce the behaviour
boot c:
Expected behavior
installer should continue
What operating system(s) this bug have occurred on?
Windows 10 22H2
What version(s) of DOSBox-X have this bug?
2024.10.01 (VS SDL1 64-bit)
Used configuration
default except:
machine = pc98
Output log
Additional information
The game I tried is Night Slave, but it doesn't really matter, since it can be reproduced with any 2 floppy images and just use
dir
to check if change disk did take effect.The game installer says "please boot from hdd, installation aborted" (in Japanese) if not boot from hdd image.
If I install the game in np21w, then boot the hdd image with the game installed in dosbox-x and run the game, it works.
As for the duplicated drive letters, If I only mount the hdd image and
boot c:
, guest OS then only sees drive A, no more drive B, should I report this as a separate issue?I did not try if this bug exist in non-pc98 mode.
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: