@Mysha:I think I am beginning to understand what you are referring to... you meant dos as a device as it was when AmigaOS started out as tripos ?
I guess, but here were talking about the early days of AROS (by today's standards). Sure, Amiga had taken DOS as a library as a quick solution. But AROS was not going to make that same mistake; it had instead implemented DOS as a device, as it should be. The advantage was obvious: AROS didn't need anything special for DOS. I expect the disadvantage was also obvious: For AROS to behave like ADOS it needed constant exceptions to behave more like a library.
At some point while I wasn't there - being fed up with all the errors accepted as normal - AROS was switched to DOS as a library. After that, no more talk about DOS as a device, but I can't help but feel we lost something, there.
Also note that AROS is (or at least suppose/intends to be) 100% API compatible with AmigaOS 3.x, therfore the same RKRM's can be used to develop for AROS. The thing that is new however is hidd devices which is an abstraction layer between hardware OS..
Yes, but even apart from the hidds, we have plenty details that are different. For one thing, by law we can't copy the AROS manuals. For another, the history revealed in the manuals is often different, and with it comes a different set of example programs. Also, the tools we developed, and which should be described, are often different because they stress other aspects.
Having said that the RKRM's will ofc. tell you nothing about how things are actually implemented/structured in AROS.
There is that.
If we continue with this, do we have a moderator who can spilt this sub-thread off from its parent? I don't think we're on-topic any more.
