Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!UICVM.BITNET!U46050
From: U46050@UICVM.BITNET ("JOHN ZAFIRIS ")
Newsgroups: comp.sys.atari.st
Subject: (none)
Message-ID: <8904120448.AA24499@ucbvax.Berkeley.EDU>
Date: 12 Apr 89 04:23:18 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 34

>Date:     Wed, 05 Apr 89 10:54:12 BST
>From:
>USQB015%LIVERPOOL.AC.UK@Forsythe.Stanford.EDU                        Subject:
>Re: how to kill a mouse cursor
>To:       INFO-ATARI16@SCORE.STANFORD.EDU
>Easy,
>     Use A-line instruction 10 $a i.e. opcode $a00a
>e.g. put exactly this instruction in your code (if you've not heard of line
>A instructions this may seem a bit wierd, but I
>assure you it works)
>                                       dc.w     $a0
>Mark Powell

sorry for the slightly butchered retelling of the message but...
I am familiar with the line-A calls and the VDI ((or is it AES)... the GEM
type) calls for mouse cursor handling.  None clear up the problem.
I assumed that calling the hide mouse line-A opcode several zillion times
and then using either the line-A show mouse code with a cleared "mouse hidden"
counter or the VDI (?) code to show the mouse cursor no matter how many times
it was hidden (which works otherwise) would fix the problem but it did not.

My god... is that some kind of badly mutilated English up there or what?

anyway, I am still up that mouse hiding creek and have no system software
paddle to save me.

The desktop does not have the problems my shell has.  What does it do?  I have
tried all the leagal ways of fixing the problem that I can think of.  Does the
desktop do something illegal?  But then that would actually be legal
just undocumented.  (Atari-speak)

any helpful ideas still welcomed...

                                                         ...John