similar to: SYSLINUX 3.63-pre3 release candidate; SDI image booting

Hello everyone, I have released SYSLINUX 3.63. The main update is a fix to EXTLINUX, which would get confused by directories with deleted file entries. Special thanks to Stas Kysel of rPath, Inc. for spotting this problem and giving me an excellent test case; and of course to rPath, Inc. in general for being my employer and being extremely supportive of my SYSLINUX work! I have also

Hello, I'm a student interested in the syslinux project of Gsoc. And Isincerely hope to have the opportunity to apply the "Dynamic linker/loader for modules" project. But it seems the #syslinux channel is not so active and I can't contact a mentor about that. Could anybody help me? Thank you!

Hello,I'm going to apply the Gsoc, and I'm interested in this idea. But I'm not quite understand the exact meaning of " Dynamic linker/loader for modules ". Does it mean to implement a ELF loader to dynamic linking or make the COM32 file being enable dynamic linked like ELF? Thank you for answering!

Hi, As I have not seen any confirmation yet on the list, I just wanted to let you know that sdi.c32 works fine here, at least as fine as my initial syslinux-2.11 asm patch. I only use XPe SDI images with the following structure (of course PART blob size can vary): Type Offset Size Base Address Attr ---- ------------------- -------------------

Hi, I added support in pxelinux for SDI (Wndows XP embedded images) files a few time ago for specific needs. It works well (at least for me atm) and I think I can now submit it to this list. I get a very good improvement in speed over the traditional way of loading SDI images. * Links : The 'diff -urN' patch for syslinux-2.11 (documentation included) :

I have tackled a major bug that affected sdi.c32 especially, but might at least theoretically have affected other formats as well. It *appears* to load the SDI image I managed to stitch together with XP Embedded Studio, but it doesn't actually boot neither on my system nor in simulation; then trying to upgrade it to SP2 caused it to corrupt itself, so I'm not all that keen to trying

Hi I did a google search on this and came up with nothing. OK, in the latest release of R for windows, I want to change the gui to SDI mode. Edit -> GUI preferences Choose SDI Apply I get the message about properties not being able to be changed on a running console, and that I need to save. So I click Save, and am met with a "Save As" dialogue box with the default file called

If someone could try it out and let me know if it works, I would appreciate it... (also, if someone can actually send me an .sdi image, for testing only, I would also appreciate it...) http://www.zytor.com/~hpa/syslinux/0001-COM32-module-to-load-a-Microsoft-System-Deployment-I.patch -hpa

Hello, I tried to make my own binary with 'make efi64 install' but it fail with make[3]: *** No rule to make target `/root/syslinux-6.02-pre3/efi64/efi/../core//writestr.o', needed by `syslinux.so'. Stop. make[3]: Leaving directory `/root/syslinux-6.02-pre3/efi64/efi' make[2]: *** [install] Error 2 make[2]: Leaving directory `/root/syslinux-6.02-pre3/efi64' make[1]: ***

Dear r-devel list members, I find that adding --sdi to the Target field in the short-cut for R is ineffective in R 2.3.0 beta for Windows (version/platform details below). Setting MDI = no in the Rconsole file works, however. It's probably a bit late to request this for version 2.3.0, but it would be nice to be able to select either the SDI or MDI in the R Windows installer. Regards, John

Just found this tidbit: http://skolk.livejournal.com/ -hpa

Hi, We have been using isolinux 3.75 for a while now, to support pxelinux and UEFI we were going to update to 6.03, but seeing 6.04 has but fixes, decided to go with 6.04-pre3. First, is that about read for a "make official' ? Second, I did have to modify gnu-efi/inc/efilinks.h for the build to complete (had to remove the (intptr_t) which doesn't belong in EFI/EDK). So I've

I just pushed out SYSLINUX 3.73-pre3. The only significant difference over -pre2 was changing MEMDISK to use "safeint" by default. -hpa

I think I botched syslinux-6.04-pre3. There are two fundamental problems with the build: a) The selection of what pieces of the library gets included in the core is done manually whereas it really should be automatic; b) The build doesn't fail if there are unresolved dependencies between the libraries and the core. I will fix these. (b) is IMO fundamental to avoid this error in the

> > C_ While initially thought to be a problem with the INCLUDE > > directive, now it seems the problem is the second parameter of the > > CONFIG directive. The second parameter of the CONFIG directive (which > > sets a new CWD) doesn't seem to work correctly (tested with pwd.c32), > > specially when the new cfg file (the first parameter of the CONFIG >

As suggested, I have made a 6.04-pre3 release. In addition to updating gnu-efi to the latest version available (3.0.9 + a few patches) I wanted to make the tree compile with -Werror on my box, which resulted in pulling a thread which in turn caused a whole bunch of things to unravel :) The end result was that I ended up refactoring much of the tree so that it now avoids building a ton of

Hi, I just noticed that my file server running 2.4.18-pre3 + IDE patches & NTFS patches has this error message in the logs: EXT3-fs error (device md(9,4)): ext3_free_blocks: Freeing blocks not in datazone - block = 33554432, count = 1 This is the only ext3 error I have seen and the uptime is currently over 74 days. The error actually appeared two weeks ago. The timing coincides well with

I just found a rather embarrassing bug in PXELINUX -- and what's worse -- I wrote an email about it and killed it off accidentally :-/ It appears PXELINUX doesn't free its internal socket buffers (it has 32 of them) when it gets an error reply from the server, including "file not found." This means it will eventually run out of sockets and "go deaf." This

Hello, GSoc mentors. Last time we discussed the IRC interview. Has the time been determined yet? It seems not so many days left before the deadline of submission. By the way, I'm banned from the IRC because I am a tor user. But we can't login IRC without using tor because IRC is screened by the firewall.

Okay, thanks. I just tried 6.01-pre1, downloading the .xz file. But that won't build because the gnu-efi directory is empty. ?? On Thu, Sep 19, 2019 at 9:29 PM Ady Ady via Syslinux <syslinux at syslinux.org> wrote: > > > fixes, decided to go with 6.04-pre3. First, is that about read for a > > > Please try either 6.04-pre1, or the current (binary) packages from