From mint-bounce@lists.fishpool.fi Sun Mar 7 19:09:34 2010 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:subject:mime-version :content-type:from:in-reply-to:date:cc:content-transfer-encoding :message-id:references:to:x-mailer; bh=GMWgUHdZdAXSgn5x2QESYKCMkezs75IJeFzvvImGkLQ=; b=WbZoXpw9cpz/KDjlTdwZvpgHKZK/hbHxTr38lgRRw+UEtRt8UFrXRAg6i07UrgF97S bEnIkvNwWk2wYhAsODOnL21c283vCEAwOuvrEf6F9iGTA9y4/+/9cQ+XfWc9M9ncTpmE +WA2zkaMCLm/ZyuDSkenFminf/RFqJo4m4QVM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; b=QaYWZdDoebbtGnsw2ECEBfKEuOF/tBlywdT4ZLVpOex5FK8z3ta4+5gCOrLAYHMci5 THiQ3h9b5pAi74Lij0u1J5R3rPi/fq9BM/xBf4mYShKlum8ZXDTSe8K6ckdp0yF6ypeK siG8HFvuGceMqqHfi4yqwq117eoezOr2S576E= Subject: Re: [MiNT] Patch for xaloader.prg Mime-Version: 1.0 (Apple Message framework v1077) Content-Type: text/plain; charset=us-ascii From: Peter Persson In-Reply-To: Date: Mon, 8 Mar 2010 01:07:48 +0100 Cc: "mint@lists.fishpool.fi" Message-Id: <56900C82-0EB8-4D48-9268-C5613C238BF2@gmail.com> References: <72454075-6FA5-46CA-A174-A3AE573771A6@gmail.com> <20100301222525.bcb94ec5.mandin.patrice@orange.fr> <04F5AE6B-D53F-4EE1-BA57-9BA46392BD13@gmail.com> <1B8C9039-CFB4-4675-9E79-5D1CC4F54DAC@gmail.com> <0D259770-D6AF-408E-B721-2BD14DA6E237@gmail.com> To: "Helmut Karlowski" X-Mailer: Apple Mail (2.1077) X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: pep.fishmoose@gmail.com Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: List-subscribe: List-owner: List-post: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by mail.sparemint.org id o2809XE7032526 On 8 mar 2010, at 00.08, Helmut Karlowski wrote: > How does your loader run the kernel? Does it exit after launch or does it stay in memory? > > If it exits size doesn't matter. It stays in memory (pexec mode 200 isn't available until the kernel is installed). It uses the standard Pexec() call, and copies the DTA address from the parent (TOS) to allow the kernel binary to continue loading stuff from the auto folder. -- PeP