Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!cbatt!ihnp4!qantel!lll-lcc!lll-crg!seismo!cmcl2!lanl!dlc
From: dlc@lanl.ARPA (Dale Carstensen)
Newsgroups: net.micro.mac
Subject: Re: Odd Mac+ behavior (and "mouse thaw" FKEY?)
Message-ID: <8018@lanl.ARPA>
Date: Sat, 27-Sep-86 01:43:36 EDT
Article-I.D.: lanl.8018
Posted: Sat Sep 27 01:43:36 1986
Date-Received: Tue, 30-Sep-86 06:03:11 EDT
References: <328@hydra.riacs.ARPA>
Organization: Los Alamos National Laboratory
Lines: 26


 julian@icarus.riacs.edu writes:
> Here's a weird one that just started last night.  When I double click a
> certain folder on my hard disk the system forgets to update the cursor
> with the mouse position and i have to reboot the Mac. It still responds
> to the mouse button, as clicking causes the finder to do its normal
> highlighting.  It just won't move.
This sounds like the common "mouse freeze."  Any memory reference to the I/O
area of memory (above 0x800000?), even though not exactly on an I/O address,
will reset the SCC that tracks the mouse X and Y movement, disabling the
interrupts.  Something in the "Desktop" file of your hard disk evidently
causes Finder to reference such an address, but fortunately not if you
use "Open" or Command-O.  You could rebuild the desktop by holding down
whatever keys cause rebuilding the desktop while mounting a volume.

It is advertised that the TMON debugger includes "mouse antifreeze" which
corrects this problem soon after it happens.  I have been able to write a
program that gets the mouse moving again, but the Imagewriter remains killed
off until the next reboot.  The program is semi-acceptable in the Aztec C
shell environment, but in the Finder environment, you can't execute a program
when the mouse won't move!!  What is needed is a "mouse thaw" FKEY, and one
that restores Imagewriter operation, at that.  Does anyone know the secret to
making it work?

  dlc@lanl.ARPA
  {cmcl2|ihnp4}!lanl!dlc.UUCP