darn lucky 83+ owners with their fancy sdk. I wanna screw with my 89's settings one of these days :P

by the way, what does it mean by "chatting with other calculators" and "remote control of an 89/92/92+"?

This isn't the same thing as the SDK, though it was created using the SDK. And the 89 SDK is coming, hopefully, so you just wait. :-)

--BlueCalx

I meant that they're lucky they have their fancy sdk to create cool flash apps like that

how far off is the 89 sdk?

I suggest you browse the included cool.txt to see exactly what this is. Basically, you can "chat" (send realtime messages) between any two calculators, or control a 68k calc, so you send it vitual keypresses, and it sends back any response to the homescreen.

-Dan

What exactly is protecting your programs mean? Are the save from archive and ram clear?

No, it means making them so the user can't edit them.

Well, doesn't that mean that CalcSys can also UNprotect them as well? Besides that it's a FLASHAPP, what good is protecting anything these days?

~ferich

Well, the only thing protecting programs is good for is making sure you or someone does not edit them and mess them up. I sent someone basic game (gangwars) and the accidently messed up the whole game, luckly I could replace the code that was screwed up. Some people also cheat with unprotected games (making it so you have unlimited money). Anyway if you don't want people to be able to code rip from the program, you should make it in assembly and not give out the source code.

P.S. Can someone come out with a basic to assembly converter for the ti 83. They have one for either the ti 85 or 86 (I forget) I don't see why they can't make one for the 83. The converter does not make the program faster though, too bad, it only makes it so you can't code rip from it.

P.P.S. Someone can uncompile an assembly program, but it's hard so assembly is safe, for now.

About your last statement:

Assembly programs are very easily de/uncompiled. I could do in a several seconds with ease.

However, there is a small problem, and that is variable names and labels and other things are really messed up.

i.e. If in the original program, NumberOfTimesPersonDied is a variable, then in the uncompiled version it might look like just random numbers (like $45A9). Same with labels...instead of jp MainLoop you might see jp 1203...or something of that matter.

This is totaly unrelated but when backing up your 83+ to a computer using a program what is the appropriate name to use? I'm using cal at the moment.

I usually use Matt because that's the name I always use, even when I'm not backing up my calculator using a program.

-Matt ;)

how much archive space does calcsys v1.1 take? the older version i think took 16384 bytes.

The exact same amount as a matter of fact...All applications on the 83+ take up a multiple of 16k.

-Dan

is it possible to make a flash app to make the 83+ more like the 86 (the menu-based system/able to key in commands from home screen rather than using menus/switch from caps to lowercase/et cetera)?

im not very knowledgeable with the ti-83+ or other flash clacs... (ive only held an 89 twice and it took me 10 min the first time to figure out how to run mario) Is this app for the ti-83+ able to do these type of things beacuse of the fact it is a flash app or can all calcs do these things from regular asm

Well, a program like Calcsys could be written to run in RAM, but its much better off as an application for a couple of reasons. First, It is very easy to crash the calculator on purpose, or by accident, from Calcsys. If Calcsys was in ram, then it would be lost once you crashed the calculator. Second, It doesn't require a shell to run. (You can run asm progs without a shell on the 83+, but only if they are under 8k or so). Third, It would take a lot of working because in general only 8k programs are allowed, while calcsys is 16k. Fourth, you save 16k of ram, by having it always in archive. Fifth, its easily accesable from the APPS menu :).

-Dan

Actually, I don't believe that the compiled code for CalcSys is actually 16K (I am not sure how big it is because I have not downloaded it). The reason it takes up 16K on the 83+ is because an app, no matter how big it is, has to take up a multiple of 16K bytes in the Flash ROM. This is the page size of the memory. You could have an app that is 100 bytes compiled, and it would still take up 16K on the calculator. This was meant just to be informative, not to cause arguments. Anyways, this sounds like a pulchritudinous application for 83+ users. I have an 83+, but I rarely use it (I prefer my 89). Way to go TCPA!

You're quite right...its a full 120 bytes short of taking up the 16k. (I should know, I wrote the code :)

-Dan