similar to: PXELinux 2.00 doesn't timeout on one of my systems

Hi Peter, we are looking at PXELinux to use it for reinstalling PC's. PXELinux works fine, is such way that the option "LOCALBOOT" behaves as expected in version 1.76. v2.00 the "LOCALBOOT 0" doesn't work on some hardware (systems like Compaq EVO, Compaq EN SFF, in other words, systems that have the Intel chip on the system board). The prompt shows "leaving

Howdy. We've got a couple IBM x440 (Summit) 8-way Xeon systems that I've been trying to get netbooting for a while. Since we use Kickstart and SystemImager to load OSes on our systems, a system has to be able to netboot before it can be made available to folks for project use. System BIOS is the current one, v1.08. They're booting from a planar BroadCom Tigon3 adapter. BIOS

Okay - all I'm trying to do here is smbclient from my Slackware Linux box (SNUFFY) to my Windows NT 4.0 SP3 Server (BURT). Burt is a BDC and is participating in WINS via my internal WINS Server. The Scope ID for the WINS Server is HARVESTWEB - but I'm not sure how to set that in SAMBA. My password server (I assume) should be my PDC with is GROVER (146.115.109.8) Eventually, I want to be

Hi, The menu timeout isn't cancelled but restarted when there's only a single item in the menu and I try to move the selection. The selection flashes but of course does not move. Tested with pxelinux under QEMU: $ qemu -net nic -boot n -net user,tftp=tftpboot,bootfile=/pxelinux.0 pxelinux.cfg/default: UI menu.c32 TIMEOUT 100 LABEL single KERNEL blah Adding another menu item

Hi guys! I tried to boot memtest86+ v4.2 (renamed memtest.bin to memtest), and i have issues to boot it with pxelinux 5.x and greater.Pxelinux 4.06 works fine both memtest 4.1 and 4.2. With version 6.00 no error message caught, only writes out dots. Any keypress does a reboot.With version 5.01 the error message is the follow:Loading images/memtest/memtest86... okBooting kernel failed: Bad file

We are having many successes with Asterisk and starting to get the hang of it. But, I am still having problems getting my Budgetone BT100 (firmware 1.0.4.50) to work fully. I can receive calls, but cannot make them. We have the latest version of Asterisk, Fedora Core 3, Digium TDM400P with one FXO and one FXS card configured and working well. We have a PSTN line going into the Digium card,

On Fri, 28 Jun, at 08:13:03AM, N?meth P?ter wrote: > Hi guys! > I tried to boot memtest86+ v4.2 (renamed memtest.bin to memtest), and > i have issues to boot it with pxelinux 5.x and greater.Pxelinux 4.06 > works fine both memtest 4.1 and 4.2. > With version 6.00 no error message caught, only writes out dots. Any > keypress does a reboot.With version 5.01 the error message is the

> Hello, > > FYI. This problem looks similar to the problem I reported in Februari > http://www.syslinux.org/archives/2013-February/019517.html > > Kind regards, > Wim. > > On 06/28/2013 10:02 AM, Matt Fleming wrote: > > On Fri, 28 Jun, at 08:13:03AM, N?meth P?ter wrote: > >> Hi guys! > >> I tried to boot memtest86+ v4.2 (renamed memtest.bin to

Hi, I am trying the simple menu passswd in syslinux 3.11, and it seems that if I set the timeout option, the menu passwd is ignored. For example: ----------- default menu.c32 timeout 70 prompt 0 noescape 1 MENU MARGIN 5 MENU MASTER PASSWD $4$x$03NXHMe7QS0Ukxlkyh684LkWdqY$ label local MENU DEFAULT # MENU HIDE MENU LABEL Local operating system (if available) MENU PASSWD localboot 0 label

Hello, FYI. This problem looks similar to the problem I reported in Februari http://www.syslinux.org/archives/2013-February/019517.html Kind regards, Wim. On 06/28/2013 10:02 AM, Matt Fleming wrote: > On Fri, 28 Jun, at 08:13:03AM, N?meth P?ter wrote: >> Hi guys! >> I tried to boot memtest86+ v4.2 (renamed memtest.bin to memtest), and >> i have issues to boot it with

> > Alright... I have released SYSLINUX 1.76-pre1 and 2.00-pre7 with this > > workaround included; please test and I'll promote 1.76-pre1 to 1.76 if > > it works. > > I can test only in couple of days... I.e. on Toshiba... it does. a.

Additional information: I was tried it with 2 virtualbox (version 4.2.14r86644).1rst: debian weezy with isc-dhcp-server, pxelinux5.01, pxelinux 6.00, tftp-hpa2nd: empty virtualbox booting from virtual network card. So memtest 4.1 and 4.2 worked with pxelinux 4.06 Peter > Date: Fri, 28 Jun 2013 09:02:30 +0100 > From: matt at console-pimps.org > To: coolpet80 at hotmail.com > CC:

> a little more digging into this and it appears it''s that different > browsers > handle the keypress at different times (from what I can see, there are 3 > events triggered when you press a key, keydown, keypress, and keyup). I > changed line 1531 to ''keypress'' from keydown and on all of the browsers I > tested (safari, opera, konqueror) it appeared to

Hi all, we are writing a cross browser Javascript control that enhances the HTML text input element in order to accept only digits (more or less). Supposing that ''domText'' is the DOM element corresponding to the HTML text input, we wrote the following: Event.observe(domText, "keypress", this.onKeyPress.bindAsEventListener(this)); where this.onKeyPress =

Some kernel images use the Linux kernel boot protocol and header structure, but do not actually have any protected-mode code. For instance, grub's 1024-byte lnxboot.img consists of 1024 real-mode bytes and 0 protected-mode bytes; you can concatenate it with a full grub core.img to produce a self-contained bootable kernel, but you can also use it standalone as the kernel with the core.img

Hi all, hopefully someone in the list will be able to advise me on what to do with a problem that's bugging me. I have a number of machines that simply have problems understanding "localboot 0". My configuration is such that after the machines happily remotely install via PXE+kickstart the "default" file on the PXE server will resort to telling the client to boot from

Hello, We're using the PXELINUX to boot remote kickstart and Linux rescue images. Recently we got some new hardware (Compaq DL360) which required me to upgrade from PXELINNUX 1.75 to 2.02. Everything works fine on the new hardware, but the "localboot 0" option now just hangs on some of our older boxes. Specifically, our "Tyan Thunder 2510" motherboards with integrated

On reboot, one out of 10 times, reboot (from hardware initialization) stops. Referring to this portion of the dmesg -v output, of a successful boot, where i have marked ">>>HERE<<<" is where the boot freezes on an unsuccessful boot. This is a constnat problem, on 6.2 as well as 6.3 unchanged. ata0-master: pio=PIO4 wdma=WDMA2 udma=UDMA33 cable=40 wire acd0: setting

I have problems getting the TIMEOUT value work the same way LILO/GRUB does it.. ie it should wait until the timeout and then use the default value. However, it goes straight for the default value without waiting a single second (and a TIMEOUT value of 500 should mean 50 seconds, as it counts in 1/10th of a second, right?) SYSLINUX (isolinux) 2.00 ----8<------8<---- SERIAL 0 38400 TIMEOUT

Hello, I'm reporting a bug, see attached syslinux.cfg I'm using submenu entries to emulate checkbox inputs. The idea is simple, there are submenus generated for all possible cases, and each Enter keypress loads appropriate submenu section. The logic of the menu is correct. Just syslinux has some bug. It doesn't set MENU DEFAULT properly for all submenus. If your first Enter keypress