Use Vmware\Virtualbox.

No man,I can't. Because I'm working on a ARM soc where I can't install vmware or virtualbox. Instead,dosbox is supported.

and I'm trying to install Windows ME on DosBox

That's not what DOSBox is for and it won't work.

why not ? which big differences there are between installing windows 95 or windows me ? they are built on top of dos,both.

windows 95 is not really supported either. It's just for fun. Nothing else.

they are built on top of dos,both.

Pretty wrong, but I'll neither discuss that here nor is this of any interest for your "problem".

no man,it's not only my "problem",it's a problem for everyone wants to install windows 98/me with more than 400 MB of disk space.

and I don't know what's your problem. Why are you tired ? and with whom ?

there is a problem allright if anyone wants to install 98/me on DosBox that DOES NOT SUPPORT them... can you find where the problem is?

Qbix wrote:

windows 95 is not really supported either. It's just for fun. Nothing else.

It is a game.

regardless what you want with your img files,
you might want to check if fdisk doing its job properly.

iirc, some version of fdisk glitched against > 512 MB hdd
other alternative is to format the img outside of dosbox and use -fs fat afterward

i believe i found where it went wrong marietto2008

I will create a 'flat' hard disk image with cyl=1219 heads=16 sectors per track=63 total sectors=1228752 total size=599.98 megab […]
Show full quote

I will create a 'flat' hard disk image with
cyl=1219
heads=16
sectors per track=63
total sectors=1228752
total size=599.98 megabytes

you see, when using -size , your hdd image must conform to CHS limitation, that defined by INT 13h

1INT 13 - DISK - READ SECTOR(S) INTO MEMORY
2	AH = 02h
3	AL = number of sectors to read (must be nonzero)
4	CH = low eight bits of cylinder number
5	CL = sector number 1-63 (bits 0-5)
6	     high two bits of cylinder (bits 6-7, hard disk only)
7	DH = head number
8	DL = drive number (bit 7 set for hard disk)
9	ES:BX -> data buffer

your hdd must not have Sectors / Cylinder > 63,
your hdd must not have Cylinders / Heads > 1023 (1024?),
your hdd must not have Heads > 255 (256?)

with cyl=1219, it will interpreted having (1219 mod 1024) 195 Cylinders instead.
Lets do the math: 512 * 63 * 195 * 16 / 1024 / 1024 = 95.9765625 MB

so, you might want to creates hdd images with < 1024 cyclinders, but with more heads instead.

And that will help winME on an arm device in what way? Nice suggestion.

most likely not, since FAT32 capable OS most likely bypass using INT 13H, and directly accessing L.B.A instead.
A functions that doesn't exist in dosbox. But he probably doesn't know this.

Oh I'm absolutely sure everything is going through int13 in dosbox. But you probably don't know that.

i'm totally agree with you WD.

images is nice to have though, just like how almost (all?) PC98 emu's games distributed.

Individual files inside the images less likely affected by outside inteferences such as:
- accidentaly deleted by dubious cleaner programs for 'un-used' extension, or
- accidentaly deleted by OS-reInstallation for being considered as 'harmful' or
- their access locked by FUD Antivirus, etc..

About int13,
some old (low grade) AT computer's controler (WD-1003?) only capable accessing 16 heads, and such reflected in bios that only lower 4 bits of DH register can be used for head selections.
This probably the main cause of rumor saying FDisk can only handle < 512 megabytes hdd.

I think bximage programmer also affected by this 'limitiation'.

Is dosbox also have this limitation?

The limitations in dosbox are pretty much what int13/2 requires.

thats good to know, thanks

Windows 9x DOSBox Guide (Not officially supported)