I got too anxious. Read the Edit2 on the first post. That will probably fix your problems.

It obviously depends on the video. But if you get around 30% compression, around 90 seconds. Meaning that it holds more video than sound.

I forgot to mention in the first post, don't garbage collect with this on your calculator. Some of the pages start with FF and the app will surely get corrupted.

It takes about 1 minute on calc to install or uninstall.

You could even pull a battery while doing a really long calculation to get a ram clear. In fact, the only time you won't get a ram clear is if the OS is doing nothing.

Or you could pull a battery, wait about 5 seconds, hold delete, then put the battery back in. That is just as effective as pulling all 5 batteries and it has saved me from several nasty crashes.

I would love to see someone glitch axe badly enough to unlock flash. And then they'd have a heck of a time trying to do all the flash copying back and forth.

Really, I would image the whole program would be one big Asm( statement.

That would actually take some work. I could either make a menu hook, which defeats the whole purpose of this. Or I could change it to some token that no one ever uses and rewrite that to say the game.

So for instance, I could take ClockOff, change it in memory to The Game. And then change the Memory Menu to display that. The only problem is that ClockOff would look funky from now on.

Edit to your edit:
    I can change any menu I like to any other option, I just can't add data, only delete it.

Problem solved, I thought about this today during school. The memory menu is still the best way to delete stuff, so why not just hide it? I put it in the Stat>Tests>Bottom. I overwrote ANOVA(, but who uses ANOVA(? (It's still in the catalog )

You can just reinstall this right over the old one, it does the whole thing so it's just redoing what the first one did.

zStart would help if combined with Omnicalc's memory block function. Of course they could always disable Omnicalc and kill it, but a simple ram clear wouldn't fix their problems.

I'll look into this and probably fix it tomorrow. I'm thinking of changing the menu data so that the Reset menu only has 1 option, which is RAM clear. I could also completely wipe out the Mem > 2 menu. Do you want that too?

Edit:
    I can just change the Mem > 2 to like sin( or something. That would kill it.

Pulling the batteries out has no effect on flash. It is the same as forcing a RAM clear by holding DEL in while you insert a battery.

Darl, I believe that your problem is that you are simply out of memory. The reason that this is not apparent though is that you have 76k left. But that 76k is not continuous. Flash is made up of sectors, and each sector is made up of 4 pages that each contain 16,384 bytes. When you archive something, it is fine if it crosses a page boundary, but it cannnot cross a sector boundary. So that 76k that you see is free is actually just the little bits and pieces left at the end of your sectors.

The reason that you managed to up your limit to 12 is that during all your memory shifting, you managed to get the programs to fit better in your sectors. Imagine trying to fill several large boxes with smaller boxes, obviously, if you do it haphazardly, you will not get as many to fit as you could if you tried some sort of strategy.

Now to make the most of what you have left. If you really want to squeeze all the space out of the calculator that you can, here is what you can do:
1. Send all you programs to your computer (apps don't matter)
2. Make sure your variable archive is clean (a reset Vars wouldn't hurt)
3. Sort them by size.
4. Send them back biggest to smallest
Hopefully, doing this will make the programs fit into the sectors in the most efficient way and you will be able to maybe fit 16 apps on. But don't forget, you only unlock an extra sector for apps when you manage to not use another 65,536 byte sector because apps and programs cannot exist in the same sector.