So you thought you would find here an impartial, knowledgeable comparison of RISC OS with the more popular and better known operating systems? Think again; I have been so steeped in RISC OS, since even before its appearance two decades ago, were that possible, and I am so ignorant of other operating systems, that I cannot honestly deliver to you a balanced picture. Well, that is the modern usage of apology over with, so let us get on to the older sense. Note: This is the 2nd entry to our Alternative OS Contest which runs through 14th July!
To view parent comment, click here.
To read all comments associated with this story, please click here.
Member since:2005-09-17
I think it would be fair to say that this is also a feature of the OS. Writing an OS that loads from ROM is different from writing an OS that runs from ROM. The latter requires a clear separation between the code space and the memory that the code uses, along with an architecture that allows it. Perhaps I'm over emphasising this a little, but RISC OS certainly had to be designed specifically to allow it to run from ROM.
I think all modern operating systems do that, though. Remember that most use disk caching to load programs: code pages are mapped directly to (read-only) pages in the disk cache. This saves memory, allows code to be shared between programs, and makes things faster. If you allow writing to code areas, everything gets much less efficient as the whole page of memory, including the unchanging code, has to be copied.
Still, you might want to code from ROM to a read-only RAM area anyway, depending on whether RAM access is faster and how much free RAM you have.
Member since:
2005-07-13
"The knowledge that even if you wipe the entire drive, your system will still boot and be usage is great too, although that's more a feature of the way the OS is delivered (in ROM) than the OS itself."
I think it would be fair to say that this is also a feature of the OS. Writing an OS that loads from ROM is different from writing an OS that runs from ROM. The latter requires a clear separation between the code space and the memory that the code uses, along with an architecture that allows it. Perhaps I'm over emphasising this a little, but RISC OS certainly had to be designed specifically to allow it to run from ROM.