A83: Re: Re: Re: Filesystem-scanner
[Prev][Next][Index][Thread]
A83: Re: Re: Re: Filesystem-scanner
The point is that something crashed and messed things up. It's ram. It was
a bug. You don't know what was messed up. So you reset and send everything
back to it, and fix the bug in the program that caused the problem (or if
it's not yours, don't run it anymore). If you have something on your calc
that you _really_ need for a class or something, then either don't run any
assembly stuff on it, only run things that you are certain are stable (my 86
hasn't been reset in the last two years), or have a second calc handy with
the data on it.
If you think it's something worthwhile, then go for it. But, for example,
what are the chances of just a couple bytes in the VAT getting messed up?
How do you know it wasn't more than that, or that the program's data is
messed up? Most programs are stable and don't corrupt things (at least on
the 86, would assume the same is true on the 83). If you are always having
problems with things getting corrupted, then it would be wise to figure out
which program is doing it and not use it.
> But most of the errors in the filesysten can be fixed:
References: