Doesn't anybody remember what a pain it was to write a new CP/M bios? Its
specific to the hardware (thats why its there!) If you want to support
non-IBMPC hardware, you either need to 1) write a translation layer, "IBM"
bios to whatever is on your box
2) write a BIOS, arrange to load it somehow, and point Elks at it.
3) get a bios for whatever it is (usually the vendor of a single-board can
come up with something, here.)
-----Original Message-----
From: Dan Olson [mailto:[EMAIL PROTECTED]]
Sent: Thursday, May 13, 1999 1:43 AM
To: Ansel
Cc: Mailing List
Subject: Re: NanoX version 0.3 released
> >easily handle. Personally I'm of the opinion that using the BIOS for
> >everything possible is a great shortcut. Lots of device drivers talk to
> Shouldn't ELKS ultimately be able to run on systems without a BIOS?
I was going to suggest this a *long* time ago, but never did. What about
using a file with BIOS info as is done with CP/M, then a machine need not
be IBM-compatable or a built in BIOS to run ELKs. Any thoughts?
Dan
