search for: isodos

...> > All right, thanks. I'm going to continue to try a few things and let > you know what finally worked. > > For other people's reference, here a couple of links that might be > useful to understand what is going on: > > http://people.cs.uchicago.edu/~gmurali/gui/isodos.html > > http://www.mega-tokyo.com/osfaq2/index.php/ > Disk%20Images%20Under%20Linux > > http://www.pcguide.com/ref/fdd/mediaGeometry-c.html > > Thanks, > > Salman > > On Jan 13, 2005, at 4:32 PM, H. Peter Anvin wrote: > >> Oh yes, and look at the mkdiskim...

...following message WARNING: Using suspect partition PRI:1 FS 0e: with calculated values 175-9-63 instead of 21-254-63 But the same message also apply if I use the 1.4M freedos image itself. Probably something change, because in Murali document http://people.cs.uchicago.edu/~gmurali/gui/isodos.html he mention being able to do 10M image. The syslinux doc talk about mkdiskimage to create disk image. I try to use it without success. What I did is the following mkdiskimage /tmp/dexter1.img 2 255 63 (this create a 16M image) mount -o loop,offset=32256 /tmp/dexter1.img /mnt/loop ++ I copy...

...ng suspect partition PRI:1 FS 0e: with calculated values > 175-9-63 instead of 21-254-63 > > But the same message also apply if I use the 1.4M freedos image itself. > > > Probably something change, because in Murali document > http://people.cs.uchicago.edu/~gmurali/gui/isodos.html > he mention being able to do 10M image. > > The syslinux doc talk about mkdiskimage to create disk image. I try > to use it without success. What I did is the following > > mkdiskimage /tmp/dexter1.img 2 255 63 (this create a 16M image) > mount -o loop,offset=32256 /tm...