@amigakit

>Se changed the website to detect what region your IP is from and then switch to the appropriate currency. Please try again and
>let us know if it is working for Finland.

I did not find any option for that... Do you have to be logged in to use that detect feature?

>We will be opening a EU office soon.

That's good news! Do you already know in what country that office will be located, and whether the VAT of that place is applied for purchases (or the VAT of each customer's home country)?

A request to AmigaKit and A-Eon... Could you please explain us, as clearly as possible, how the Brexit exactly effects on purhases made from countries inside EU, and especially on different hardware products from A-Eon (Cyrus+, A1222, AmigaMouse etc...)?

If I have understood right, the origin of the product has now effect on how it is treated in customs of EU countries.

A couple of specific questions:

1) How should the AmigaKit www-page be opened so that it would show the prices correctly in EURs? If I open first https://amigakit.amiga.store/?currency=EUR, and then choose any product, the price is '0', until I choose again 'EUR' from the top of the page. If I then select another product, the price is again '0'. How can I keep the page using 'EUR' constantly?

2) So far some A-Eon dealers, like Alinea in Germany, has been forbidden to sell Cyrus+/X5000 outside their own country. Now, when AmigaKit is outside EU (and thus more expansive place for many EU citizens) and Alinea inside it, has this unnecessary limitation finally been removed? If not, WHY?

Important note to all: this question is addressed to AmigaKit/A-Eon, not to anyone else. So please do not fill this thread with the usual fruitless specutations etc... Thank you .

@SinanSam460

Is your Cyrus board a beta revision (2.1)? Have you ever changed the CPU fan or is it still the original one? If I remember right there was some improvement concerning the CPU fan in the later 2.2 revision.

Is the ambient temperature in your area very high...? If you have a new CPU fan at hands, and some properly cooled place nearby, it might be good idea to test whether the problem is anyhow dependent on temperature. If the issue is inside the P5020 as it seems to be, even a small temperature change may have effect on it.

A repair center (preferably inside EU, as AmigaKit/Varisys will soon be outside) would be a good idea!

Have you looked at the data sheets for P5020:

https://www.nxp.com.cn/docs/en/data-sheet/P5020.pdf

I do not know whether it can help to fix the problem but at least you can see more precisely what is not working... (e.g Vdd_ca, page 57)

I noticed that logging with Odyssey to 'Posteo' (posteo.de) stopped to work a couple of days ago... The login button is now inactive and has the text: "Please enable javascript". Javascript is 'on' in my settings, though, and I have not changed lately any settings of Odyssey. 'Spoofing' has not any effect on this issue.

Posteo's customer support said that they do not 'lock' intentionally any software (like some other companies!), and suggested to delete cookies and caches. But I checked that I have not any cookies saved for Posteo.

So, what might be wrong? Does it still work for any other user?

@amigakit

>I am unaware of any drivers that the X5000 is missing. Are
>you able to tell me what driver is omitted?

The 'lsi53c8xx.device' driver module is broken and totally useless in X5000!

See here:
https://forum.hyperion-entertainment.com/viewtopic.php?f=57&t=3768

Have been waiting for over three years for the fix to be published, in order to get access to my SCSI disks and use the data stored on them!

So, as Hyperion is not willing to publish a working driver, when will A-Eon include a replacement module in the Enhancer software?

@Paul
Are you using the 'Sound' prefs from 'Enhancer package' or the OS4.1 native 'AHI' prefs for controlling your card? If you are using the first one, try to remove the AHI settings file (ahi.prefs) from Sys:Prefs/Env-archive/Sys, if present. Then reboot.

If that does not help, try the opposite: remove the settings file for Enhancer 'Sound' and try the original 'AHI' to setup you card.

BTW, do you have also some other sound card in your machine? Removing the audiomode file (in Devs:Audiomodes) for that second card might also help.

@Paul

If the problem is originally the same I noticed with Odyssey and YAM, it should be already fixed:

http://muidev.de/ticket/431#

I do not know if the fix has already been released, but there are a couple of workarounds, like using an older version of Clock, or disabling from the program's MUI settings 'Drag&Drop/Autostart' option.

@Spectre660

> It is possible that you don't actually have the driver for the Polaris card installed on the USB startup drive . It is currently sold as an
> extra pre release item of the the Enhancer 2.0 as Enhancer 2.0 has not been released yet. Solution is to try booting from a supported older model
> video card.

Indeed... I had forgotten that detail and gave somewhat missleading info to Paul in the earlier thread. Sorry...

The other possibility is to buy that Radeon HD 3.x drivers prerelease packeage (that purchase gives the right to download the Enhancer 2.0 software, too, when ready). But it is available via AmiStore which can only used from a working AmigaOS system.

Paul: maybe you could contact AmigaKit and ask for some custom arrangement for purchaasing that 3.x driver package?

@Paul

>So I ordered an X5000/20 motherboard from Amigakit rather
>than waiting longer for an X5000/40.

Congratulations!-)

Did you already get a confirmation about your order? Did they give you any info how fast they can currently send the Cyrus board...?

AmigaKit has been very difficult to contact lately :-/.

>I'll be getting the boot USB stick with the Enhancer pack
>included. Should I be able to boot into a working screen
>using the USB boot and this card? Or do I have to get an
>older card to set it up first, and then get this Gigabyte
>card put in?

The 'emergency boot stick' has both AmigaOS and the enhancer software installed, so it should be possible to boot directly from it, if just your graphics card is suported by the latest RadeonHD and RadeonRX drivers.

But you may have to first go to the UBoot cli and give there the "USB reset" command. At least my X5000 does not boot from any USB disk without that.

>Is getting into and maneuvering around the Uboot screen
>pretty similar to how the A1 Uboot worked?

I do not know about A1 Uboot, but there is one big problem with X5000: there is no complete documentation about the Uboot commands and env variables. You have to manage with the information you can get from Uboot cli itself using commands like 'env print'.

I cannot get the seat selection to work with Odyssey on this railroad company's site:

https://shop.vr.fi/onlineshop/Welcome.do?request_locale=en

(You can test it by choosing e.g. from "Helsinki" to "Turku").

When I get to the screen where there is the "select seats" button and click it, there should be opened a car/seat map window in html format, but instead there appears just a note suggesting to install flashplayer (this happens also with Firefox if the security settings are too tight or there is an adblocker active - flash is really _not_ needed if the settings are correct!).

What settings should I use in Odyssey to get the seat selection to work? I have already turned of the internal adblock option and tested most of the spoofing options.

The Clock v.53.29 can cause a problem with MUI programs when dragging objects, resulting in a system freeze. If I open the clock on WB screen in analog (with arms) mode, and then open e.g. YAM and try to drag an attacment of a mail message to a disk, I get a system freeze (mouse and keyboard do not work, the clock stops). Also Odyssey shows similar problems. This issue is 100% reproducible in my X5000.

If I change the clock mode to analog or go back to v. 53.21 Clock, the problem dissappears completely.

According to the analysis of Thore Böckelman (http://muidev.de/ticket/431), the new clock version seems to use for unknown reason 'global screen locking', which causes a conflict with MUI programs used on the same screen. I'm not programmer, so please have a look in that ticket to see more details! There are also a couple of workarounds mentioned in it.

I noticed a couple of days ago that Instagram stopped totally to work with Odyssey. I get only an empty screen with a logo in the middle. I have tested all the betas and also the MOS version of Odyssey, no difference.

Any hope to get it to work again...? Odyssey was the only way to watch them in Amiga as all the PPC Linux browsers have currently the 'reversed colors' problem with Instagram videos!