MUI installation leads to forceful unwanted ASL patching

I ran AmiUpdate just to make sure everything was upto date. One of the things was MUI which required a manual install. So there was a directory in RAM: named Unpacked. So, I just installed it using the "Install" script in there.

Problem is, all my file requesters etc are using this MUI versus whatever it was using before and I want it how it looked before.

Does anyone know what to do?

Regards.

This looks suspicious and it is at the end of my UserStartup:


Before, this was not in my user-startup.

And, before - at the beginning of my US:

But, now it is:


Just wondering what to do.

@rjd324

Without having been there yet myself, I'd say you should remove, or comment out, the ";BEGIN MUI ASL" to ";END MUI ASL" section in UserStartup so you don't get the PatchASL program run.

WTF is MUI doing forcing an ASL patch on people

Okay, I have just commented out the ASL patch and now it is okay.

@rjd324

This has been covered before

...and you can leave what MUI added to the user-startup, that's how the latest MUI roll, got it in my user-startup aswell for quite some revisions now

BTW, I don't think AmiUpdate has anything to do with this, so why refer to it in the subject?

Best regards,

Niels

@nbache
Fixed.

@rjd324

Its all down to the installer, in that if you set it to 'Beginner' then you do not get asked if you want to replace the ASL requester with the MUI one. Set it to anything else and you have the choice.

What I always hated about MUI is the arrogance of its developers in assuming if we installed MUI it meant we wanted all MUI all the time in as many places as possible. While it was always an impressive piece of software it was also massively over-engineered for what it actually needed to be and why ClassAct was the better implementation. Shame it came much later on by which time MUI was a mandatory dependency to be able to use some of the best apps of the time.