![]() 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.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |