Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!uwm.edu!linac!att!ucbvax!UTCVM.BITNET!MQUINN From: MQUINN@UTCVM.BITNET Newsgroups: comp.sys.apple2 Subject: Re: Coca-Cola Demo Message-ID: <9104122203.AA28382@apple.com> Date: 12 Apr 91 21:56:52 GMT References: Sender: daemon@ucbvax.BERKELEY.EDU Organization: The Internet Lines: 30 On Fri, 12 Apr 91 19:18:54 GMT said: > >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 >. There are two ways of writing to the Battery RAM: 1. writing DIRECTLY to it. - This would be virtually impossible to detect, unless your PIF is examining EVERY instruction the program does. Of course, this is completely impractical and would slow things down several times. 2. Change the BRAM with the TOOLS. This would be possible to catch. This is similar to the way SAM virus interceptor works on the Mac. So, if an application is doing number one, it's impossible to prevent. If it's doing number 2, then there shouldn't be much problem. If someone is going to write this, how 'bout going a little further and intercept drive write operations? SAM GS? ---------------------------------------- BITNET-- mquinn@utcvm <------------send files here pro-line-- mquinn@pro-gsplus.cts.com