similar to: Syslinux site down?

[This email is either empty or too large to be displayed at this time]

[This email is either empty or too large to be displayed at this time]

[This email is either empty or too large to be displayed at this time]

hello, i've a problem with syslinux on an intel sbc2 server board (other boards are ok). versions up to 1.48 work fine but from 1.49 there is a problem. when booting linux the system hangs after the message: Uncompressing Linux... Ok, booting kernel. sometimes there that message isn't displayed and the system just hangs with an empty screen. can you help me? best regards simon

[This email is either empty or too large to be displayed at this time]

> On 10/30/2013 10:29 AM, Ady wrote: > > > >> > >> A Google search with site:syslinux.org should work. > >> > >> -hpa > > > > As I pointed out in the ML more than once during the last months, > > that method *might* give, in some "random" case(s), a relevant > > result. But since Google has stopped caching /

On 06/04/2013 06:16 PM, Matt Fleming wrote: > Folks, > > Finally, Syslinux 5.10 has been released. This release includes a merge > of the 4.10 development branch, which means that there's a new network > stack availble, based on the lwIP embedded TCP/IP stack. The jump from > the previous 5.01 release to 5.10 may be a little confusing, but a new > network stack is such a

On Sun, Sep 13, 2015 at 9:22 AM, Patrick Masotta <masottaus at yahoo.com> wrote: > >>>> > > It is also working here; I think this particular PNG issue is fixed. > > > > It's worth to mention that the replaced code looks valid to me; that's why I think > > this is probably some sort of compiler bug. It was really hard to find. > > We

Hi Fi $ rpm --query --file /usr/bin/objcopy binutils-2.25.1-9.fc24.x86_64 $ cd syslinux-7cd1ed6/ $ make bios ... make[3]: Leaving directory '/tmp/syslinux-7cd1ed6/bios/gpxe' make[2]: Leaving directory '/tmp/syslinux-7cd1ed6/bios' make[1]: Leaving directory '/tmp/syslinux-7cd1ed6' $ file bios/core/*.bin bios/core/isolinux.bin: data bios/core/isolinux-debug.bin:

>>> > It is also working here; I think this particular PNG issue is fixed. > > It's worth to mention that the replaced code looks valid to me; that's why I think > this is probably some sort of compiler bug. It was really hard to find. > We should keep an eye on this issue; it might appear somewhere else. Eww.? The original code was merely an empty define.?

The program name of the module can't be retrieved with argv[0]. I tested it by running cat.c32 (com32/samples/cat.c32). In Syslinux 3.85, argv[0] returns an empty string. In Syslinux 4.00-pre36, argv[0] returns some garbage characters. ISOLINUX 3.85 2010-02-20 ETCD Copyright (C) 1994-2010 H. Peter Anvin et al argv = 0x00182c44 argv[0] = 0x07fbffc3 = "" argv[1] = 0x00182c34 =

>>> > > The empty define should work; actually it did work for many years... > > Your just proposed change was my first attempt for solving this but for some > reason it did not work. After testing a lot the only way I've found to solve this > bug was defining a "real" empty function. I know, 100% hacky but it works. If the voiding doesn't

On Tue, Aug 11, 2015 at 9:11 AM, Patrick Masotta via Syslinux <syslinux at zytor.com> wrote: > >>> > > > Please implement these new changes over your last non-debug > > working build (multi-nic fix) and let's see how it goes. > > > > https://github.com/ppatpat/syslinux/compare/master...ppatpat:zlib?expand=1 > > > > Please report

> Hi, > > I have been using syslinux on my portable disk with success on many > types of machines (both bios boot and EFI boot) > > I however hit a small issue recently > > If I use menu.c32, on some UEFI systems (HP) the menu does not appear > after the vendor splash screen. The system however goes ahead and > after the timeout configured in the menu system

Thank you Gregory your code worked to remove the border in syslinux! It wasn?t the Alpha (that changes the opacity of the border color), but it was the ?shadowing? that had to be changed, so ?none? in the shadowing column worked(you notice the border come back if you change ?none? to ?std?) reference this link for terms: https://wiki.syslinux.org/wiki/index.php?title=Menu#MENU_COLOR ! I am also

[This email is either empty or too large to be displayed at this time]

Thanks Gregory, my mistake, your explanation was half right and your code was fully right, I meant to say the key is setting the first two digits in the foreground and background to "00" (which means transparent) this will delete the color of the border, and then making the shadowing variable equal to "none" this will delete the shadowing black line that appears by default. See

Folks, Finally, Syslinux 5.10 has been released. This release includes a merge of the 4.10 development branch, which means that there's a new network stack availble, based on the lwIP embedded TCP/IP stack. The jump from the previous 5.01 release to 5.10 may be a little confusing, but a new network stack is such a large change that it deserved a significant bump in the version minor number.

Hi, is there an easy way to circumvent the SYSLINUX novice protection thing? intended users don't know about CTRL key to circumvent it. I'm trying to make a generic bootdisk for systems of 8086 - Pentium4. however the bootdisk is slow, so I'd like to use Syslinux + Memdisk to load a diskette image. then the text displayed to user will be: 1) FreeDOS bootdisk (accelerated, 386

On Jul 2, 2013 7:37 PM, "Patrick Verner" <distrozilla at gmail.com> wrote: > > System: Dell OptiPlex GX620 (Both BIOS A10 and A11 affected) > Medium: Physical CD-RW > Observed: ISOLINUX 5.11 0x51D1AE48 ETCD_ is the only line displayed > on-screen. A flashing cursor trails at the end of the line. Escape key does Is "ISOLINUX 5.11 0x51D1AE48 ETCD_" (assuming