Amiga.org
Amiga computer related discussion => Amiga Software Issues and Discussion => Topic started by: Targhan on March 06, 2003, 08:54:27 PM
-
Guys,
I want to make a shared document (Amiga.org, Morphzone, AmigaRealm, GFX-Base, Amiga-News.de, etc, etc) that can warn users of possible MUI Class conflicts.
I have gotten about sick of install software package-X, only to find that I can't open my MUI prefs anymore. Any volounteers who would like to help on the project, please PM me.
Feel free to post information about a bad MUI Class in this forum. The information we will need is:
1. Name of the Class. (.mcc .mcp)
2. Version of the Class
3. The system you had the trouble with, whether it be OS3.1, 3.5, 3.9, MOS, Amithlon, UAE, or any other implementation of the Amiga API.
4. The symptoms of what this class does that is evil.
========== Example ===================
1. BetterString.mcp / BetterString.mcc
2. 11.6 (12/19/2000)
3. Amithlon, Contrib Pack 3, OS3.9
4. Slows all MUI apps to a crawl, also MUI Prefs will crash
==========================
Finally, please keep any post of this nature to one MUI class per post (save for things that have both the .mcc and .mcp)
Once the list begins to take shape, I will try to make it available from the normal community web-sites. This way, there will be no dissappearing acts ;-)
-
Let me start with one bad class I found recently:
1. TWFmultiLED.mcp and .mcc (.mcp is probably the cause).
2. Version: 12.4, 12.5.
3. OS3.9 on Amiga.
4. Throws lots of ramlib hits when the MUI prefs program is launched, even with a ramlib stack patch.
-
Another:
1. Term.mcc
2. Version 27.3.
3. OS3.9, Amiga.
4. Throws enforcer hits.
-
One last one (don't wanna hog the forum with these obsolete classes):
1. Mesa.mcc, .mcp
2. Version: 12.0
3. Amiga, OS3.9
4. Throws lots and lots of enforcer hits.