![]() ![]() Adding JIT or not is a matter of changing the cpu engine, but the memory layout changes anyway and you have to convert addresses Your point 4 is exactly the same as my point 3. It would be dead slow (yes, have you tried pc emus on pcs? they run FAR slower than the real thing). (lol) The idea of emulating a PowerMac emulating the entire cpu has no sense. "emulate a PowerPC on a PowerPC should be less hard than it seens." ![]() MAME requires cycle exact emulation and Mac emus for Amiga 68k or MOL/SheepShaver on Linux have more in common with virtual machines than with emulators. MAME is a completely different emulator and I don't understand how you can compare them. ![]() edit- Remember that these memory functions are already available in OS4 for example and that will cause that we'll have less emulators and that the most interesting ones (like ppc mac for example) will never work on MorphOS. Sorry Mr Schmidt, but this is disapointing. And as Ralph Schimidt hasn't any interest in helping the MorphOS emu community and don't wants to allow developers to create new interesting apps (with Memory Management functions we would be able to port nallehpuh, puhderbaer etc and have PAULA emulation just like in Amithlon). This is slow, but the only thing you can do without the memory management docs.īut don't expect to make SheepShaver run (or the 68k mac amiga emus to run directly), you'll need the area from 0x0000 to 0x3000 free for your emus or the damn MMU functions. You would use UAE's 68k emu and you would not use real memory locations and you would have to convert the addresses (for example adding an offset). (surprise, surprise, no docs from Ralph and he don't wants to release it) This point causes that a MOL port is impossible for MOS because 3.x functions aren't enough.ģ.- Recompile basilisk2 completely for PPC. There are various solutions for this:ġ.- Write a tool that reserves the memory area from 0x000 to 0x3000 (that may require help from the main MOS developers because no info is available about memory management functions).Ģ.- Write a tool that uses the MMU to remap the damn memory area to another location. #MAC EMULATOR SHEEPSHAVER PATCH#It's used directly by MacOS to store local variables and it seems that it's not easy to patch the rom to use other location. #MAC EMULATOR SHEEPSHAVER DRIVERS#Well, I know, why it doesn't work, but what I don't understand is, why didn't anyone fix it? All these emulators use drivers as for gfx so for sfx, so why?Īs you will remember you used a program called prepareemul or rsrvcold/warm to reserve the first kilobytes of memory for the mac emu. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |