A new version of OpenTTD (0.4.8-RC2) was released tonight:

http://sourceforge.net/project/showfiles.php?group_id=103924&package_id=111717&release_id=435963



MorphOS related fixes:

- game doesn't crash anymore if no TCP/IP stack is present (UDP sockets were used even if network-availability was set to false)

- fixed crashes (or hits when you don't use maxhits boot parameter like me ;) in filerequesters when going to volume root.



full fix list (compared to RC1 which was not released for MorphOS): http://sourceforge.net/project/shownotes.php?release_id=435963&group_id=103924
and full fix list (RC1 vs. previous release 0.4.7):
http://sourceforge.net/project/shownotes.php?release_id=431904&group_id=103924

Have fun.

regards,
tokai

Nice, thanks!

BTW: how is this maxhits boot parameter used, and what does it do?

boot boot.img ramdebug maxhits=5

Then your system completly freezes when u get more than 5 hits in row. This is useful to stop malfunction programs from going berserk (e.g. SFS ;) or (if you have more than 256MB ram but no serial) to catch a proper ramdebuglog with the initial hits after a reboot. If you don't use maxhits its almost impossible to get the initial hit (which can lead you to the exact reason of a crash/ malfunction of software) - very useful for developing. No need for 2 computers or stone-aged serial stuff.


It works quite well if you know what you're doing. But if you use too much broken software its probably contra-productive for normal users. I personally wouldn't run the system w/o it anymore.

regards,
tokai

Quote:
It's also useful to stop you from being able to save any important documents which you might have open (before rebooting), when some other program couses a few hits too much.
Quote:
umm, are you sure that you don't mean "less than"?

Another argument worth trying is "logserver" which will output all hits in a CLI window. That way you will know when they happen.

logdebug output is a worthless stripped down version of the real thing.
Unusable for real debugging.

Quote:
For "average user" it's a good way to find out which program is behaving badly, when the entire system feels unstabile.