Home Page Forums MAME MAME Creating chd from hard disk image.

Hi all,

I'm trying to use a raw dump of the CF card from one of my 5150 machines, created on the XT-IDE interface,

I have created a raw dump of the CF card under linux using : dd -if=/dev/sdb -of=IBM5150.hd
I can boot the pcega machine with the XT-IDE device in an ISA slot and the above IBM5150.hd mounted as the hard disk and the disk is recognised within the emulated XT-IDE, however it gets the geometry wrong, so won't boot.

So next I tried to create a chd with the correct geometry :

chdman createhd -i IBM5150.hd -o IBM5150.chd -chs 3,255,63 -c none -f

Note the CHS values where what was reported by hdparm -g /dev/sdb on the source CF card.

However when I mount the created chd file in MESS, XTIDE doesn't recognise it and I get no hard disk

What am I doing wrong?

Cheers.

Phill.

It doesn't recognize the drive at all or it's not bootable?

Have you tried specifying the sector size when you create the chd, add -ss 512.

Hi all,

Have now tried specifying sector size which seems to have made no difference.

Mess recognizes the CHD but XT-IDE doesn't see it as a disk.

Oddly I've just tried it with the hdc hard disk device**, and that recognizes the chd, which to me possibly indicates a problem with either the XT-IDE driver or bios.
**It still doesn't work properly because the geometry is wrong

Cheers.

Phill.

Does XT-IDE have some way to configure the geometry, like was common in the BIOSes of 386/486 PCs?

No it uses the IDE enquiry command to get the geometry / LBA info from the drive and then translates if needed.

Cheers.

Phill.

Right I think I've got it working, it boot correctly now.

Basically I put the CF back in the PC, and used Norton utilities "edit absolute sector" to determine the max C,H,S and set those values when chreating the CHD file namely :

chdman createhd -i Bio-IBM-5150-3.hd -o Bio-IBM-5150-3.chd -c none -chs 60,16,63 -f -ss 512

Cheers.

Phill.

Glad that worked, but it seems like there's a problem if the geometry hdparm reports isn't right. Transferring card images between real and MAME is an important (if probably not-often-used) use case.