It might be an idea to talk to NicJA about mmu.hidds and the like, when I spoke to him about it, he said he had a better idea... I think his idea was abstract it a bit more... probably using his new cpu.resource.
Anyway, I still am not convinced by direct 68k emulation... A much better idea would be to have a special library loader that creates virtual libraries on the side of the system that doesn't have the native library at run time.
I really like the idea of keeping 68k programs running in a UAE context, so that I can run all my old Hardware hitting games (the only things I have left of my Amiga software that I can't get equvilents on my PC), and because it offers crash protection.
The direct 68k emualtion might me a nice (even desirable) short term solution, but in the long run I would prefer the UAE solution for these reasons:
1. Greater compatibility with Amiga software.
2. Greater system stability.
3. Reduced resource overhead.
4. Platform independance.
5. To encourage more native software.
6. Greater User control over the 68k software.
7. To allow the easy bypassing of legacy system components.
8. Externally matintained Emualtion software (less AROS resources required).
:-)