Idk about poty because I am doing almost the exact same thing that realSound does. That is where I got the idea.

But I realized that when I'm doing 22khz, I actually burn 82 t-states per byte. I'll have to look into compression because that would be awesome. I have 4 more hours coming up tomorrow. So I'll probably figure it out.

So I caddy during the summer, which meant that today I had 4+ hours of just thinking. And here is the result.

I have made a program that will play sound on the 84+'s with the bad ram. I just started it a few hours ago, so I'm still working on it. But I have gotten near perfect sound quality from my calculator. It uses pulse width modulation (turning the link port on and off really fast) to get the amount of voltage it needs to play a note. I currently have it set up for 44.1khz, because I wanted to keep this on off above the human level of hearing. But then shortly after I made it I realized that it is playing a 44khz note and not a 22khz note. So I'll be working on 22khz because 44kb/s really eats up calculator memory.

I also have proven to myself that my speed program was right when it said my calculator runs at 15.8 mhz and not 14.9 mhz like the first speed test program said. I figured this out because I have the song set to play at 15.5 mhz and on my calculator and it runs too fast.

I'll put a video on youtube once I get 22khz working. If you are going to test this, don't use wabbitemu. Your sound card doesn't know what to do with a 44khz note and it will sound awful. So make sure you test it on a real calculator. It is currently set up in an app and a program, the app is the music, and the program is the program. This is so I don't have to resend it every time I change it.

If you want to make your own song. You have to put it in 44,100 hz, mono, 8bit. Then use a hex editor to cut off the header, replace all zeros with ones, and put a zero at the end. (Song starts 4 bytes after "DATA"). Then you have to find a way to convert it to an app and send it to your calculator. I used brandonW's new binTo8xk and then used wappsign.

I have also included the little demo I made for myself. It's only 5 seconds long but it's 340,000 bytes on calculator. Oh, and someone please laugh at the source, the technique I used has max sound quality at the cost of the programmer. (255 subroutines each 1 t-state different from each other.

452: You have Blockdude for your pc. http://www.freedownloadscenter.com/Games/Puzzles/Block_Dude_for_PC_Download.html

453. You port a calculator game to the PC.

Add one more person with this interesting quirk to the list.  My old 84+ doesn't do this, but I just tested it on my new 84+se, and it works on there (no omnicalc ram restore, tho :'().
Serial: S-0306F (84+), P-0909M (84+se - a mysterious P factory calc!)

P's are normal, they just always have bad ram. Old table. K's are the weird ones.

Windows 7 might kill it. I'm in XP.

I don't think the battery pull itself is what does it though. You'll notice that when you pull a battery, when the screen turns back on, it was displaying the same thing it did before it turned off. This would mean the the lcd ram didn't get cleared. It would probably also mean that it's settings didn't get cleared either. That is probably the job of the OS to clear.

I couldn't find the spot in the OS where it happens, but I found it in the boot code. The boot code sends: 40h, 05h, 01h, 03h, 17h, 0Bh, and 0EFh. This makes me think that these aren't defaults. (13h-17h are undefined, but 13h-16h raise my contrast)

Also, not many people realize this because no one does it, but if you pull out the little battery as well as the AAA's. When you turn the calculator back on, the screen displays a bunch of garbage. Which makes me think that this is the only time that the lcd ram loses power. Maybe it will reset the screen flip settings too.

And as a response to thepenguin's posts on the first page: OS modification is easier than you think, but ld is not gonna work

I know, lol.

Someday I'll probably make robot unicorn attack. But it'll be one of those programs where it's just all out how it looks and I don't care about memory. I'm talking full screen 8 level grayscale title, detailed ground and enemies, and full screen background parallax. The title + background are already 7k.

But it would be epic...