similar to: menu.c32 is not a COM32R image

Hello, I have a simple shell script that I use to generate an iso installer depending on the release version that I want. The thing is that I extract isolinux and menu.c32 from the syslinux rpm of the latest redhat release. The reason I am doing it this way is because of the This is what does it: copymenu32() { # $ cat /local/kickstart/templates/os-updates.txt # RedHat-5.8|20120425

Hello ! I am completely new to syslinux. I followed this instruction manually: http://www.wonkity.com/~wblock/docs/html/pxe.html I am on debian and do not have syslinux installed, but using this debian 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

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, I just found this post: http://syslinux.zytor.com/archives/2005-September/005814.html ONTIMEOUT was broken in menu.c32, and you fixed it. But the fix broke support for LABEL references in ONTIMEOUT. I changed my "ONTIMEOUT local" to "ONTIMEOUT .localboot -1" and it works! Anoying is that I tried ONTIMEOUT LOCALBOOT -1 before. This failed, but after having a look at the

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 When I tried to use the menu.c32 from SYSLINUX 3.30-pre1, the simple menu have different background color than that in 3.20. 1. use the menu.c32 from SYSLINUX 3.30-pre1, the simple menu is: http://lfod.nchc.org.tw/stick/syslinux/syslinux_menu_3.30_pre1.jpg 2. use the menu.c32 from SYSLINUX 3.20, the simple menu is:

Fellow syslinux fans, I'm using syslinux on a boot floppy (I'll call this syslinux A) to invoke an etherboot image (zlilo style) which invokes a tagged NBI image from my DHCP/TFTP server. The tagged NBI image is created using mknbi-dos and also uses syslinux (I'll call this syslinux B), a linux kernel and an initrd file. It works perfectly if syslinux A has a basic .CFG, e.g.:

> On 8/4/17, Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > > > Thanks for the response. Yep, done. I downloaded from kernel.org > 6.04-pre1, and compiled it. I made certain only using those files. FWIW and just FTR, I suggested the pre-built binaries already included in the official archives. If I were to suggest compiling anew, I would had pointed to the

Well in those three days I did identify and correct the problem with using a number (0-9) as the hot key. The following is the section of code in menu.c32 responsible for displaying the menu entries: display_entry(const struct menu_entry *entry, const char *attrib, const char *hotattrib, int width) { const char *p = entry->displayname; while ( width ) { if ( *p ) { if (

Hi, Try running menu.c32 from Syslinux 4.06 under qemu -vga none without disabling console output, for example: SERIAL 0 SAY ls menu LABEL ls COM32 ls.c32 LABEL menu COM32 menu.c32 This invocation works well: $ qemu -hda extlinux.img -serial stdio But this fails after invoking "menu": $ qemu -hda extlinux.img -serial stdio -vga none Syslinux 5.xx and 6.xx does not exhibit this

On 8/5/17, Ady Ady via Syslinux <syslinux at zytor.com> wrote: > Since you are using only 2 menu entries, would you consider the > possibility of using the msg file(s) and the boot prompt, while > avoiding the use of (vesa)menu.c32 for this particular project? If you > do, there is room for improvements. > > Thanks for the info. Yes, I previously did not have a menu, for

> 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

Thanks very much for syslinux and pxelinux,they bring me many conveniences.I have problem in some computers.My english is very poor,so i submit in chinese and poor english.First I say sorry! ????pxelinux???sis900??????????? ????????default???????menu.c32??vesamenu.c32????? ???default???????DEFAULT memdisk c=638 h=2 s=18 floppy append initrd=netboot.zip???????????????????????? ???3com?boot image

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: #>

Hi, I am trying to use the Simple Menu system for SYSLINUX/ISOLINUX, but it fails to work. The menu apper, I can select menu entries, but pressing "ENTER" just takes me back to start. It seem like menu.c32 just reloads. Pressing Space does almost the same, exept the selected item is the one on the bottom instead of the top. By pressing ESC and getting back to command line, I am able

Hello, First, could you make a tar.gz instead of a tar.xz (at least on debian)? I compiled the syslinux-4.05+dfsg I would like to ask you if I shall copy the menu.elf + menu.c32 to the concerned directory? The menu.elf is needed or it shall be renamed as menu.c32 ? Shall ldlinux.sys be too coming from same file? my simple example of menu: default menu.c32 prompt 0 MENU TITLE Sample Menu

On 8/4/17, Ady Ady via Syslinux <syslinux at zytor.com> wrote: > >> Note, I am using syslinux from Ubuntu 16.04.2, presume that is 6.03. >> >> Regards, >> Barry > > Before investing time in replying to each different (unexpected) > behavior, I would suggest testing with *pre-built* binaries from > 6.04-pre1 downloaded from kernel.org (considering the

Hi, I've recently did some extensive testing with PXELinux and I must say it's great! I've tested it with several pc's and VMware vm's at home, this works flawlessly. However at my work, we only use MS Virtual PC 2007 and so on. I've started today to testimplement pxelinux into wds/ris, this seems to work but when I want to display a menu eg: default menu.c32, then

This is to report a bug with "menu.c32". I've found that this module does not behave correctly if the last menu item is disabled. syslinux.cfg ======================================== DEFAULT X1 UI menu.c32 # LABEL X1 MENU LABEL First item COM32 hdt.c32 # LABEL X2 MENU LABEL Second item MENU DISABLE ======================================== The last item is disabled , but

Hi, I'm attaching a patch to Syslinux dealing with a handful of issues that were preventing me from using the simple menu interface. Issues covered: * Enable "MENU ONERROR" as a keyword on par with "ONERROR". * Enable hidden menu entries to be used as ontimeout and onerror entries (probably the least estheticalla pleasing part, sorry about that.) * Make global

Hello, I am using a menu with the help of menu.c32 which looks like this on a serial console (HP ILO Virtual Serial Port): +----------------------------------------------------------+ | Main | ---------------------------------------------------------- | |