Paladin of the Pegasos
Posts: 1596 from 2012/11/9
From: Manchester, UK/GB
@
Papiosaur - I think, overall, that too much emphasis has been made recently of the incompatibility of the now unavailable Chrysalis Pack that you used to produce on a regular basis.
For me, it was a great way to enhance the somewhat "bland and clinical" appearance of the base version of MorphOS, which I began using (registered) in 2012, and even though there were a few very minor troubles with it, often French language based (tut, tut, et zut alors

), I never had a major outage with it. I liked the additional skins and appearance of the default folders that could be installed that the Chrysalis Pack offered. Frankly it is a pity that some of that content was not embraced by the MorphOS Development Team as an official enhancement pack.
Maybe this could be considered as a useful option in the near future, as installing so many great add-ons would take ages to discover via Easy2Install, as good as that utility is, for a new MorphOS user. So, for me it made it so much easier to enhance my system in one-go with the Chrysalis Pack, that the few minor niggles that it caused were worth it, overall!

However, surely now a base enhancement pack could be assembled from all the great utilities and other programs that are stored on MorphOS Storage - in an agreement with the MOS Dev. Team?

At least the few minor niggles I had with the Chrysalis Pack are not like I am now having with v3.20 - which
freezes my A1145 iMac if I run Jukebox (system utility), which is the main
fault in the v3.20 release that I have reported back to the MorphOS Development Team (2 of its important members) . . . now
that IS a serious failure!

I have since manually "cleaned" my System partition of any possibly troublesome/duplicate files in the main folders, i.e. C, Classes, Data, Devs, L, Libs, Locale, Prefs, S, that could have originated from the Chrysalis Pack. So, I know my system will not be a factor in any failures I have with the system software in most circumstances, but these files were not the cause for the "freeze" with v3.20 - it is v3.20 itself that is to blame and whoever in the MorphOS Development Team that did not do their due diligence in ensuring it all worked harmoniously before it was released.
That said I never had any issue with the files that were believed to have originated from the Chrysalis Pack that I removed. As it seems they never interfered, for me, with the day-to-day running of my MorphOS system, but it is nice to have learned from "geit" what should be where, and what should not, and I feel more settled that my system is not going to be the cause of an issue going forward.

It is just that v3.20 needs fixing for my iMac G5 iSight hardware, and I cannot believe that the MorphOS Development Team let this issue, amongst a few others for my hardware (which I have reported) slip through their usually so careful process of checking a release that was considered ready before they did just that! I can only hope for a quick resolution to this current situation with MorphOS v3.20.
MacMini 1.5GHz,64MB VRAM, PowerBooks A1138/9 (Model 5,8/9),PowerMac G5 2.3GHz(DP), iMac A1145 2.1GHz 20", all with MorphOS v3.19+,Airport,Bluetooth,A1016 Keyboard,T-RB22 Mouse,DVD-RW-DL,MiniMax,Firewire/USB2 & MacOSX 10.4/5