Only works for bximage generated images.

Well, it happens to be just the program I use (I'm the one who devoted a whole chapter about it in the Wiki)...so what gives?

Dunno, shall i blindly change code and hope that some of the changes
made it work for you, too?
Maybe post what imgmount parameters you are using, an empty generated
sample image that doesn't work etc.

Forget it, newesr images worked. I guess it only works with the latest verison of bximage.

However, you still must supply the parameters in the creation of the image, for example:

1"dosbox.exe" -c "mount d ." -c d: -c "imgmount 2 brandnew.img -size 512,63,16,14 -fs none -t hdd"

Yep, think for fs=none it doesn't work or something.

What older version of bximage did you use? What were the parameters
that it produced?

I have no way to know which version did it. I've deleted the old image now anyway.

I've just used the defaults + 7mb (just like I've described in the Wiki).

wd wrote:

Only works for bximage generated images.

I think I've missed this hint in the readme file. 😒

What?

I mean, 'cause now I know how to create images recognized by imgmount, I'll try to run this feature again. 😉

I tried using the image detection feature with DosBox CVS 11-30-2007 today and it was unable to do so for any image size.

This is with BXIMAGE v1.17 dated 2002/11/26.

Okay I just downloaded the latest version of Bochs with bximage v1.32 dated 2006/06/16 and it's not detecting the size either. So unless I'm an idiot (highly likely) this feature is broken.

what ere the specs of the image?

I've tried 10meg, 100meg, 500meg, 1000meg, 2000meg images.

Then I do an "imgmount c xxx.img".

It then tells me that it can't find the geometry and to specify the cyl,etc,etc.

If it works for you do you have a known good image I could try?

Well it assumes the sectors to be 63, and heads 16, i'll see if it still works
with later bximage versions.

Um you didn't specify the fs parameter. That is of course needed for raw
unformatted images, so using "imgmount 3 some.img -fs none" is to be used.

You can only mount partitioned/formatted disks as drive letter (fs fat).

This is the command I have been using which works fine:
"imgmount 2 503.img -size 512,63,16,1021 -fs none"

Hmm, just created a 50mb image with the old and the latest version of bximage and it works fine, using "imgmount 2 50.img -fs none"

It seems my problem was this...

I would load up DosBox and type in:

"imgmount 2 50.img".
I would then receive the error message: "Must specify drive letter to mount image at".

So I would then type in "imgmount c 50.img".
I would then receive the error:
"Could not extract drive geometry from image".

So I guess it was my idiocy after all.

I noticed that this command crashes DosBox.

"imgmount 2 503.img -fs fat16 or imgmount c 503.img -fs fat16". (-fs none works fine)

whereas

"imgmount d 503.img -fs fat" works fine.

Wow, I never realized you could mount HD images in DosBox while still having access to the host file system in DosBox!

Wow, I never realized you could mount HD images in DosBox while still having access to the host file system in DosBox!

😀
I don't know if it still holds true, but I *think* using imgmount like this (not booting it but using it as a drive) was not the most stable one for some reason. I could be very well wrong about this 😀

How you can have images larger than 500 MB in official DOSBox:

- Create one with BxImage.
The geometry values have to be recalculated:

Cylinders maxes out at 1024 for DOSBox, however heads can be up to 256.
BxImage will suggest a cylinders value above 1024, so divide cylinders by 2 and multiply heads with 2. Cylinders still bigger than 1024? Do it again and again. You'll get up to about 8 gigs with that.

Example:

From BxImage: -size 512,63,16,1422
Recalculated: -size 512,63,32,711

Take a look at these threads:
Maximum HardDisk size emulation.

Problem with the Harddisc Image Totorial

Regards