Displaying 3 results from an estimated 3 matches for "metakern".
Did you mean:
metagen
2003 Dec 16
2
syslinux bootsector info?
...e diskspace that it would save by not including this program)
I found a way around the 386-dependency for syslinux by first using another loader which gives you the choice to boot either freedos bootsector directly, or SYSlinux's bootsector.
http://www.coli.uni-sb.de/~eric/stuff/soft/specials/metakern-11oct2003.zip
SYSLINUX A:
copybs A: A:\syslinux.bin
copy /b A:\meta-all.bin + A:\metaboot.bot + A:\syslinux.bin A:\metakern.sys
SYS A: A: BOOTONLY /K METAKERN.SYS /L 0x60
(kernelname, loadaddress, and bootonly-parameter causes only bootsector to be written, not any DOS system files copied)
this...
2004 Aug 17
1
syslinux write intended bootsector to bootsectorfile support?
...or drive A: to a 512byte user-specified file
Perhaps to allow both at the same time even SYSLINUX A: A: A:\SYSLINUX.BIN could be possible
SYSLINUX [place-to-copy-ldlinux.bin-to] [place(s) where to put bootsector(file)]
I'm supporting 8086+ instead of 386+, so I need another bootloader (called MetaKern) before SYSLINUX. That other bootloader requires that I append bootsectors of the OSs I want to load: 1) Syslinux and 2) FreeDOS.
Currently I do:
SYSLINUX A: // write both LDLINUX.BIN and Syslinux bootsector to A:
COPYBS A: A:\SYSLINUX.BIN // obtain bootsectorfile from Syslinux bootsector
COPY /B...
2004 Dec 29
4
SYSLINUX 3.00-pre8: Let's try this release thing again
Okay, spending the time to dot t's and cross i's (or something like
that), I think I have something now that can be called 3.00-worthy, so
let's call it a release candidate.
Changes over the earlier 3.00 prereleases:
- -m and -a options now supported by the DOS installer.
- PXELINUX now allows IP addresses, FQDNs, and truncated hostnames when
specifying an alternate TFTP server