freebsd-nq/sys/i386/boot/dosboot
Poul-Henning Kamp df8f292395 Try to win back the "removal of most crufty code" trophy from markm:
Remove WD formatting code which has never worked in 386bsd or FreeBSD.

Remove  DIOCSSTEP and DIOCSRETRIES ioctls as well, they belong in
history, along with the SMD disks.

OK'ed by:	bde
1999-09-01 11:32:52 +00:00
..
ansi.h $Id$ -> $FreeBSD$ 1999-08-28 01:08:13 +00:00
boot.c $Id$ -> $FreeBSD$ 1999-08-28 01:08:13 +00:00
boot.h $Id$ -> $FreeBSD$ 1999-08-28 01:08:13 +00:00
bootinfo.h $Id$ -> $FreeBSD$ 1999-08-28 01:08:13 +00:00
cdefs.h $Id$ -> $FreeBSD$ 1999-08-28 01:08:13 +00:00
dinode.h $Id$ -> $FreeBSD$ 1999-08-28 01:08:13 +00:00
dir.h $Id$ -> $FreeBSD$ 1999-08-28 01:08:13 +00:00
dirent.h
disk.c $Id$ -> $FreeBSD$ 1999-08-28 01:08:13 +00:00
disklabe.h Try to win back the "removal of most crufty code" trophy from markm: 1999-09-01 11:32:52 +00:00
dkbad.h $Id$ -> $FreeBSD$ 1999-08-28 01:08:13 +00:00
dosboot.c
dosboot.h
endian.h $Id$ -> $FreeBSD$ 1999-08-28 01:08:13 +00:00
exec.h $Id$ -> $FreeBSD$ 1999-08-28 01:08:13 +00:00
fbsdboot.c
fbsdboot.exe.uu
fbsdboot.mak
fs.h $Id$ -> $FreeBSD$ 1999-08-28 01:08:13 +00:00
imgact.h $Id$ -> $FreeBSD$ 1999-08-28 01:08:13 +00:00
inode.h $Id$ -> $FreeBSD$ 1999-08-28 01:08:13 +00:00
Makefile $Id$ -> $FreeBSD$ 1999-08-28 01:08:13 +00:00
mexec.h $Id$ -> $FreeBSD$ 1999-08-28 01:08:13 +00:00
param.h $Id$ -> $FreeBSD$ 1999-08-28 01:08:13 +00:00
protmod.c
protmod.h
quota.h $Id$ -> $FreeBSD$ 1999-08-28 01:08:13 +00:00
readme
reboot.h $Id$ -> $FreeBSD$ 1999-08-28 01:08:13 +00:00
sys.c $Id$ -> $FreeBSD$ 1999-08-28 01:08:13 +00:00
syslimit.h $Id$ -> $FreeBSD$ 1999-08-28 01:08:13 +00:00
sysparam.h $Id$ -> $FreeBSD$ 1999-08-28 01:08:13 +00:00
types.h $Id$ -> $FreeBSD$ 1999-08-28 01:08:13 +00:00

Hi Everybody!

This is version 1.5 of "fbsdboot", a program that allows you to boot a kernel
from a MS-DOS partition or a FreeBSD partition. This program runs using DOS.
It works with various memory managers (like  EMM386, 386MAX) under certain
circumstances.

First, a FreeBSD kernel is always loaded to memory starting at 0x100000. To
assure that loading the kernel *does not* overwrite memory used by memory
managers, high memory for the kernel is allocated and after loading the kernel
it's moved to 0x100000.

Second, there are many ways to switch to protected mode which is necessary to
start the kernel. Each BIOS gives you the possibility to use INT15H (AH=89H)
to do that. But some memory-managers like 386max does not allow you to use
this method.

An other way to do the switch is to use DPMI services, but they do not
guarantee, that the protected mode application is executed with privilege
level 0. Therefore this method is *not* used.

VCPI services offer another way to switch to protected mode, and VCPI servers
are built into "emm386.exe", "386max" and "qemm". That's why, this method is
implemented in fbsdboot.exe.

Fbsdboot.exe tries to switch to protected mode using VCPI services. If they're
not available INT15H is used to do the switch. If that fails, it's not possible
for this version of fbsdboot.exe to boot a kernel :-(.

You can get commandline options of fbsdboot if you start it with "-?" as option!

I don't know, if fbsdboot works with QEMM, as I don't have the possibility to
test it.

Enjoy and have fun!

Christian.
cg@fimp01.fim.uni-linz.ac.at


PS: Many thanks to Bruce Evans for his assistance!