AxRuntime

[deadwood]

The segfaults can be easily reproduced:
1) right-click with the mouse;
2) an extra horizontal bar with the menu appears;
3) move outside of the AROS application window frame.

Thanks for coming up with sequence that casuses the crash. I created a bug report here: https://github.com/deadw00d/AROS/issues/67

Does the crash happen only if you move the pointer outside of AROS application? There was a bug with right-click crash earlier, but it happened immediatelly after right click.

Are you able to run the program through GDB and get me a trace of crash?

[cdimauro]

No, the crashes happened only when moving the mouse pointer outside of the AROS "window area". In fact, I was also able to select some menu entry when the menu was reachable within the window area.
OK, next time I'll try to use gdb.

[OlafS3]

@Deadwood

the problem with Scalos prefs still exist. Fortunately i found a workaround by doing it with Scalos prefs in 3.X and then copying it over. These pref files work in both Aros 68k and X86. Perhaps it is solved later. Scalos is nice, in some areas not as good as Magellan but perhaps more like amiga user expect.

[cdimauro]

Are you able to run the program through GDB and get me a trace of crash?

Just added a comment on your GitHub issue, with log and screenshot.


The trace is very limited, but I hope that it's useful.


Let me know if you need more or some different tests.

[deadwood]

Thanks, let's continue investigating in the bug ticket on github.

[deadwood]

Run Linux GUI apps on the Windows Subsystem for Linux (preview)
Running WSL GUI Apps on Windows 10

Hi, I'm writing up documentation on using AxRuntime on Windows and I have a question about the links your provided. The first link is Microsoft one and it sounds very simple to get WSL2 running. However the second link seems to be about WSL (the first one) and using a third party application to gets things working. I assume these are redundant, that is if you have recent enough version of Windows 10 you should use the first guide, if not use the second one. Which approach (WSL2 or WSL + 3rd party application) are you using for testing AxRuntime under Windows 10?

[magorium]

@deadwood:
Please note that the first link is not intended for use with windows 10:

You will need to be on Windows 11 Build 22000 or later to access this feature. You can join the Windows Insiders Program to get the latest preview builds.

That is why I wrote earlier that m$ (as usual) is messing things up. From their own technical documents: You can and can't use x-server with WSL1, you need windows 10 build blah in order to be able to install WSL2, oh, it is actually windows 11 on another document etc. etc.

The only thing for sure is that cdimauro knows the requirements and what steps he took to get things running for him. Unfortunately (actually yeah!) no windows for me anymore so can't help there, sorry.

[deadwood]

Thanks, I didn't notice that. Let's wait for cdimauro response.

[cdimauro]

Run Linux GUI apps on the Windows Subsystem for Linux (preview)
Running WSL GUI Apps on Windows 10

Hi, I'm writing up documentation on using AxRuntime on Windows and I have a question about the links your provided. The first link is Microsoft one and it sounds very simple to get WSL2 running. However the second link seems to be about WSL (the first one) and using a third party application to gets things working. I assume these are redundant, that is if you have recent enough version of Windows 10 you should use the first guide, if not use the second one. Which approach (WSL2 or WSL + 3rd party application) are you using for testing AxRuntime under Windows 10?

The problem that I had is that just following the first link it didn't worked out. I wasn't able to launch any GUI application from WSL2.


Only when I've installed VcXsrv I was able to do it (and providing the IP of my Windows machine on the DISPLAY envar).


