Path: utzoo!utgpu!watmath!watdragon!rose!ehoogerbeets
From: ehoogerbeets@rose.waterloo.edu (Edwin Hoogerbeets)
Newsgroups: comp.sys.amiga
Subject: Minix and AmigaDOS (was Re: AmigaMINIX, some answers)
Message-ID: <15561@watdragon.waterloo.edu>
Date: 1 Aug 89 22:35:24 GMT
References: <2939@solo3.cs.vu.nl> <2059@cbnewsc.ATT.COM> <469@tardis.Tymnet.COM> <SHADOW.89Aug1004439@pawl.rpi.edu>
Sender: daemon@watdragon.waterloo.edu
Reply-To: ehoogerbeets@rose.waterloo.edu (Edwin Hoogerbeets)
Followup-To: comp.sys.amiga
Organization: U. of Waterloo, Ontario
Lines: 19

In article <SHADOW.89Aug1004439@pawl.rpi.edu> shadow@pawl.rpi.edu (Deven T. Corzine) writes:
% Joe> They said: "AmigaMINIX boots from a normal AmigaDOS floppy".
% Joe> unambiguous reference to AmigaMINIX being started near the end of
% Joe> the startup-sequence, after your SetMap command.
% Joe>   Which means AddMem can go in there, no problem.
% If there's actually a startup-sequence, yes.

Doesn't AddMem tell *AmigaDOS* that there is more memory? If so, how is
AmigaDOS going to tell Minix about it? Minix is an OS of itself, and
takes over the machine, effectively doing the equivalent of a reboot.
When it boots on a PC, the MSDos stuff is never seen.

The boot code on the floppy is used as a bootstrap to get Minix
started. You may have to write your own custom hard drive drivers and
AddMem type stuff for all the neat goodies you have on your own machine.

Use the source, Luke!

Edwin