search for: fdboot

...mmand(str) and parameters > > I don't think that's it, but fair enough, try this sample config: > ************************************************# Test File: isolinux.cfg > default vesamenu.c32 > ALLOWOPTIONS 0 > LABEL Test kernel whichsys.c32 append -iso- memdisk initrd=fdboot.img -sys- initrd=fdboot.img > MENU END************************************************ > > I am using binaries from 6.03-pre11 from kernel.org. I used vesamenu.c32 and fdboot.img (FreeDOS) for the example but they are not required. > Accepting that this is a silly use of whichsys.c32,...

> > Thanks Ady, you were spot on, and I should have tested that scenario! > I narrowed the issue down to a line in my config: > > > ALLOWEDOPTIONS 0 > > > The comment next to it in my config indicates this was added to > disallow users dropping to the console with Escape or Tab, a > restriction I would like to keep. BUT, when this is set whichsys >

Hello, there is a "fdboot.img" floppy drive image included with FreeDOS ISO file. It's a floppy image file: root at debian64:~# file -s /home/martin/FreeDOS/isolinux/fdboot.img /home/martin/FreeDOS/isolinux/fdboot.img: x86 boot sector, FREE-DOS BEta 0.9 Bootloader KERNEL.SYS, code offset 0x40, OEM-ID "FreeDOS...

I don't think that's it, but fair enough, try this sample config: ************************************************# Test File: isolinux.cfg default vesamenu.c32 ALLOWOPTIONS 0 LABEL Test kernel whichsys.c32 append -iso- memdisk initrd=fdboot.img -sys- initrd=fdboot.img MENU END************************************************ I am using binaries from 6.03-pre11 from kernel.org. I used vesamenu.c32 and fdboot.img (FreeDOS) for the example but they are not required. Accepting that this is a silly use of whichsys.c32, running the same thi...

...be a bug in ELTORITO.SYS itself, as MDISKCHK lists the drive properly as E0. Below captured from redirecting to COM1 in QEMU: Drive 00 is MEMDISK 4.04: Address = 0x094ce000, len = 720 sectors, chs = 40/2/9, loader = 0x33 (ISOLINUX), cmdline = nopassany initrd=/isolinux/fdboot.img BOOT_IMAGE=/isolinux/memdisk Drive E0 is MEMDISK 4.04: Address = 0x09549000, len = 7461 sectors, chs = 65535/255/15, loader = 0x33 (ISOLINUX), cmdline = iso initrd=/isolinux/fdbootcd.iso BOOT_IMAGE=/isolinux/memdisk Drive 00 is MEMDISK 4.04: Address = 0x094...

Hello ALL, I've got a diskless server working (under Gentoo), booting on it works. (a linux session start with no problem.) My Big problem, is to get Memdisk to boot with PXE. In fact memdisk is loaded, but it cannot find the img file. I've tried a lot of thing, but nothing works... tftp use : /diskless the config file for PXE in then in : /diskless/pxelinux.cfg/ the root for the

...ccept this license, you can't use this software. In that case, press ENTER now. see license by pressing F2" # this is isolinux.cfg prompt 1 default harddisk ontimeout harddisk label harddisk localboot 0x80 // or -1 ??? label freedos //www.freedos.org kernel=memdisk append initrd=fdboot.GZ label 1 kernel=memdisk // ..ALIAS command would be nice append initrd=fdboot.GZ F2 showdoc.com gpl2.txt F0 bootmenu.txt then bootmenu.txt has something with "hey, press 1 to start FreeDOS setup" regards, Bernd Blaauw

...solinux, Memdisk, Menu, Sample programs. Since 3.10preX, Memdisk's INITRD can take multiple files. However, can it also take a few different always-present media, like imagefile(s) on harddisk or floppy, or take the floppy itself? LABEL loadDiskImageFromFloppy kernel memdisk append initrd=fd0/fdboot.img # or initrd=A:\FDBOOT.IMG ??? or take the floppy itself: LABEL loadFloppyIntoRAM kernel memdisk append initrd=fd0 # or APPEND initrd=A: ??? Bootable cdroms for example have a data area and a bootfile area. It's easy to obtain the bootfile (disk image) from the cdrom, it's relatively...

Try the following and let us know. If it doesn't work, we'll try other alternatives. *** DEFAULT vesamenu.c32 ALLOWOPTIONS 0 LABEL test COM32 whichsys.c32 APPEND -iso- iso -sys- sys LABEL iso LINUX memdisk APPEND initrd=fdboot.img LABEL sys LINUX memdisk APPEND initrd=fdboot.img *** Regards, Ady.