Maybe my configuration is still messed-up (I haven't reinstalled from scratch my WSL2 Ubuntu image). Someone else with an "untouched" Windows 11 machine could just try the first link and see if everything works.

@deadwood:
Please note that the first link is not intended for use with windows 10:

You will need to be on Windows 11 Build 22000 or later to access this feature. You can join the Windows Insiders Program to get the latest preview builds.

That is why I wrote earlier that m$ (as usual) is messing things up. From their own technical documents: You can and can't use x-server with WSL1, you need windows 10 build blah in order to be able to install WSL2, oh, it is actually windows 11 on another document etc. etc.

There's nothing messed-up, besides my current WSL2 machine maybe. 


It was clear and documented that WSL1 was a command-line only tool.


As it was clear that GUI support for WSL2 (not 1) was officially coming with Windows 11 (which I've).


P.S. If Microsoft products are messy, then you have not enough experience with Linux et all. 
I was able to have working Wi-Fi on my AMD C50 subnotebook only after installing one of the many Ubuntu derived distros: all previous ones (also not Ubuntu-based) failed miserable. It was my last resort and fortunately it worked out, otherwise the subnotebook was stored taking the dust now...

[magorium]

I'm not in for a full debate on this topic, but just click the first link (read that windows 11 is prerequisite), then read and click the first link that says you need windows 10 build blah.

It was clear and documented that WSL1 was a command-line only tool.

Hmz, I wonder why ever VcXsrc was being written.... and what it can be used for 

As it was clear that GUI support for WSL2 (not 1) was officially coming with Windows 11 (which I've).

Officially perhaps yes. But it was already possible with Windows 10 (and with WSL 1, using x-forwarding).

You _can_ take that with a grain of salt because I do not have any hands-on experience with WSL (1 or 2) but a gentle search on quack quack fly seem to do wonders (and actually makes sense as well).

P.S. If Microsoft products are messy, then you have not enough experience with Linux et all. 

True 

In the end, deadwood is in search of a reliable source so that he can quote from that (or base his documentation on it). Your experience helps (thank you for sharing) but I am assuming that it is common knowledge that x works for WSL2 on win 11. I am also assuming that it is the niche (WSL1/win10 or perhaps even wsl2/win10)  that is currently of more interest.

[cdimauro]

I'm not in for a full debate on this topic,

Not needed: let's just clarify the situation, for the benefit of the other users. 

but just click the first link (read that windows 11 is prerequisite), then read and click the first link that says you need windows 10 build blah.

Sorry, but I don't see Windows 10 on it. The first link which I encounter (going through the above first link of the two that I gave) points to the Windows Insider Program, which is general for both Windows 10 and 11.

It was clear and documented that WSL1 was a command-line only tool.

Hmz, I wonder why ever VcXsrc was being written.... and what it can be used for 

That's a different story. As I've stated, WSL (1) officially supported Linux only for command-line.


But Microsoft did nothing to prevent people for enabling GUI applications on it. It's simply (well, not that simple: it required some changes which where not really straightforward.) extra stuff that external people tried and succeeded. 

As it was clear that GUI support for WSL2 (not 1) was officially coming with Windows 11 (which I've).

Officially perhaps yes. But it was already possible with Windows 10 (and with WSL 1, using x-forwarding).

Sure. Nothing to say about that: see above.

In the end, deadwood is in search of a reliable source so that he can quote from that (or base his documentation on it). Your experience helps (thank you for sharing) but I am assuming that it is common knowledge that x works for WSL2 on win 11. I am also assuming that it is the niche (WSL1/win10 or perhaps even wsl2/win10)  that is currently of more interest.

Correct.

[deadwood]

Hi All,

Thanks to efforts of @cdimauro, AxRuntime is now confirmed to be working on Windows 11 using WSL. There were some issues that required a new release, 41.3 which is now available: https://axrt.org/index.php?tab=download. More information can be found in the documentation: https://github.com/deadw00d/AROS/blob/alt-runtime/arch/all-runtime/docs/distribution/README or a few post above. Enjoy!

[OlafS3]

interesting 

[braincure]

Dear friends. When I started my retirement life, I was pretty much into hobbies. Kuksa glass, wooden spoon, my real profession is like painting. Now, clearing up this huge mess, I started to get involved with the amiga, which has made my life a painter-graphic designer. However, I noticed some things. According to my investigations in this area, Amiga os 3.2.1 is for original hardware, Amiga os 4.1fe is for new amiga clone hardware, but with an emulator. "MorphOs" is for new amiga clone hardware and older hardware with Apple Power processors. Finally, I reviewed Aros 32 and 64. Aros x32 seems to have single processor support. Aros 64 multi-processor support. It seems that Amiga developers always have a weakness. Not focusing on up-to-date hardware and competing seems to have followed no rational path. I want to know this. What applications can be called vital that work on Aros 32 and not on Aros 64? Like emulators. Could you give information. Which version (x86-x64) is currently in active development? Has there been an effort to add multiprocessor support for x32? Thank you in advance for your interest. I can't even imagine what it would be like today if the Amiga had progressed in the right way. stay with love.

[AMIGASYSTEM]

Hi braincure, to know the situation just read the various discussions on this forum, sure AROS x86 ABI-v0 is the system that has remarkable softawre, all the others have no dedicated software except some sporadic application.

The problem is that AROS developers are few while users theoretically are "many" even if passing through, just look at the movement of this forum, so many visitors but only very few linger to discuss, as a result there is no growth and right information.

I do not know the technical functions of the CPU on AROS x86 ABI-v0, but I can assure you that on my Dual-Core AROS x86 is blazingly fast.