Vanilla OS4.1FE cannot auto update to current.

[Yoji]

I posted an issue with updating my old OS4.1RE install here
viewtopic.php?t=5148

So I know it not great, but to compound the importance of a proper fix, I wanted to do a fresh install of AmigaOS4.1FE
My expectation was that I should be able to do the install and update to current without issues, i.e. mimic the experience of a new user who wants to embark on the OS 4.1FE experience.

It didnt go well.. (as an install on WinUAE 6.0.1)
So (following a guide) I managed to do it (with quite a few missteps, as guide was old, so few things slightly different, which threw me a few times)
So it was booting fine, and was updated with update 1, 2, and hotfix 2.
So now time to run AmiUpdate,
It finds some updates, but then when it goes to second update server, it prompts me to login for "AmigaOSUpdateServer" so I logged in with my credentials.
I needed update AmiUpdate again, so went through the process, but this time the lib update did not go the same way..
In my AmigaForever install, it said I should use the command "CopyStore", which worked, but is an unknown command on the WinUAE install env at this point, so that was strange. (I managed copy it to the libs dir with the normal copy command). And then AmiUpdate installed OK, so I am at 2.58 again.
But running AmiUpdate now, it finds some patches...
Worse.. if I try and update the presented updates.. (first one is AmiSSL Libraries (5.25) I get a guru meditation from the amiupdate task with "error of type DSI (Data Storage interrupt) and then things just hang/lock up until I kill the whole session..

So wont bore you with all the pain... but turns out it does look like its all FUBAR... you cannot update to "latest" from a vanilla install, there are intermediate steps that AmiUpdate does not handle

In the end I manually updated AmiSSL-5.1-OS4.lha..
That seemed to be the magic update.. Once I did that, AmiUpdate managed to update it to 5.25 without the Guru error and all other updates then seemed to go through OK

So I now seem to be fully up to date..
WoW.. what a painful process, but at least sorted now.

P.S. now that I am up to date, the "CopyStore" command that I mentioned above is now available, so I guess that must have been installed as part of one of the updates.

Whoever in charge of OS4 should def take a look at making it work properly.

P.S. Install guide was https://thomas-rapp.hier-im-netz.de/os41uae/index.html

[Yoji]

LOL, May be Hyperion heard me, just seen that update 3 was released yesterday!!!
May be that will resolve.. by going to update 3, it may in effect jump start everything to "catch up" and all be OK.
Dont plan to do a fresh install again to test... but fingers crossed.

[MichaelMerkel]

I posted an issue with updating my old OS4.1RE install here
viewtopic.php?t=5148

[...]
So now time to run AmiUpdate,
It finds some updates, but then when it goes to second update server, it prompts me to login for "AmigaOSUpdateServer" so I logged in with my credentials.
I needed update AmiUpdate again, so went through the process, but this time the lib update did not go the same way..

the problem is, that amiupdate needed an update to fox problems with connecting to the update servers. but the update could not be fetched from amipdate isself due to the problems with the older version...
the only possible solution is to download the lates amupdate package manually from amiupdate.net.
additionally SSL has moved on... so also the latest amissl package is required. that also should be fetched (e.g. from aminet) and installed.
after that amiupdate should run fine and be able to download and install all updates.

regards...
michael

[Yoji]

Thanks,

That should never be allowed to happen.
I dont know how sophisticated AmiUpdate is..i.e. how good it is at handling dependencies, but there is no way a patch should be put on the servers that cannot be actioned by the update process. If it needs a new AmiUpdate version, then that should be presented first, and the patch then presented when the required version of AmiUpdate is in place.
Through proper planning and care, it should always be possible for a new user to get from a vanilla install to the current "up to date" version via updates and the built in update tool
The problem is solved for now, since it looks like Update 3 does solve the problem and bridges the gaps that I experienced.
So just need Hyperion to do better and not let such a gap open again in future.

[nbache]

Please read my reply in your other thread.

Best regards,

Niels

[Yoji]

Thanks,

But you are mistaken when you say
"And it's not Update 3 itself which solved the issue, but AmiUpdate 2.58. Because it was known that this version had solved the previous Catch-22-like issues, it was decided to include it (still as a contribution) in the Update 3 archive." in the other thread, I replying here, as this is the thread where I specifically say

And then AmiUpdate installed OK, so I am at 2.58 again.
But running AmiUpdate now, it finds some patches...
Worse.. if I try and update the presented updates.. (first one is AmiSSL Libraries (5.25) I get a guru meditation from the amiupdate task with "error of type DSI (Data Storage interrupt) and then things just hang/lock up until I kill the whole session..

So wont bore you with all the pain... but turns out it does look like its all FUBAR... you cannot update to "latest" from a vanilla install, there are intermediate steps that AmiUpdate does not handle
In the end I manually updated AmiSSL-5.1-OS4.lha..
That seemed to be the magic update.. Once I did that, AmiUpdate managed to update it to 5.25 without the Guru error and all other updates then seemed to go through OK

So the AmiUpdate update to 2.58 was not enough on its own.

Since I have not tested, I cannot be sure it fixed, but I expect update 3 also updates the required Libs that was causing the guru (as well as the AmiUpdate to 2.58 fix).

[nbache]

If you had installed AmiUpdate first, before installing Update 3, the problem wouldn't have occurred.

Best regards,

Niels

[Yoji]

If you had installed AmiUpdate first, before installing Update 3, the problem wouldn't have occurred.

Best regards,

Niels

What!!!?? Your reading comprehension is not great (may be you are excused as with your Name, may be English is not your first language).
PLEASE reread what I said carefully... I even repeated the important bit in my latest reply, and then comment.
Remember.. this thread and initial post outlining the problem was posted BEFORE Update 3 was released..

Thanks.

[nbache]

Yeah, sorry, disregard the bit about Update 3 (it's just that a lot of my mind has been focused on Update 3 lately). But the point I wanted to make was that if you install the working version 2.58 of AmiUpdate before trying to use it to install anything else, things should go much smoother.

Best regards,

Niels

[Yoji]

But the point I wanted to make was that if you install the working version 2.58 of AmiUpdate before trying to use it to install anything else, things should go much smoother.

But thats exactly what I did!!!!
Installed Vanilla... Installed update 1,2,hotfix 2
Then AmiUpdate 2.58 (along with the required lib update to allow 2.58 to install).
And then using AmiUpdate failed with the guru error....
So may be you being careful with words in saying "things should go much smoother", it clearly just FAILS.

So while this may all be moot now.. since Update 3 would sort it, PLEASE understand what I have said (as your comments still suggest you have not understood).