Hi All,

After two days of solving compilation and memory corruption errors, I finally get a first teaser screen shot of Odyssey working on 64-bit!

I guess this is the first ever 64-bit browser in Amiga-land.

Not yet usable, but at some point I should be able to share alpha versions for people who want to test.

Thanks deadwood, as soon as it is available I could test it on AROS One 64Bit !

Will there also be a 32Bit version?

Yes, both versions will be releases in parallel

Great Deadwood thank you

And now it actually connects and renders websites

Good

I have a laptop ready to host the 64-bit version of aros

deadwood

Great work. This is a much needed web browser.

Congrats!!

Well, it has taken me much more time than anticipated but... OWB 64-bit now works on Linux and Windows (through WSL) using AxRuntime! See attached screen shots.

These are still alpha versions and pretty unstable, but starting from today I can finally use Odyssey on daily basis.

This post is made using Odyssey from Linux

Thanks deadwood, what differences are there with what we have on x86?

is the same recompiled version

That's some really good news that 64 bit is working.

Thanks for your efforts. Much appreciated.

@AMIGASYSTEM

Functionality-wise it is the same. The difference is that 64-bit can address more RAM and CPU has newer instructions, so in effect the compiled binary and JIT might run faster. Additionally, on AxRuntime SMP is enabled, so the browser can use multiple CPU cores to render/work faster on heavy sites.

it is interesting to know that on axruntime the smp is enabled but I am not able to make an ad hoc distribution

the idea would be to start from the base of linux by taking the basic packages to boot the DE and then axruntime, i will wait patiently for future updates, the idea of using aros on each computer is interesting but i don't want to install a whole distribution and then boot aros like you do on windows with winuae

Hi All,

After some more work, first public version of 64-bit AROS is available!

To make the setup easier, @retrofaza prepared a very detailed tutorial:

https://arosnews.github.io/OWB-aros-linux-hosted/

Right now what can be tested in 64-bit OWB on 64-bit AROS hosted. In coming days we will also share turorial how to use OWB on Windows and Linux. Stay tuned!

This build of OWB uses the same code base as recently released update for 32-bit. If you notice any stability issues, please share them in this thread.

For the first time, BETA version of 64-bit Odyssey browser is available for people willing to try it out on either AROS-hosted or directly on Windows 11 or Linux. We prepared detailed turorials on how to install it on each of the supported platforms.

Odyssey on AROS:

https://arosnews.github.io/OWB-aros-linux-hosted/

Odyssey on Linux:

https://arosnews.github.io/OWB-axrt-linux/

Odyssey on Windows 11:

https://arosnews.github.io/OWB-axrt-wsl2/

We are looking for feedback on this development version, so please report back any stability issues or bugs you find. Please also keep in mind that this version still uses an old engine (201507) so there will be issues with rendering websites.

Posted from within OWB inside WSL2 in Windows!
The right menu works, file requester works, got to see ram disk et all, although when I closed the first time it closed the envirnoment!

It states "AxRuntime does not support AllocAbs(nommu_AllocAbs)"
The keyboard does not correspond to the one being used, neither on windows nor in linux
I had to click on the address bar a few times so it didn't lose focus
When moving and resizing the windows, I have to do it blindly.

Overall though, it's quite pleasant experience/surprise!

Update:
I've noticed it to be a recurring issue that causes a loss of focus when entering text again in the address field. Initially, I thought the problem occurred because it was the first time the program was running. However, I've realized that the issue arises whenever the dropdown suggestion box appears. Afterwards, when I was typing "amigaworld.net," the autocomplete dropdown appeared, and I had to click to continue typing. Worst still, it led it to a crash.

It behaves differently regarding the update/scale of ui. I loaded Firefox on WSL and it worked as expected, moving the full window, scaling...

Hi pixie,

Thanks for the tests! Comments from me:

1) No visual feedback when moving/resizing is a known issue related to WSL. It work on Linux. It will be fixed in one of the next runtime releases.
2) I guess keyboard is stuck at english. It is not synchronized with what the host is using.
3) I took a note of crash report with drop down box