I am asking this just to see what the general consensus is amongst you guys. Will, any program, over some time of usage on a system (with or without interference from other programs), eventually become unstable. If so, why?

I have posted this both here and on cemetech.


Would it be possible to have a patch made for a TI-84+ SE or any type of graphing calc so that you create a System Restore point, just like on Windows. And that this "restore point" should encompass the OS itself, archive, RAM (optional), and the certificate. And, if anything should happen that would make your calc's OS go down or even the certificate be damaged, the calc intercepts the corresponding error message and gives you the option of entering System Restore, and undoing whatever caused the problem.

I'm already started on the optimizations section.

Quote

Valid label specifications may be from 1 to 99 and from A to ZZ.

I know this is being nitpicky, but can't you use _theta_?

Umm. Good question. Can u. I never got that high, as I started in order.

Because, the "calc off" command doesn't really turn off the calc. It just turns off the LCD, but the processor moves forward onto the next instruction. So when you press ON, the Pause 1000 is already done, so now "HI" is on the screen.

At least I think thats how it works. correct me if I'm wrong.

Check the size of the program itself. Here's what I see...

Whenever you run the "CalcOff" hex (Asm(EF0850C9)), the calc turns off, but the program doesn't quit. Then, as it turns on, the calculator's Startup App relaunches the program again. Thus, each time the program is used, you add another running instance of the program to memory, and that causes your "missing RAM".

Well, I mean similar to this:

PrgmA

:While 1
:PrgmA
:End

I am starting to read in a minute. So far, though, I noticed something:  Your ' characters show up as Õ. For example calculatorÕs.

This may be because I started in Word and then converted into .rtf. I'll look into it.

Err, this might sound kind of bad, but...

Quote from: ACaglino

This is very dangerous. There are no errors produced.

Not true.  It is not very dangerous if you know what you are doing, and errors *are* produced.


I'll make that clarification, thanks.

Quote from: ACaglino

The RAM is relatively unorganized and unprotected.

Not true.  It is quite organized.


Do you have any sources that can help me explain its memory structure?

Quote from: ACaglino

A fixed part of the calculatorÕs RAM cannot be edited, used or modified.

Yes it can, it's just dangerous.


*In TI-Basic, it can't. I'll clarify, though.

Quote from: ACaglino

-TI-84

There is no such thing.


Ok.

Quote from: ACaglino

a program designed for use on a TI-83 Plus will not work on a TI-83 or lower

Yes it can.


I'll switch that to: "While some programs written for the TI-83 Plus will run on a TI-83 or lower, there are just as many that experience compatibility issues." How's that?


I don't mean to nitpick, but I'm trying to help you make a good tutorial.

I welcome it. Keep 'em coming.

Actually, I think the only way to really damage your calc with assembly is if you unlock flash and do a bad manipulation.

I'm not going to delve that deep into it.


Also you might want to specify that the total calc RAM is 32 KB and that the use can only use 24 of it. Right now it seems a bit like you say the entire RAM totals 24 KB.

Is there some sort of "map" of the memory I can enclose?

Ok, got more time to read now. On chapter 3, now.

For planning, I would add a note that if someone is new to the language or never coded a game before, he should start small. Starting too huge without making sure if you can do a project and if it's feasible at all can discourage you.

I'll mention that.


I would also give some references to memory leaks in the Lbl/Goto part, warning people that misuse of them can cause errors when the program is running for a while (and slow down).

Can you elaborate a little?

Edit: Also, as a side note, if I have left out any important topics or you want to add something to it, please either post here or email to me at [email protected]. I'm pretty sure I've missed at least one major topic.