Here you can find side projects of the staff and great projects which we think should get extra support. (Note that featured projects are not projects by staff members of MaxCoderz)
Could it be possible to emulate 83+SE speed?
When I make it go reallyreallyfast and I take a SS, why isn't the SS really really fast?
What about the 86?
By the way, if any of you are interested, you can read my thesis here. I can't say I'm really satisfied with it, but it was mostly done in a rush (and still submitted late ).
PTI saves the state when you exit it—obviously, since it picks up where you left next time you run it; these are the .pti files that appear next to the respective ROM images. You can also use the .sav files that VTI produces: load the corresponding ROM image first in a slot, then drop the .sav file onto that slot.
Hmmm I found a bug I think. When I was adjusting the hieght of the lcd group and hex view it automatically set the top of the lcd group to the bottom of the debugger.
I keep getting an "Unsupported VTI save state" error.
Thought I think I have found a work around... I just got the calc to the state I always want it at when I start, and made the .pti file read-only. Yay for cheating.
PTI doesn't seem to like sending files flagged as archived (the two 'unknown' bytes after the variable name, usually 0x00,0x00 are 0x80,0x00 when sending an archived variable). Is this by design or is it error trapping assuming a corrupted file?