Thanks for the fix, which I too had noticed, but hadn't actually reported to "Bug HQ" as I wasn't sure what I would say about its sporadic appearance in the RAM: directory, but it's nice to know it's been tracked down and is going to be gone from the OS from now on.

I have had a few weird instances since I installed the ramrootfix.lha file in WBStartup.

It may not be due to the fix, but I have been using MorphOS now for about 8 years and these 3 moments have never occurred prior to installing the "fix" in WBStartup, and as far as I know I have not installed anything new on my system recently that was likely to cause the following events;

1. unable to move an icon to a free area of Ambient with the mouse. It kept jumping back to the position it was in previously. Later, without rebooting, this process worked OK, same Ambient desktop, same icon.
2. Unable to move an Ambient icon when using/pressing the keyboard keys (Cmd+Alt) as virtual mouse, the cursor moves but does not subsequently move the icon, the cursor slides over Ambient desktop, and the icon remains where it was. Here again, a bit later, without rebooting, this process worked OK, same Ambient desktop, same icon.
3. Swapping from one partition/directory where I had added an icon to a folder, I then went to the mirrored partition/directory to find that the icon had seemingly been added there, but on re-loading the second/mirrored directory the icon had vanished (never been there, but was like a mirage, of sorts, over the directory/folder). I was able to add the icon, but I cannot explain why the icon was seemingly in the second storage partition/directory when I had not copied it there, and it then became apparent that it was not actually there, which seems really weird/puzzling.

Your issues are unrelated to ramrootfix.

@ Piru - Any idea what they are related to?

@Piru

You guys in the MorphOS Team rule! You haven't dropped the ball in all these years, always squeezing bugs out, striving for perfection. Please do continue!

Quote:

There is probably some other application causing trouble. You installed the patch, which changes the memory usage, as it probably fills a very small area of memory. Some other application loaded later on is now using a different memory area.

Normally this is not an issue, but if the application is faulty and using more memory than allocated from the OS. Do to the change of memory chunks the illegal overwritten memory is different. Probably ambient memory areas get partly overwritten and causing your issues.

Finding the faulty application is not so easy, as by disabling any application you may change the order of used memory chunks, so even when removing a working application the problem could appear as gone, but only because the faulty application is overwriting less important data. As a result problems and crashes may not appear right away, but for sure cause trouble.

You can use a tool like MungWall to find the broken application. It is required to run this tool as soon as possible during boot, so a maximum amount of memory chunks can be put under survailance. It will slow down your computer a little, as it checks every memory section for leaks, when closing applications. In most cases it will point out problematic applications.

MorphOS 3.16 is now released with the fixed ram-handler.

Once your system has been updated to MorphOS 3.16 the "ramrootfix" can be deleted from WBStartup.