search for: pbatard

On 2016.03.06 13:13, Gene Cumm wrote: > Did Visual Studio actually complain about this one? WDK compiler (which I also use) if I recall correctly. At any rate, some older compilers do not like double initializations like this one, and I don't think this change should be much of a contention point, since it doesn't introduce any liability. Regards, /Pete

...ys from Syslinux 4.06 and 5.10 [2]. If ldlinux.sys was present in any shape of form on future 5.x based ISOLINUX images (such as appended at the end of isolinux.bin), I could simply pick up that file, and install it as if it had been embedded in the app. Regards, /Pete [1] https://github.com/pbatard/rufus/blob/master/src/syslinux.c [2] https://github.com/pbatard/rufus/tree/master/res/syslinux

...less you also want to consider people who may be compiling part of the Syslinux source using WDK with /W3 (which I wouldn't mind being able to reinstate for Rufus compilation, but in that case, Syslinux would also need these additional cast patches). Regards, /Pete [1] https://github.com/pbatard/rufus/commit/db0880e534e4e9504e8c283256fbfbd0683abded#diff-729493b04f2117d4290873c20e986726 [2] https://github.com/pbatard/rufus/commit/db0880e534e4e9504e8c283256fbfbd0683abded#diff-9b695506cac9f006f20d03d23ee289e0 [3] https://github.com/pbatard/rufus/commit/db0880e534e4e9504e8c283256fbfbd0683abd...

...omework. So, there again, I will simply say thanks for bringing attention to these matters, while at the same time mention that I'm simply gonna pass on those, since they appear irrelevant with regards to the context that matters in my application... Regards, /Pete [1] https://github.com/pbatard/rufus/blob/b9caf8b6058de12bf028f907471561a6aa50f7e9/src/format.c#L349-L366

H. Peter Anvin schreef op 9-8-2013 7:37: > Sorry. If you are substituting any files you should substitute them all. I assume it's not possible to store a copy of the LDLINUX.SYS binary at the end or inside of either ISOLINUX.BIN or LDLINUX.C32 then? Then at least it could be extracted, for those distributions not having LDLINUX.SYS / SYSLINUX(64).EXE present on their CD. Having

...l options panel. Once you do that, you should find that "Syslinux v4" and "Syslinux v5" are listed as extra options in the "Create a bootable disk" dropdown. Or you can see [3]. Regards, /Pete [1] http://en.wikipedia.org/wiki/Partition_type [2] https://github.com/pbatard/rufus/blob/master/src/format.c#L838 [3] https://github.com/pbatard/rufus/wiki/FAQ#wiki-Advanced_Mode

...be compiled using Visual Studio, the Windows Driver Kit or MinGW (32 or 64), I have a few patches that I'd like to submit. The following fix 2 minor issues, as well as a add a feature to ease up the isolinux ISO -> syslinux USB conversion process. Regards, /Pete [1] https://github.com/pbatard/rufus

Hello, is there a way to start a efi-application (bios update tool) from syslinux ? best regards Johann

...completely (hopefully with 0 alterations). If "-f" is specified but not necessary (indicating a user/tool that isn't being cautious), consider throwing a warning while still allowing the install and returning a success to the caller of the installer. > [1] > https://github.com/pbatard/rufus/blob/ade5639c0047ee813f71a8bfef8b1cc7be551009/src/format.c#L349-L377 > [2] http://hjem.get2net.dk/rune_moeller_barnkob/filesystems/fat.html > [3] http://pierrelib.pagesperso-orange.fr/filesystems/fat16.html -- -Gene

...es to memset/memmove/memcpy, which are the only calls I see in there that I could see impacted. Besides, for obvious compatibility reasons, I would advocate using -D_GNU_SOURCE as a compiler option if one really needs it, rather than have it in a source. Regards, /Pete [1] https://github.com/pbatard/rufus/tree/master/src/syslinux [2] http://www.ridgecrop.demon.co.uk/index.htm?fat32format.htm [3] http://rufus.akeo.ie/files/syslinux-6.03/ [4] https://github.com/geneC/syslinux/commit/e4fc443f9b70f188963ff33e0a16ccb72a553540

Hi, i began to implement a common lookup function for SUSP and Rock Ridge entries: /* Obtain the payload bytes of all SUSP entries with a given signature. @param fs The data source from which to read CE blocks. @param dir_rec Memory containing the whole ISO 9660 directory record. @param sig Two characters of SUSP signature. E.g. "NM", "ER", ...

...n help avoid the multiplication of embedded files. Regards, /Pete PS: It looks like Syslinux v4.07 has officially been released, but there doesn't appear to be any mention of it at http://www.syslinux.org/wiki/index.php/The_Syslinux_Project [1] http://rufus.akeo.ie [2] https://github.com/pbatard/rufus/issues/165 [3] http://sourceforge.net/p/clonezilla/discussion/Clonezilla_live/thread/e00567cd/

...u also need to cater for people who replace the standard Syslinux versioning scheme with their own stuff, which makes for an even more interesting breakdown. All in all, this means the Syslinux projects does get not so kind words when I commit the necessary changes in Rufus: https://github.com/pbatard/rufus/commit/0fceb3843370ddc2d4c1b1d8f57c2c132758e78b So I have to second Ady here and indicate that, as far as I am concerned, 'A "version" such as "6.03" [is not] enough'. Maybe a nano, or something that is internal to Syslinux and gets increased for each pre, at t...

...existing Large FAT32 format code without realizing that doing so will break Syslinux installation. So it may still be worth relaxing the check especially if, as Ady pointed out, not having all sectors addressable doesn't make a disk any less valid. Regards, /Pete [1] https://github.com/pbatard/rufus/blob/ade5639c0047ee813f71a8bfef8b1cc7be551009/src/format.c#L349-L377 [2] http://hjem.get2net.dk/rune_moeller_barnkob/filesystems/fat.html [3] http://pierrelib.pagesperso-orange.fr/filesystems/fat16.html

On 03/02/16 16:19, Ady via Syslinux wrote: > > That's not what common users are forced to deal with. Syslinux's binary > files in the wild come from different sources (official upstream > Syslinux, distros' packages, others). > > Since v.6+ (and possibly, even before it) a re-build might show some > inconsistencies between "the same version" of

Hi Ady, I won't comment on the reasons why the original computation was wrong, but thanks for the detailed analysis. On 2016.02.26 08:05, Ady via Syslinux wrote: >> Thus we can finally get a formula for Fs that satisfies the above: >> >> Fs = (To - Rs + Nf * Cs) / ((Ss * Cs / Fe) + Nf) + 1 > > I believe such formula is slightly inaccurate too. > > My

Ady, before responding to you further, I'll ask you now to take onje more (fresh) look at this thread that I started over in the GParted forums: http://gparted-forum.surf4.info/viewtopic.php?pid=31834 Please note that I have now followed-up on myself and that I have added quite a lot of new & additional information. It now appears to me that GParted's reporting of the status of

...ng that doing so will break Syslinux installation. So it may > still be worth relaxing the check especially if, as Ady pointed out, not > having all sectors addressable doesn't make a disk any less valid. > > Regards, > > /Pete > > > [1] > https://github.com/pbatard/rufus/blob/ade5639c0047ee813f71a8bfef8b1cc7be551009/src/format.c#L349-L377 > [2] http://hjem.get2net.dk/rune_moeller_barnkob/filesystems/fat.html > [3] http://pierrelib.pagesperso-orange.fr/filesystems/fat16.html I would like to point out that being able to allocate / address at least...

Hi Ady, On 2016.02.25 02:08, Ady via Syslinux wrote: > There is an "extra" sector, in comparison to... what exactly? Sorry if I wasn't clear. I think I implied that the Large FAT32 fat size had an extra sector compared to minfatsize, when of course I meant the opposite (the Large FAT32 has one less sector than the minfatsize computed by the unpatched code, hence the check