Displaying 3 results from an estimated 3 matches for "comboot_seg".
2009 Oct 13
2
isolinux problem since 3.74
...dword [HighMemSize] ; Memory managed by
Syslinux
push dword com32_cfarcall ; Cfarcall entry point
push dword com32_farcall ; Farcall entry point
push dword (1 << 16) ; 64K bounce buffer
push dword (comboot_seg << 4) ; Bounce buffer address
push dword com32_intcall ; Intcall entry point
push dword command_line ; Command line pointer
- push dword 6 ; Argument count
+ push dword 7 ; Argum...
2007 May 25
1
multiple comboot files?
...omboot file?
If the comboot file could be instructed to load in a reserved high segment,
or even just after the BDA, the
available memory reported by the bios (INT 12 and INT 15 AX=E820h)
could be reduced, but I dont know if this approach will work under syslinux.
>From the source, it looks like comboot_seg is 4000, right in the middle.
Also, related to the first question, if I want to disable one of my
ISR's just before loading a kernel, I need to execute another smaller comboot
file to restore the IVT and other hardware registers.
When some action is exceuted, by say a keyword label, or default...
2003 Apr 16
1
SYSLINUX 2.04 released
...e 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, and by the
fact that the 1000h segment managed to get unused in all
derivatives...
* PXELINUX: Attempt to negotiate full Ethernet-sized blocks
(1468 bytes) using the blksize option.
* SYSLINUX: Resurrect the old no-mt...