similar to: com32

This module is able to power off a system via APM. It replaces the poweroff COMBOOT module. Signed-off-by: Sebastian Herbszt <herbszt at gmx.de> --- com32/modules/Makefile | 2 +- com32/modules/poweroff.c | 88 ++++++++++++++++++++++++++++++++++++++++++++++ 2 files changed, 89 insertions(+), 1 deletions(-) create mode 100644 com32/modules/poweroff.c diff --git

Hi there, Is there any updated document on COM32 format? http://www.syslinux.org/doc/comboot.txt Is there any updated memory map? http://www.syslinux.org/wiki/index.php/Memory_Map_(General) is there any updated info on Dynamic Module Loading Using the ELF Format? http://www.syslinux.org/wiki/index.php/GSoC2008_Stefan Thanks, Best, Patrick

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.

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

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,

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

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 *, 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

Hi, I've checked the archives for my issue, and while there is relevant discussion, the problem the original poster was asking about didn't seem to have been resolved then either (~2 years ago). At any rate, basically what I'm trying to do is send (possibly receive) UDP packets via the PXE stack using the com32 API (using version 3.11 of syslinux). I have followed both the comboot

Hi all, I used syslinux to load linux on DiskOnChip in PC104 for one embbeded project suceefully for several months. But due to power lost sometime the image is corrupted. I want to develop a COM32 util to check CRC for the images and load the good ones. I read in the comboot.doc that com32 can use read file SYSLINUX API call to read a file, and the file must below 64K limit. But the image files

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)

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

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:

For several years now, I've been using Syslinux/Isolinux to load boot systems and love it. At times, I've messed up making a config file or forgotten the name of a file on the CD (or USB flash drive) and didn't want to take the time to load the CD into another machine or boot a DOS or Linux OS to search. The ability to browse the CD/USB drive would prove beneficial in these

Hello, In case anyone is interested, here are the source code for comboot and com32 modules for powering down a computer using APM. I started work on the ACPI version of it, but it will take some time to parse the spec. Regards, Luciano Rocha -- lfr 0/0 -------------- next part -------------- ; **************************************************************************** ; ; apmoff.asm ; ; A

Hello, I'm going to prepare a multiboot computer laboratory for students. I need to have a central server to order which system should be booted (systems are on local hd). I hope it can be done with pxelinux, but I met a problem during tests. At this moment I have one system (linux) on a disk an lilo in MBR. PXE booting from network looks fine, but I can't boot locally: <copying

Hello, I am writing a simple module for measuring boot time. I would like to get a timestamp when syslinux is run and then pass it as kernel parameter and work with the timestamp later.. It seems that POXIS time.h functions are not implemented yet(?) in COMBOOT. I was reading this http://www.linuxfordevices.com/c/a/Linux-For-Devices-Articles/Benchmarking-boot-latency-on-x86/ earlier today

From: Gene Cumm <gene.cumm at gmail.com> COM32: Improve opendir() to deal with no '/' at end of string Signed-off-by: Gene Cumm <gene.cumm at gmail.com> --- Originally, this was going to be 3 patches but I ended up doing a little more. Currently, the COMBOOT call required a '/' to recognize that you're searching for a directory. This checks and automatically

I have a small problem with my COM32 image. It is more related to how the COM32 images get their arguments. Here are the relavent parts of my isolinux.cfg ----- # default image = defimg default defimg # Boot automatically after 5 seconds timeout 50 # By default auto select image. If no autoselect list # found, then boot into prep label defimg kernel readker.c32 append prep