If it's only 4 bytes difference, is there a way to fix it with calcsys?
And what do you mean by deleting realvar R? I don't think I used it.

(Btw I think it would be a good idea to add Grammer 2 to the downloads section if Grammer is already there)

Oh, also, I found the problem...kind of.
The problem wasn't in solve(0, (I think), but rather in Archive "UROL3Sav1
It archives, but it hangs and gives me ERR:MEMORY

It looks like you are either overwriting a variable (pointing to map or tile data) and not restoring it, or you are creating new data and not restoring pointers. I would make sure to unarchive stuff at the very beginning of the code and then archive when the person is exiting if you want to archive. Also, creating any programs or appvars (other types are okay) should be done in the beginning. The reason is if you decide to search for a label and store it to P, then you create or delete a var or do something like that, P will be pointing to the wrong place (RAM gets shifted, depending). I don't know if that helps?

EDIT: Also keep in mind that though the flash chip will last for years, the more you archive, the shorter its life span will be before the flash chip won't work.

EDIT2: I haven't looked much at the code, but it definitely seems like you are modifying pointers that you need to either keep or restore.

EDIT3: Also, solve(0, returns a pointer to the newly created var, so you don't need to follow it with Get(
EDIT4: Jumping to labels in other programs is not supported yet at all o.o

What was added in AR01 and AR02 over the last version btw? I only tried the previous ones but I wondered if any change occured graphically before I download?

Also in the dungeon map there's a missing wall tile at the entrance.

As discussed on IRC, there was a brief period of time when I added the new optional arguments to solve(0 that it stopped working properly, but I fixed it a few hours later

As for calling labels in other programs, it may have worked through shear luck, but it will not work all the time under normal circumstances. I will try to add an optional argument to Lbl to specify the variable, though.

So what appears to be going wrong, still, to me is that you aren't updating variables properly or you are changing them and appears to only be a problem when saving.

I am going through and trying to figure out exactly what is wrong, but my guess is inconsistent saving

Okay, I found the problem as I already said in chat  :]
Pretty much, all the creating of new vars and whatnot destroyed pointers to key data, specifically the Map and sprite info. So all you need to do to fix it is to add this at the very end of routine .M19:
Get("VM→M
Get("VS→S
Get("VT→T