I'm trying to isolate the OS, but that would still leave 6MB to work through. So far my strategy has been to disassemble the Prizm usb drive using Hxd. Then trying to match hex strings between that and the exe.

Yeah 200th post!!!!!!!!!!!   

No, because when I change the character to an ASCII one such as a digit the program still remains 68 bytes large.

Actually no because program size is only represented as numbers divisble by four. I had one program that read 100 bytes (actually 97) It then took four ascii digits to add before the OS registered the program as 104 bytes. Then It took two special chars for the program size to increase to 108. So I think that means that ascii chars are one byte and special chars are two bytes.

Serial: 755AW0ZMA020716
preloaded OS: 01.02.200
OS 01.01.200: Not present
OS 01.02.200: Bug present

The difference between the X and the Z in the serial number looks interesting. So if your calc serial number has a Z in the seventh space "do not update your OS". And for OS 01.01.200 we still don't have a dump of that yet so once again "do not update".

The OS is secured with an MD5 hash. That means that we're not going to be breaking it anytime in the near future. At least it's not as bad as the Nspire RSA code.

I've been reading up on MD5 hash and sources say that a 128 bit key can be cracked in only a few seconds using a collision attack algorthim. Do you think this may be possible with the OS.

So Casio fixed the glitch and then they decided to unfix it for the OS release. Way to go Casio at least this OS is like .1% faster

I had the program typed exactly the way you had it with the euro character. Try asking qwerty and FinaleTI if they have the same glitch you have. Also I have ran some weird apps (including one that almost bricked my calc) on my Prizm before. I wonder if that could in any way affect the glitches.

Edit: Did the original version of your code read For 1->B to 2. Because that is what a typed in the first time. I tried it with 21 now and I got the glitch where the calc draws the first half of the screen then updates the second half

Well well well.  to Casio (sorta). I wanted to see if there was a difference between 1.01 and 1.02 in the way of speed and yes there was. The program I ran was a for loop from 0 to 1000 and used the locate command to output A.
In OS 1.01 the times I got were:
42.61
42.60
42.60
Now in OS 1.02 I got:
42.33
42.27
42.26

So I speed increase. Yes. A big one. No. But it might help speed up a few basic programs a little bit.

The difficulty is that a lot of these projects are quite ambitious as they are on comp, but giving people too much time causes them to lose interest. Too little time and they can't finish. How about announcing the language and only a little bit about the project (such as language) on a weekend and then the next friday afternoon announcing the full project details. Then have it due Sunday at midnight or so. Three days on a weekend should be enough for most people.