Ghidra is addictive. Found a good entry point for the #PocketViewer simulator and now I can't stop naming variables in the decompiler.

For those curious: plugview.plg seems to handle the screen rendering and it has a lot of public symbols and uses many known Windows APIs, so it could be a good way for me to find where VRAM resides in the emulator and maybe on the real system.
But I also rediscovered a PV blog with lots of useful utilities (like GetOS!) and even some OS patches. I already found some useful info about the memory map in the source code for GetOS2.
Still, reversing the simulator can be of some service yet! Right now I rely on some wonky AHK scripts to automate it, it would be much better to inject code directly into it with Frida, or to extract useful bits out of

Made some very small progress on the #CollapseOS #PocketViewer port by figuring out more of the int86 routine.
https://git.sr.ht/~raingloom/collapseos-cpv/blob/fb11e8485cf795272e8e62d285e99d92be174908/int86.asm
cc #theWorkshop #theFoundry

ps.: my #assembly skills are pretty newbish and rusty, so consider all comments uneducated guesses 

Hey #Casio I have some questions...

enum bool {FALSE=0, TRUE=1, HALF=2};

cc: #C #PocketViewer