Re: A85: Interesting discovery

To: assembly-85@lists.ticalc.org
Subject: Re: A85: Interesting discovery
From: Dines Christy Justesen <c958362@student.dtu.dk>
Date: Tue, 22 Sep 1998 19:18:20 +0200 (METDST)
Delivered-To: assembly-85-outgoing@towerguard.unix.edu.sollentuna.se
In-Reply-To: <1ce36678.3605c1ff@aol.com>
Reply-To: assembly-85@lists.ticalc.org


This bug was discovered a long time ago, but no one has been able to find
anything useful to do with it. Aparently when you press space and then
solve it messes up the memory, which is  why Usgard is 12 bytes. The size
of a ver is based on the information in the to first bytes of the var.

Dines

__________________________________________

Dines Justesen
Email: c958362@student.dtu.dk
WWW  : http://www.student.dtu.dk/~c958362/
__________________________________________

On Sun, 20 Sep 1998 PXGray@aol.com wrote:

> 
> Does everyone know about the way to screw up the memory after a memory
> erasure?
> 
> 1. Go to the solver and put in a blank space (" ") as your equation.
> 2.  Ask it to solve.  It will error
> 3.  Go to the catalog and put any function in the 3rd custom menu slot
> 4.  View your xStat list.  It should be filled with hex garbage.  Now,
> anything you do in the memory, aside from erasing it (which, by the way, fixes
> what you have done) will cause an error overflow.
> 
> I did this same procedure, except I had Usgard installed, along with some
> games, and now Usgard reads as a 12 byte string.  I need to know if there is a
> way to confirm the calculator's reading.  I am not yet sure if that is the
> cause of the error, but it is only lead I have right now.  Can someone else
> try it?
> 
> -Gray
>

References:

A85: Interesting discovery

From: PXGray@aol.com