I have been trying to find the information by searching through the archives and google, so I am sorry if this question has been asked before I just have not been able to find an answer. I have a syslinux boot floppy which loads to the boot prompt, I wish to load a .gz image which is on my hd0 0 by using memdisk as the kernel. I have tried to kernel memdisk append root=/dev/hd0 0 (also just

...ng and let us know. If it doesn't work, we'll try > other alternatives. > > *** > > DEFAULT vesamenu.c32 > ALLOWOPTIONS 0 > > LABEL test > COM32 whichsys.c32 > APPEND -iso- iso -sys- sys > > LABEL iso > LINUX memdisk > APPEND initrd=fdboot.img > > LABEL sys > LINUX memdisk > APPEND initrd=fdboot.img > > *** > > Regards, > Ady. > _______________________________________________ > Syslinux mailing list > Submissions to Syslinux at zytor.com > Unsubscribe or set options at: > http://www....

...slow, so I'd like to use Syslinux + Memdisk to load a diskette image. then the text displayed to user will be: 1) FreeDOS bootdisk (accelerated, 386 computer minimum) 2) FreeDOS bootdisk #load 360KB diskette image from the bootfloppy into RAM - speedup!!! label 1 kernel memdisk append initrd=fdboot.img label 2 kernel freedos.bss the novice protection will warn too early. A: is accessed a lot, so a speedup by using Memdisk is welcome. However the SYSLINUX warning won't let the bootdisk boot on a 8086/80286 system I guess. before you ask.. no decent Ramdisk program for FreeDOS yet :( 1....

rename the VMlinuz*.* to file 'vmlinuz' (no quotes ofcourse). a bootfloppy leaves me enough diskspace, not 860KB. format as FAT12 (ofcourse), install Syslinux (I do this on Win2K with syslinux.exe A:, win9x: syslinux.com A:) my example: http://www.fdos.org/ripcord/beta9rc4/fdboot.img unfortunately no Linux involved. If I could only show a Knoppix bootfloppy (but it's part of a 700MB download). anyways, the following files should be present (MEMDISK optional) ldlinux.sys 8.104 Systeembestand 09/12/2003 17:05:56 MEMDISK 23.548 Bestand 05/12/2003 15:51:42 sysl...

HOPEFULLY fixes the 3.05 initrd bug. Please try it out and confirm; I will try to release it as 3.06 tomorrow. SIGH... -hpa

MEMDISK included in the freshly released Syslinux v3.10 is unfortunately broken. v3.09 works properly. Scenario: Isolinux --> MEMDISK --> FDBOOT.IMG (FreeDOS 360KB diskette image). Then try to access drive B: , which normally is your first diskette drive with driveletter A:. However, in this case MEMDISK occupies A:, and real diskdrive becomes B: Bug: when accessing B:, you're asked to swap disks, after which you see the mirrored con...

perhaps the boot-from-cdrom code in Smart Boot Manager? Bernd >>> No, since booting from CD-ROM requires that the El Torito part of the BIOS is activated, which it won't be if it didn't boot from CD-ROM in the first place. ---------------------------------------------------------------- Op deze e-mail zijn de volgende voorwaarden van toepassing:

...to loop mount a buried partition from within a hard drive image.) To enlarge existing floppy images, I originally learned of newmkfloppyimg.sh from this mailing list, and had followed the procedure http://www.syslinux.org/wiki/index.php/Large_floppy_images to go from a current 1.44MB FreeDOS fdboot or fdoem to a 10MB version thereof, but trying to boot the result with MEMDISK led to an infinite loop of MEMDISK banners. That's where the discussion started, and turns out I titled the thread poorly: it really has nothing to do with MEMDISK! 1) newmkfloppyimg.sh calls mkdosfs to create an...

...artition > from within a hard drive image.) To enlarge existing floppy images, I > originally learned of newmkfloppyimg.sh from this mailing list, and had > followed the procedure > http://www.syslinux.org/wiki/index.php/Large_floppy_images > to go from a current 1.44MB FreeDOS fdboot or fdoem to a 10MB version > thereof, but trying to boot the result with MEMDISK led to an infinite > loop of MEMDISK banners. That's where the discussion started, and turns > out I titled the thread poorly: it really has nothing to do with MEMDISK! > > 1) newmkfloppyimg.sh c...

I have periodically been trying to get memdisk to boot images larger than your average 1.44Mb floppy and have always been unsuccessful. I cannot boot anything greater than 1.44Mb. The systems I'm attempting to do this with are not too old but they are not recent either. One is a Asus P5A and the other is a Intel SE440BX both with the most recent bios firmware patches available applied. If

I would like to implement a replacement MSCDEX driver (based on the replacement in FreeDOS SHSUCDX http://johnson.tmfc.net/freedos/shsucdx.html and SYSLINUX) however instead of talking to disk BIOS calls or PATA chipset I would like it to talk to the NDIS driver and act as a TFTP client simply forfulling application get block requests through TFTP. Its not clear where the ISO9660 CD