Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!cs.utexas.edu!samsung!umich!terminator!merit.edu!jgs
From: jgs@merit.edu (John Scudder)
Newsgroups: comp.sys.mac.misc
Subject: Re: Wanting to snub Emulators
Message-ID: <1990Oct31.194600.5090@terminator.cc.umich.edu>
Date: 31 Oct 90 19:46:00 GMT
References: <1990Oct27.190254.8511@cpsc.ucalgary.ca> <107918@convex.convex.com> <1990Oct31.140745.12752@cbnewsc.att.com> <1990Oct31.150313.9742@wuarchive.wustl.edu>
Sender: usenet@terminator.cc.umich.edu (usenet news)
Reply-To: jgs@merit.edu (John Scudder)
Distribution: usa
Organization: U of Michigan, Merit Network
Lines: 26

In article <1990Oct31.150313.9742@wuarchive.wustl.edu> hp48sx@wuarchive.wustl.edu (HP48SX Archive Maintainer) writes:
>There is one sure way to KILL any running mac emulator in RAM on any
>machine. Just find the address of the ROM, and then start at that
>address, and place 64k or 128k  random characters, or plain zeros for
>that sake. This will surel y crash the machine if the ROM has been
>copied to RAM, but if the emulator runs using the real stuff, i.e.
>original (or fake) Macintosh ROMs, then this will do nothing.
>
>So just rewrite your program, and go for a clean kill  on pirated
>macintosh ROMs.
>
>Povl H. Pedersen
>eco8941@ecostat.aau.dk   /   hp48sx@wuarchive.wustl.edu

I believe that there is an accelerator board for the SE that caches the
ROMs in SE motherboard RAM and puts applications in RAM on the
accelerator itself.  (Accelerator data bus is 32 bits wide so is twice
as fast as the motherboard bus.  I'm not sure whose board it is, it was
a while ago.  GCC, maybe?)  The above scheme for killing emulators might
also do a fine job of killing these accelerated Macs.  It could also
potentially kill any new machine Apple chose to build which might cache
ROM to RAM (pure speculation on my part; I haven't heard of such a
machine).

--John Scudder
  jgs@merit.edu