In the article was the following *gem*>"Paul revealed that in May 2002, a number of engineers left Pace but continued to provide contracted support of RISC OS to the corporation while developing the Iyonix product for Castle. Paul said the differences between RISC OS 5 and 4 were already noticeable back then, and now the two operating systems are now very different internally. We understand that RISC OS 4 has become particularly modularised with the introduction of its hardware independence, and the way in which the components communicate with each other is significantly different between RISC OS 5 and 4."
Ok so RO4 Select is more hardware independent. Then it should be a doddle to port to the Iyonix shouldn't it !
Unless of course hardware independance has nothing to do with portability to other hardware (non-sequitur and all that that is).
Also the OSes being "very different internally" is irrelevant - when I call OS_WriteC it works because at the API level *both* OSes are the same - if they weren't code for each one would *not* run on the other (or on earlier platforms either). I don't give 1 or 2 hoots *how* either party implement OS_WriteC (or any of the myriad other SWI's) other than they are documented at the API level. That really is *all* that is required.
The other point that had me gagging was the !Printers herring of the long wavelength (i.e., RED) variety. ROL could *not* open source *all* of !Printers because they *had not the right to do so*. They *could* (and did) release the bit *they* had rights to (the UI/Front end). The failure of one "partial" OSS release can hardly be used to verify or refute the applicability of a "wholesale" Open Sourcing (or substantial OSS release of RISC OS).