Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site dartvax.UUCP
Path: utzoo!decvax!dartvax!mss
From: mss@dartvax.UUCP (Mark Sherman)
Newsgroups: net.micro.mac
Subject: Thunderscan and Appletalk
Message-ID: <3155@dartvax.UUCP>
Date: Tue, 28-May-85 08:45:51 EDT
Article-I.D.: dartvax.3155
Posted: Tue May 28 08:45:51 1985
Date-Received: Tue, 28-May-85 20:21:13 EDT
Distribution: na
Organization: Dartmouth College, Hanover, NH
Lines: 21


We just got a Thunderscan. According to a brief note in the package,
Thunderscan has difficulties on a Macintosh which has been used on
Appletalk. Apparently Appletalk leaves some information in nonvolatile
memory (I guess the parameter ram/clock chip) which Thunderscan relies
on in some way. The suggested "work around" is to turn off the
Macintosh, remove the battery for the clock, wait thirty seconds for
the charges to trickle away and then put everything back together.
Although Thunderscan claims to be coming out with a version of their
software which will interact properly with Appletalk, I thought an easy
patch in the mean time would be to write a program that flips those
magic bits to something benign -- it appeals to me more than taking the
battery out of machine. A quick call to Thunderscan (supposedly a
technical support person) revealed no information: all he knew was that
there was a problem with the interactions between Appletalk and
Thunderscan but he had no idea what a parameter ram was nor what could
be stored there.  My suspicion is that some of the "reserved for future
use" bits have been used, but rather than performing experiments, I'm
asking if someone else has already solved the problem (or at least
knows the technical info that I need to write the program).
		-Mark