Path: utzoo!attcan!uunet!aplcen!uakari.primate.wisc.edu!zaphod.mps.ohio-state.edu!rpi!pawl!kudla From: kudla@pawl.rpi.edu (Robert J. Kudla) Newsgroups: comp.sys.cbm Subject: Re: Super Snap Shot Cart Detection?? Message-ID: Date: 29 Sep 90 05:05:07 GMT References: <418@news.nd.edu> <1990Sep15.171530.12692@xenitec.on.ca> <436@news.nd.edu> <438@news.nd.edu> <-VJ%B=+@rpi.edu> <443@news.nd.edu> Organization: Rensselaer Polytechnic Institute, Troy, NY Lines: 28 In-Reply-To: treesh@bach.helios.nd.edu's message of 24 Sep 90 15:11:46 GMT >>>>> On 24 Sep 90 15:11:46 GMT, treesh@bach.helios.nd.edu said: t> Anyways, you say that some of your software does not work with the t> cart plugged in, even if its in disabled mode right? Thats just t> want Im looking for. I am not trying to get my software to make t> use of the routines inside the cart, Im just trying to let my t> software know if the user has that cart plugged in, so that if it t> does see it, it will erase itself!! Aha, but I'm using an old version of the Final Cartridge, not Super Snapshot. There's a *big* difference.... the FC had little ROM and no RAM, so it had to use the computer's resources and was *never* fully transparent. It also did trash the cartridge ROM bytes, I believe. t> problem with it is that its makes ANYONE a hacker. Im trying to write code t> that can not be vied in the montior, saved to the disk. That's nice, so I just disassemble the damn thing and reconstruct the object module as it would exist in the machine while it's running. Then again, I suppose that's a little more complicated than pushing the button. t> I guess you would say Im sorta an anti-hacker! Im more into the protection t> then the breaking of the protection! Yeah, but you're fighting a losing battle. If a program can be executed, it can be copied - it might take an inordinate effort, but then, that's what makes hacking fun, no?