similar to: SYSLINUX 4.04 problems

Hello all, I have a boot server (running Debian Lenny x64) with a number of bootable options already configured (freedos, memtest, sysresccd etc). What I am struggling to do now is add Ubuntu and Debian netinst images so that I can boot from the network and have all the boot options available as if I was using a CD-ROM. The problem is that (as far as I can tell) the Ubuntu and Debian

If there is anything that you think should have been in Syslinux 4.04 which isn't there please holler now. -hpa -- H. Peter Anvin, Intel Open Source Technology Center I work for Intel. I don't speak on their behalf.

Hello. I've been testing pxelinux.0 (4.04-pre14) on some laptops: - HP EliteBook 6930P with BIOS F.18. - HP EliteBook 8440P with BIOS F.06. - Dell Latitude E4310 with BIOS A06. When booting pxelinux.0, the machines first display some random letters in different colors and then reboot. We've been using 4.02 for some time without problems. I've tested 4.03 too and it seems to work.

The syslinux-4.0.04-pre11 and pre10 have 20MB tar.sign files that other versions don't, and has dates for Jan 01 1970. It appears these are the uncompressed tar files rather than a signature for the file? ftp://ftp.kernel.org/pub/linux/boot/syslinux/Testing/syslinux-4.04-pre1 1.tar.sign One other note. Last time I checked, it was still using 2010 as the latest date in the

1. \ at end of lines (in pxelinux.cfg/default, etc) causing/allowing line-wrap ? for those of us who prefer 80 column screens, and 1 item per line. 2. label-specific APPEND adds onto global APPEND ( currently replaces it IIUC ) maybe this needs a separate keyword ADDAPPEND (255 char limit still applies im sure) 3. strip trailing # comments ( I havent verified that it

I am hoping for some advice regarding another index problem. The code below is intended to assign a value of 'V' if values on certain variables are >= 1, assign a value of 'N' if values on certain variables are >= 1 on other variables and assign a 'O' if values on any variable which have a value <= 0. The outcome of this code is to assign a single

> > Both sticks show very unusual factors for heads and sectors > > which are hardly intentional. If BIOS gets confused like fdisk, > > then the failure to find files is quite plausible. > > > > ------------------------------------------------------------- > > > > Could you please exercise what is described for Linux in > >

After way too long, a new production release of Syslinux is finally available. Syslinux 4.04 is primarily a bug fix release, but with some new features. Changes in 4.04: * PXELINUX: Fix handling of unqualified DNS names. * PXELINUX: Fix timer bug when PXELINUX might be unloaded (Gene Cumm). * core/writedec.inc: Fix duplicate declaration and overflow

I thougt somebody might like to know - I got a fresh copy of 4.04 from http://www.kernel.org/ - when building on a 32bit system, the build fails at first. I had to do a "make spotless" to get a successful build. make[2]: Entering directory `/home/per/workspace/syslinux-4.04/diag/geodsp' ./mk-lba-img lba.img ./mk-lba-img: ./mk-lba-img: cannot execute binary file make[2]: ***

I've been working with Matt Burgess here on this problem, and have found the following: syslinux 3.08-pre10 ? broken >>> config.inc:max_cmd_len=255 syslinux 3.08-pre11 ? works >>> config.inc:max_cmd_len=1023 syslinux 3.08 ? works >>> config.inc:max_cmd_len=1023 syslinux 3.09-pre1 ? works >>> config.inc:max_cmd_len=1023 syslinux 3.09-pre2 ? broken

The BIOS on my laptop does not support booting from USB. I would like to be able to have my Windows XP on a partition on a USB disk drive and be able to run from the USB disk using perhaps a CD or floppy to bootstrap the system. My questions: 1). Is there a way to use syslinux and friends to do this? 2). If not, is there some other boot loader that may work? 3). Is there any hope at all?

I tried moving up to 4.04 this weekend - seemed to work fine, except that the keyboard didn't work (for selecting what to boot). I went back to 3.86 instead, which worked fine. Anything special about 4.04 in this respect? /Per Jessen, Z?rich

Hallo, syslinux, I've just tried to compile syslinux 4.04 for slackware - it stopped when it tried to execute Entering directory `/path/to/diag/geodsp' ./mk-lba-img lba.img "strace" shows execve("./mk-lba-img", ["./mk-lba-img", "lba.img"], [/* 49 vars */]) = - 1 ENOEXEC (Exec format error) dup(2) = 3

I used syslinux 4.03 for my brand new usb-stick (16GB FAT32, no Partition Table). It works, but on some computers i get "boot error". My investigation reveals three bugs in the boot code. Int 13 function 8 destroys the contents of register ES. Ah, now it is corrected in version 4.04 pre 5. Well done. I am happy now. But there are still other bugs. Look on version 4.04 pre 5,

Trying again to get a last call for Syslinux 4.04. I really want to release it this week. -hpa

IRC user ernini first noticed this. We both tried using gpxe/gpxelinux.0 from Syslinux-4.04-pre22. ernini used pxechain to a commercial NBP which RETs (the same as PXELINUX) and failed. Both of us had success with core/pxelinux.0 from Syslinux-4.04-pre22. For my test, I have a VM in VMware Server 2.0.2 (VMHW v7). I loaded gpxelinux.0 using the VM's built-in PXE ROM. Then I used

Okay, I have found a workaround for the build problem that affected -pre13 and -pre14, and as a side bonus I have pulled a couple of fixes, including Sebastian's latest gfxboot updates. -hpa

Hello, In my testing environment I have two VMs on ESXi 5.0. VM A = dhcp/tftp/PXE/http server, running CentOS 6.2. Syslinux 4.04 with the included gpxelinux.0. VM B = PXE boot client. If I run CentOS 6.2 also on the VM B, I can easily transfer 50+ MB/sec over http between the VMs (wget, links). Now, if I PXE boot gpxelinux.0 on the VM B, and start to download bigger initrd image over http the

I was hoping for some advice regarding indexing, From a dataframe there are 27 variables of interest, with the prefix of "pre". [7] "Decision" "MHCDate" "pre01" "pre01111" "pre012" "pre013" [13] "pre02" "pre02111" "pre02114" "pre0211" "pre0212"

Hi There, I have setup the following SAMBA + LDAP, Domain Controller, with smbldap-tools-0.9.8 SLES - 11.2 (For Samba, Separate System) samba-3.6.3-0.18.3 SLES - 10 (For LDAP Backend, Separate System) openldap2-2.3.19-18.7 The above setup is working fine and the password policies are all fine. Problem - If the user changes the password at the Windows Client sambaPwdLastSet changes date to