similar to: pxelinux 5.00-pre6 sub menu not working

I think the Syslinux 5.00 branch is now at the point where I believe it it is feature complete and should be able to replace the main Syslinux branch. As such, it is important that we get wider testing, and especially that people let us know if and where it breaks. As of right now, there aren't any known bugs...

Most excellent! The pre-compiled syslinux6.03-pre6 binaries work great! I'm able to load syslinux.efi and all necessary support libs. I get my expected syslinux boot menu. I've used syslinux 5 / vesamenu for yrs (Legacy PXE boots). So I know my way around from here. Thanks Gene & Feri. And thanks Peter, for making me feel better -- it's the TFTP protocol that's bizarre, I

Ah, Mondays. The following oops happened after approximately eleven days of uptime. The machine was not under any particular load at the time. Following a forced reboot, all filesystems replayed the journal successfully. Relevant log entries leading up to the oops: Nov 4 04:54:08 localhost kernel: attempt to access beyond end of device Nov 4 04:54:08 localhost kernel: 03:02: rw=1,

Hello, While attempting to build syslinux-3.52-pre6 for testing (my SCSI machine won't boot from CD-ROM with 3.51) I hit this problem: nasm -O99 -f bin -DDATE_STR="'3.52-pre6'" -DHEXDATE="0x46c22b21" \ -DMAP=pxelinux.map -l pxelinux.lsr -o pxelinux.bin pxelinux.asm pxelinux.asm:1206: error: short jump is out of range nasm -version NASM version

Hi, I tested this version and it works all right ! Thanks a lot for the quick fix. Do you still want to see the output in order to check everything is OK, or you don't need it ? --------------------- Sylvain Faivre EdifiXio - AIH Team +33 1 56 90 51 24 www.edifixio.com > -----Message d'origine----- > De : H. Peter Anvin [mailto:hpa at zytor.com] > Envoy? : mardi 18 novembre

I have decided to make SYSLINUX 2.10-pre6 a release candidate. Please test it out if you can; if it works OK I will release it as 2.10 some time in the middle of the week. Thanks! -hpa

I have, hopefully, found and fixed the issue with non-kernel binaries that appeared in 3.35. As a result, I have pushed out 3.36-pre6 and am classifying it as a release candidate. Please try it out, especially if you have had problems with 3.35. ftp://ftp.kernel.org/pub/linux/utils/boot/syslinux/Testing/ -hpa

Hi, just tried 1.73-pre6 pxelinux: - booting linux works - memdisk with 1.44M Dos image works - the 'kbdmap'-parameter fails: [..] Unknown keyword in config file. Missing parameter in config file. boot: - and it doesn't remap any keys. I tried 1.66 with the same config file and it works, it accepts 'kbdmap' and also remaps the keys. Regards, Josef

Hi everybody Just wanted to ask that. pre6 with ext3 work fine for me so far. Bye Tim

It seems that at least SYSLINUX 1.73-pre4 and -pre5 had some very serious bugs in it, so here is a SYSLINUX 1.73-pre6 to test out; don't be surprised if there are more in short order... :) ftp://ftp.kernel.org/pub/linux/utils/boot/syslinux/Testing/ -hpa

Hi everyone, I have released SYSLINUX 2.00-pre6. The only difference against -pre5 is that I finally got around to fixing mbr.asm so that it produces a working MBR. http://www.kernel.org/pub/linux/utils/boot/syslinux/Testing/ I will probably try to do a binary-only release of the COM32 port of newlib libc sometime this week. The only reason this will be a binary-only release is that the

Hi all, It looks like the announcement about 2.08-pre6 never went out... it is 2.08-pre5 with Murali's "onerror" command added. -hpa

> In Syslinux 6.03-pre6: > > _ The txt/html/*.html files are currently created 3 times, one for > each firmware. I think they should be created only once (under the > main txt/html/ directory), just as the rest of the documentation is. > In that case, the <respective_firmware>/txt/html/ subdirectories > should not even be created. > > _ The bios/dosutil/

> On Mar 4, 2014 7:42 PM, "Ady" <ady-sf at hotmail.com> wrote: > > > > > > > In Syslinux 6.03-pre6: > > > > > > _ The txt/html/*.html files are currently created 3 times, one for > > > each firmware. I think they should be created only once (under the > > > main txt/html/ directory), just as the rest of the documentation

In Syslinux 6.03-pre6: _ The txt/html/*.html files are currently created 3 times, one for each firmware. I think they should be created only once (under the main txt/html/ directory), just as the rest of the documentation is. In that case, the <respective_firmware>/txt/html/ subdirectories should not even be created. _ The bios/dosutil/ directory contains copybs.com and eltorito.sys,

On Mar 4, 2014 7:42 PM, "Ady" <ady-sf at hotmail.com> wrote: > > > > In Syslinux 6.03-pre6: > > > > _ The txt/html/*.html files are currently created 3 times, one for > > each firmware. I think they should be created only once (under the > > main txt/html/ directory), just as the rest of the documentation is. > > In that case, the

Hi, Below is the installation output and the first use output for FL 7: superman@travisf-linux:~$ cd Programs superman@travisf-linux:~/Programs$ ls AdobeReader_enu-7.0.9-1.i386.tar.gz netbeans-6.0m10-full-linux.sh ASSP_1.3.1-Install.zip RealPlayer flstudio7_RC6b.exe RealPlayer10GOLD.bin ImportExportTools-1.2.xpi Serial Numbers.odt

*When I run sh winetricks gecko, the following happens:* superman at travis-lin:~$ sh winetricks gecko --13:43:26-- http://source.winehq.org/winegecko.php?v=0.1.0 => `winegecko.php?v=0.1.0' Resolving source.winehq.org... 209.46.25.134 Connecting to source.winehq.org|209.46.25.134|:80... connected. HTTP request sent, awaiting response... 302 Found Location:

On Wed, Jul 04, 2012 at 05:12:00AM +0200, Helmut Hullen wrote: > Hallo, Dag, > Du meintest am 04.07.12: > > > I tried to package 5.00-pre6 on RHEL using the known routine: > > > make clean > > make installer > > make install-all > > > and I get: > > [...] > > Perhaps you try Matt Flemings 5.00-pre8 version: > >

Hi all, I have configured Asterisk to call to PSTN phone from our IP phone, But I am unable to call my IP phone from a PSTN phone (If I called any number between 21494350 and 21494399, the card should route my call to my IP phone, IF my configuration was correct). I have done my research and gathered bits and pieces of information (which are vague by the way) but still cannot call my IP phone from