Improving stability of AmigaOS 3.0 - 3.9

[matthey]

Good topic but let me simplify a bit...

1. Buy and install AmigaOS 3.9
2. Apply patches at http://amikit.amiga.sk/patches.htm
3. Make a bug fixed software ROM with Remus from http://www.doobreynet.co.uk/beta/
4. Install the ROM with BlizKick for accelerators supporting MAPROM http://aminet.net/search?query=Blizkick.lha
or
Install in bootable flash memory like Kickflash or Deneb

I didn't use Piru's exec. Although it's faster, it was based on an "older" exec and never updated. If stability is what you're after then I recommend the 3.9 exec when using AmigaOS 3.9.

[matthey]

I use mmu.library package also. There is a newer version of mmu.library here...

http://evogt.free.fr/amigasoft.html

It's in the MuMin V43.10 archive.

[matthey]

AmigaMance wrote:

Seriously, i'm all for AOS 3.9. I admit that there is no point in running 3.0, but some people chose to use 3.1 or 3.5 for whatever reasons.

I don't see any point in running 3.5. 3.9 has everything 3.9 has and more. I can see why someone would run 3.1 for simplicity, speed and low memory usage.

Yes, it was based on the same exec which the exec of 3.9 was based...
Perhaps it never updated because there was no real need for an update.

I don't think that this exec is more or less stable than the 44.1 one.

I believe the newer exec has some new features/improvements that Piru's exec doesn't. I'm no expert that could name them, though. There aren't any glaring bugs in Piru's exec. I wouldn't think Piru's exec would offer improved stability unless running an earlier exec that had bugs.

[matthey]

klx300r wrote:
I'm using 3.5 with BB1 and 2 installed with no stability problems at all so far( knocks on wood)..are these updates/patches good for 3.5 too :-?

No, They patch specific versions of 3.9 files. Most of the bugs AmigaMance mentions are present in 3.5 although some may have fixed in the BoingBags. You can use a newer Setpatch that may fix some of the problems. I am using SetPatch V44.38 which should be the newest. Is does stack size checking for CON:, RAW:, RAM:, PAR:, PRT:, SER: for example.