similar to: [PXELINUX] menu.c32/vesamenu.c32 and MS Virtual PC 2007 --> Hang/crash

----- Doorgestuurd bericht van dkbrig at gmail.com ----- Datum: Thu, 29 Jan 2009 11:16:06 -0600 Van: Danny <dkbrig at gmail.com> Onderwerp: upscode2.c Aan: adkorte-guest at alioth.debian.org Hi, I apologize if you are not the correct person, but I was wanting to submit a bug report for the upscode2.c driver but could not find a way to do that from the NUT website.

Hello everyone I'm new to using menu.c32 and vesamenu.c32. I have used the original method of using pxelinux menus. I've read the wiki page and it speaks of being able to create submenus by making one of my menu options reference to (vesa)menu.c32 as the kernel and append the config file. I'm not sure I'm doing it correctly it was a little over simplified. Any help would be

Hi, I've been trying a couple of day now, but I can't seem to figure it out. On www.etherboot.org, I found the example of configuring gPXE so that it mounts an iSCSI lun and then boot from CDROM so you are able to install on the LUN. But if I use gpxelinux.0 (latest release 3.73), with sanboot.c32 like this: label sanboot2008srv menu label ^[iscsi] Windows server 2008 kernel

I'm integrating DBAN (http://dban.sourceforge.net/) into our PXE boot menu system (using vesamenu.c32) but it just hangs when I'm using vesamenu.c32 and confusingly when I revert our menu system to using vesa.c32 it works ok. I've stripped out any extraneous configuration but it still seems to have the same problem. When I use this in pxelinux.cfg it boots into DBAN ok: default

Hi, UTF8 is a standard today. Nevertheless it seems to be impossible to display UTF8 characters in vesamenu.c32. Am I wrong? There is nothing about that in the docs. Are there plans to make vesamenu.c32 UTF8 capable or make syslinux capable e.g. for LC_ALL=de_DE.UTF8? Best regards, Uwe Galle

I'm currently building a tree-like boot menu for my network, using pxelinux and vesamenu.c32. I jump from one page to another with "kernel vesamenu.c32" and "append newmenu". However, at some points I'd like to use the classic interface, for example with a distribution install image (in order to have the exact same interface as on the CD). I tried loading pxelinux.0

Hi group, currently I try do make my own PXE bootscreen. There is one thing i dont like. When I use vesamenu.c32 there is always a table on the screen (I mean the border lines are visible) Is there any command i have to add to the default file that this border lines are unvisible ? Thanks in advance

hi list sorry my english is not perfect :( im using pxeboot with vesamenu.c32 in default file i load a backgroundpic (*.jpg) but the vesamenu border overlaps pieces of my background picture ^^ my question is an all coders from syslinux can you make a MENU command like topmargin MENU LABEL xxxx MENU WITH xx MENU MARGIN xx (from left) .... MENU TOPMARGIN xx (from top) <- new to

Hello. vesamenu.c32 can currently display a PNG image along the menu. But when the kernel is started, the image is lost. LILO supports bmp-retain option, where the bitmap graphic is retained when control is passed to the loaded kernel image; i.e., the screen is not blanked to alphanumeric mode before starting the kernel. Is it possible for vesamenu.c32 (or syslinux in general) to support

Hi, Maybe I am just not looking in the right spot but I can't figure out how to set a default menu in my isolinux.cfg. This is what it looks like: PROMPT 0 TIMEOUT 40 DEFAULT /boot/vesamenu.c32 LABEL cubez MENU LABEL Graphics mode (Compiz) - Experimental KERNEL /boot/vmlinuz APPEND vga=0x317 initrd=/boot/initrd.gz ramdisk_size=9999 root=/dev/ram0 rw chexpand=256 load=cubez

Hello, vesamenu.c32 from syslinux-3.75.tar.bz2 is broken in my tests with: - qemu 0.9.1 -cdrom iso_image - qemu 0.9.1 -cdrom iso_image -std-vga - virtualbox 2.2.0 (Sun version) It blocks right after showing the copyright notice. I've since compiled the following versions in my machine, running Fedora 10: - syslinux-3.63 - syslinux-3.72 - syslinux-3.73 - syslinux-3.75-143-g080bf56 I did a

I have a handful of machines with older S3 Virge video onboard. They do not show the vesa menu and instead appear to revert to the older menu.c32. Vesamenu.c32 works fine with every other machine I've tried. I thought this video chipset was Vesa compliant... When I run the included vesainfo.c32 many different video modes are returned. Perhaps there's a readme I've overlooked

Hello I'm using PXELinux with vesamenu.c32 to load a custom knoppix image I made and to allow access to the WDS menu. The problem is that the PXElinux loads the menu automatically (unlike WDS which asks the user to press F12 before loading the menu) and I want it to load only if the user presses F12 in 5 seconds. So I tried using the hidden function of the menu with the timeout option

I've recently started the effort of porting my "simple.c" menu system to use vesamenu.c32 instead. I really like the graphical interface, and the READMEs have been very helpful. What I am curious about is whether or not there is an option for adding entry separators similar to the add_sep(); option which is available in the "simple.c" menu system? Right now I have set up

All, I've been setting up an etherboot-PXE-syslinux environment for booting a number of HP/Compaq servers. Today I was playing around with using vesamenu and background pictures, and I noticed a weird behaviour when I used vesamenu.c32 with and without a timeout. I will obviously be needing a timeout for unattended operation, but whilst I was testing I had it disabled most of the time.

I was having a display problem with memtest86 and dos via a memdisk image not displaying properly when launched using vesamenu.c32 and using a PNG background image. Instead of proper text output the display mode is not changed and the existing menu image is corrupted by the outputted text. This seems to be similar or identical to a problem describe in a previous mailing:

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

This appears to be a bug: In case the TEXT HELP for a menu entry extends over several lines and you manually set MENU HELPMSGROW and MENU HELPMSGENDROW, the last line of the TEXT HELP will not be visible. Concrete example: MENU HELPMSGROW 24 MENU HELPMSGENDROW 26 LABEL bug TEXT HELP This is the first line, it is visible :D This is the second line, it is hidden :( ENDTEXT MENU LABEL Bug KERNEL

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I have done some additional testing, and gotten it a bit close to what I was looking for. I had to modify the cat.c to eliminate the printing of the arguments and file name, and added a Press Enter to return menu line. With the below isolinux.cfg the options do display the files, and pressing enter than returns to the vesamenu. DEFAULT

> Hello, > > I'm experiencing an issue where if I use vesamenu.c32 with PXELINUX 6.03 when network booting a virtual machine hosted on VMware ESXi 6.0, it hangs (the version message is printed and then nothing - the VM has to be powered off and back on again). > > This happens no matter if I choose the E1000 network interface or the VMXNET3 network interface when creating the