- you had AmigaOS Update 1 installed.
- you attempted to update to Update2 FE2. During the installation you attempted to update the kicklayout file but "it crashed".
- you could no longer boot into WB, presumably because of not being able to update the kicklayout file.
- you could no longer boot into the boot menu because of the keyboard.
- the HDD was found not to be good.
- there was confusion with which format the HDD should be.
- you CAN boot into WB using the flash drive IF the HDD is disconnected.
- then, the thumb drive became corrupt.
- you would have preferred a CD.
- you then replaced the battery on the MB and cleaned the components as well as receiving a new flash drive
- but now, the motherboard required SD card is corrupt.

That is quite a journey.

Let's see what SERIAL has to say. I am sure we will get there in the end.

Did you ever manage to get into the boot menu?

Also, serial would be good.

Hanging on a white screen is what happens when you are using a card that needs the more recent radeon drivers, but the flash drive only has the older one or limited one.

You either have to
1. put the more recent driver on the flash drive or
2. ensure you have an older gfx card.

No one should have to go through this, but it is what it is.

A serial cable is also important since we could confirm that all of this started because of the modification to the kicklayout. It would then also have confirmed that your new issue is the issue with the gfx driver.

Regardless, you will need to boot into the flash drive and so it would be important to know which card you have.

Which gfx card? Could it be that the thumb drive is not using the radeon drivers that support your graphics card?

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.

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

I wouldn't think the boot selector would be effected by changing kicklayout.

Somewhere there is an error in the kicklayout and serial output would help. I cannot remember if you can make it show serial output instead of the splash screen.

Easiest would be to boot from some recovery USB / CD and load up your HDD system partition's Kickstart/Kicklayout.

@maijestro
https://github.com/3246251196/openmohaa/tree/AmigaOS4_0_81_1

I'll throw this on github soon. I am not working on it any more since I have what I want out of it, which is to play on the AB server v2 rocket rifle only. For me, it is playable enough.

Can you point to the repository or provide it so that I can also test this?

Needs a version of libstdc++.so that has that symbol.

Right. So when I am downloading my "special" movies - I should avoid HEVC?

Okay. Thanks for the info.

@Hans
Thanks for the response.






Radeon mentioned above.

@maijestro
I didn't say it is the best possible. Only that of all the builds so far, the latest is the best performing one.

@TheMagicSN
I cannot reproduce your problem on my X1000, so I don't know.

@TheMagicSN
maybe you are interested in the above comment.

r756 should no longer rely on bsdsocket.library.

@maijestro
It is release mode just with a bunch of debugging symbols so that would not affect the performance. Let me know the level and whether I can "teleport" there quicker... Out of all the builds, this one will be the better performing one.

As for bsdsocket, I will check this when I get the time.

Thanks.

@maijestro
r755. Added version string. Increased scope of optimization. Fixed a few more alignment issues due to increasing optimization scope. Re-introduced gstab debugging symbols.