From mint-bounce@lists.fishpool.fi Sat Sep 18 09:35:59 2010 X-Authentication-Warning: antyk.ibi.uw.edu.pl: draco owned process doing -bs Date: Sat, 18 Sep 2010 15:32:31 +0200 (CEST) From: Konrad Kokoszkiewicz To: m0n0 cc: mint@lists.fishpool.fi Subject: Re: [MiNT] WIkI- GEM=ROM In-Reply-To: Message-ID: References: <955668.40921262-sendEmail@descaro> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.0.1 (antyk.ibi.uw.edu.pl [127.0.0.1]); Sat, 18 Sep 2010 15:32:31 +0200 (CEST) X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: draco@ibi.uw.edu.pl Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: List-subscribe: List-owner: List-post: > "If the MiNT is supposed to execute GEM, you should specify the full > path and filename. You can also request MiNT to execute the TOS AES > residing in ROM. WARNING: this is not recommended, you should use a GEM > version instead, that is multitasking friendly. If your init program is > not GEM, you should use INIT " > > Does this warning also apply to Systems where MultiTOS is loaded - or > maybe machines where MultiTOS is burned into ROM? The statement above applies to the single-tasking GEM shipped in the ROM of ST/TT/Falcon computers. It doesn't have anything to do with MultiTOS, because MultiTOS = MiNT + a multitasking AES (specifically, AES 4.0 and 4.1). A "multitasking AES" is by definition also multitasking friendly, so I don't see how the warning could apply. I don't think either that there are machines where a multitasking AES is burned in ROM. > In the end I'm curious if FreeMint could be part of the ROM... As far as I remember the code, it cannot. Pozdrawiam KMK