So now you're using figure names to solidify the BS?
Get Ben to email me - and tell me OS4 wont be 100% PPC then I'll accept it. Until then I'll just look at what is in front of me which is an AmigaOS version recoded in pure C, ready for compilation. It is version 4.0.
I see this going to a debate over what is the OS and what is not as you admit the core parts will be PPC.
You noddy - the OS is THE core part.
You don't know the difference between an emulator and a binary-compatible API-reimplementation
Lets see:
Emulation of Processor =
Emulation of API =
MOS is not AOS kernel but Quark. Therefore the API is different. This dictates naturally then the AOS 3.1 ability is an API emulation. 3.1 binary happens to be 68k which also naturally dictates that it emulates the processor. At either point it is emulation. There is no API reimplementation, MOS does nothing the same as AOS beyond this implementation. There is no crossing of the paths as you would suggest.
And yes I do know MOS used AROS modules, but as you say on source code level, so it is modified for the relevant API. You are creating a hole for yourself by giving me the text to target.
So tell me if you really got a working copy of AOS4, why is it that then Ben could only demonstrate a highly patched/updated AOS3.x (on 68k) and a text-mode kernel ?
ATM the OS4.0 exists as a 68k modular distribution. It is not a patch, the way it works is that all the files are replaced that aren't in ROM, and the ROM is disected and renewed much like Blizkick. No patching, all replacing.
It is in C, and the recompilation takes no time at all. In the latter stages of low-level HAL implementation we shift to PowerPC.
The reason why the amigaONE was only shown with the text based ExecSG was written in the latest progress report - so why use that as a false example?