interrupts and CPUScheduler have come a long way. I would say that they're approximately done, except that programs are crashing and burning when they come to their end, and not ceasing to exist gracefully. The end of each one is heralded by a memory access violation, followed by a failure to find a current process that is not null. The latter isn't wholly surprising, what IS surprising is the programs persisting until they hit memory access violations. I don't know if it was like this before, but this problem is preventing runall from performing seamlessly.