2016, om 05:30, schreef Chris Charabaruk : Here is a more precise explanation in a post in SheepShaver SheepShaver is rigidly mapping memory as if it is not running in anotherĮnvironment. Use memory that SheepShaver wants to use.
Possibly you have some other software on the host that happens to Sometimes the problem seemingly goes away by If the problem arises, it is usually solved by aįresh restart of the host computer and/or changing the amount of ram that
The issue is known, but many users still run SheepShaver in Windows 10 Working dynamically? It seems like it would fix many of the compatibility Is the rigid memory mapping truly necessary? What's preventing it from Reply to this email directly, view it on GitHub #100 (comment), or mute the thread. You are receiving this because you were mentioned. 2016, om 16:26, schreef Chris Charabaruk happens after restarting the computer and reducing the RAM allocation for the : I find it hard to believe that SheepShaver would be trying to allocate memory for the guest in kernel space or that the memory manager would be unable to allocate the space requested for the guest RAM. Maybe you have a lot of additional software starting automatically at startup? Try different values for ram (like 128MB or 256MB or 512MB), each time after a fresh restart of the host computer. If you search SheepShaver forum for "Cannot map second Kernel Data", you will find threads going back to 2009. SheepShaver does nasty things when trying to allocate memory.