Path: utzoo!attcan!uunet!wuarchive!zaphod.mps.ohio-state.edu!mips!dimacs.rutgers.edu!rutgers!rochester!uhura.cc.rochester.edu!ee.rochester.edu!seah
From: seah@ee.rochester.edu (David Seah)
Newsgroups: comp.sys.apple2
Subject: Re: Running games that don't quit
Keywords: games quit
Message-ID: <1990Oct5.175244.20413@ee.rochester.edu>
Date: 5 Oct 90 17:52:44 GMT
References: <2045@oucsace.cs.OHIOU.EDU>
Reply-To: seah@ee.rochester.edu (David Seah)
Organization: University of Rochester Department of Electrical Engineering
Lines: 22

In article <2045@oucsace.cs.OHIOU.EDU> bchurch@oucsace.cs.OHIOU.EDU (Bob Church) writes:
>There was a post a short while back about running games that had
>been converted to Prodos. The poster said that they usually would
>not quit correctly and he had to reboot. How about running them
>with Davex active? With Davex I can do a control-reset and get
>back to it's control. I realize this probably isn't all that 
>essential but fixes can be fun too :-).

A lot of the Old Classics took pains to protect themselves from control-
reset-happy hackers.  They either would reroute the reset vector to some
internal routine (like a memory purge or just a restart) or just futz
the power-up byte at $3F4 to force a simulated cold-reset.  In either
case, the link back to Davex would be dead.  Davex might even be dead,
too, since alot of your Old Classics treated all of memory as their
stomping ground and, well, stomped over everything...just the way I
like it! :)

...a DOS 3.3 dinosaur in a ProDOS world...that's me :(
-- 
Dave Seah |       Omnidyne Systems-M         | INET: seah@ee.rochester.edu  |
          | "User-Friendly Killing Machines" | America Online: AFC DaveS    |
  ^..^    +-----------------------------------------------------------------+