Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!usc!samsung!uunet!mcsun!unido!fauern!faui43.informatik.uni-erlangen.de!csbrod
From: csbrod@informatik.uni-erlangen.de (Claus Brod (turo))
Newsgroups: comp.sys.atari.st.tech
Subject: Re: 1st Word Bug
Message-ID: <1991Jan10.122132.14795@informatik.uni-erlangen.de>
Date: 10 Jan 91 12:21:32 GMT
References: <1590@tharr.UUCP>
Organization: University of Erlangen, Germany
Lines: 48

steveh@tharr.UUCP (Steve Hamley) writes:
>*****************************************************************
>*
>* This file was created by SYS_MON, the ATARI ST System Monitor,
>* copyright by Karsten Isakovic, Berlin
>*
>* It is forbidden to publish this file or extracts of it without
>* the copyright header !
>*
>* Return  Program Func     Stack    Function     Arguments
>*   addr     name   no      addr        name

> $0BA26C WORDPLUS X_38   $0CF360  Supexec        CODE $0AA9D6 ->
>* Disables the key repeat by making a supervisor mode call to a routine which 
>* clears bit 1 of system variable $484, conterm. This seems to be so so you 
>* can't enter keypresses faster than they can be processed. (You know the 
>* problem, repeat a command key too long and you sit around waiting for the 
>* screen to catch up.)

This is the only practical way to avoid this problem properly. I do
the same in an editor routine of mine. I _know_ that it is not OK
to do this as you are struggling with AES and XBIOS keyboard routines
at the same time, but there seems to be no better way, and it
works with all available TOS versions.

If someone out there (maybe @atari) knows some better way to handle
this, please let me know. We are not satisfied with this solution,
but it's the best we could find so far.

Apart from that, I really think the phantom typist is a TOS bug.
It occurs in many programs, not only in WPLUS. Some friend of
mine told me at the last Atari fair in Duesseldorf that he
thought he had found the reason for it, and that it lies in
an internal TOS routine that is responsible for some keyboard
functions. It is not only called as a normal subroutine but also
from an interrupt, and it is not properly guarded to avoid
problems when the interrupt occurs while the main program is
in this routine at the same moment. A description of this has
been sent to Atari US (to Ken Badertscher, to be exact), as
I have been told. So maybe Ken knows more about it now and can
shed some light on it?


----------------------------------------------------------------------
Claus Brod, Am Felsenkeller 2,			Things. Take. Time.
D-8772 Marktheidenfeld, West Germany		(Piet Hein)
csbrod@medusa.informatik.uni-erlangen.de
----------------------------------------------------------------------