Well, it seems people are starting to get some things working, and my
Yes. I've personally tried it, and there were no problems. It seems
Urg. I fu**ed up. As has been pointed out, it is much easier to use tar
on a disk-image. Stupid of me not to think of that, even though that's
what tar is for. Even so, I should at least have done some kind of
readme for the mtools files.
If you want to read files from the DOS-partition, the mtools programs
should work. They need some setting up: you need to tell them what
devices A,B and C are. This is done by making the appropriate links to
/dev/dosX (X=A,B,C). A and B are assumed to be floppies or small
harddisk partitions, ie a 12-bit FAT. C is assumed to have a 16-bit fat.
To read a 1.44M dos-floppy in A:
mknod /dev/dosA b 2 28 # tell linux that A is 1.44Mb floppy
mdir A:
etc.
To read your DOS-partition (16-bit FAT):
mknod /dev/dosC b 3 1 # 1 partition on 1 drive: don't use 0
mdir C: # as that's the whole disk, not one prt
12-bit harddisk partition:
mknod /dev/dosB b 3 1
mdir B:
Note that if you have a small partition, you probably have a 12-bit fat
on your harddisk as well, and you should use A or B for it, not C.
If you don't know what type of FAT you have, try with both B or C.
Note that A/B/C has no relation to the MS-DOS devices, even though
There /should/ be no trouble with IDE drives, so hopefully that isn't
the problem. One possibility is that everything works, but the
video-card isn't a colour-VGA. If you are using a mono-mode, the screen
map is elsewhere (I think, I'm not really used to the IBM video modes),
and linux happily writes to the wrong location. Thus the only thing you
see is "Loading system ...", which is written with BIOS-routines.
If this is indeed the problem, you should be able to test it by booting
up, putting in the root diskette, and pressing ENTER. Hopefully the
drive will run for a while, and then stop. Try doing something blindly
(write ls /mtools<enter>), and see if the flopp...
