Some WarpOS programs use variables from the PPCTASK structure, e.g. after a FindTaskPPC(0) it looks at the PPCTASK_MSGPORT and does a WaitPortPPC(). The PPCTASK structure is different from the OS4 task structure and wrong values are being used.
In case of the PPCTASK_MSGPORT: this is now emulated. Unknown at this point is whether other values of the PPCTASK structure are being used by programs.
WarpStat and showtasks look at this structure too. But they first crash by trying to get to the task list using LockTaskList. I guess I have to support that in a way.
Some WarpOS programs use variables from the PPCTASK structure, e.g. after a FindTaskPPC(0) it looks at the PPCTASK_MSGPORT and does a WaitPortPPC(). The PPCTASK structure is different from the OS4 task structure and wrong values are being used.
In case of the PPCTASK_MSGPORT: this is now emulated. Unknown at this point is whether other values of the PPCTASK structure are being used by programs.