3 ms·
>(AmigaOS) For how cutting edge it was, it was an unstable POS too. AmigaOS 1.0 release sure was. From 1.2 onward, it's trivial to get higher uptimes than wind
by snvzz 6y ago
>(AmigaOS) For how cutting edge it was, it was an unstable POS too.
AmigaOS 1.0 release sure was. From 1.2 onward, it's trivial to get higher uptimes than windows 9x.
I consider 2.0+ (~1991) pretty modern. I haven't seen a crash in a very long time, and I always have some Amiga running.
- LocalH 6y agoThe only real problem with the AmigaOS architecture is the lack of memory protection.
- iuguy 6y agoIt's only really a problem if your software isn't designed for it. Most of the problems people had with DOS memory protection issues were due to the lack of standardization around memory management. Similarly so with Windows 3.x, running DOS programs from Windows on top of DOS was never going to work well. Even Windows95 had its problems. On the Amiga it didn't have this problem. There was AmigaOS and that was it. The base hardware was for the most part tightly coupled to the OS and the architecture was designed to provide standardised mechanisms for accessing hardware that were fairly stable. The Amiga had different stability issues of course, but my A4000 manages fine without memory protection despite having a full MMU on-board.
- LocalH 6y agoI mostly meant in terms of security in the modern age. Few people in their right mind (in the realm of computing enthusiasts) would use AmigaOS as their only daily driver because of it. There’s a reason all modern OS architectures have memory protection as a core feature. In 2020 you really don’t want any process on your system to be able to access, let alone clobber any other process space.