Displaying 2 results from an estimated 2 matches for "n133".
Did you mean:
133
2017 Apr 17
0
Patch: Fix isohybrid.c tool under Windows platforms
...of
> miscalculation and/or unwanted insertion of (CR) characters?
The appropriate remedy is to use "b" with fopen().
Its absence in isohybrid.c is an obvious translation error which happened
when the perl lines at
http://git.zytor.com/syslinux/syslinux.git/tree/utils/isohybrid.in#n133
open(FILE, "+< $file\0") or die "$0: cannot open $file: $!\n";
binmode FILE;
were converted to the C lines at
http://git.zytor.com/syslinux/syslinux.git/tree/utils/isohybrid.c#n970
if (!(fp = fopen(argv[0], "r+")))
err(1, "could not ope...
2017 Apr 17
2
Patch: Fix isohybrid.c tool under Windows platforms
> Hi,
>
> Colin Finck wrote:
> > Precisely, if isohybrid currently finds a 0x0A (LF) byte in the MBR code
> > (which exists in the strings), it adds a 0x0D (CR) before, thereby
> > shifting the MBR bytes to the right and making it invalid.
> > This can be fixed by opening the file in binary mode with the "b" flag.
>
> This is a very reasonable