well this was my argument in the begining, we should allow this BIOS to
support "REAL" bios calls like int 13 and int 10... if you include basic
BIOS functionality, you can allow any "decent" operating system to
startup... including LILO
-----Original Message-----
From: Winter Jörg [mailto:joerg.winter@disch-gmbh.de]
Sent: January 31, 2000 10:54 Am
To: openbios(a)elvis.informatik.uni-freiburg.de
Subject: [OpenBIOS] Starting Linux from the C environment
> ----------
> Von: Stawnyczy, Evan[SMTP:EStawnyczy@geo-logistics.com]
> Antwort an: openbios(a)freiburg.linux.de
> Gesendet: Montag, 31. Januar 2000 15:48
> An: openbios(a)elvis.informatik.uni-freiburg.de
> Betreff: RE: [OpenBIOS] Fine.
>
> my understanding of lilo is that if you place it on the boot sector, you
> can
> load the boot sector to a point in memory (I cannot recall exactly where
> right now, you can email me farther if you need to) and simply jmp to it.
> Actually all boot sectors work the same way...
>
Basicly you are right. But lilo makes extensive use of *real* BIOS
functions like int13, int10, int16, and some strange
int15-shift-this-memory-to-ems function that I forgot the functioncode of.
I´d rather do this in C and burn a barebone Kernel onto my Disk ...
But I´m not sure if I kill my own running environment by copying a
Kernel to mem at 0x10000. Furthermore I have no idea if the
segment-deskriptor-setup is suitable for an immediate start of a kernel
image ...
I´ll try this tomorrow and keep you up to date if I succeed on this
...
> eMail: mailto:Joerg.Winter@Disch-GmbH.de
>
>
-
To unsubscribe: send mail to majordomo(a)freiburg.linux.de
with 'unsubscribe openbios' in the body of the message
-
To unsubscribe: send mail to majordomo(a)freiburg.linux.de
with 'unsubscribe openbios' in the body of the message