similar to: Nasty Bug (BIOS?).

Changes in 3.10: * gcc 4.0.1 compilation fixes. * Add support for querying the PCI BIOS in libcom32 (used by ethersel et al.) * Fix PCI handing (ethersel etc) on several old chipsets (and VMWare.) * Try to deal with systems with broken EBIOS. * New API call to do "localboot". * New API call to query features.

I have just pushed out SYSLINUX 3.10-pre9. Please test it out, especially everyone who has been working with me on various systems trying to get them to work, or have had recent breakage. -hpa

> > To be clear, I am not saying there is no bug - there might be. > I performed the following test with several versions of Syslinux: 1_ Execute: 'extlinux --once=non_default_label --install /mnt/sda1' ; 2_ In first reboot, the "non_default_label" should be executed; 3_ In second reboot, the default label should be executed. Results: _ 4.05 to 4.07: OK. _

Hello Erwan, You will find below a pull request for the bug reported by Robert Jordan in the disk library. The first patch is the one he tested (see http://syslinux.zytor.com/archives/2010-September/015341.html) and the second one is a sanity check for the number of sectors written by call ( see http://syslinux.zytor.com/archives/2010-September/015342.html). Thanks, The following changes

Tested floppy boot on two machines (one PII 350, one 486DX4) Floppy boot with syslinux is very very slow, more than 18 mn to boot a linux kernel from floppy on the 2 machines. Tested with 3 different disquettes that were know to work, boot is reached after this very long time. Noise from floppy head make think floppy wait approximatly one minute between each read. No problem with pxe boot with

Hi All, A colleague of mine is using syslinux-3.20-pre8, syslinux.com, under DOS to install syslinux loader. It gives "sector read error". He re-compiled syslinux.com under a linux box, and used it successfully to install the loader from DOS. He is installing it on a hard drive (C:) He booted from a floppy and ran: "syslinux.com C:" at A:\ prompt He tried with

I have just released SYSLINUX 3.00-pre9. The only change versus 3.00-pre8 is that the MEMDISK query API now reports the boot loader ID byte, per Bernd's suggestion. This is a release candidate, and I plan to release it as 3.00 *tomorrow*, unless I hear back anything bad. -hpa

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

hi Peter, everyone, I recently installed extlinux on my CF drive. after a few botches, it works, with menu.c32 too. Heres a few notes/observations: - menuing seems pretty sensitive to presence of tabs in extlinux.conf, unlike with pxelinux.cfg/default, Is this an oversight, or something Im misremembering ? - extlinux doesnt have the timeout after menu-choice. if I dont choose, it times out and

On Fri, Mar 24, 2017 at 05:38:31PM +0100, Thomas Schmitt via Syslinux wrote: > isohdpfc pushes the CX value to the stack which it gets from INT 13 AH 41. > Quite surely bit 0 of that CX is not set. But bit 2 "Enhanced Disk Drive" > could be set. > https://en.wikipedia.org/wiki/INT_13H > > I understand on David's BIOS after > > andw $1,%cx

Hi all, I have officially released SYSLINUX 3.20: Changes in 3.20: * EXTLINUX: New options --install (-i) and --update (-U), to make it clear if a boot loader should be installed or updated. For now, defaults to --install for compatibility; a future version will require one of these options. * New library functions to load and place files in

On Jun 05 2014, Ady wrote: > > I'm working on a system derived from ARCH linux, running what they > > call version 6.02-4 of the syslinux package (which would be your > > version 6.02 plus their/our patches). I've got a syslinux.cfg > > ArchLinux currently is already using 6.03-pre12 or newer, so I would > suggest for you to update. I want to keep the

Hi, i am looking now at the code which i assume loads the rest of isolinux.bin. The entry point for program execution from the MBR is obviously at http://git.zytor.com/syslinux/syslinux.git/tree/core/isolinux.asm#n186 (Do i get it right that this is the Intel syntax ? (Gronfff)) If POP yields the victim of the most recent not yet popped PUSH, then this does not look correctly coordinated

Hi! as i know that you like test reports, here are some... Testing environment: CompactFlash card, connected with an USB adapter to a Compaq Evo D310 frontal USB port. This machine boots via USB quite well with syslinux. 3.09 boots ok, no problem 3.10-pre2 does not boot 3.10-pre3 does not boot 3.10-pre4 does not boot 3.10-pre5 locks up pc 3.10-pre6 locks up pc 3.10-pre7 writes

Thomas Schmitt wrote: > My main point of interest is which block is really loaded as first one > of isolinux.bin. [Program snipped.] > (It could be shorter if i did not insist in big endian words.) Why insisting? Anyway appended is a dumper version. I could put up a binery version if needed. Let me know if so. -- MartinS /*

Hi, friends It is described at this page: http://superuser.com/questions/195275/usb-boot-no-default-or-ui-configuration-directive-found <http://superuser.com/questions/195275/usb-boot-no-default-or-ui-configuration-directive-found>help, thanks! -- regards chenge

Hi, C/H/S addressing and reading of first block seems to be ok in isohdpfd.bin. The main suspect for the failure of the attempt with isohdpfd.bin is the number or content of the blocks read after the first one. But i have no clue why isohdpfc.bin should do better than isohdpfd.bin. They differ just by one instruction (JC = 0x72 versus JMP = 0xEB) which both are performed before the reading and

I have just pushed out Syslinux 3.81-pre7; the only delta over -pre6 is a small change to meminfo.c32. I expect to make a 3.81 release probably early next week, so this is a last call notice. If you have any outstanding issues, or you have tests you want to do and want some more time (Dag - I know you said you were going to try to do some tests over the weekend), please speak up *now*. -hpa

On Tue, Mar 21, 2017 at 09:03:35AM +0100, Thomas Schmitt via Syslinux wrote: > I think we should offer David a binary which he can combine with > the MBR of the ISO and the image with the recognizable blocks. > I will later today upload a binary version of my block producer > and post the URL. > > The combination will be: > 432 bytes from Martin's MBR > 80 bytes

Thomas Schmitt wrote: > I still don't get the "backwards" aspect. (Probably not enough background > knowledge.) Sigh. inst x, y gas use x and possibly y, operates according to inst and puts the result in y. Intel lives with the misconception this should mean use y and possibly x, operate according to inst and put the result in x. If you come from gas background the first