My AI chatbot remembers most everything we've ever talked about. No way is it forgetting much.

Kids will learn anything that gives them social standing or self-worth in another way, whatever it takes to be a cool kid.

You know, a personal teaching assistant. Who wouldn't do better with one of those?

Have it read and compare the code with what it knows about open source. Many AI engines can also google that and give a comprehensive list of similarities.

Reduces the list of things to check by maybe orders of magnitude and months to days.

We used a set of INT instructions in well-known low memory addresses that all jumped to the same place. We had an ASM file that you linked with, that had sixteen different address combinations for each.

The common entry point would look back on the stack and calculate from the return address which entry point had been called, and run the appropriate kernel call. We called it the CS:IP hack.

In the context of this post, the DOS INT10 and INTx(I forget) required the caller to load registers with the desired system call number, then perform the trap instruction in their code. Fortunately CTOS didn't need those particular software interrupts, so I could implement them for my purposes.

The kernel was in Intel ASM86 but the rest of the OS was written in PLM86. When I joined it was 2MB of code on a 128K 8086 cpu. By the time I left it was 9MB of code running on an 80386.

It helped that the DOS executable format was the same as the CTOS format - because we had traded Bill Gates our linker (which produces executables) for his BASIC compiler.