OS4.1FEu1 Installer 53.9 thinks it is 43.1

coldacid · 12 April 2020, 06:07

And it causes the installer script for MUIBase to bomb out since it demands 43.3 or newer to run. Has anyone else come across this? I'm going to comment out the installer version check in the script but this is weirding me right out.

ma693541 · 12 April 2020, 08:59

I see that you live in Canada. Try not to localize your setup to french if that's your native language. I tried to install Picasso96 on an 68K machine that was localized to Norwegian, I found out the same as you, script stalled/bombed out, when the localization was on Norwegian.

So you have found the second, bad written installer script I know about.

coldacid · 12 April 2020, 17:04

Nah, I have language set to English. And I don't think it's the script itself, Installer is returning the wrong version number. Instead of returning 3473417 for the @installer-version value (for 53.9), it's returning 2818049 (for 43.1), and the MUIbase installer script compares this to 2818051 (for 43.3), finding it lacking.

Going through the installer script, it's actually quite well written. Installer just is providing a different, much older version to scripts instead of its actual version.

Daedalus · 12 April 2020, 17:31

The installer reports an earlier version for compatibility. It's the same in 3.1.4. The problem is that Installer version 44 is from 3.5 & 3.9, and provides extra features that aren't available in the newer versions. So for compatibility with scripts that might expect the 3.5/3.9 installer extra features, they report v43.

Now, I thought this was reported as v43.3, since that's the latest 3.1 one and was current for many years, effectively becoming the standard, so I don't understand the 43.1 report here.

coldacid · 12 April 2020, 17:33

Yeah something is screwy with 4.1FEu1 Installer, because it should be reporting 43.3 or newer, but doesn't.

ma693541 · 12 April 2020, 18:05

Have you tried to install MUIBase before you installed Update 1 and took a backup too of important files before installing Update 1?

coldacid · 12 April 2020, 18:24

I went from 4.1FE fresh install to update 1 before I bothered installing anything else, back when I set this up.

muibase · 01 August 2022, 08:37

I stumbled over this thread after another AOS4 user reported this to me directly.

This is now fixed at head, i.e. requiring Installer V43.1 instead of V43.3. However, the latest MUIbase version 4.5 still has this problem, thus if you run into this, just edit the Install-MUIbase file and set the required Installer revision to 1 (set #installer_rev 1).

12 April 2020, 06:07	#1
coldacid WinUAE 4000/40, V4SA Join Date: Apr 2020 Location: East of Oshawa Posts: 538	OS4.1FEu1 Installer 53.9 thinks it is 43.1 And it causes the installer script for MUIBase to bomb out since it demands 43.3 or newer to run. Has anyone else come across this? I'm going to comment out the installer version check in the script but this is weirding me right out.

12 April 2020, 18:05	#6
ma693541 Computer Wizard Join Date: Aug 2007 Location: Ramberg/Norway Posts: 928	Have you tried to install MUIBase before you installed Update 1 and took a backup too of important files before installing Update 1? Last edited by ma693541; 12 April 2020 at 18:29. Reason: Wrong name on the MUI program.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
OS4.1FEu1 - Supported?	MartinW	support.WinUAE	7	08 September 2017 15:04
BigRamPlus and OS4.1FEu1	bozimmerman	support.Hardware	2	18 March 2017 08:32
OS4.1FE SDK in WinUAE - Installer fails	elowan	support.WinUAE	17	19 August 2016 10:18
Hdd 'thinks' it is full at startup	Galder	support.Hardware	9	19 May 2014 00:13
Firefox thinks Retroboard is a dangerous site...	MazinKaesar	Retrogaming General Discussion	20	16 February 2009 10:53

12 April 2020, 08:59	#2
ma693541 Computer Wizard Join Date: Aug 2007 Location: Ramberg/Norway Posts: 928	I see that you live in Canada. Try not to localize your setup to french if that's your native language. I tried to install Picasso96 on an 68K machine that was localized to Norwegian, I found out the same as you, script stalled/bombed out, when the localization was on Norwegian. So you have found the second, bad written installer script I know about.

12 April 2020, 17:04	#3
coldacid WinUAE 4000/40, V4SA Join Date: Apr 2020 Location: East of Oshawa Posts: 538	Nah, I have language set to English. And I don't think it's the script itself, Installer is returning the wrong version number. Instead of returning 3473417 for the @installer-version value (for 53.9), it's returning 2818049 (for 43.1), and the MUIbase installer script compares this to 2818051 (for 43.3), finding it lacking. Going through the installer script, it's actually quite well written. Installer just is providing a different, much older version to scripts instead of its actual version.

12 April 2020, 17:31	#4
Daedalus Registered User Join Date: Jun 2009 Location: Dublin, then Glasgow Posts: 6,334	The installer reports an earlier version for compatibility. It's the same in 3.1.4. The problem is that Installer version 44 is from 3.5 & 3.9, and provides extra features that aren't available in the newer versions. So for compatibility with scripts that might expect the 3.5/3.9 installer extra features, they report v43. Now, I thought this was reported as v43.3, since that's the latest 3.1 one and was current for many years, effectively becoming the standard, so I don't understand the 43.1 report here.

12 April 2020, 17:33	#5
coldacid WinUAE 4000/40, V4SA Join Date: Apr 2020 Location: East of Oshawa Posts: 538	Yeah something is screwy with 4.1FEu1 Installer, because it should be reporting 43.3 or newer, but doesn't.

12 April 2020, 18:24	#7
coldacid WinUAE 4000/40, V4SA Join Date: Apr 2020 Location: East of Oshawa Posts: 538	I went from 4.1FE fresh install to update 1 before I bothered installing anything else, back when I set this up.

01 August 2022, 08:37	#8
muibase Registered User Join Date: Jul 2022 Location: Cupertino Posts: 1	I stumbled over this thread after another AOS4 user reported this to me directly. This is now fixed at head, i.e. requiring Installer V43.1 instead of V43.3. However, the latest MUIbase version 4.5 still has this problem, thus if you run into this, just edit the Install-MUIbase file and set the required Installer revision to 1 (set #installer_rev 1).

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)