Re: A86: Ticklish?

Re: A86: Ticklish?

• To: assembly-86@lists.ticalc.org
• Subject: Re: A86: Ticklish?
• From: Dux Gregis <assets@eden.rutgers.edu>
• Date: Fri, 03 Apr 1998 17:02:04 -0500
• Delivered-To: assembly-86-outgoing@towerguard.unix.edu.sollentuna.se
• References: <35243BAE.BDE60DE1@eden.rutgers.edu> <35244966.EAF88616@eden.rutgers.edu> <3525533F.DB8E162B@mindspring.com>
• Reply-To: assembly-86@lists.ticalc.org

If the right flag is set ( the one which enables each of those programs)
then the calc makes a certain call to page 13 when it finds an opportune
moment (ie, getkey, when it parses, etc.).  The actual name of the program
is there so that the call can load the name into op1 and call _FINDSYM.
You can disassemble each of the calls (they are one right after another) to
figure out how it sets up each program.  You can also search for the calls
to find when they are called and what the saved registers might contain or
whether or not the zero flag needs to be set.

Stephen Hicks wrote:

> Hmm....  i just looked at the dump of page $D, and was wondering what
> all those references to (sqrt)KEY, (sqrt)CMDTOK, etc, are doing there?

• A86: Ticklish?
• From: Dux Gregis <assets@eden.rutgers.edu>
• Re: A86: Ticklish?
• From: Dux Gregis <assets@eden.rutgers.edu>
• Re: A86: Ticklish?
• From: Stephen Hicks <shicks@mindspring.com>

• Prev: A86: ase
• Next: Re: A86: Ticklish?
• Index(es):
  • Main
  • Thread