That's ok, I already figured out the format. It just looks like you put the vat entry in front of the program data. Very simple to do.

Nice job!  That's really nice. 

Ok, new idea, maybe I can make a group variable in ram and then archive it. That would be much simpler, I just have to figure out how groups work. It is also so anti-TI to have a group in ram.

While it defeats the purpose of having groups (you'd just be duplicating the RAM variables in RAM), you absolutely could have done this using _archiveVar. That's a subroutine of _Arc_Unarc, the latter which has all the checks to make sure you don't try archiving a group or something.

Quote from: thepenguin77 on July 06, 2010, 02:26:11 pm

Ok, new idea, maybe I can make a group variable in ram and then archive it. That would be much simpler, I just have to figure out how groups work. It is also so anti-TI to have a group in ram.

While it defeats the purpose of having groups (you'd just be duplicating the RAM variables in RAM), you absolutely could have done this using _archiveVar. That's a subroutine of _Arc_Unarc, the latter which has all the checks to make sure you don't try archiving a group or something.

I did use _archiveVar. The only problem was that wiki ti didn't have the inputs right, you have to call _chkFindSym right before you use it.

And ram groups are pretty funny. Since the os expects them to be in archive they get pretty glitchy and tend to clear ram when you ungroup them.

Well here it all is. The unsquisher takes the program name in string 1, using the same syntax for programs as the grouper, and converts it into hex code in a program of the same name just with A as its first letter.

"GROUPER2->Str1
Asm(prgmUNSQUISHER

then later
Rcl prgmAROUPER2

Now, can you have multiple programs in Str1. And I am at a loss. Where do you define the name of the group itself and where do you define the programs to be included? And, with the unsquisher, what happens if you unsquish and a program already exists in RAM. Overwrite or skip? and is it auto? cuz it would be best if it is auto.

And can you please provide me with a sort of readme for the stuff- i dont want to make any mistakes.

And thanks. You guys rock.

Btw just one thing: make sure those routines are safe and that you don't do bad mistakes while using them, since it involves writing to Flash. Accidentally overwriting the OS certificate == bad

No, no, no. I would never write to flash from a basic program lol. That's just scary. I make a group variable in ram and then archive it.

Group2:
Input: Str3 = group name, must be 8 characters, use spaces if it's not 8, Ex: "GROUP___"
         Str4 = programs to group, each name is 8 characters with a + or - prefixing it to show it's type
                + = unprotected/unlocked program
                - = protected/locked program
                Ex: "+A_______+BASIC___-PHOENIX_-GROUP2__"
Then just run group2, or it's hex equivalent, and your group from string 3 will be made with the programs in string 4.

Unsquish:
This program is so you don't have to type in all 500 numbers by hand.
Input: Str1 = program name, must be 8 characters with + or - prefix, Ex: "-GROUP2__"
Output: A program will be made with the same name as the original, except the first letter will be an 'A'.

Then run it and AROUP2 will be made which you can recall the numbers from.


Both of these programs auto overwrite. The group one makes a program and a group but deletes the program, so don't name your group the same as your program. Ex: Your game is call GAME, you go to make a group called GAME, your game just got deleted in the process.

By doing the auto overwrite, I basically eliminated any chance of you accidentally clearing ram, (which would suck.) Also, if either of them error, you won't really know aside from they won't have completed their task.

Edit:
    I am stupid, during my final optimize I made a little error. Fixed now though. Also, I just tested, if you don't have enough memory, thankfully you just get an error memory.

Quote from: DJ Omnimaga on July 06, 2010, 07:04:18 pm

Btw just one thing: make sure those routines are safe and that you don't do bad mistakes while using them, since it involves writing to Flash. Accidentally overwriting the OS certificate == bad

No, no, no. I would never write to flash from a basic program lol. That's just scary. I make a group variable in ram and then archive it.

Oh ok phew, I thought those programs wrote directly to Flash instead of RAM then archiving.