Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!cs.utexas.edu!uunet!uvm-gen!pegram
From: pegram@uvm-gen.UUCP (pegram r)
Newsgroups: comp.sys.atari.st
Subject: Re: Phantom Typist
Message-ID: <1502@uvm-gen.UUCP>
Date: 3 May 90 15:22:01 GMT
References: <90.115.09:59:04@ira.uka.de>
Sender: nobody@uvm-gen.UUCP
Organization: EMBA Computer Facility, Univ. of Vermont, Burlington.
Lines: 27

From article <90.115.09:59:04@ira.uka.de>, by grunwald@Tokyo.ira.uka.de (Grunwald Betr. Tichy):
> May be your mouse cable is broken. This makes the mouse response awful, until
> the mouse breaks down and there is no more response. Because the cable moves
> the error is not stable. Try what happens, if you stretch the cable. But do
> it careful. I had that problem for several months until I had to recognise,
> that the mouse keys did not work and the pointer moves only in one direction.

> Knut Grunwald

Yes, that is a common problem, but it's not the phantom typist.
Wesley Kaplan mentions that it happens with rushed keyboard input,
especially with lots of deletions.  The same thing happened to me in
the exact same situation with Tempus II under Neodesk 2.03 and
including Turbo ST 1.6.  An awful lot of the original system was
replaced with that software running.  As was stated here on the net
before, the problem is relatively high up in the Tos - Gem software
hierarchy and possibly includes a problem with the IKBD processor
firmware.  I have the crash dump (it happened shortly after I
verified that I had finally seen the elusive typist) that Neodesk
provided and will post the thing when I remember to bring it in to
work.  Hope you ST wizards can make something of it.

Bob Pegram (Internet: pegram@griffin.uvm.edu)

P.S. 
   1985 520ST (no modulator), Tos 1.0, 2.5meg RAM, + hard disk. 
				RBPIII 8-)