similar to: EDD error RE: Re: SYSLINUX 2.12-pre7 released

>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

(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

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

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

>No, but you can write a comboot/com32 module to do it if you wish. I meant for syslinux.exe/com (the installer). that BIOS issue is now handled in the driver the author wrote. Unfortunately I can't find another cdrom which boots but lets me access A: to really demonstrate it's the BIOS which is doing this. Every non-emulation cdrom either uses isolinux (even ReactOS bootloader) or

a member of the FreeDOS project has transformed Smart Boot Manager into a COM32 module for Syslinux. Might be a bit more usefull than Syslinux -> memdisk -> imagefile -> Smart Boot Manager ( -> 'boot from cd -> cdrom ) I've inserted it into this diskette image: http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/beta9sr1/fdos1440.img That's nice to

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

HPA, is it possible to add GZ support in syslinux itself? Some standalone software compresses very well, but is not compressed. Example is the Memtest86+ binary (90KB uncompressed --> 35KB gzip'd) and maybe Smart Boot Manager (gzip'd COM32 binary instead of normal COM32 binary?). I'm using both on a simple bootdisk, and all space savings are welcome. a workaround could ofcourse

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.

This was sent to lkml, I think it may be interesting to this list... ----- Forwarded message from "J . A . Magallon" <jamagallon@able.es> ----- Envelope-to: mfedyk@mikef-linux-x86.matchmail.com Delivery-date: Fri, 02 Nov 2001 16:38:49 -0800 From: "J . A . Magallon" <jamagallon@able.es> To: Lista Linux-Kernel <linux-kernel@vger.kernel.org> Subject: ext3 for

Hi all, I have just pushed out SYSLINUX 3.55-pre5 and 3.60-pre7. I have decided to give them both release candidate status, with the intent of having a simultaneous 3.55 (bug fixes only) and 3.60 (new functionality) release. Please test them out and let me know how they do. -hpa

Hi all, I have merged Tim's patches to the mboot loader, and have pushed it out as 3.20-pre7. I guess I'm going to actually have to make a 3.20 here soon... -hpa

I'm trying to use this universal DOS TCP/IP boot disk available here: http://members.iinet.net.au/~bdriver/bootdisk/ It requires an MS-DOS formatted disk created by Windows XP. It works great as a floppy but doesn't boot at all with memdisk. The problem can be simplified down to just the XP boot disk. If you make an MS-DOS startup disk with XP on a floppy, dd the floppy to an image

I just uploaded SYSLINUX 3.72-pre7. I'm hoping this will be the final 3.72 prerelease. Please test it and holler if something is (still) broken. -hpa

Still interested in pre-compiled binaries for 6.03-pre6. But my comment about 6.02 TFTP brokenness may speak more to my lack of understanding of the TFTP protocol than to any pxelinux 6.02 code problems. It seems that when TFTP sends an OACK back to syslinux.efi, it sends it from another port than 69. So, it seems to be opening a data connection back to the TFTP client off an ephemeral port.

On Thu, Jul 4, 2013 at 10:44 AM, Shantanu Gadgil <shantanugadgil at yahoo.com> wrote: > On Thu, 7/4/13, Matt Fleming <matt at console-pimps.org> wrote: > > Subject: Re: [syslinux] Syslinux 5.11-pre7 not working > To: "Shantanu Gadgil" <shantanugadgil at yahoo.com> > Cc: syslinux at zytor.com > Date: Thursday, July 4, 2013, 4:51 PM > > On

Hi all, I've decided to move SYSLINUX 3.30-pre7 to release candidate status (the difference from 3.30-pre6 is pretty much that 3.30-pre7 contains a very simple compiled-in graphical background if the user doesn't specify MENU BACKGROUND.) Please test it out and let me know. Thanks, -hpa

I'm going to promote SYSLINUX 3.32-pre7 to release candidate unless someone objects, with the intent of releasing 3.32 immediately after Christmas. Please let me know if there are problems that should make me *not* do so, even if you have previously reported them. -hpa

I have just pushed out Syslinux 3.80-pre7. I am slightly concerned about putting this into the release tree at this point: I was working with some of the shuffler code, and found that the memory map handling was actually severely buggy on some of my test cases. Resolving that problem took rewriting most of syslinux_add_memmap(). However, against better judgement :) I decided to check in the

I have just released SYSLINUX 1.75-pre7. Barring any showstopper bugs, this WILL be the final 1.75, so please test if out, and if you find problems speak now or forever hold your pizza. After 1.75 is out I'm going to be spending most of my time on the new 2.00 release. http://www.kernel.org/pub/linux/utils/boot/syslinux/Testing/ -hpa