Updating system

@Tuvok
Yes, you are perfectly correct Tuvok 😡

@SteffJay
If you have no booting media, you can download .iso from Hyperion site and made USB stick:
https://forum.hyperion-entertainment.com/viewtopic.php?t=3857

@sailor
I have logged in but cannot find the file.
Can you give me a direct link to it please ?
Many thanks.

@SteffJay
I am sorry, I have no X5000, so I cannot see it.
Only downloads of registered systems are visible.
Did you registred your AmigaOS 4.1FE on Hyperion?
Here areyour registered systems.
Here should be download of AmigaOS 4.1FE.

Please, an some X5000 user confirm, if dowloads are on Hyperion site?

Hi. Yes, they are there if you have registered the key.

@SteffJay

I am sorry to see this horror story. I sincerely hope that you can recover.

I do not own an X5000, but I am very happy that I had a CD-ROM drive and backup CD to fall back to on those occasions that I ran into problems.

---
redfox

@experts/hyperion guys

Surely there is a way to modify the installation routine to automatically adjust the kicklayout file for owners of X5000 and X1000, instead of using this risky method of expecting the user to make the changes manually.

And, yes, keep a copy of the original kicklayout file just in case.

---
redfox

It's not perfect, but you should have a USB stick at the least with your X5000, and you should be able to boot into the boot menu. Yes, the incompatibility of some keyboards is annoying.

Anyway, that is just my opinion. I see though: it is not particularly user friendly unless all the planets align.

@redfox

Quote:Of course there is, and this has also been discussed, e.g. back when preparing Update 2.

But there are so many ways a Kicklayout file can look (I have one with 25 different active configs - yes, in one file), and so much that can go wrong, so in the end it was decided not to try it.

Maybe one day someone will get the idea to write a simple GUI tool to maintain Kicklayout files; if anybody bites, I'm willing to test and make suggestions etc.

Best regards,

Niels

@redfox

Of course, the whole thing is a bit annoying if you just want to get your system up and running, as in our example.

To be honest, you should not change anything on the recovery USB stick as it is for emergencies and you can get back your system that is no longer working. I personally like the idea of the recovery USB stick and I also got it when I bought my X5000.

Can AmigaOs4.1 also be booted from a USB-CDRom? I haven't tried this myself.

@nbache

Wow, Niels! That must be quite a configuration.

Cheers,
redfox

When I received my X5000 from Amedia with the recovery key, I immediately created an Img version on my Mac just in case.

@skynet

Quote:

Of course you did.

Did John teach you, or was ist Sarah?

@redfox

Quote:Yeah. Many years of testing (alpha, beta, RC) and having to be able to fall back etc. Maybe half of them are not in use any more, but I keep them so I don't have to get used to new numbers/letters to press in the AmigaBoot menu.

Best regards,

Niels

@nbache
yes, some kicklayout configurations are very complex. Kudos to yours 25 alternatives. I had maximum seven.

But what about simply add to installation script:
sed -i 's/p5020sata.device.kmod/p50x0sata.device.kmod/' kicklayout?

It solves vast majority of configurations. If somebody has his extra-special, such guy has no problem to change it by hand.

@sailor

A fresh OS4.2 iso will solve all these problems :)

There is another scenario when updated kickstart modules and kicklayouts becomes problematic.

I don't always have my kickstart folder in sys:kickstart

But having an "novice" mode and advanced mode would be better for kickstart configurations where novice mode would be used most of the time with a standard kickstart-layout that just works.

The problem with these "solves most normal situations" solutions is that they don't necessarily.

Say you have just two boot partitions, one for daily use and one for fallback. And you have the Kicklayout covering both in the first one's Kickstart dir. Some smart friend has set those up for you, and you know that when you make an update, and something goes wrong, you can always boot the fallback system and fix it (or get help to fix it).

So if you run this update on the daily partition, you certainly don't want a sed line to change both your configurations in your one Kicklayout file, because then your fallback system is dead in the water. The line in Kicklayout now refers to p50x0, but you still have the old p5020 file in the fallback's Kickstart.

Situations like this are the reason for the decision not to try doing the update automatically.

Believe me, it was a lengthy discussion, and much can be said for both opinions, but in the end, that's how the decision was taken.

Best regards,

Niels