If I'm not mistaken, I think 2 GB (or maybe even 504 MB) are the largest supported partitions with IDE emulation at the moment.

Ok - first the disclaimer - I am a newbie to DOSBox ...
BUT - I did a lot of this sort of thing, back in the day, when those big drives first came out and we had to make them work with the then current Operating Systems...

So ... I'm not too sure of how DOSBox is emulating IDE Support?
[history lesson 1990s]
BUT ... on the IDE Systems - standard was two (2) IDE Controllers, a Primary and a Secondary IDE Controller - each capable of controlling a Master and a Slave IDE Drive.
AND ... the IDE design, with special (custom?) cables, allowed for up to 4 actual IDE Drives on each controller - how some systems piggy-backed a backup-tape drive to two hard disk drives.

Then there were the two(?) size restriction factors that had to be overcome ...
... First - the BIOS limit on physical sizes - based on the field size for the cylinders/heads/sectors numbers (around 504 MB?).
LBA - Large Block Area(?) w/int13-patch - replaced "sectors" with "clusters" (where each cluster could have a base-2 factorial of sectors) ---
--- thus the bios thought it was feeding the IDE Controllers secter numbers - which the IDE Controllers were using as cluster numbers.
... 2nd was the FAT16 FS limits on logical sizes (about 2-4 GB) - Partitioning was the workaround - unitl the FAT32 FS was implemented to overcome this limit;
until Microsoft switched their support to only NTFS (about the time WIN-XP was released).
[/history lesson 1990s]

Maybe this gives someone some sort of an idea/clue of what needs to be done?

And - then again - going back over the "autoexec" commands:
- are you really trying to mount an '-fs none' image to a drive letter (d) ? I believe that I read somewhere that a number (ex: 3) is proper for images that don't (yet) have a FS!
... as you have the c.img mounted as master (2) ... the d.img might be mounted as slave (3)? (or maybe 4 - as a second master - might work? Although this doesn't match your IDE example.)

if you use imgmount d, for win95 the "d" images can only contain 1 partition, and can be only up to maximum FAT16 capability for win95 to recognize it.

if you mount a hdd images that contain more than one partitions,
it must be mounted not to drive letter, but to drive number.

NetPCDoc wrote:

So ... I'm not too sure of how DOSBox is emulating IDE Support?

If you wish to educate yourself, the details are available around DOSBox-X branch , though the patch in question is currently in development and I'm not sure if the 504 MB barrier has been bypassed already. The subsequent page suggests it might be.

Joey_sw wrote:

if you use imgmount d, for win95 the "d" images can only contain 1 partition, and can be only up to maximum FAT16 capability for win95 to recognize it.

FAT32 support was introduced in Windows 95b; as the OP is running Win95c, it should be able to recognize FAT32 partitions. Mounting to a drive number is probably a good idea for starters.

Standard DOSBox (without IDE emulation) has no FAT32 support and thus has a 2 GB limitation for hard drive images, if I'm not mistaken.

Guys!

Im asking for help with the SVN Daum DOSBox (as u can see in the startpost). This Build support 8gig Images! So please help me to get it working.

I see a email address posted on his webpage. Mabye you should try that.

These forums are for the official version of DOSBox.

Fexel wrote:

Im asking for help with the SVN Daum DOSBox (as u can see in the startpost). This Build support 8gig Images!

What, exactly, makes you so sure of that?

So please help me to get it working.

So did you try
imgmount 3 .\images\d.img -size 512,63,255,1023 -t hdd -fs none -ide 1s