Ronald P. Regensburg wrote:
The changes are still made only to the SheepShaver source? So we do not need to worry about effects for BasiliskII?
As of today, all my changes are within SheepShaver source.
But, I think I'm going to need to change the VM allocation routine in the Basilisk II source.
Remember the "File already exists" bogus message? That was because the Mach memory allocation function used by Basilisk II on OS X doesn't set the C errno variable, which the program was using to get the error code.
I fixed it by changing the higher level code to ignore the errno value, and instead use a constant that indicates it couldn't allocate memory.
However, the memory allocation function it uses on Linux does
set errno, which means that my code is losing valuable information, expecially when it can't set the low memory area due to permissions
I'm thinking that a better fix would be to change the Basilisk II code so that when it gets a bad result from the Mach memory allocation, it sets errno. Then the higher level code can go back to the way it was before, and it will work for both OS X and Linux.