Ronald P. Regensburg wrote:
The nvram fix seems to work for when no initial nvram file is present, but a couple of times I got a SIGSEGV while booting with a pre-existing nvram file (or ~/.sheepshaver_nvram file) that was created with a different setup (different MacOS version, different rom, earlier SheepShaver build). So far, I have not been able to reproduce this reliably.
My fix only affects when SheepShaver initializes a new NVRAM file (or after the NVRAM/PRAM/XPRAM has been zapped). It has no effect on any processing that takes place with an existing NVRAM.
Note: I'm still having trouble booting OS 8 on an Old World ROM, with and without my change. I suspect another NVRAM issue but I'm not sure yet.
(I am getting a little confused about what is and what is not (yet) committed to CVS and I do not know how your work and Myrd's work relate. The better default settings for a new VM are not available when the SheepShaver executable from this latest build is used in the SheepShaverLauncher.)
When you build SheepShaver now, it picks up a different version of the built-in preferences editor. The Launcher is a separate Xcode project, which has to be built separately, in Xcode
. It is not built by the "make" build system.
Maybe the code for the better default settings is not in CVS yet.