similar to: pxelinux and DISPLAY

I've begun tinkering with syslinux v3 and have uncovered an anomoly with the DISPLAY file when called by pxelinux.0. If I have: DISPLAY boot.msg With an "^Xsplash.lss\n" in the file boot.msg (exactly: 18 73 70 6C 61 73 68 2E 6C 73 73 0A) file, it will fail to load the rle image. And produce some goofy results in the tftpd log: Jun 5 06:27:06 pxe in.tftpd[24649]: RRQ from

I've been working with Matt Burgess here on this problem, and have found the following: syslinux 3.08-pre10 ? broken >>> config.inc:max_cmd_len=255 syslinux 3.08-pre11 ? works >>> config.inc:max_cmd_len=1023 syslinux 3.08 ? works >>> config.inc:max_cmd_len=1023 syslinux 3.09-pre1 ? works >>> config.inc:max_cmd_len=1023 syslinux 3.09-pre2 ? broken

I am hoping for some advice regarding another index problem. The code below is intended to assign a value of 'V' if values on certain variables are >= 1, assign a value of 'N' if values on certain variables are >= 1 on other variables and assign a 'O' if values on any variable which have a value <= 0. The outcome of this code is to assign a single

Well, with this simple patch I'm able to load initrd from a different disk. It's not finished, it's just to ask you if I'm going in the right direction... I have also some suggestion/question: - many boot sector I saw use [bp+xx] addressing to gain some bytes. Why don't you use such method? - had syslinux been tested with usb floppy? You test dl however using usb floppy dl ==

Well, with this simple patch I'm able to load initrd from a different disk. It's not finished, it's just to ask you if I'm going in the right direction... I have also some suggestion/question: - many boot sector I saw use [bp+xx] addressing to gain some bytes. Why don't you use such method? - had syslinux been tested with usb floppy? You test dl however using usb floppy dl ==

I have released SYSLINUX 2.08-pre11. It is the same as 2.08-pre10 except I have added logical partition support to the chainbooting module (still no partition hiding or anything like that.) Unfortunately I have no way to test this at the moment, so I thought I'd release a -pre11 and see if someone was willing to take it for a spin.

The syslinux-4.0.04-pre11 and pre10 have 20MB tar.sign files that other versions don't, and has dates for Jan 01 1970. It appears these are the uncompressed tar files rather than a signature for the file? ftp://ftp.kernel.org/pub/linux/boot/syslinux/Testing/syslinux-4.04-pre1 1.tar.sign One other note. Last time I checked, it was still using 2010 as the latest date in the

On Wed, 24 Jul, at 01:22:18PM, Matt Fleming wrote: > On Wed, 24 Jul, at 01:41:49PM, Igor Sverkos wrote: > > Hi, > > > > syslinux-6.02-pre10 works! I'll get my menu. > > How about booting memtest with -pre10? Actually, make that -pre11? -- Matt Fleming, Intel Open Source Technology Center

Im trying to use newer simple-menu features, and have found that the following config-file (closely based on wiki pxelinux example) - fails for 3.62-pre11, - works for 3.62-pre10 where 'working' is successive reloads such that re-edits of file are seen on next reload and broken is issuing this error: Initial menu has no LABEL entries! boot: #>

Parse the TIMEOUT keyword from the config file and pass it to gfxboot core. Signed-off-by: Sebastian Herbszt <herbszt at gmx.de> Index: syslinux-3.82-440-g6483c80/modules/gfxboot.asm =================================================================== --- syslinux-3.82-440-g6483c80.orig/modules/gfxboot.asm +++ syslinux-3.82-440-g6483c80/modules/gfxboot.asm @@ -657,8 +657,7 @@ gfx_input:

Petr Vandrovec wrote: > Hello, > one of FreeDOS developers pointed out (in > http://www.vmware.com/community/thread.jspa?threadID=11324&messageID=109507&#109507) > that FreeDOS does not work under VMware when using ISOLINUX 3.0x. After > looking at their ISO image I downloaded syslinux-3.05, and there seems > to be bad bug: > > You have this in kernel.inc:

The gfxboot COM module currently ignores the DEFAULT entry set in syslinux config file and always default to 0 instead. This patch parses DEFAULT entries in the config file and set the default entry accordingly. Signed-off-by: Christophe Fergeau <cfergeau at mandriva.com> --- modules/gfxboot.asm | 34 ++++++++++++++++++++++++++++++++-- 1 files changed, 32 insertions(+), 2 deletions(-)

--AkbCVLjbJ9qUtAXD Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi all! On behalf of the netfilter core team I have the following announcement: The following kernel versions habe a bug in include/linux/list.h, which causes netfilter's connection tracking code to misbehave: 2.4.10-pre10 2.4.10-pre11 2.4.10-pre12 2.4.10

So here it is. Ugly and far from acceptable shape but nonetheless it seems to work. Parts are borrowed from syslinux core and of course the gfxboot patch for syslinux 3.63. Syntax: gfxboot.com <bootlogo file> - Sebastian --- /dev/null 2007-09-21 23:50:58.000000000 +0200 +++ syslinux-3.73-pre6/modules/gfxboot.asm 2008-11-22 19:01:10.000000000 +0100 @@ -0,0 +1,883 @@ + absolute 0

> Damn, I messed up the git tags so I wasn't looking at an accurate list > of changes between -pre1 and -pre2. > > Your error is likely being triggered by the recent kernel changes. For > x86-64 we now try to boot a Linux kernel via the 32-bit entry point. > It's possible that code doesn't work correctly with vmware. > > Could you grab -pre10 and change the

This is the latest version of the gfxboot module. It's supposed to work on all Syslinux derivatives. I am not sure about the copyright notice and would appreciate any input. - Sebastian Index: syslinux-3.74-pre17-2-g2a9ddec/modules/Makefile =================================================================== --- syslinux-3.74-pre17-2-g2a9ddec.orig/modules/Makefile +++

I was hoping for some advice regarding indexing, From a dataframe there are 27 variables of interest, with the prefix of "pre". [7] "Decision" "MHCDate" "pre01" "pre01111" "pre012" "pre013" [13] "pre02" "pre02111" "pre02114" "pre0211" "pre0212"

I have released 3.08-pre10, which includes a version of 'raw' support which should work when the CPU is in big real mode (called 'bigraw', appropriately enough.) Note that it will ALWAYS put DS and ES in big mode; there isn't any really sane way to test if they should be or not. -hpa

hi, i've tested with 2 version of awdflash and uniflash: here the results: it only worked with freedos, not with win98 dos; with win98 the images were not bootable; but that does not matter; freedos is ok. awdflash 8.27.45: flash ok awdflash 8.27.41 (uses protected mode): flash ok uniflash 1.40: when starting flashing the program freeze. awdflash 8.27.45 never worked before so i think this

Attempts to load *.lkrn images were failing with "Not enough memory to load specified image". These images have the su_ramdisk_max header field set to zero, and the code in core/runkernel.inc was limiting MyHighMemSize too early (before the load_high call used to load the main part of the kernel). Signed-off-by: Sergey Vlasov <vsu at altlinux.ru> --- core/runkernel.inc | 13