similar to: eltorito.sys

Displaying 20 results from an estimated 30000 matches similar to: "eltorito.sys"

2012 Dec 22
1
ElTorito.sys Scanning Strategy
Good day to all. Since we've adopted Gary Tong's and Bart Lagerweij's ElTorito.sys (now modified by H. Peter Anvin and tiny changes from myself), I'd appreciate if anyone with more El Torito experience might criticize my comments below and advise as to how they might be wrong. Some of it is off-topic GRUB4DOS detail; safe to ignore. A bit of history: FDUBCD ("FreeDOS
2010 Jun 19
0
ELTORITO.SYS, MEMDISK, MDISKCHK.COM Commits
H. Peter, three simple commits here[1] (for_hpa branch). Gert, sample binaries are here[2]. --- mdiskchk: Add --no-sequential mode It might be useful to suppress MDISKCHK.COM's classic behaviour of probing all BIOS drive numbers in search of MEMDISKs. Some BIOSes might not enjoy being probed. --- memdisk: Correct El Torito termination response Two
2009 Dec 18
4
SYSLINUX 3.84 released
Syslinux 3.84 has been released. This is a mixed minor new features/minor bug fixes release. Changes in 3.84: * SYSLINUX: make the DOS installer work for MS-DOS 7.x/8.x (Win9x/ME) again. * HDT: updated to version 0.3.6 (numerous changes.) * mboot.c32: now supports video mode setting if requested by the image. * MEMDISK: Fix floppy images of
2010 Jun 28
1
Syslinux 4.00 released
After 64 prereleases, 626 commits, 52,742 lines of changes, and tons of work by many, many people, Syslinux 4.00 is now officially released. Syslinux 4.00 is the first of a set of major code restructuring releases. The single biggest new features are btrfs and ext4 support, and support for disks larger than 2 TiB. Huge thanks to: - Intel, for sponsoring mine, Alek Du's and Feng Tang's
2005 Jan 16
0
ElTorito from Floppy (was: Re: Can I use...)
a member of the FreeDOS project has transformed Smart Boot Manager into a COM32 module for Syslinux. Might be a bit more usefull than Syslinux -> memdisk -> imagefile -> Smart Boot Manager ( -> 'boot from cd -> cdrom ) I've inserted it into this diskette image: http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/beta9sr1/fdos1440.img That's nice to
2010 Nov 30
2
Syslinux Digest, Vol 92, Issue 25
Sorry Gene, I got the version of binutils is 2.17. I download the latest Binutils to make the *objdump* and *objcopy*. with both of these utilities to create new pxelinux.raw. then, the error message shows me that, objcopy -O binary pxelinux.elf pxelinux.raw ../lzo/prepcore pxelinux.raw pxelinux.bin ../lzo/prepcore: pxelinux.raw: output too big (30165, max 0) make[1]: *** [pxelinux.bin] Error 1
2016 Mar 08
0
Syslinux 6.04-pre1
On 08.03.2016 17:36, H. Peter Anvin wrote: > On 03/08/16 07:49, poma via Syslinux wrote: >> >> ... >> nasm -f elf -Ox -g -F dwarf -DDATE_STR="'6.03-156-g1ac927d'" \ >> -DHEXDATE="0x56deef98" \ >> -Di386 \ >> -I/tmp/syslinux/core/ \ >> -l ldlinux.lsr -o ldlinux.o -MP -MD ./.ldlinux.o.d /tmp/syslinux/core/ldlinux.asm
2010 Dec 02
1
Syslinux Digest, Vol 93, Issue 1
All, Thanks for all your help. Now, I can compile the latest source code base on RedHat 5.5 after update nasm(to 2.09) and binutil(2.17). And *make spotless* before *make* under core/ directory. But with the new pxelinux.0, the PXEClient can not bootup. The error info, No valid file system found! And stuck in there. I think maybe the gcc cause the problem. My gcc version is 4.1.2. Thanks aaron
2016 Mar 08
0
Syslinux 6.04-pre1
On Tue, Mar 8, 2016 at 6:00 PM, H. Peter Anvin <hpa at zytor.com> wrote: > On 03/08/2016 02:53 PM, Gene Cumm wrote: >> >> Poma, in my opinion, this behavior means it's your/Fedora's responsibility >> to propose a change that distinguishes between broken and working NASM >> 2.11.06 or revert the commit in your/Fedora's build. >> > > Yes, it
2016 Mar 08
2
Syslinux 6.04-pre1
On 03/08/16 07:49, poma via Syslinux wrote: > > ... > nasm -f elf -Ox -g -F dwarf -DDATE_STR="'6.03-156-g1ac927d'" \ > -DHEXDATE="0x56deef98" \ > -Di386 \ > -I/tmp/syslinux/core/ \ > -l ldlinux.lsr -o ldlinux.o -MP -MD ./.ldlinux.o.d /tmp/syslinux/core/ldlinux.asm > head.inc:26: fatal: NASM 2.11.06 is known to miscompile Syslinux >
2016 Mar 08
1
Syslinux 6.04-pre1
On Tue, Mar 8, 2016 at 3:21 AM, H. Peter Anvin via Syslinux <syslinux at zytor.com> wrote: > On 03/06/16 10:02, Ady via Syslinux wrote: >> >> 1_ The NEWS file would not be an adequate place to post such >> information, for several reasons. >> >> 2_ Expressing the problem with NASM in such a way would be very >> inaccurate. The problem is in NASM
2009 Jun 09
0
SYSLINUX 3.82 released
Hi everyone, I have pushed out Syslinux 3.82 to the usual places. Again, special thanks to my employer, Intel, for letting me spend time working on this stuff ;) -hpa Syslinux 3.82 is a bug fix release for 3.81. Changes in 3.82: * isohybrid: fix the -partok logic for loading from a partition. * ISOLINUX: deal with systems which return from INT 13h with interrupts
2009 May 29
2
Syslinux 3.81 released
Hi everyone, I have pushed out Syslinux 3.81 to the usual places. Again, special thanks to my employer, Intel, for letting me spend time working on this stuff ;) -hpa Syslinux 3.81 is primarily a bug fix release. The main new features are halt-on-idle support and some features to isohybrid, including the ability to boot from an image written to a partition. Changes in 3.81: *
2009 Oct 05
2
Syslinux 3.83 released
Hi all, I have just released Syslinux 3.83. Special thanks to my employer, Intel, for letting me spend time on this. It is somewhat of a meager release despite four months, as most of the work has gone into the future-work branches. -hpa Changes in 3.83: * PXELINUX: clear memory before handing over to a chainloaded NBP. This may help avoid a bug in Windows RIS. *
2013 Jul 15
2
[LLVMdev] [PATCH] x86/asm: avoid mnemonics without type suffix
On Mon, Jul 15, 2013 at 11:40 AM, H. Peter Anvin <hpa at zytor.com> wrote: > On 07/14/2013 12:49 PM, Linus Torvalds wrote: > > This is also why the Intel manuals point out that "some assemblers" can > take things like: > > bt[l] $63,(%rsi) > > ... and turn it into: > > btl $31,4(%rsi) > > This is definitely the friendly thing to
2016 Mar 08
2
Syslinux 6.04-pre1
On 03/08/2016 02:53 PM, Gene Cumm wrote: > > Poma, in my opinion, this behavior means it's your/Fedora's responsibility > to propose a change that distinguishes between broken and working NASM > 2.11.06 or revert the commit in your/Fedora's build. > Yes, it is highly problematic to have especially build tools with version numbers that don't match upstream having
2008 Apr 10
0
SYSLINUX 3.63 released (and 3.70-pre9)
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
2005 Jun 16
4
SYSLINUX 3.09-pre2: release candidate
It appears that increasing the command line limit to 1023 caused the .bss memory area to overflow. Unfortunately NASM didn't detect this as it ought to have and therefore I didn't catch it as an error. I have dropped the command line limit to 511 characters and released it as 3.09-pre2. This is a release candidate; please test it out and if it works I'll make it 3.09. -hpa
2006 Jul 14
2
Export to LaTeX
Dear Everybody! I want to export data to LaTeX. As I want to employ the data as freely as possible I want to avoid the xtable-command and instead generate some List like \MyOwnPrettyCommand{Adam}{Auer}{17} \MyOwnPrettyCommand{Bertram}{Bauer}{14} \MyOwnPrettyCommand{Christoph}{Huber}{75} \MyOwnPrettyCommand{Damian}{Dorfer}{69} \MyOwnPrettyCommand{Emanuel}{Eder}{43} with \MyOwnPrittyCommand
2003 Apr 16
1
SYSLINUX 2.04 released
I have released SYSLINUX 2.04, mostly to address the 2.03 MEMDISK bug. At the same time I'm getting the PXELINUX blksize and SYSLINUX installer changes out there, which hopefully is a good thing. New release mostly to address the MEMDISK corruption issue. Changes in 2.04: * ALL: Reclaim even more low memory by observing that comboot_seg == real_mode_seg is perfectly fine,