I want to improve solver so that it works like this. A = B. Instead of 0=B-A. And to do this, I am going to have to screw with the system monitor and solver's context vectors. I know almost nothing about these because there isn't much information released about them. But I know that people have the information. So basically, I just need to be filled in.

The sdk, was slightly helpful, along with wikiti. But what I've gathered so far is this. cxMain and the 6 vectors after it are basically a call table. When an event happens, one of the vectors is followed and the code is executed. But each one of those vectors appears to have it's own guidelines just like the hooks do. I can probably figure out the usage with enough debugging, but some notes would be greatly appreciated.

Edit:
    So I'm starting to figure some of it out. It looks like for cxMain, it gives you A = key, and you return the new key to be pressed in A with NZ set if it should be used.

The main thing I'm trying to figure out now is how the screen get's drawn. It doesn't look like cxRedisp ever gets called.

Do you remember the URL to that unsupported info section of TI website by any chance? I am curious if archive.org might have some stuff there...

Ah ok thanks, because SirCmpwn asked TI for USB doc a few times before to no avail, and I was wondering if it was located there before.

Thank you so much. This answers almost all of the questions I have been having for about a year. It seemed like there was all this knowledge that was out there, but it wasn't written anywhere. This finally fills a huge void in my understanding.

@FloppusMaximus: Perhaps you should add those to wikiti. They'll be much more accessible there.