From mint-bounce@lists.fishpool.fi Thu Jul 23 12:56:58 2009 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:references:message-id:from:to :in-reply-to:content-type:content-transfer-encoding:x-mailer :mime-version:subject:date:cc; bh=Gkm8Ddfpnf/iHmO6xKf3dlfpPkaWLFuaf+d16+m6Bu0=; b=iMRjITJfR9kGoKhFWaUqoa9oTF8B+UMge7G2jn7jRTgsgDyP6FpdqZOLktW9NLLS3p C5aUlNNVbdSjLDSe+wQr1PS7dXs5EkDygsbtrW623+ixJGmgtXTe4do1TN/brTUAVNRW 1bnRetcwIuw2JmH+Ccu4whL/eiNybSV7/MKd8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=references:message-id:from:to:in-reply-to:content-type :content-transfer-encoding:x-mailer:mime-version:subject:date:cc; b=yEVTZLRtf0BGTIOr66t1Z4l0zdzxWYxHvLNyetqCluMeySl/igJ6ZA0dAZWsrI5BTh fDKh5EvKnzjTDHZk4WxrgbUQnBjUmhdY+dMXyxbRhAbZBRuVLNeSjM5taaEtMixREzTc guDq9qbMz+yPLzLhTOITrMrwEyXWlQ9C+59UU= References: Message-Id: From: =?utf-8?Q?K=C3=A5re_Andersen?= To: Lonny Pursell In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes X-Mailer: iPhone Mail (7A341) Mime-Version: 1.0 (iPhone Mail 7A341) Subject: Re: [MiNT] XaAES Date: Thu, 23 Jul 2009 18:52:55 +0200 Cc: "[MiNT] Mailing-List" X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: kareandersen@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 n6NGuwI1005344 On 23. juli 2009, at 18.32, Lonny Pursell wrote: > on 7/23/09 6:46 AM, Konrad Kokoszkiewicz wrote: > >>>> I don't know anything about this stuff, but MiNT should behave >>>> exactly >>>> as TOS, especially for programs that are not MiNT aware. >>>> This looks like a bug in MiNT... >>> >>> If someone could explain the intention of this, there could >>> possibly be a >>> workaround in XaAES. Until then you can just disable this feature >>> in MiNT by >>> #defining MM_INSERT 0 in keyboard.c, as I wrote before. On my MiNT >>> the >>> Bconin-returns are ok now. >> >> It is me who basically wrote the keyboard.c module, but it was so >> long ago >> that I don't remember such details. I mainly used the Atari >> Compendium as >> a reference, and own experiments to verify, if the reference is >> correct. >> It is possible that it is written there and I missed failed to verify >> that. >> >> Anyways, if you're sure that it will improve the compatibility of the >> keyboard behaviour so that it will behave more like TOS, fix that. >> It is >> the intention of the module to emulate the TOS behaviour as closely >> as >> possible. > > Speaking of keyboard.c > > This section: > > # if 0 > /* bit 2 of conterm variable decides, whether we > * put the shift status to the buffer or not. > */ > if ((*(uchar *)0x0484L & 0x04) == 0) > c0 = 0; > # endif > > Shouldn't this be bit 3 ?? > > > -- > Lonny Pursell http://www.bright.net/~gfabasic/ Nope, count from 0 :) Also, #if 0 #endif is, the c preproccessor equivalent of remming out a bunch of lines... -Kåre