From mint-bounce@lists.fishpool.fi Sun Sep 12 13:24:32 2010 Message-ID: <4C8D0BDA.6060608@online.no> Date: Sun, 12 Sep 2010 19:20:26 +0200 From: Jo Even Skarstein User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.12) Gecko/20100826 Thunderbird/3.0.7 MIME-Version: 1.0 To: mint@lists.fishpool.fi Subject: Re: [MiNT] No keyboard with GEMROM References: <4C8CFCB7.20605@freesbee.fr> <00516965.01c73262f612@smtp.freeola.net> <4C8D0169.4050107@freesbee.fr> In-Reply-To: <4C8D0169.4050107@freesbee.fr> Content-Type: text/plain; charset=ISO-8859-1 X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: joska@online.no 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 o8CHOV99022453 On 09/12/2010 06:35 PM, Vincent Rivière wrote: >> I know nothing about this stuff but I remember that one of the >> long-term aims of Mint is to get rid of the dependencies on TOS. > > Am I wrong or one of the main goals of MiNT should be to not break clean > things that work on TOS ? I hope a working keyboard in GEM applications > is not too much... Strange, the keyboard works in all apps here. But then I'm using an AES intended to work in a multitasking environment, and NOT the ROM AES. Anyway, have you tried NOHOG.ACC? Back in the days before a usable AES existed, you had to run this ACC to be able to use ROM AES with MiNT. That might still be the case. Jo Even