Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!mips!pacbell.com!att!news.cs.indiana.edu!noose.ecn.purdue.edu!en.ecn.purdue.edu!platkus
From: platkus@en.ecn.purdue.edu (Shawn W Platkus)
Newsgroups: comp.sys.apple2
Subject: Re: Coca-Cola Demo
Message-ID: <1991Apr12.191854.29533@en.ecn.purdue.edu>
Date: 12 Apr 91 19:18:54 GMT
References: <8539@crash.cts.com>
Organization: Purdue University Engineering Computer Network
Lines: 19

In article <8539@crash.cts.com> plucky.duck@pro-midnightex.cts.com (Terry Guelfo) writes:
>In-Reply-To: message from u9050728@cs.uow.edu.au
>
>It is not a demo, but a disk full of utilities.  Included are Block Warden,
>SpeedySmith (don't use it if you don't like things to write to your BRAM),
>a bunch of other block editors, etc.  It is chock full of stuff.
>



This gives me an idea.  Is There a way to write a desk accessory or an init
that could detect if something was writing to battery ram?  Maybe intercept it,
and ask the user if they want to abort or proceed?  I don't know too much about
how the battery ram operates as for as programming goes.

Thanks

Platkus
.