search for: _syslinux_

...alone). For debugging (and for reporting in general), we should try to be more accurate. If I may... If I were to say something like "Syslinux doesn't boot", I would mean that I cannot even get to a simple Syslinux's "boot:" prompt. In other words, I would mean that _Syslinux_ (in one of its variants / family members) is failing to boot. Whether the problem is in Syslinux itself or in some other area (HW, FW, user error, inadequate configuration...), that would be the first troubleshooting matter. Next, if _Syslinux_ works, I would try to load a simple LABEL from CL...

On 05-08-15 04:17, Ady via Syslinux wrote: >> Now... why is vesamenu.c32 crashing like it does now? Why is the version >> I tried without Gene's latest patches crashing before even beginning to >> load the first stage: ldlinux.e64? > I think you were "hinted" about this before. About what? Did I miss something obvious? I now know why it did not load

I'm thinking it might be an interesting idea to pass ipappend-style metadata (and quite possibly additional information, e.g. obtained from DMI) when making a http request, but I'm not 100% sure about the best way to do it. Options are pretty much: 1. some kind of metavariables in either the configuration file or in the filename syntax. + very general. - cumbersome for the

...linux/6.02 Connection: close I'm supposed to get cookies, per this line in syslinux.txt - but cant figure out where to put it in the config file to have it be accepted. SENDCOOKIES bitmask [PXELINUX only] When downloading files over http, the SYSAPPEND strings are prepended with _Syslinux_ and sent to the server as cookies. The cookies are URL-encoded; whitespace is *not* replaced with underscores. This command limits the cookies send; 0 means no cookies. The default is -1, meaning send all cookies. This option is "sticky" and is not automatically reset wh...

> If I may... If I were to say something like "Syslinux doesn't boot", I > would mean that I cannot even get to a simple Syslinux's "boot:" > prompt. In other words, I would mean that _Syslinux_ (in one of its > variants / family members) is failing to boot. Whether the problem is > in Syslinux itself or in some other area (HW, FW, user error, > inadequate configuration...), that would be the first troubleshooting > matter. I don't think I bluntly stated it this way. If I...