similar to: DBAN and vesamenu.c32

Displaying 20 results from an estimated 5000 matches similar to: "DBAN and vesamenu.c32"

2016 Jun 15
2
PXELINUX 6.03 / vesamenu.c32 hang
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 VM. The same problem
2016 Jun 16
2
PXELINUX 6.03 / vesamenu.c32 hang
Hello, Thanks very much for your suggestions. I have double checked that all .c32 files are from the same version of syslinux. What I don't know - I only put those .c32 files I have in there on the basis of trial and error - is what .c32 files are actually needed for menu.c32 and/or vesamenu.c32. I thought perhaps there might be a .c32 file missing that I needed to put in there (though
2016 Jun 15
0
PXELINUX 6.03 / vesamenu.c32 hang
> 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
2016 Jun 16
0
PXELINUX 6.03 / vesamenu.c32 hang
I've just tried 4.07 and that has the same results. I should note that I appear to be in error about things working OK with menu.c32 as opposed to vesamenu.c32 - I do indeed see the menu (which with vesamenu.c32 it does not get that far), but when I attempt to choose the Windows Deployment Services option, it hangs. Thanks, Dan Jackson (Lead ITServices Technician). -----Original
2010 Mar 17
1
USB Thumbdrive + dos ghost boot image + drive too small = confusion
I will really hate myself if this has already been solved, i searched the archives but didn't really find anything pertaining to it. I have a 2.88mb dos boot floppy image, with ghost.exe, dos nic drivers, and dos system files. It works fine when burnt to a cd. As for the thumbdrive when trying to configure this hpghost.ima file to run from my syslinux.cfg menu, it works and boots up fine but
2016 Jun 16
2
PXELINUX 6.03 / vesamenu.c32 hang
Just tested with the latest VirtualBox and that works OK, so it's definitely something specific to ESXi 6.0.0 (it worked previously under 5.x ESXi versions). Thanks, Dan Jackson (Lead ITServices Technician). -----Original Message----- From: Syslinux [mailto:syslinux-bounces at zytor.com] On Behalf Of Jackson, Dan via Syslinux Sent: 16 June 2016 09:27 To: 'syslinux at zytor.com'
2008 Oct 08
2
default menu option using vesamenu.c32
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
2007 Jan 25
4
vesamenu.c32 and cat.c32
-----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
2010 Aug 27
3
slightly OT: dban
I'm trying to nuke a Dell Optiplex GX620. I've got a perfectly good dban 1.0.4 that I've used a bunch of times... but on this machine, it says starting, then dies, saying "dban has finished with non-fatal errors. Check the log for more information" It never gets to the interactive menu. Now that I've disabled the non-existant floppy drive, at least it does say "to
2012 Sep 23
2
any plans for UTF8 in vesamenu.c32?
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
2006 Oct 30
2
Going back to classic menu from vesamenu.c32
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
2019 Sep 29
3
vesamenu.c32 and EFI
Hello! I've been attempting to add EFI support to a linux live distro (slax), it's built on a syslinux bootloader. I can get EFI to work using menu.c32 on syslinux 6.03; however ideally we'd like the VESA menu as well. When we use the vesamenu.c32 and libcom32.c32 from 6.03 we end up with a blank screen and the machine seems to hang. I've tried adding MENU RESOLUTION based on
2007 May 12
1
vesamenu.c32 new command
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
2007 Aug 31
1
vesamenu.c32 retain image
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
2007 Sep 02
2
submenu using vesamenu.c32 and menu.c32
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
2011 Mar 23
2
Problems with recompiling vesamenu.c32
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
2009 Apr 29
3
Strange behaviour when using vesamenu.c32 and PXELinux
Hello, I was wondering if anyone had any ideas and perhaps solutions around an error i've been experiencing when using vesamenu.c32 (and the other non-vesa menu too). I have tried three different versions (the latest three) of pxelinux and the other files. The problem exists in all of them. My setup is pretty simple, filename defined in dhcpd, boot up from pxe, starts requesting configs, and
2009 Sep 02
3
Question about PXE and vesamenu.c32
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
2006 Sep 28
2
S3 Virge DX and vesamenu.c32
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
2009 Apr 24
1
vesamenu.c32 broken? blame F10?
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