[A83] Re: What is the problem with flash writes (in general)
[Prev][Next][Index][Thread]
[A83] Re: What is the problem with flash writes (in general)
Apps can do it, I don't know about other programs. Apps can create an APPVAR
and bcall ArcUnarc. It might be wondered, however, what the point of this
would be, since the sorts of data usually stored in APPVARs is (usually)
small stuff, which best resides in RAM. An exception to this is TI's
ridiculous Transformation Graphing App, which for animations creates a
picture of each and stores all of them into an APPVAR. This thing can get
huge, and it might be nice to archive it in this case (isn't going to be
changed once its created anyway, unless its deleted...)
Generically speaking, writing back to the program is bad style. The only
case where it might be useful is high scores. Using something such as an
APPVAR ensures that settings are specific to individual calculators.
Consider the all to common problem of someone getting a password program
from someone else, but not knowing what their password was, and then the
person they got it from mysteriously dies... Okay that last part doesn't
usually happen but you get the point.
-----Original Message-----
From: assembly-83-bounce@lists.ticalc.org
[mailto:assembly-83-bounce@lists.ticalc.org]On Behalf Of james l
Sent: Monday, July 09, 2001 10:22 AM
To: assembly-83@lists.ticalc.org
Subject: [A83] What is the problem with flash writes (in general)
Not really that no one has been able to do them in their programs, but the
fear of failure.
"Minimum 1,000,000 program/erase cycles per sector
guarantead" -Am29F400B.pdf
(amd's tech doc on it)
Writing to it for everything, would be a hazard, but having programs do
write-back to the flash for storage, shouldn't hurt at all. (if we could do
it)
Just my .02USD
James L.
Follow-Ups:
References: