A few weeks ago I tried to talk a guy through dumping the ROM of his COMPAQ Portable 386
from inside DOS over email. The resulting file must have been corrupted by a banking scheme as the driver complained about a "ROM error".
I the meantime I got a Portable 386 by myself, and I dumped the ROMs by reading them out directly, but simply plugging them into the at386 driver doesn't work - the RAM is counted until 128K or 192K, and then a "Memory error" is shown.
My machine comes with the regular 2MB RAM on board and a 4MB expansion, counting up to 6144KB during the POST.
Interestingly enough, the machine has been modded to accept a 210MB harddisk as "Type 1", and this is reflected on the handwritten ROM labels. This Portable 386 has a Seagate 1239A drive installed that is chock-full with a boot manager (Bootcon) and company software in DOS and Windows 3.1 flavours. Exiting Windows or the DOS file manager forces a shutdown.Here
and on the FTP are the ROMs, docs, DOS distributions and a bootdisk made on the Portable 386 as well as photos
After some coaxing I managed to dump the harddisk on a Linux machine via dd, but after converting the image to CHD, I can see the contents, but the image doesn't boot (I used ct486 to autodetect the harddisk parameters).
Could someone please find out the C-H-S parameters for the modified Type 1 210MB harddisk from the Portable 386 BIOS, so I can try to image the harddisk again with those parameters? Is there another trick to get a bootable disk image using dd (I used "sudo dd if=/dev/sda of=filename"; sda was determined by "sudo fdisk -l" first).
While I won't be able to release the hard disk image (the company this machine belonged to still exists), I'd like to preserve the unique setup.