similar to: LABEL command.

Hello all, I've been following this project with interest, and have had great fun implementing Isolinux within the FreeDOS cdrom distribution. Since I'm not that an expert at Linux, I would like to know how I can *succesfully* generate a bootable image from a partition. Situation is like this: (640MB RAM on system) 60GB IDE harddisk, primary partition 1 win98 500MB extended partition

(Sorry, Outlook webmail prohibits me from proper replying/quoting) >it has the nice effect that you can load the El Torito >CD-ROM driver. Which seems logical if you boot a kernel (like Linux, or Memdisk with an imagefile), but not when doing a local boot (diskette/harddisk) In other words: boot from cdrom, and if you then load a disk-image, eltorito.sys should load. If not loading a

HPA, a longterm reminder. See below. Can you also make a LABEL ignore other labels if no KERNEL statement is found in between? That way you could define multiple aliasses for an entry. label foo label bar label memtest kernel memtestp foo ignores 'label bar' , 'label memtest' and executes 'kernel memtest' bar ignores 'label memtest' and executes 'kernel

On Sat, Sep 22, 2012 at 08:31:51AM +0200, Bernd Blaauw wrote: > Op 22-9-2012 0:58, H. Peter Anvin schreef: > > > MEMDISK doesn't load anything. Syslinux loads things, and uses a block > > size of (typically) 63.5K which is the maximum supported by EDD 3.0. > > Thank you very much for stating this performance limitation to > syslinux core, and likely linux.c32

Dear Syslinux bootloader list, I'm running into a few issues concerning Syslinux modules here, hoping you can answer one or more of the following questions: * Where's "ifmemdsk.c32" ? 4.05, 4.06pre1 and latest 4.10pre seem to lack it. Only the "ifmemdsk.c" file, which is likely sourcecode. Not seeing any "ifmemdsk.cbt" legacy comboot module. * Do COM32

This is a minor tweak on 3.11-pre2. If nothing new comes up, I will release this as 3.11 probably early next week. -hpa

Is there any documentation available about what block size MEMDISK uses to load (big iso/harddisk) image files? Experimenting with cptime.c32 on a Lexar Triton Jumpdrive (64GB, 170MB/s read in Windows, 150MB/s write in Windows) on bootable USB3.0 resulted in the following, depending on specified block size: * 2048 bytes --> 25MB/s * 2MB --> 61MB/s It would be nice to know at which speed

hm, nice algorythm thingie. I'm not a programmer, so here goes: currently: F1 helpfile.txt probably results in DISPLAY helpfile.txt perhaps extend this option: F1 arg1 arg2 arg3 argX if arg1 does not exist, abort (currently also done?) if arg1 ends in COM extension, execute it and pass the optional arg2/3/X parameters if arg1 ends in C32 extension, same thing. else DISPLAY arg1 // arg1

I'm running into an issue which I didn't expect to encounter. When specifying the "nopassany" parameter to hide physical drives, I'm getting different output from ELTORITO.SYS (v1.5, syslinux distro) such that it fails. My intent is a LiveCD functionality with a DOS RAMDISK program taking over as drive C:, meaning either no FAT partitions on harddisks and removable disks

>information a bit closer; it'd find that it's marked accordingly. UDMA2.SYS author now worked around it, it seems you do something with "DPTE" in isolinux.asm but not using it (probably for memdisk or direct floppy/harddisk emulation?). also something about EDD v1.1 and v3.0 specifications and setting bits to 1. Anyway, the driver works now on: BIOS -> cdrom ->

I've recently returned to working on FreeDOS again after quite some time, and read about an unmerged MEMDISK branch that allows to boot DOS-based ISOs. This seemed quite usefull to me as it allows for faster modifications to my code/scripts/disklayout. The general idea was to install Syslinux 3.83 to harddisk, then add the modified Memdisk from that boot-land forum, as well as my ISO. In

I have an application/program which shows 'bios EDD error' when using Isolinux (with either loading an image directly through MEMDISK, or booting to A:), and not when using a bootdisk directly or booting a bootdisk directly which has SYSLINUX on it. configuration: bootable cdrom with Isolinux 2.11/2.12pre9 as bootloader. 1.44MB bootdisk with MSDOS.SYS/IO.SYS and the UDMA2 dos driver,

Hello Bernd, I think you might wanna known this. Cheers Geert Stappers ----- Forwarded message from postmaster at fontys.nl ----- From: postmaster at fontys.nl To: stappers at stappers.nl Subject: Delivery Status Notification (Failure) Date: Sun, 13 Mar 2005 23:56:03 +0100 This is an automatically generated Delivery Status Notification. Delivery to the following recipients failed.

Tried MSDOS7.0(win95osr2) only not freedos. Why hard disk images may fail with msdos ? De"Blaauw,Bernd B." B.Blaauw at student.fontys.nl A "fabrice.maraval" fabrice.maraval at laposte.net Copies syslinux at zytor.com Date Thu, 18 Mar 2004 22:59:53 +0100 Objet RE: [syslinux] (no subject) > What operating system on the Bochs harddisk images? > > FreeDOS seems

Does SYSLINUX have any idea which DOS driveletter would be assigned to the disk it is booting from? At www.veder.com someone is trying to build a USB flash drive. However, FreeDOS does not seem to boot correctly from it (bootsector trouble maybe, or kernel itself is confusing drives), thus we're thinking of using Syslinux + Memdisk + bootimage, but somehow we want to be able to also access the

>The way the El Torito CD-ROM is going to look like to the program, is >that it looks like an additional hard disk which a very high drive >number (typically 9Fh or so); MS-DOS will normally ignore this since it >asks the BIOS how many drives there are and ignores the rest. >Does the error message come from UDMA2.SYS or...? > -hpa yes, it comes from UDMA2.SYS, it does a

HPA, is it possible to add a parameter/argument to syslinux.com/syslinux.exe to specify a file? currently it's something like SYSLINUX A: I'd like the following also to be possible: SYSLINUX A: A:\SYSLINUX.BIN It still copies LDLINUX.BIN to A:, but writes the generated bootsector intended for drive A: to a 512byte user-specified file Perhaps to allow both at the same time even SYSLINUX

Hi, is there an option to have the DISPLAY command issue a pause after each screen full of information? I've been searching for a way to have users to agree to (or at least be able to read ) the GPL license. "by issueing a command other than F2 you agree that you are bound to the terms of the GNU Public License that is used on this FreeDOS beta9 cdrom. You can read the license terms by

I have a Lilo.conf file, which I have tried for many hours to convert to Syslinux. I looked around on the web for references on translating some of the components. I want to convert it to Syslinux/Isolinux. Any suggestions would be greatly appreciated. When I tried to convert it I made sure that the kernel and initrd had proper DOS names and such. -Michael =:LILO.CONF:= prompt timeout=10

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: