From:	arh14 AT cornell DOT edu
Date:	Tue, 27 Apr 1999 13:48:12 -0400 (EDT)
X-Sender:	arh14 AT travelers DOT mail DOT cornell DOT edu
To:	djgpp AT delorie DOT com
Subject:	Writing an OS
In-Reply-To:	<199904260406.AAA24563@delorie.com>
Message-ID:	<Pine.SOL.3.91.990427134359.3388A@travelers.mail.cornell.edu>
MIME-Version:	1.0
Reply-To:	djgpp AT delorie DOT com
X-Mailing-List:	djgpp AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

Thomas Hruska said:

> I also hate to burst your bubble, but you can't use the
> printf() statement in an OS unless you write your own low level version.

Bah!  If you are writing for an x86 system and have x86 code, why can't 
you use it?  Build it on another computer, or just write in assembly and 
link in the stdlib, right?  Then just jump to it...what's so hard about 
that?  Now if you're writing an OS for a totally *foreign* computer with 
different instruction set, yes, you will be up a creek...

> On top of this, you have to write disk drive controller code, HD controller
> code, figure out where everything will go in memory, etc.              

That's the yucky part...

I have taken a look at the FreeDOS source and started hacking a bit at 
it, although I don't have much time to do so.  The "Gaz" site looks 
interesting...thanks for the links.

Aaron

- Raw text -