Yeah, I had this problem in MirageOs too. I wish both were made to keep the folders (and their remaining content) intact after a crash.

This worked for Mirage (only one though)--archiving the appvar. But the next time u run mirage, it gets unarched

I always thought that it could just copy the appvar to the ram, as in reading directly from the archive.

actually, once I use MirageOs, when I exit it it gets archived again, even if I manually unarchived the appvar first. Btw when I ran Mirage the first time, the appvar was archived by default too.

If you don't believe me, I have recorded a video with my digital camera as a proof and I will post the link here if you still try to prove me wrong.

Idk, it's strange, really . But yeah, the point is that when I used folders in Mirage before, if I got a RAM clear in a game running from there, all the content in the folders were moved back to Main and I had to move all programs again.

I think I remember Brandon saying a few times (unless I'm mixing this up with something else, which is possible) that you can work around that by unarchiving the variables and setting their folders, then archiving them back. Then the folder settings will be more permanent.

IIRC, it was because it uses the VAT to store the folder ID. The VAT entry can't be modified permanently while a var is archived, I don't think—I think it's only updated once when the var is initially archived.

I guess it's kind of like on the 68k calcs if you have a bunch of archived variables in a particular folder, and then you rename the folder without unarchiving anything. If the calc crashes or does a soft reset, the variables reappear in the previous folder name rather than the renamed one. That's because archived variables have headers in the archive that says what folder they're supposed to be in. Unless you unarchive and rearchive them again, that entry isn't updated since it's in flash rather than RAM, so data about the new folder name stays in RAM and is therefore temporary.