3 ms·
>(oh, and if not for C= incredibly horrific management). I believe that to be the real, non-surmountable problem. Newer generations with better hardware and m
by snvzz 4y ago
>(oh, and if not for C= incredibly horrific management).
I believe that to be the real, non-surmountable problem.
Newer generations with better hardware and memory protection would have been totally possible.
Virtualization could have taken care of backwards compatibility.
Some practical modern examples include:
- Whdload, which patch and wrap floppy-booted games so that they can run from the harddisk, allowing for returning back to multitasking when done, with optional MMU protection.
- AROS, an AmigaOS-like open source OS, which can run classic Amiga software through reasonably well integrated emulation.
- MorphOS, a PowerPC AmigaOS-like OS with similar slick emulator integration.
- gpderetta 4y agomemory protection would be hard I think, right? The whole OS was based around message passing by just linking a message to the target process message port pointer. edit: but, as per your other comment, you know that. How do you see protection working in amigaOS? Just share the pages that are needed for messaging and protect everything else?
- snvzz 4y agoA flag day would be needed. This means literally breaking the ABIs. New interfaces would take care of setting up shared memory or doing cross-space copying. There's always ways to deal with old software, such as through virtualization.
- erikarn 4y agothat's why the later OS releases after amiga/commodore imploded extended some of the memory APIs to say "This needs to be globally visible". That way you'd allocate message memory in globally accessible memory and the MMU could do "things". (Not that I'm a fan of that solution, just saying, they had to hack around it.) https://wiki.amigaos.net/wiki/Exec_Memory_Allocation https://wiki.amigaos.net/wiki/Exec_Memory_Allocation (I don't do later amigaos things though :-)