search for: com32r

...n box as a tftp server. I had to modify the instructions given by the installation above. I downloaded the 6.02 version and copied the files to the tftp root. I am using dnsmasq as a tftp server and the client is served with the image, but it's getting no menu. I got first: menu.c32 not a COM32R image. I learned to press the TAB key and I see the entries, I gave for this box. Then I selected the "reboot" entry and got a similar error: reboot.c32: not a COM32R image. I found no exact configuration example and I am now really very confused, because I even connot differentiate...

Hi there, first, thanks a lot for syslinux! I'm aware that one can't mix syslinux 4's MBR + ldlinux.sys with syslinux 6's COM32R modules. Fair enough. Now, I need to know how strong this "versions *must* match" requirement is when dealing with different versions of syslinux 6.x. E.g. * MBR and ldlinux.sys installed by syslinux 6.03-pre1 * all *.c32 modules installed by 6.03-pre14 Has this a chance to work? O...

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

I have seen this happening because the versions of the menu.c32 module and the installed syslinux do not match.

...ecked menu.c32 checksum (i checked isolinux.bin's as well, but it seems its checksum is always changing after mkisofs), isolinux is going through, all were good. I'm using syslinux-4.02-8.el6.x86_64.rpm. Today when I was about to rebuild a server, I'm getting the "menu.c32: not a COM32R image" message. I'm pretty sure nothing has changed (syslinux rpm, the script), but I'm not sure where to begin troubleshooting anymore. Can anyone give me a clue? regards, Marc

...we're going to have a very hard time making Syslinux 4.00 be the full-featured everything-in-C release I had hoped for, or perhaps more specifically, that it is justifiable to sit on the current filesystems-in-C code waiting for the rest. That would probably mean productizing the transitional COM32R module format, unless a better solution for memory management can be found. Looking forward, I have experimented with using lwIP for PXELINUX. The good news is that the performance is *very* good -- I have reliably pulled about 250 Mbps over a local network, with peaks up to 600 Mbps. The downsid...

> Hi there, > > first, thanks a lot for syslinux! > > I'm aware that one can't mix syslinux 4's MBR + ldlinux.sys with > syslinux 6's COM32R modules. Fair enough. Now, I need to know how > strong this "versions *must* match" requirement is when dealing with > different versions of syslinux 6.x. E.g. > > * MBR and ldlinux.sys installed by syslinux 6.03-pre1 > * all *.c32 modules installed by 6.03-pre14 >...

...ot GUI. Thus, hang. (and, relying on localboot 0x00/0x80 instead of CHAIN.C32). Trying with 3MB or more seemed to work just fine * is there a working version of memdisk.c32 [http://reboot.pro/14468/] ? COM32 modules seem to be version-dependant and trying this with 4.05 ended up with "not a COM32R image" so I guess it's written for 4.04. * How's Syslinux influencing gate A20? And MEMDISK? They both seem to result in different A20 access methods being displayed by various memory managers under FreeDOS. One of them actually manages to crash unfortunately. My apologies for the...

...text section in hello.c32. - With the starting address, I can reliably pass to gdb the correct starting address of .text section, so it can jump to the correct code when connecting to QEMU with a gdb stub. The only remaining problem is how to reliably find out the starting address of the first COM32R module, so I don't have to manually insert hello.c32 every time I build a different syslinux version. Any idea is highly appreciated, thanks. > Care to elaborate on what you're attempting to debug? Currently, I'm trying to debug a module that must run on a BIOS environment, bo...

While playing with the current master of Syslinux, I figured out two bugs I'd like to share with you. 1- Missing menu entires If you consider a file with the following entries, only the first item appears label mga32 kernel anything label mga64 kernel anything Looks like the number at the end of the label is giving some headaches to gfxboot. If I do rename this two entries by

Hi list, I ran a syslinux drive on a QEMU machine with a gdbstub opened. I tried the simplest modules: the hello.c in com32/samples/ directory, which is compiled into hello.c32 in bios/com32/samples/. I already compiled the module with debug info attached via -g option added to CFLAGS in the Makefile. However, the problem is that the generated module is a shared dynamic module, which only

...isolinux failing to boot a kernel whenever I navigate and trigger the menu via serial console. My test machine is a DL585 G2, with iLO2. Navigating and booting the kernels off of the video console works 100% of the time. With the serial connection however, I _sometimes_ get a "menu.c32: not a COM32R image" error. Sometime it works fine. I suspect the serial connection is sending extra characters. I tried running wireshark from my local pc, enabled telnet on the iLO2 GUI, and did some packet captures. However I don't have an idea of how it looks like when there are no extra characters...

xe vm-start vm=debian Your license has expired. Please contact your support representative. Network and Management Interface XCP 0.5.900-36486c I was seriously under the impression we fixed this, now all my images are offline is there any way to fix this without reinstalling everything ? _______________________________________________ Xen-users mailing list

...in of=/dev/sda extlinux --install /boot/extlinux If I then reboot the system, it is able to boot into either Fedora 19 or Fedora 21 without any problems. It is true that I do get some minor complaints: SYSLINUX 4.05 2011-12-09 Copyright (C) 1994-2011 H. Peter Anvin et al menu.c32: not a COM32R image boot: But I can select the desired label from the "boot:" prompt, and now it boots successfully into Fedora 21. > The behavior you are describing "sounds" as if some version mismatch between the > bootloader file and some c32 module might be going on, although...

...> However, the problem is that the generated module is a shared dynamic module, which only contains relative address. Because of this, the generated debug info is also wrong because the actual addresses are absolute addresses and the debug info must match them. SYSLINUX v4.00 made it dynamic. COM32R means relocatable. I'd consider either using a breakpoint then, if gdb allows, realign to the new address, OR just use printf()/dprintf() calls as necessary. dprintf() use would require a SYSLINUX core with such enabled and a real serial port and probably only be applicable for BIOS. Care to...

Hello, I'm using iPXE to chain to menu.c32, here is the boot script: #!ipxe dhcp chain http://my-site/menu.c32 http://my-site/boot.php After ipxe promote "http://my-site/menu.c32...... ok", the machine hangs. Then I try to figure out where it does stop. First I put a printf() statement in In syslinux/com32/menu/menumain.c:main:, right after start_console(), then boot

Hi Everyone, This question might be a long shot, but is it possible to mix and match com32 programs written against Syslinux 3 with com32 programs written against Syslinux 4 without recompiling. We are trying to have our com32 programs run with different versions of Syslinux without modification. Appreciate any advice, thanks in advance.

I'm using LiveUSB-Creator to create a bootable USB drive from CentOS-6.0-i386-netinstall.iso, and it gives me an error at startup: vesamenu.c32: Not a COM32R image I can hit tab and select "linux" and then it loads vmlinux and the initrd, says "Ready", and then just hangs. I'm not sure what's supposed to happen next. "vesa" and "rescue" do the same thing. The error message above apparently is caused by...

...t; If I then reboot the system, it is able to boot into either Fedora 19 or > > Fedora 21 without any problems. It is true that I do get some minor > > complaints: > > > > SYSLINUX 4.05 2011-12-09 Copyright (C) 1994-2011 H. Peter Anvin et al > > menu.c32: not a COM32R image > > boot: > > The reason being a mismatch version between the c32 modules and the version of the > bootloader. Yes, of course, but that's not a significant problem. The system still boots. > > I don't think it's a mismatch issue. I have followed the...