What happens if you make a program with more than 65,535 bytes?  I ask because the program definition in user memory has two bytes for size, which leads me to the concusion that FFFF is the maximum size.

Wouldn't the next data past 65536 overflows elsewhere in the memory, causing potential issues?

It would probably have to be slightly smaller, so the VAT entry and such could fit in archive.

Each sector of archive is 64KB, and programs cannot overflow from one sector to another. So, a couple of bytes are used at the beginning of the sector for OS purposes, then a number of bytes would be stored for the backup program name and such, then the rest would be available for program data.

I tried editing the filesize once w/ a hex editor to FFFF and my calc acted randomly when I checked the memory, like the filesize is missing and/or the RAM clears...

I don't remember exactly... I have to reproduce some of my favorite glitches I discovered while hacking my calculator, then post it on the forums.

I actually got a Bad Address error today, when trying to unarchive Sam Heald's Mario, of all things. It gave a large memory leak, too. I had to manually create a new program, copy the data to it, and delete the old one. Calcsys is awesome that way

Calc84 I had this happen on some of my games before without even running ASM. It's annoying when you doNt know how to use Calcsys well or don't have it handy , cuz you can lose lot of progress