similar to: ONTIMEOUT LOCALBOOT -1 and menu.c32 -- Solution: "ONTIMEOUT .localboot -1" works!

Hi, I am having some problem with LOCALBOOT and menu.c32 This is my isolinux.cfg: ------------------------------------------- default menu.c32 timeout 50 prompt 0 ontimeout local menu title "TITLE" label livecd menu default manu label "LiveCD" kernel gentoo append initrd=initrd.igz root=/dev/ram0 init=/linuxrc looptype=squashfs loop=/ livecd.squashfs

With windows, if your "virtual" floppy is drive B:, then windows will treat it specially. It will basically copy the contents into memory from real mode using int13h, knowing that it will not be able to access the device after it switches to protected mode. I asked a few days ago about support for making a memdisk image behave as drive B:, but got no answer. :-( We have our

Maybe I missed something here. What I want to happen is PXE boot on a timeout will boot to the hard drive. But, what happens is my comboot menu, which is default, loads right away and the ontimeout only happens when I escape out of the menu. My pxelinux.cfg/default: default menu timeout 100 ontimeout localboot # The Main Menu label menu kernel mainmenu.com append keeppxe #

I just started to play with syslinux 3.11 and have some problems with the configuration. I want to implement following: wait 5 seconds till the users chooses the right label. if nothing is done for 5 seconds it should boot from next boot device specified by the BIOS. I configured syslinux like that: default menu.c32 prompt 0 timeout 50 ONTIMEOUT localboot totaltimeout 200 display boot.msg MENU

Hi, It is becoming a bad habit for big OEM vendors to sell computers & servers without floppy drives. Unfortunatly both Windows and Linux (RedHat) need a floppy drive to load storage drivers etc. during installation. This is what I was thinking: Use ISOLINUX and MEMDISK to load a floppy image of a driver disk into memory as a viritual floppy drive "A:"/"/dev/fda" And then

Hi, when trying to boot from local disk with PXELINUX v 3.09, the systems just beeps and hangs. The last message appearing on the screen is "Booting from local disk..." Running PXELINUX v 3.07 works for me (but I'd like to use v.3.09 because of the increased max command line size. The BIOS boot priority configuration is PXE/Disk/Disabled. Grub is installed in the MBR of the

> ONTIMEOUT is meant to be a label I think that wrong . :) Actually, I just looked at my config and I have TIMEOUT .localboot -1 -----Original Message----- From: Ardill, Robert (DTEI) Sent: Thursday, 31 August 2006 10:05 AM To: 'Greg_Chu at Wendys.com' Cc: 'SYSLINUX at zytor.com' Subject: RE: [syslinux] Time out would not boot from local drive ONTIMEOUT is meant to be a

Hi. I'm trying to get around the problem of an overloaded tftp server causing a pxelinux client hanging at the boot: prompt, waiting for input (no one will input anything to it). The server is OK enough to give the pxebootloader but not the config file, as in this thread: http://syslinux.zytor.com/archives/2004-June/003662.html So, in that case, I guess setting TIMEOUT to some

> On 9/23/2015 12:14 AM, Ady via Syslinux wrote: > > > About your customers' setup... > > Are they using official binaries downloaded from kernel.org? > > Yes. Stock versions, no local modifications. > > > Which exact version of Syslinux are they using? > > I've tried versions 3.86, 4.07, 6.01, 6.03. > We can only generally use 4.07 or less

Hi, we use PXELINUX in our product to show a boot menu on client computers, with options like "Boot from local hard disk", "Install Windows", etc. Unfortunately, a lot of computers seem to have broken BIOSes and won't boot with the LOCALBOOT command, and need to be booted with chain.c32 instead. We also have encountered some computers where it works only the other way -

I've finally gotten around to playing with the advanced menu, though the complex example is definitely still beyond me. I'm trying to figure out a few basics from it, such as the tab key for line editing (don't know what I've done wrong here since it seems like I copied that part right) and the timeout. It looks to me like the only ontimeout implemented so far is an option to not

On Mon, Oct 26, 2015 at 2:09 PM, Alan Sparks via Syslinux <syslinux at zytor.com> wrote: > I'm still trying fruitlessly to get some sort of local disk boot from > syslinux EFI to work... using the 6.03 modules. Tried various > combinations of configurations on Gene's test binaries. > > For reference this is on different models of HP Proliant Gen-9 systems > with

On Mon, Oct 26, 2015 at 02:03:08PM -0600, Alan Sparks via Syslinux wrote: > On 10/26/2015 1:46 PM, Geert Stappers via Syslinux wrote: > > On Mon, Oct 26, 2015 at 12:09:40PM -0600, Alan Sparks via Syslinux wrote: > >> I'm still trying fruitlessly to get some sort of local disk boot from > >> syslinux EFI to work... using the 6.03 modules. Tried various > >>

Hi, We have been testing the localboot functionality today and it could be useful if localboot was a com32 module rather than a configuration directive so that one can use it on the boot prompt, rather than require a menu entry/alias at all times. A more userfriendly localboot.c32 could do this and allow eg for friendly device-names. localboot next localboot floppy0 localboot hdd0 or

Summary ======= I am having trouble with com32 API call AX=0014h [3.10] Local boot [PXELINUX, ISOLINUX] Input: AX 0014h DX Local boot parameter Output: Does not return My observation is that is returning from the call and is not localbooting the system. Detail ====== I am using a com32 program to configure some hardware before I boot from the local

Our site has many Dell OptiPlex 790s, all of which are unable to use the 'localboot' PXELINUX option as they either hang at 'Booting from local disk...' or immediately reboot depending on which SYSLINUX version is used. Many people have suggested using chain.c32 to chain load the local disk as a workaround, but this causes problems with Windows 7 BitLocker as it detects the chain

On 10/26/2015 1:46 PM, Geert Stappers via Syslinux wrote: > On Mon, Oct 26, 2015 at 12:09:40PM -0600, Alan Sparks via Syslinux wrote: >> I'm still trying fruitlessly to get some sort of local disk boot from >> syslinux EFI to work... using the 6.03 modules. Tried various >> combinations of configurations on Gene's test binaries. > > The test binariers Gene

A bug in command localboot was introduced in version 6.03. This bug was created because of inserting memsets in core/localboot.c. The third memset before /* Read one sector */ clears the field ireg.edx, which was assigned earlier and is required for subsequent __intcall0x13. So localboot type works as localboot 0. I think, this third memset in core/localboot.c is useless and excessive.

i am trying to use chain.c32 with isolinux to load WinPE/BartPE/etc and I can not get it to work. I have tried with the simple.c32, and just from the isolinux prompt. I have tried 3.32-pre6, 3.20, and jumped back and tried 3.08. All configurations fail with 'Cannot read Master Boot Record'. The boot sectors are known to be good, and are known to work with chain.c32 with pxelinux.

I'm bringing back an old thread, but I'm still having problem with this: http://etherboot.org/pipermail/gpxe/2010-March/000571.html The summary of that thread is that with gpxelinux.0, on some computers the command LOCALBOOT 0 will hang the computer. Around the same time as the original thread, there was a patch to add localboot -1. Also in the original thread, it was proposed to use