similar to: Local boot problem

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

Can't hold it off any longer... here it is :) Changes in 2.00: * ALL: Add support for "COM32" (32-bit COMBOOT) images. * ALL: Add an API for COMBOOT/COM32 images. See comboot.doc for details. There is a C development environment for COM32 being created; it should be ready at some point in the future. * Fix mbr.asm so that it

Hi all, Sorry if this question seems odd. Is it possible to use syslinux to boot from a regular hard disk? I know that's exactly what grub, lilo etc. are doing, but I would really like to utilize the comboot option of syslinux. Are there LBA limitations to such a setup? Shachar -- Shachar Shemesh Lingnu Open Source Consulting ltd. Have you backed up today's work?

HAS_LOCALBOOT is set unconditionally in config.inc. Signed-off-by: Sebastian Herbszt <herbszt at gmx.de> diff --git a/core/comboot.inc b/core/comboot.inc index 59db7ec..d6f670c 100644 --- a/core/comboot.inc +++ b/core/comboot.inc @@ -723,13 +723,9 @@ comapi_idle: ; ; INT 22h AX=0014h Local boot ; -%if HAS_LOCALBOOT comapi_localboot: mov ax,P_DX jmp local_boot -%else

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

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 #

Signed-off-by: Paul Bolle <pebolle at tiscali.nl> --- doc/comboot.txt | 12 ++++++------ 1 files changed, 6 insertions(+), 6 deletions(-) diff --git a/doc/comboot.txt b/doc/comboot.txt index 4b4b880..04d5deb 100644 --- a/doc/comboot.txt +++ b/doc/comboot.txt @@ -986,27 +986,27 @@ AX=0024h [3.80] Cleanup, shuffle and boot, raw version ++++ 32-BIT ONLY API CALLS ++++ -void

Signed-off-by: Paul Bolle <pebolle at tiscali.nl> --- doc/comboot.txt | 12 ++++++------ 1 files changed, 6 insertions(+), 6 deletions(-) diff --git a/doc/comboot.txt b/doc/comboot.txt index 4b4b880..04d5deb 100644 --- a/doc/comboot.txt +++ b/doc/comboot.txt @@ -986,27 +986,27 @@ AX=0024h [3.80] Cleanup, shuffle and boot, raw version ++++ 32-BIT ONLY API CALLS ++++ -void

Dear Syslinux developers, I'd like to continue the discussion about this: http://www.syslinux.org/archives/2014-February/021659.html i.e. different directories for *.c32 files of BIOS, EFI32, and EFI64. I am wondering why we can not have *.c32 for the COMBOOT files of BIOS, *.e32 for the COMBOOT files of EFI32 *.e64 for the COMBOOT files of EFI64 As now the ldlinux file of syslinux 6.0x has,

gfxboot uses those three calls, but currently doesn't really handle returns from them. syslinux_boot_linux (lib/syslinux/load_linux.c) can return ("bail" label). syslinux_local_boot (lib/syslinux/localboot.c) has a comment which says "returns only on failure". The documentation for "Local boot" in doc/comboot.txt says "Does not return". Which is correct?

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 was just debugging why TFTP booting did not work any more on a system that had pxelinux.0 was updated. ?Since version 5.00, support for 16-bit COMBOOT modules has been dropped, and c32 modules switched from the COM32 object format to ELF.? Ugh. Well, updating the *.c32 files was enough to make the Linux discless thingy work again. BUT! The MirBSD bootloader actually took advantage of

On Thu, Dec 4, 2014 at 11:27 AM, Thorsten Glaser <t.glaser at tarent.de> wrote: > On Thu, 4 Dec 2014, Gene Cumm wrote: > >> Ady has an excellent point. Try the following instead: >> >> LABEL test >> MENU LABEL test >> COM32 pxechn.c32 >> APPEND pxebsd.0 > > Thanks, that works! How do I use that in the generic case? > The

On Thu, 4 Dec 2014, Gene Cumm wrote: > Ady has an excellent point. Try the following instead: > > LABEL test > MENU LABEL test > COM32 pxechn.c32 > APPEND pxebsd.0 Thanks, that works! How do I use that in the generic case? The ?pxebsd.0? file can be called as? ? PXE loader ? COMBOOT (16-bit) ? DOS .COM ? Multiboot (although it switches back to 16-bit mode

Hi Aaron, i know it is not an interactive menu - but in my 'config' file i call for a textfile to be displayed : DISPLAY menu.txt that contains all my labels. See the first part of my 'config' : label 0 LOCALBOOT 0 label 1 KERNEL memdisk/memdisk APPEND initrd=images/w2k/unatt.ima label 2 KERNEL memdisk/memdisk APPEND

Hi, I am trying to understand how to use the COM32 mechanism in syslinux 2.00pre8. It seems very interesting even though the comboot.doc docs are very difficult to read for me. Here is my problem: I gave a look to the hello.c example in the sample dir and I could not find anywhere what to do with the hello.c32 file produced through the Makefile. I tried putting it in a 2.00pre8 syslinux boot

On Thu, 2014-12-04 at 21:26 -0500, Gene Cumm wrote: > > Thanks, that works! How do I use that in the generic case? > > The ?pxebsd.0? file can be called as? > > > > ? PXE loader > > ? COMBOOT (16-bit) > > ? DOS .COM > > ? Multiboot (although it switches back to 16-bit mode immediately) > > ? from its own bootsector, if installed on disc (blocklist)

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

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 Does subject exist? Is it possible to get MAC address, video card, RAM and the storage of a harddrive by using comboot? And can some one help me? /Kenneth