Here is the fix for 2.43.

While we're on the topic of protecting groups, I also added in two more programs. For 2.43 and 2.53 respectively, these stop the OS from deleting all your groups during press to test. It has always bothered me that it disables all your programs, and then deletes all your groups.

As far as these patches go, they are all undo-able. When you run them, a menu pops up with a fix and unfix option.

Wow, this is great! Another bug fixed!

And then I ruin the celebration

I just got another bug with grouping, which allowed me to ungroup some but not all of the files in the group. The ungrouping stopped halfway with a different error: ERR:MEMORY. I'm sure there was plenty of space, both RAM and archive, because larger groups still worked perfectly. Then I did a GarbageCollect, which took only a few seconds, proving that there was still a lot of free archive space. For some reason, the group then worked. It's actually happened before, too, but the last time I had it happen to me was a few years ago, so it's about as uncommon as the bug in the main topic. Does anyone know about this one?

Seeing that a garbage collect fixed it, it would mean there is another way to make a group straddle a page boundary that causes problems. If you can find a way to repeat the problem, I can fix it. But until I can watch the variables in an emulator that does the error memory, I really can't fix it.

I'm just wondering, are the patches permanent? Like when you ram clear or even all clear, the ERR:VERSION error won't occur again? I just really want to not have to keep the patches on my calc forever 

On that same note, you can't send your OS to someone else while you have the patch installed. That's why I have the undo option. Although for most people this isn't really a problem. It only becomes a problem when you have that person who managed to delete their OS or similar. (Pulling batteries during garbage collect) And you have to send them a new one. But for the most part, you can always find a clean OS.

Yeah, it's certainly due to the TI-Z80 OS checking the signature before trying to send itself to another calculator. That's what the TI-68k OS does, at least.