similar to: Problem with mailing list archive?

On Sun, Oct 14, 2018 at 1:00 PM Ady Ady via Syslinux <syslinux at zytor.com> wrote: > There seems to be some problem in the mailing list public archives. Not really. Just some unexpected results. > Since 2018-Oct-01, in my mailbox I received 3 emails from Thomas > Lurmeau (via Syslinux, of course), whereas the public archive shows > only 2 (the first one is not there ATM).

Ok i have founded it ! Thanks ! My project is to realize a usb booting key with all distributions of Windows and linux. Mon problem is that i don?t know how to build it and how can i have two diferrently Windows on it.. Do you have alleady done this ? Obtenez Outlook pour iOS<https://aka.ms/o0ukef> On Sat, Oct 6, 2018 at 1:53 PM +0200, "Gene Cumm" <gene.cumm at

> We now have a new archive repo at zytor.com. Almost all resources and > communication channels depend on zytor.com being on-line, including the > mailing list itself. > > Please note how the "bounces..." address is still "at zytor.com". > Whether that has any (positive or negative) influence in some case / > support / troubleshooting / configuration,

On 2/20/19 5:22 PM, H. Peter Anvin via Syslinux wrote: > On 2/18/19 8:56 AM, Ady Ady via Syslinux wrote: >> >> BTW, until very recently, we used to have a "syslinux-commits" mailing >> list (and its archive). >> >> Would it be possible to have "syslinux-commits" back (and its archive)? >> >> IIRC, it was "linked" to the

On Fri, Jul 3, 2015 at 2:28 AM, Ady via Syslinux <syslinux at zytor.com> wrote: > FWIW, I am still against releasing 6.04-pre1 yet. Why? A pre-release is not a full release. It means we're getting ready and have something that we want more people to test, especially those who can't reliably build test binaries, especially those who can't build any. Yes there are open

Hi all ! I have a little question about the last edition of Syslinux ! Where is the syslinux.exe which should be into \syslinux-6.03\win64 ? Maybe should i compile it but i don't know how to do it on Windows operating system.. Thanks for your answer !! Best Regards !

> 2015-11-20 8:15 UTC+01:00, Ady via Syslinux <syslinux at zytor.com>: > >> > > >> > I don't like the idea of changing "UI" (e.g. command line options that > >> > might be used by some users) without very well-thought reasoning. > >> > >> This is not an UI. AFAIK, this script is not shipped to the user. I > >>

> More context to this: syslinux_run_command calls into load_kernel(), and somewhere behind load_kernel things break. This is also broken at the boot: console prompt. Any commands executed at the boot: prompt also lose all parameters. > > > With the latest 6.03pre I'm seeing an issue where no parameters are passed to the image executed via syslinux_run_command(). > > An

@Carl, I'll repeat what I said in my prior email: you don't have to keep looking, we already achieved what you want (considering that you are willing to "disregard" the screen problems and similar issues, at least for now, according to your own emails). In short: 1_ Re-read my email from 2018Dec05: www.syslinux.org/archives/2018-December/026247.html where I posted

Hi, As someone who just recently came to the Syslinux project, with a different agenda but still a Syslinux noob maybe I can add my perspective. The Doc/Wiki makes perfect sense from a DEVELOPERS point of view, but I think the point here is maybe from a USERS point of view not so much. Even approaching syslinux with the purpose of building a custom .c32 module and leveraging the core syslinux

> > > > I don't like the idea of changing "UI" (e.g. command line options that > > might be used by some users) without very well-thought reasoning. > > This is not an UI. AFAIK, this script is not shipped to the user. I > don't even see what a user could do with it. > > Well, the Perl script _is_ shipped in the official release, and the

> I'm testing syslinux PXE EFI boot with VMware workstation 9.04 running > on Windows 8.1 > > VMware correctly performs the DHCP request indicating either > the "EFI IA32" or "EFI BC" architecture and the TFTP server > correctly sends back w/o error the "corresponding" syslinux.efi > "EFI BC" -> EFI64\syslinux.efi >

> HI, > > On 29/07/2014 22:23, Ady wrote: > > > Even without such "Mac" hardware at hand, it might still be helpful > > to test mkisofs 3.01a24 and then check the resulting ISO image. > > Perhaps Didier can update his current version of mkisofs and retry > > with his current scripts/receipts. > > I will upgrade the cdrtools package from

On Thu, Nov 15, 2018 at 1:10 PM Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > Here are some comments and questions for you. > Thanks. I've have my scripts to a better state, including installing/using qemu to uefi and legacy boot the usb stick for testing. It mostly works for me, but the "wget a tarball of binaries" step isn't going to sit well with

> 2015-11-19 17:30 UTC+01:00, Nicolas Cornu via Syslinux <syslinux at zytor.com>: > > - Remove padsize argument as it is never used. > > - Add an usage printed when $file is not set or --help, -h > > is the first argument. > > - Add basic tests for this script. > > --- > > mbr/checksize.pl | 27 ++++++++++++++++++--------- > >

Hello Ady thank you very much for the accurate reply and for saving my time :-) Best Regards, On 17.10.18 18:06, Ady Ady via Syslinux wrote: >> is it possible to boot a 32 Bit Kernel on 64 EFI firmware with Syslinux? > > In theory, booting 32-bit kernels from 64-bit EFI is supposed to be > supported by "efi64/efi/syslinux.efi" since 2013Jun. > > In practice:

> On 01/06/2016 00:28, H. Peter Anvin via Syslinux wrote: > > There seem to be a bunch of bug fixes in the 6.04 branch that people > > really need. Do we know of any current regressions? Otherwise we > > really ought to just push the button... > > I am a user of syslinux 4.0.7 to boot installers on BIOS aka Legacy. > > Knowing that 4.0.7 has been released on

Hi Ady, On Sun, 22 Oct 2017 22:49:53 +0000 Ady Ady via Syslinux <syslinux at zytor.com> wrote: > Let's not forget that upstream Syslinux FTBFS when building with > binutils 2.27+: > > "ldlinux.elf: Not enough room for program headers" > > Workaround in Debian's package: > _ Add --no-dynamic-linker to link lines > _

Another prerelease for the 5.00 (elflink) branch should be making its way to the mirrors now. The shortlog for -pre7 to -pre8 is listed below. Just like the 4.06 branch I was really hoping to drop a final release this week. Once 4.06 is out I'll merge that into 5.00. If you can, please test it out and let know any of any bugs you find. Because so much of the core infrastructure is rewritten

On Sat, Nov 17, 2018 at 1:54 AM Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > > > On Thu, Nov 15, 2018 at 1:10 PM Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > > > > > Here are some comments and questions for you. > > > > > > > Thanks. > > > > I've have my scripts to a better state, including