robotti at godmail.com
2005-Aug-21 00:59 UTC
[syslinux] Large disk image boot. Any suggestions%2
>I tried the commands that you have presented and I running into >problems. I tried the ideology that you presented with both 32 and 16mb >configurations with no luck. Is there something that I'm missing? > >The win98se boot disk boots (just downloaded it from bootdisk today) so >I used that as a based for the boot file. > >Item 8c works fine (1.44 image) but 8b fails. > >dd if=/dev/zero of=boot32mb.bin bs=1M count=16 >/sbin/mkdosfs boot32mb.bin >ms-sys -f -6 boot32mb.bin >mount -o loop boot32mb.bin boot32mb >cp win98se/msdos.sys boot32mb/ >cp win98se/io.sys boot32mb/ >cp win98se/command.sys boot32mb/ >cp win98se/command.com boot32mb/ >umount boot32mb > >With the entry in default of: > >label 8b > kernel memdisk > append initrd=bigboot/boot32mb.bin >label 8c > kernel memdisk > append initrd=bigboot/win98se.bin > >drwxr-xr-x 2 root root 4096 Aug 20 13:48 boot32mb >-rw-r--r-- 1 root root 16777216 Aug 20 14:38 boot32mb.bin >drwxr-xr-x 2 root root 7168 Dec 31 1969 win98se >-rw-r--r-- 1 root root 1474560 Aug 20 13:29 win98se.binI guess it won't work because boot32mb.bin isn't floppy size, so it needs to be partioned like a hard disk for memdisk to boot it. I don't know offhand how to get it to work.
robotti at godmail.com wrote:> > I guess it won't work because boot32mb.bin isn't floppy size, so it > needs to be partioned like a hard disk for memdisk to boot it. >If it's not conventional floppy size, you need to explicitly specify "append floppy c=XX h=XX s=XX" where c/h/s are the appropriate cylinder/head/sector geometry. -hpa
robotti at godmail.com
2005-Aug-21 04:21 UTC
[syslinux] Large disk image boot. Any suggestions%2
>If it's not conventional floppy size, you need to explicitly specify >"append floppy c=XX h=XX s=XX" where c/h/s are the appropriate >cylinder/head/sector geometry. > > -hpaSo, it would be like this for a 16MB image. label 8b kernel memdisk floppy c=16 h=64 s=32 append initrd=bigboot/boot32mb.bin You can use minfo to get c, h, and s. You need to install the mtools package. Put this in /etc/mtools.conf. drive x: file="/test/dos.img" dd if=/dev/zero of=/test/dos.img bs=1M count=16 mkdosfs /test/dos.img ms-sys -f -6 /test/dos.img minfo x: device information: ==================filename="/test/dos.img" sectors per track: 32 heads: 64 cylinders: 16 mformat command line: mformat -t 16 -h 64 -s 32 x: bootsector information =====================banner:"MSWIN4.1" sector size: 512 bytes cluster size: 4 sectors reserved (boot) sectors: 1 fats: 2 max available root directory slots: 512 small size: 32768 sectors media descriptor byte: 0xf8 sectors per fat: 32 sectors per track: 32 heads: 64 hidden sectors: 0 big size: 0 sectors physical drive id: 0x0 reserved=0x0 dos4=0x29 serial number: 430801B9 disk label=" " disk type="FAT16 "
robotti at godmail.com
2005-Aug-21 04:35 UTC
[syslinux] Large disk image boot. Any suggestions%2
>So, it would be like this for a 16MB image. > >label 8b > kernel memdisk floppy c=16 h=64 s=32 > append initrd=bigboot/boot32mb.binI mean. label 8b kernel memdisk append initrd=bigboot/boot32mb.bin floppy c=16 h=64 s=32
Seemingly Similar Threads
- Large disk image boot. Any suggestions%3
- Dell machine boots a Windows formatted FAT16 USB drive not a Ubuntu formatted FAT16 drive.
- [PATCH 01/10] arch:powerpc: return -ENOMEM on failed allocation
- "Vixen" HVM shim package available in virt-xen-testing
- Help with fdformat