Paladin of the Pegasos
Posts: 1289 from 2003/2/25
From: binaryriot
i NEVER experienced any of the weird stability problems you describe here with my MOS1.4.2 install on Peg2 G4.
Yes, crashs can happen, e.g IBrowse crashes sometimes (e.g. on eBay), that's an app fault of course and not a major stability problem of morphos or something. Of course MorphOS has bugs too, which can also lead to crashes.
But what a few describe here is beyond normality and obviously caused by wrong installation or broken apps.
A few tipps to solve your problems:If you have only 256MB ram or less then connect the peg with a serial cable to another machine and check/ grab the debug log with a terminal application. It will slow down the machine, but it helps to find out which bad app causes the problems for you. If you found out then delete this broken app or fix the installation etc.
If you don't have second computer or serial cable but more than 256MB ram you can use
ramdebug and maxhits option.
configure the bootfile in openfirmware as:
boot.img ramdebug maxhits=3
(change boot.img to name of your boot.img file ofcourse)
That means as soon 3 hits happen, caused by broken/bad apps your system
will freeze. When that happens, reboot directly into morphos again. Then execute "getramdebuglog morphos.log" (you find the getrandebuglog tool on the morphos support ftp) and check the file morphos.log, it will contain same information as you would get with serialdebug.
Check which app caused crashs and why and then delete/uninstall this app or fix the installation.
If you have problems to understand the morphos.log (debug output) then please join irc (#morphos on de3.arcnet.vapor.com) and ask some friendly ppl which have more experience in reading/ understanding the debuglog. They will help you.
In no way you should assume ramdebug is the better solution, just because it slow downs the system less tahn serial when problems happen. The
ONLY solution is to find the problem and try to fix it.
regards,
tokai