similar to: Ideas for contrib infrastructure

Working on fixing lower-priority bugs that I didn't want to risk destabilizing the 2.07 release for: Changes in 2.08: * Add "timeoutcmd" to allow timeout to have a different action than just pressing Enter. * Fix bugs in the COMBOOT/COM32 command-line parsing. APPEND now works with COMBOOT/COM32 images.

Hi, I need to add an additional feature to Murali's menu system: sending and receiving UDP datagrams. I have no experiences with writing programs at such a low level. Therefore, I need some help. 1) How to transfer IP address and other options from PXElinux to comboot? 2) I got PXE specification, ver. 2.1 (sept. 1999); can I follow it safely? 3) Is there an easy interface to use PXE stack

Maybe I missed something here. What I want to happen is PXE boot on a timeout will boot to the hard drive. But, what happens is my comboot menu, which is default, loads right away and the ontimeout only happens when I escape out of the menu. My pxelinux.cfg/default: default menu timeout 100 ontimeout localboot # The Main Menu label menu kernel mainmenu.com append keeppxe #

Since lot of people want this thing, I will try to take a stab at it. For now, I will hard code the menu in the code, and then somebody else can remove that restriction. May be we can add some kind of keyword to the config file which syslinux ignores and the comboot menu does something with it. I have one question about comboot: If I write a DOS program using C (compiled using watcom -3 -mt -osx

On the SysLinux page, there is a screenshot of "COMBOOT Menu System for SYSLINUX developed by Murali Krishnan Ganapathy" (Advanced Menu System). I was wondering where I might be able to download this menu system in full to work with? If you dont want to share, I understand, but I am really intrigued by this and want to learn more, and maybe make my own design if I can figure it out.

This version contains a fix to mbr.asm, plus a version of Murali's menu system, but ported to gcc. Although gcc produces much bigger 16-bit code (since it's really 32-bit code with prefixes) I figured it would be much easier for people to deal with since it requires the configuration to be compiled in. That being said, it's a *very* powerful menu system, partially *because*

I have just released SYSLINUX 2.09-pre4 with a few changes: a) SYSLINUX should now correctly handle mode changes from within a COMBOOT program. b) Tweaks to the menu system to avoid the "grey text on black" problem. c) A new color scheme for the menu system (Murali, check it out and see if you think it works for you.) ftp://ftp.kernel.org/pub/linux/utils/boot/syslinux/Testing/

Hi. I want to use PXELinux to build a dynamic boot menu for a computer lab. Sometimes, the machines need to be in Linux mode/Windows mode/allow the option of Linux/Windows. I configured this all fine with PXELinux. My problem is really one of security. Someone can plug in a laptop with a DHCP server, and tftp server and fake a lab machine to boot into any mode they desire, or even

Goodness, how many prereleases has there been in the last week... have lost count... Anyway, I have implemented the already-promised chainbooting API, and have included a sample program to chainboot floppies (it works for harddisks too, but only for the MBR.) As a bonus, in the process I actually discovered that booting .bs/.bss images under SYSLINUX was actually broken... that has been

I'm installing syslinux on an embedded board that will only be reachable via boat+hike or helicopter. This will be a somewhat experimental platform, so I can't make a read-only filesystem on CF. What I'd like is to have two root filesystems on a CF card, one that is a read-only "fail-safe", and a 2nd that is the "normal" system I experiment with. What I'm

HPA, I believe I've found a possible bug with /menu. This against the unmodified -pre5 snapshot. SRC: http://www.survivaldisk.com/menutest.c COMPILED: http://www.survivaldisk.com/menutest.com It's easiest explained if you just compile the .c and experience it for yourself, anyways. If you have two submenus nested within each other and then call a third menu it will bring up the

Comments inline > -----Original Message----- > From: H. Peter Anvin [mailto:hpa at zytor.com] > Posted At: Thursday, November 14, 2002 1:40 AM > Posted To: Syslinux > Conversation: [syslinux] MSDOS not working: problem Solved > Subject: Re: [syslinux] MSDOS not working: problem Solved > > > G. Murali Krishnan wrote: > > > > In short: Is it possible to

Does the COMBOOT stuff with 2.04 work correctly with function calls? or does one need to write it as one huge function? If memory serves me correctly, there was some problem if hello.c was modified to include additional functions, in an earlier version. - Murali

I just found a rather embarrassing bug in PXELINUX -- and what's worse -- I wrote an email about it and killed it off accidentally :-/ It appears PXELINUX doesn't free its internal socket buffers (it has 32 of them) when it gets an error reply from the server, including "file not found." This means it will eventually run out of sockets and "go deaf." This

It seems that quite a bit of stuff built up very quickly after the 2.07 release: Changes from 2.07 to 2.08-pre6: * Add new configuration command "ontimeout" to allow timeout to have a different action than just pressing Enter. * Add new configuration command "onerror" to allow a custom command to be executed in case the kernel image is

On Tue, 25 Jun, at 01:09:47PM, H. Peter Anvin wrote: > Not really... let's just document "make bios". There's preliminary documentation in doc/building.txt. -- Matt Fleming, Intel Open Source Technology Center

Hello Where can I get example in assembly, using COM32 API ? I'm trying to make simple "Hello World" using COM32, but this code does not works 8-( org 0x101000 ; this number I get from comboot.doc _start: mov ecx,msge-msg mov ebx,msg mov ah,0x02 .L: mov dl, byte [ebx] inc ebx int 0x21 loop .L .Z: jmp .Z ; \infty loop msg: db "Hello World !" msge:

Is there a way to tell pxelinux to boot to floppy. I need an option in my comboot menu for this. Thanks Aaron

I mentioned in a private email recently that it would be useful if syslinux had a malloc implementation. I have one now if anyone's interested. -- Hebe 2004-02-08 14:26:08.183 UTC (JD 2453044.101484) X = -1.159504592, Y = 2.015990327, Z = 0.638260245 X' = -0.010415779, Y' = -0.003652077, Z' = 0.001024628

Is there a way for isolinux/syslinux to execute a list of comboot files immediately at startup, and only once? I have a bunch of small comboot .com files that I want to batch run immediately, then after that do a DISPLAY boot.msg similar in some ways to an autoexec.bat. For example: DEFAULT mycd APPEND ramdisk_size=100000 init=/etc/init lang=us .... TIMEOUT 300 ONSTARTUP mybatch <- ???