similar to: Suggestion for improving syslinux man page.

My reason for patching circa line 225 is that I think it is clearer. The reason for patching circa line 575 is http://bugs.debian.org/647603. They concluded that a .0 file is recognized not only by PXELINUX. And what is NBP? --- a/doc/syslinux.txt 2011-12-07 04:53:29.201556663 +0200 +++ b/doc/syslinux.txt 2011-12-07 04:50:11.000000000 +0200 @@ -221,7 +221,6 @@ LABEL label The following

Hi, I've read that Syslinux supports bzImage files now, but when I use pxelinux (which I hope also supports it) with a bzImage, I get : COMBOOT image too large What can I do to fix this ? Kind greetings, Wim Godden

Hi folks, I'd like to write a graphical menu for a rescue Linux system I'm currently working on in my spare time. I'm experimenting with VESA for this... but my real questions are: How do I boot a Linux kernel from a COMBoot (.cbt) program ? Supposed I have syslinux.cfg that looks like this: DEFAULT menu LABEL menu KERNEL menu.cbt LABEL linux KERNEL kernel.bzi Do I have to use

Hi, What the the size limit of booting bzImage file with syslinux ? I have tested different sized bzImage files, and when the files are small <800K, they work with syslinuz, but at some size larger they fail to work. This was the same problem loadlin1.6 had, but loadlin1.6c fixes the issue, and I can boot bzImage sizes up to 1.5Meg with loadlin, but syslinux fails. Can you confirm this

Hi folks, Syslinux 5.00 is out in time for the holidays. This release includes a lot of changes from 4.06. I've included the NEWS entries below, which highlight the major changes. Lots of assembly code has been rewritten in C, which makes further development much easier (and also really helped for the 'firmware' abstraction that appears in Syslinux-6.00-pre1). So be on the lookout

Hi Peter, While testing I noticed a problem with the launching of comboot files. When you start a comboot, the user command line text is copied to the comboot's PSP, but the default append options or the virtual kernel append options are not copied. This means I can't have an isolinux.cfg as follows: default bscript label bscript kernel bscript.cbt append myscript.txt because

Hi, As requested on IRC, here are the step-by-step instructions to reproduce the failure I see: On http://rom-o-matic.net/gpxe/gpxe-1.0.1/contrib/rom-o-matic/build.php: output format: .dsk NIC type: e1000_82540 x CONSOLE_PCBIOS x CONSOLE_SERIAL BANNER_TIMEOUT: 20 COMCONSOLE: 0x3F8 _ COMPRESERVE COMSPEED: 57600 COMDATA: 8 COMPARITY: 0 COMSTOP: 1 x DOWNLOAD_PROTO_TFTP x DOWNLOAD_PROTO_HTTP _

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

I have an issue to boot iPXE with Syslinux 5.01. However, the same method works for Syslinux 4.06. The error messages I got is (see attached png file): =================================== iPXE 1.0.0+git-20120202.f8840ba-3 -- Open Source Network Boot Firmware -- http://ipxe.org Features: VLAN HTTP iSCSI DNS TFTP AoE SRP BzImage COMBOOT ELF MBOOT PXE PXEXT /syslinux/ipxe.lkn: command not found

First of all Great software, Do you know how I can get the syslinux to display a help screen and then return to the menu, or where I can find information on making .cbt files.. Thanks. Your help would be much appreciated Rene -------------- next part -------------- An HTML attachment was scrubbed... URL:

LDLINUX.SYS uses a working directory. The documentation seems to improve if that fact is made explicit. So the working directory is added to the documentation (with a bit of vagueness and possibly not entirely correct, to keep it readable). Signed-off-by: Paul Bolle <pebolle at tiscali.nl> --- This is a result of today's discussion of a previous patch ("Describe the --directory

Hi Please excuse my english ... Does somebody have a .c32 , .cbt or .exe program to shutdown an ACPI and/or APM BIOS PC from PXELinux or DOS ? Or could be shutdown added as an option to PXELinux ? School environment, remote administration. On night time the electrical power is turned off in labs and PC loose WakeOnLan(WOL) and AlertStandardFormat(ASF) capabilities. In the morning when the

I started with Vivek's ELF bzImage patch from Oct last year, mashed it to apply to hpa's new setup/boot code. This patch does a couple of things, which would probably be better split into multiple patches: 1. Glue an ELF header onto the front of bzImage. This is a real ELF header at the front of the file. Breaks akpm's laptop, apparently, but it works for me. 2.

I started with Vivek's ELF bzImage patch from Oct last year, mashed it to apply to hpa's new setup/boot code. This patch does a couple of things, which would probably be better split into multiple patches: 1. Glue an ELF header onto the front of bzImage. This is a real ELF header at the front of the file. Breaks akpm's laptop, apparently, but it works for me. 2.

Dea-R community. I'd like to draw your attention to an issue I have recently encountered while doing my current data analysis. I've got an unexpected (to me) result from the command: > augPred(lmList(my.object)), 'my.object' being a grouped data frame of class: > class(my.object) [1] "nfnGroupedData" "nfGroupedData" "groupedData"

I''m working with some internally created software that is very closely tied to the kernel version. I *must* use version 2.6.23.9 of the kernel with a couple in-house patches applied. I''d like to be able to virtualize some machines and run this software within Xen. Because Xen does not currently support bzImage kernels I am struggling to get my kernel small enough for a zImage

OK, here's another go-around. This patch leaves the bzImage itself unmodified, but it changes the payload into an ELF file. That is, the 32-bit decompression/relocation+compressed kernel is now a properly formed ELF file. One thing that fell out of this is that code32_start end up being a pointer to the ELF header rather than an entrypoint. Rather than reproducing Vivek's (?) hack of

OK, here's another go-around. This patch leaves the bzImage itself unmodified, but it changes the payload into an ELF file. That is, the 32-bit decompression/relocation+compressed kernel is now a properly formed ELF file. One thing that fell out of this is that code32_start end up being a pointer to the ELF header rather than an entrypoint. Rather than reproducing Vivek's (?) hack of

ldlinux.sys uses a working directory. The documentation seems to improve if that fact is made explicit. So the working directory is added to the documentation (with a bit of vagueness and possibly not entirely correct, to keep it readable). While we're at it, also convert the name ldlinus.sys to lowercase everywhere, even if it's clear its name is used in a DOS context. Signed-off-by:

Hi All, I have a rather unique (at least from reading the archives) situation that has me stumped, and I'm hoping the gurus can help. Here's my problem, I have a Solaris 2.8 server running Samba 2.2.8 which sits on two networks (no routing between networks). On one side of the Samba server are 100 PCs running a mix of Win95 and Win98 which have touch screens and no keyboards, that are