Some image files can't be mounted about dosbox-x HOT 33 CLOSED

The HDI image is so small, that IMGMOUNT doesn't consider it a hard disk image, because anything smaller than 2880 sectors (2.88MB) is assumed to be a floppy disk.

from dosbox-x.

Fixed. Images with file extension .hdi are now assumed to be a hard disk image which allows the image to mount.

from dosbox-x.

I think problem of hdi & fdi images are fixed by #4825.
Please check.

from dosbox-x.

You can try the latest nightly for the unmountable hdm file.
Also, you can boot the image by imgmount 0 even with the current release.

from dosbox-x.

Very strange. The hdm boots fine on 2023.10.06 release.

Anyway, you can find nightly builds quite easily.

from dosbox-x.

Fixed the mounting error. (Of course tested the image that failed in the current release)

from dosbox-x.

You can show an example, can't you?

from dosbox-x.

You can show an example, can't you?

D.O. Doki Doki Disk 8.hdi.zip

from dosbox-x.

@joncampbell123
boot.zip
It's a .fdi whcih can't be mounted.
Add a .nfd.
Tenshi-tachi no Gogo.zip
It's a T98FDDIMAGE.R0

from dosbox-x.

Does it fix the .nfd? Where is the release? I want to test it.

from dosbox-x.

It's not released yet, but you can try the latest nightly build.
I haven't checked your nfd sample yet, but I tested hdi & fdi images myself.

from dosbox-x.

Your provided nfd image seems not a MS-DOS formatted disk. It can't be read on MS-DOS running on np21 as well.

IMGMOUNT 0 [.nfd file]
boot a:

seems to work.

from dosbox-x.

21/W is not 21.
https://simk98.github.io/np21w/
Please try this one.

21/W is O.K.

https://github.com/joncampbell123/dosbox-x/assets/5364709/6ebd6958-9ac4-43ba-a18f-e2b76d39e414
Can't be mounted on PC-98 mode.

from dosbox-x.

You didn't carefully read my comment.
Boot MS-DOS on np21/w and type the commands I did before complaining.
Also, the procedure you showed in the video doesn't follow my instructions.
Very dissapointing.

from dosbox-x.

https://github.com/joncampbell123/dosbox-x/assets/5364709/f3548514-e388-4886-bb7c-dd353f5effad

Not work. Black screen. What could go wrong?

Now I understand what you said. The .nfd can't be list directory, can go to the drive, but the dir command is failed.

from dosbox-x.

Yes, you can't IMGMOUNT a: an image when it is not MS-DOS formatted.

And for the blank screen, it is very strange. As I already uploaded the screenshot, it is working for me.
I tried on VS x64 SDL2 nightly build and old 2023.09.01 VS x64 SDL1 release (the screenshot below).
Since I can't reproduce, we have to see what other differences are there.

from dosbox-x.

Information about NFD r0
https://www.pc98.org/project/doc/nfdr0.html

Information about other image
https://www.pc98.org/project/fivec.html

I hope these documents can help to fix the issue.

from dosbox-x.

Add .hdm.
O.K.hdm.zip can be mount
error.1.hdm.zip cant' be mounted

https://dosbox-x.com/wiki/Guide:Managing-image-files-in-DOSBox‐X
I don't find .hdm from this url, so I also upload the O.K. one.

from dosbox-x.

2023.10 version imgmount 0 and boot a: no effect.
How can I get the nightly? I'll try later.

from dosbox-x.

If boot a: will force close.
dosbox-x.zip My conf here.
I see.
Another question, how do I swap disk if imgmount 0?
Test nightly for .hdm, it's O.K.
.fdi need imgmount 0.
.nfd still black screen.
.hdi is O.K.
@maron2000
Which lng file cause dosbox-x garbled characters?

from dosbox-x.

You can change the image to load from the dropdown menu.
Consult the wiki for details, the address is what you mentioned above.

boot.fdi you provided successfully mounts as well.

And your question about lng file, I have no idea since I usually don't use translations myself.
Does it matter with mounting the images?

from dosbox-x.

Garbled characters will make me can't understand the command wether it succeed. I remain US, JP, zh_CN and zh_tw, then no garbled characters.
Still have some garbled characters
So strange. I can't mount the .fdi. I will upload the gif.

Maybe try vs build.
Thanks your reply.

from dosbox-x.

@joncampbell123 @maron2000
Really, the .fdi bug only in the MingGW build, VS bulid is O.K. But .nfd still black screen in VS bulid.

from dosbox-x.

We have to check what's going on in MinGW builds.
The blank screen problem is another issue, I think mounting itself is okay.

from dosbox-x.

@joncampbell123 @maron2000 Really, the .fdi bug only in the MingGW build, VS bulid is O.K. But .nfd still black screen in VS bulid.

Can you check if it has something to do with whether or not "rb" is needed for fopen() or O_BINARY is needed for open()?

Remember that on DOS/Windows systems, functions like open()/read()/write() by default have that translation mode to convert between \r\n and \n and back and that can screw with binary formats if you're unaware.

from dosbox-x.

I currently work on Visual Studio to fix and test, so if I have some time I will try MinGW as well, ofcourse considering your advise.
Whether the fixes are working on Linux and/or mac, may matter on where and how to fix.

from dosbox-x.

MinGW build couldn't fetch the BPB parameters at all, so currently it will not work.
We have to see why.

from dosbox-x.

Fixed the mounting issue for MinGW builds.
Please confirm.

from dosbox-x.

dosbox-x-mingw-win64-20240220143038 Failed.

from dosbox-x.

That's too bad. I can't reproduce, so I think something is wrong in your environment.

from dosbox-x.

@maron2000
Same config file, the VS build is O.K and MinGW is error. What is it caused by？
@joncampbell123
https://github.com/joncampbell123/dosbox-x/actions/runs/7977124696
dosbox-x-mingw-win64-20240220165609
This build is O.K.
So, what could go wrong?

from dosbox-x.

I don't have any intention to find out what is wrong in the older versions, as long as it is working with the latest nightly.
You can find out yourself.

from dosbox-x.

Add another can't be mounted .hdi file.
Rusty.zip
dosbox-x-mingw-win64-20240221033525 failed.
This is the same game another version .hdi file. It's O.K.
Rusty.zip

from dosbox-x.