similar to: ElTorito from Floppy (was: Re: Can I use...)

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,

Is the new Isolinux series effecting hardware in a different way as 2.xx series? I'm getting a system crash in VMware. I guess this is a Vmware issue, but thought you might want to know. 2.xx series works OK for me. I get to see 8 dots when loading a 360KB imagefile, following by crash message mentioned below. Replacing MEMDISK by old version does not matter, only replacing isolinux.bin 3.05

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:

Hello HPA, I think on harddisks, Syslinux is going to lose somehow from other bootloaders like LILO, Grub and others. However, SYSLINUX is still VERY usefull for removable media like diskettes, Zipdisks, USB Flash keys, etc.. I don't know if the fact that Syslinux is now installed using blockmapping is really breaking the usefullness for harddisks. You already mentioned system attribute

>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

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

isolinux: Extremely broken BIOS detected Yoper 2.1 --------- ISOLINUX 2.11 2004-08-16 isolinux: Loading spec packet failed, trying to wing it... isolinux: Extremely broken BIOS detected, last ditch attempt with drive = 9F isolinux: Disk error 01, AX = 4209, drive 9F Boot failed: press a key to retry... Helix 1.5 --------- ISOLINUX 2.04 (Debian, 2003-06-06) isolinux: Loading spec packet failed,

(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, 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

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

This isn't a syslinux issue, but I don't see a mailing list setup for the zisofs tools. Forgive me if this is sent to the wrong place. The sloppy option does not work as documented in the mkzftree man page. Here is the patch I used to enable it. --- zisofs-tools-1.0.7/mkzftree.c.sloppy 2007-05-15 08:42:20.000000000 -0400 +++ zisofs-tools-1.0.7/mkzftree.c 2007-05-15

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.

Hello Everyone, In short, I have the following questions: Is there a known problem with PXE booting and LinuxBIOS? Will pxelinux.0 not work with a serial console? Is there a way to convert pxelinux.0 into an ELF file? The Long Version: I am working on installing Rocks Cluter distribution on a LinuxNetworx cluster. The hardware was donated to my college, and the CS

I just merged a version of the eltorito.sys sources, reconstructed by Eric Auer to match the 1.4 binary and then converted to NASM by NoMySo, to the Syslinux repository; I would greatly appreciate if people would test it to make sure it didn't break in conversion. -hpa

H. Peter, three simple commits here[1] (for_hpa branch). Gert, sample binaries are here[2]. --- mdiskchk: Add --no-sequential mode It might be useful to suppress MDISKCHK.COM's classic behaviour of probing all BIOS drive numbers in search of MEMDISKs. Some BIOSes might not enjoy being probed. --- memdisk: Correct El Torito termination response Two

Good day to all. Since we've adopted Gary Tong's and Bart Lagerweij's ElTorito.sys (now modified by H. Peter Anvin and tiny changes from myself), I'd appreciate if anyone with more El Torito experience might criticize my comments below and advise as to how they might be wrong. Some of it is off-topic GRUB4DOS detail; safe to ignore. A bit of history: FDUBCD ("FreeDOS

Hi, I am compiling a tiny linux kernel 2.6.10 to be used together with linuxbios. The boot phase will go as follows: linuxbios->tiny linux kernel->initramfs The initramfs shall use dhcp to get it's address and then tftp a full featured kernel. This kernel must be started through kexec. I use a tweaked networkdriver in the kernel and cannot use a normal PXE boot. Which files should I

Something is not right as I have added files to the server that has never shown up on my backup machine - so everything is NOT being update by any means. I finally removed rsync - version rsync-3.0.6-12.el6.x86_64 and installed the same version that is on my server which is rsync-3.1.1-1.el6.rfx.x86_64 Now everything is working as expected. Perhaps there is something between the two different

I really want to thank you for taking time to help me with this. I have changed the rsyncd.conf as per you suggestion below. I have several different systems that sync to the server and today they were showing this Number of files: 25832 Number of files transferred: 78 Total file size: 49441191919 bytes Total transferred file size: 37421120 bytes Literal data: 36955331 bytes Matched data:

In Syslinux 6.03-pre6: _ The txt/html/*.html files are currently created 3 times, one for each firmware. I think they should be created only once (under the main txt/html/ directory), just as the rest of the documentation is. In that case, the <respective_firmware>/txt/html/ subdirectories should not even be created. _ The bios/dosutil/ directory contains copybs.com and eltorito.sys,