Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!lll-winken!lll-lcc!well!dsmall
From: dsmall@well.UUCP (David Small)
Newsgroups: comp.sys.atari.st
Subject: Re: magic sac info wanted
Message-ID: <4136@well.UUCP>
Date: Sun, 4-Oct-87 23:58:47 EDT
Article-I.D.: well.4136
Posted: Sun Oct  4 23:58:47 1987
Date-Received: Wed, 7-Oct-87 07:21:58 EDT
References: <5468@drutx.ATT.COM> <1500@dasys1.UUCP> <2564@alvin.mcnc.UUCP> <21084@ucbvax.BERKELEY.EDU>
Reply-To: dsmall@well.UUCP (David Small)
Distribution: comp
Organization: Whole Earth 'Lectronic Link, Sausalito, CA
Lines: 13
Keywords: magic sac, st
Summary: Hardware accesses


In article 5084, jmorton@euler.Berkeley.EDU asks what sorts of things
crash the Magic Sac.
Programs which access the SCC serial chip directly cause a bus error on
the ST hardware and fail. Also, programs that directly access the VIA or
IWM chips can fail. Magic Sac ver. 4.32 and above include code which
examines the bus-error post-mortem information and attempts to recover;
it's successful a good portion of the time.
  Copy protection schemes that go straight to the disk controller (IWM)
are still the biggest cause of problems.

-- Thanks, Dave
p.s. I'm rather a net novice here but will answer questions if you
send themmidrgente, te,