similar to: Syslinux 3.83 released

Hello, Starting version PXELINUX 3.83 2009-10-05, i am not able to boot anymore using "localboot 0" entry. It show "" Booting from local disk... """ Then loop on the network boot of the interface then after a few try show the message: """ It appears your computer has less than 268K of low ("DOS") ... Boot failed: press a key to

Syslinux 3.86 is out; it is a bug fix release. Syslinux 4.00, starting with Syslinux 4.00-pre38, is now officially in beta test. Special thanks to Intel Corporation, my current employer, for their support for my Syslinux work. Changes in 3.86: * chain.c32: fix chainloading the MBR of a hard disk (broken in 3.85). * mboot.c32: report the boot loader name in the information structure. *

Syslinux 3.85 is a bug fix and minor new feature release. The biggest change is undoubtedly that gPXELINUX is now considered feature complete, and should be able to be a drop-in for PXELINUX for all uses. Special thanks to Intel Corporation, my current employer, for their support for my Syslinux work. Changes in 3.85: * gPXELINUX: updated to gPXE 1.0.0. gPXELINUX can now do NBP

Well, it has to happen at some point, so I have officially pushed out SYSLINUX 3.72. The big news in this release is of course the ISOLINUX hybrid mode support (a single image which can be booted either from a CD-ROM or from a hard disk/USB stick), but there are plenty of more goodies in here, including the label listing (not technically completion) on the Tab key. As usual, huge thanks to

Hi, I once again have a problem with memdisk failing to boot a harddisk image to update my Thinkpad X200s firmware. I extracted the harddisk image from the eltorito type 4 ISO using the isobar tool. Then I added memdisk using this image as initrd to my grub, rebooted and it boots into PC DOS and then freezes (ctrl-alt-del still works to reboot the system). Inside Qemu however it works fine

Changes in 3.61: * EXTLINUX: fix crash when accessing an empty file. * elf.c32: If a PHDR segment is present, load it. * Fix SHA-1 and MD5 passwords. * ISOLINUX: fix booting when mastered without mkisofs -boot-info-table (broken since 3.50, sigh...) * Handle BIOSes which emit multiple contiguous valid memory regions in the e820 map. Begin3 Title: syslinux Version: 3.61 Entered-date:

Hi, I'm doing a small hobby project writing some tools to put DOS boot images and Linux rescue images on a USB stick. For this I have partitioned my USB stick in 2 partitions, one 192MB partition with a VFAT filesystem (for the normal use) and a second partition with an ext3 filesystem. My aim was to provide a graphical menu (grub) to access the different images using memdisk. Since

Has anybody tried to boot a dos disk via memdisk with a usb flash device as a primary hard drive? I have a 512MB flash key that when connected becomes my primary hard drive (new bios) - 0x80. If I boot a MS-DOS 7.10 floppy, one gets the command prompt and I can see the contents of my flash key as drive C:. But, if I make a image of the floppy and boot the image via memdisk, then memdisk

Some people have reported portability problems with SYSLINUX 3.00, mostly due to the use of HDIO_GETGEO_BIG, which is deprecated; additionally, the advanced menu system wouldn't build for everyone due to a spurious reference to %ebp. This release fixes these things, plus makes the extlinux installer default to zipdisk geometry (64 heads, 32 sectors) if it can't guess anything else.

Hi Thanx guys for the help on understanding howto read dmi info! I now have a custom boot menu for install of different linux versions based if they have been installed before (reinstall is ok for users, first install is not), and installquirks like if we detect odd hardware, we add install options to redhat installer so it can install anyhow (for instance hp dc7800 who needs pci=nommconf as

Finally, the 4.06 release is out there. Thanks to everyone who helped by submitting patches and testing! Peter snuck in a change at the last minute that fixes the GCC 4.7 MinGW struct layout incompatibility in a different way. Here are the highlights of this release, Changes in 4.06: * Support for NTFS, by Paulo Alcantara. * EXTLINUX: more robust device detection, allow user to

Now that pxechain.com can work (with my patch to core/pxelinux.asm), a PXE Chainload COM32 is not as big of a deal but I agree with HPA that it would be a good idea, especially considering the possible flexibility that this may allow. For the moment, I've named the chain module pxechn.c32 in order to not collide with the name pxechain.com when not specifying the .com/.c32 extension.

Hi, I was wondering if 1680K floppy support in memdisk was planned, impossible or undesirable :) I noticed RIP is providing a slightly more stuffed 1680K floppy (but no 2880K floppy) and I had hoped memdisk could support this. Kind regards, -- dag wieers, dag at wieers.com, http://dag.wieers.com/ -- [all I want is a warm bed and a kind word and unlimited power]

Hey all, I recently updated to syslinux 3.83, I am getting machines rebooting or locking after loading PC DOS. Most notably with Hitachi's Disk Fitness Test (http://www.hitachigst.com/hdd/support/download.htm#DFT) Version 4.16. At first it was a trickle, and now it seems I am having the issue with more hardware. I downgraded to syslinux 3.81, and everything is happy again. The Current

Hi, I was wondering what's the best standard file extension for zipped DOS disk images and ramdisks. I've been using the following standard: .zi kernels, memtest86, memdisk .igz .img.gz zipped floppy images and ramdisks I'd rather have a different extension for ramdisks, maybe .zim zipped floppy images .zrd zipped ramdisks Any ideas ? It would also be nice if syslinux

On Sat, Jun 8, 2013 at 1:17 PM, H. Peter Anvin <hpa at zytor.com> wrote: > I have to say I wonder how much of this is iPXE and much is syslinux... > > Gene Cumm <gene.cumm at gmail.com> wrote: > >>On Thu, Jun 6, 2013 at 5:01 PM, H. Peter Anvin <hpa at zytor.com> wrote: >>> Very odd! >>> >>> This shows a TFTP connection being correctly

... it has a slightly modified version of Paul's VKernelBuf initialization patch. I modified it to initialize the whole buffer instead. I found, on careful reading of the spec, that it's actually possible to patch the DHCP packets in PXE memory. This might help the handling of NBP chainloading in PXELINUX, by making the pathname of the chainloaded file available to itself. I

I just pushed out SYSLINUX 3.73-pre3. The only significant difference over -pre2 was changing MEMDISK to use "safeint" by default. -hpa

Can pxelinux be used to chain other *network* bootloaders directly? I.e., keep the pxe stack but replace itself with an alternate network boot loader (eg, the intel nbp, or, more specificly, an arbitrary bootloader for another OS)? I'm sure this is an obvious FAQ but I can't find reference to it (sorry). Obviously memdisk could be used to load other OSes, but I have been given a strict

Hello everyone, I have just released SYSLINUX 3.70, which is the first version which includes gPXE for support of non-TFTP network scripts, as well as a large number of other enhancments. gPXE support is still somewhat experimental - in particular it still doesn't support chaining other NBPs. Very special thanks to: - rPath, Inc, my employer, for the uncountable hours I've spent