Can't map second kernel data area (W8.1 x64)
Moderators: Cat_7, Ronald P. Regensburg, ClockWise
Can't map second kernel data area (W8.1 x64)
When starting a fresh copy of SheepShaver on Windows 8.1 x64, I get a "Cannot map second kernel data area: 487" error, no matter what combination of programs are open or closed. A previous thread suggested moving SheepShaver to a flash drive, but that didn't work for me. What am I doing wrong, and how do I fix it?
- Ronald P. Regensburg
- Expert User
- Posts: 7832
- Joined: Thu Feb 09, 2006 10:24 pm
- Location: Amsterdam, Netherlands
Re: Can't map second kernel data area (W8.1 x64)
I suppose you searched the forum and found this topic:
http://www.emaculation.com/forum/viewto ... =20&t=7643
Did you also see this topic? :
http://www.emaculation.com/forum/viewto ... =20&t=8143
http://www.emaculation.com/forum/viewto ... =20&t=7643
Did you also see this topic? :
http://www.emaculation.com/forum/viewto ... =20&t=8143
Re: Can't map second kernel data area (W8.1 x64)
A very strange error that is, it's like Apple have never heard of memory management.
- Ronald P. Regensburg
- Expert User
- Posts: 7832
- Joined: Thu Feb 09, 2006 10:24 pm
- Location: Amsterdam, Netherlands
Re: Can't map second kernel data area (W8.1 x64)
This is with a Windows application on a Windows OS.
(A similar issue with SheepShaver for OSX was resolved a couple of years ago.)
(A similar issue with SheepShaver for OSX was resolved a couple of years ago.)
Last edited by Ronald P. Regensburg on Thu Nov 27, 2014 5:12 pm, edited 2 times in total.
Reason:
Reason:
Re: Can't map second kernel data area (W8.1 x64)
Apple make QuickTime. Nevermind the fact that my PC doesn't even have QuickTime installed.
Re: Can't map second kernel data area (W8.1 x64)
The problem stems from how sheepshaver uses memory. It just doesn't allocate a block and use it like a normal program, instead it tries to duplicate a powermac address space in the user space. So the contention is in mapping 0x00000000 and other traditionaly reserved blocks. This is why sheepshaver will eventually be unable to run anywhere.
To fix this it'll take a reworking of how it works in general. It's not a small task.
So like the QuickTime thing you probably have another program occupying that space. You can try killing programs and services but it'll probably be a debugger or Antivirus hoping to catch 0xc0000005 access errors.
To fix this it'll take a reworking of how it works in general. It's not a small task.
So like the QuickTime thing you probably have another program occupying that space. You can try killing programs and services but it'll probably be a debugger or Antivirus hoping to catch 0xc0000005 access errors.
don't do today what you can put off until tomorrow.