Sender: shinelight AT detroit DOT crosswinds DOT net
Message-Id: <3.0.6.16.19990425212428.2b4f22b4@pop.detroit.crosswinds.net>
X-Sender: detr_shinelight AT pop DOT detroit DOT crosswinds DOT net
X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (16)
Date: Sun, 25 Apr 1999 21:24:28 -0400
To: djgpp AT delorie DOT com
From: "Thomas J. Hruska" <shinelight AT detroit DOT crosswinds DOT net>
Subject: Re: Writing an OS
In-Reply-To: <7g0ahp$1poi$1@newssvr04-int.news.prodigy.com>
References: <7fvlo1$o0k$1 AT newsserv DOT zdv DOT uni-tuebingen DOT de>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Reply-To: djgpp AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

At 07:06 PM 4/25/99 -0500, you wrote:
>Arik Funke wrote: 
>> Hy, I'd like to programm an OS and to load it with GRUB-bootloader. I use
>> DJGPP and RHIDE.
>
>Programming an OS is a very difficult task. Are you sure you want to
>take on this task?

The first thing you might want to do is join the FreeDOS Kernel Developers
list (and download FreeDOS).  <http://www.freedos.org/>.

Next visit the ReactOS (a.k.a. FreeWinNT) web site and join the appropriate
mailing lists.  <http://www.sid-dis.com/ReactOS/>.

Finally, visit the GAZ web site.  This site contains not only vital
documents on how to write generic OSes, but it also has links to over 200
other OSes on the internet.  My favorite is TOPSY...an OS on a JAVA VM.
<http://gaz.cjb.net/>.
 
Now, I mean no offense, but I am only offering my personal opinion.  Even
with the best boot loader in the world, OS programming is a "black art."
There is little documentation for 16-bit mode OSes, and even less for
32-bit OSes.  You have to scrap and save every tidbit you get your hands
on.  Not to mention, every OS works differently.  There are NO debuggers,
NO libraries, nothing at all to help you out.  It is just between your OS
and the processor.  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.
On top of this, you have to write disk drive controller code, HD controller
code, figure out where everything will go in memory, etc.

From what I can tell, you have a long way to go before you are ready to
write an OS.  I have saved you months of searching with those three links,
but I'm leaving the rest up to you.


        Thomas J. Hruska -- shinelight AT detroit DOT crosswinds DOT net
Shining Light Productions -- "Meeting the needs of fellow programmers"
         http://www.geocities.com/SiliconValley/Heights/8504
                    http://click-on.to/shinelight