there a fix for the double _LVOUnLock bug in AMOS built into FxBox 1.23, the fix is in build/Compiler.Lib and build/APCmp (and the AMOSPro editor in my local copy). the memory list corruption bug with AROS is also gone as they were probably related. AROS has a slow graphic update, AmigaOS 4.1 is very slow with conversion routines that use mathtrans.library and has no visible or a corrupted mouse pointer. the mouse issue is difficult to diagnose as in the code you can see AMOS checking the existence of and checking the details of the mouse sprite, it would fail to load and instantly quit with an error if the references were wrong. I have been through the hardware sprite initialization code and the mouse code and cannot find a problem, AROS has no problem with the mouse pointer. I hope this is due to my early not-updated version of AmigaOS 4.1?
there a fix for the double _LVOUnLock bug in AMOS built into FxBox 1.23, the fix is in build/Compiler.Lib and build/APCmp (and the AMOSPro editor in my local copy). the memory list corruption bug with AROS is also gone as they were probably related. AROS has a slow graphic update, AmigaOS 4.1 is very slow with conversion routines that use mathtrans.library and has no visible or a corrupted mouse pointer. the mouse issue is difficult to diagnose as in the code you can see AMOS checking the existence of and checking the details of the mouse sprite, it would fail to load and instantly quit with an error if the references were wrong. I have been through the hardware sprite initialization code and the mouse code and cannot find a problem, AROS has no problem with the mouse pointer. I hope this is due to my early not-updated version of AmigaOS 4.1?