Re: A86: state flags

To: assembly-86@lists.ticalc.org
Subject: Re: A86: state flags
From: Chris Phelps <chicane@reninet.com>
Date: Mon, 08 Nov 1999 17:59:17 -0800
References: <0.cf10bca6.2558c79d@aol.com>
Reply-To: assembly-86@lists.ticalc.org


ComAsYuAre@aol.com wrote:

> In a message dated 11/8/99 7:39:13 PM Eastern Standard Time,
> croop@oregontrail.net writes:
>
> > hmmm... that sounds rather complicated.  I now have two questions:
> >  1)  Yeah, I know, this is one of the most asked questions on the list,
> >  but I deleted most of them...  Is there any place in memory that is
> >  relatively safe, even after your program has run?  I'm making an
> >  interrupt TSR that may take up more than 200 bytes, but I don't want to
> >  be dependent on a PRGM variable or anything.  Hopefully I could store my
> >  extra code somewhere that the calc doesn't use. Is there such a place?
> >
> >  2)  How would I go about detecting a specific keypress at the homescreen
> >  from inside an interrupt TSR?  I don't suppose there's a temporary
> >  keypress buffer or something?
>
> What you want is a [sqrt]key program which will handle keypresses.  I would
> recommend checking the code to yugi2 for an example program.
>
> ----
> Jonah Cohen
> <ComAsYuAre@aol.com>
> http://linux.hypnotic.org/~jonah/

If its less than 400 bytes, you can use the regular int place, plus the silent
link 200 byte area.

Later,
Chicane

Follow-Ups:

Re: A86: state flags

From: Cassady Roop <croop@oregontrail.net>

References:

Re: A86: state flags

From: ComAsYuAre@aol.com