Re: Any way to pause an EXEC?

["Jayson Smith" <nospamratguyspambegone@nospamplease.bellsouth.ihatespam.net>]

Hi,
Thanks for that.  However, there's another problem.
When the first program to be modified is loaded, it has aparently
overwritten the EXEC buffer, since the EXEC stops dead at that point.  Where
is the EXEC area of memory, and is there any way to change that to avoid a
large Applesoft program clobbering it?
Thanks.

"Linards Ticmanis" <ticmanis@gmx.de> wrote in message
news:442ab81e$0$17576$9b4e6d93@newsread2.arcor-online.net...
> Jayson Smith wrote:
>
> > I am working on a crack for an old DOS 3.3 piece of software, with the
> > author's permission.  The crack defeats copy protection and applies to
> > several versions of the software.  It loads two Basic programs and
changes
> > them a bit.  I was going to use an EXEC for this, and have users just
EXEC
> > the file to crack their copies.  I need to insure the proper disk is in
the
> > disk drive before cracking the program, and don't want to put the TXT
file
> > on the software disks.  My first thought was to have the EXEC write a
simple
> > program to prompt the user to put the proper disk in and hit any key
with a
> > "GET A$" statement but the keypress is taken from the EXEC rather than
from
> > the keyboard, not only rendering it useless but also messing up the next
> > command which is now missing the first character.  So my question is, is
> > there any way to wait for a keypress in an EXEC file?
>
> You can always read the keyboard directly in hardware by doing something
> like
>
> 10 IF PEEK(49152)<128 THEN GOTO 10
>
> This will always read the real keyboard, even during an active EXEC.
>
> --
> Linards Ticmanis