AxRuntime

[AMIGASYSTEM]

@cdimauro, @AMIGASYSTEM

I think that is already possible. I saw somethink called "Linux subsystem for Windows" which allows running Linux X11 applications on Windows. Since AxRuntime is just one such application it should be possible to "run" it under Windows. I don't use Windows on daily basis, but if you do and want to experiment, I'd be interested in results.

I'll see to configure a PC that has the right setup, I'm not Linux expert, I'll follow THIS guide to install "VcXsrv" I hope it's fit for purpose.

[deadwood]

@cdimauro, @AMIGASYSTEM

Looking forward to results of your tests

[cdimauro]

Yup. I'm offshore for 3 weeks and I haven't my setup here, but I'll try once I'm back home. Anyway, following the development. 

[AMIGASYSTEM]

On my Windows 10 laptop I installed "VcXsrv Windows X Server", "BvSshServer" and "BvSshClient" successfully and everything works perfectly see screenshot.

With XLancer I can start Linux applications included in the package but I don't know how to start other external Linux applications.

It seems that to have the Windows Subsystem for Linux (WSL) on Win10 you need to have a Bulid 14393 or higher, unfortunately I have an older Buld and therefore I can not install / enable WSL, any idea to solve this?

[magorium]

It seems that to have the Windows Subsystem for Linux (WSL) on Win10 you need to have a Bulid 14393 or higher, unfortunately I have an older Buld and therefore I can not install / enable WSL, any idea to solve this?

disclaimer: not a windows user, no experience with the process. I just post what i could find.

This documentation talks about doing it the easy way.

That requires an even higher build number but, does show a link (see here) on how to how to install WSL manually (on a windows with a lower build number).

Note that in the first linked document there are also instructions on how to check your build and how to update your windows system.

(Funny that you asked how to update your windows, as the constant windows background updates was reason for me to quit windows altogether).

fwiw:
I am confused on how MS advertises the requirements, as they seem to differ on every other document. One page tells you that you cannot update to wsl2 on windows 10 (only windows 11) while another document writes that it is no problem. There are even pages that claim that you can't run x-server on windows 10 *period* and that you need to update to windows 11.

Would be interesting to know where the truth ends up 

[AMIGASYSTEM]

magorium I have read and followed that tutorial and many others, unfortunately my Windows 10 Enterprise which I find great (boots in 3 seconds, see link) is outdated and doesn't include the necessary software, also my Windows 10 is 32Bit, WSL requires a 64Bit Win10 system.

https://drive.google.com/file/d/1TaRVsm2B8KmRfb8J13_PJKX4Pz-9HV7C/view

[cdimauro]

@AMIGASYSTEM: it should be possible to upgrade your Windows 10 to the latest version, which supports WSL2 and GUI applications.
WSL(1) is really too outdated and with a lot of issues: it's usable only from command line.

[AMIGASYSTEM]

Builds lower than version 18362 do not support WSL2, I have a Build 14393

https://docs.microsoft.com/it-it/windows/wsl/install-manual

[cdimauro]

That's what I meant before: upgrade your Windows to a later version (the last one, ideally), and you should be able to install WSL2.

[deadwood]

Hi All,

A new version of AxRuntime is now available! AxRuntime lets developers compile their Amiga API-based applications as Linux programs.

The highlights of release v41.2 are:

1) AROS-Shell, an AmigaDOS-compatible Shell, is now available for you as a native Linux program. You can write DOS scripts and use shell commands to interact with Linux filesystem.
2) AxRuntime becomes a bridge between AROS x86_64 and Linux by allowing running native AROS programs as standalone Linux programs. In this function AxRuntime is similar to Wine. Wine allows running Windows programs on Linux, AxRuntime allows running AROS programs on Linux.

This release comes with 4 applications: AROS-Shell, MPlayer, WookieChat and Final Writer 7 (demo). Additionally AROS x86_64 applications like MUIbase can also be used!

A full change log of this release is available here: https://axrt.org/index.php?tab=releasenotes#AXRT412. To download AxRuntime packages and applications go to https://axrt.org/index.php?tab=download.

If you are interested in using AxRuntime for your projects or even contributing to AxRuntime, please contact me via email or PM on one of the listed sites: https://axrt.org/index.php?tab=community

Below you can see a selection Amiga programs running on a linux desktop. For more screen shots, visit https://axrt.org/index.php?tab=gallery

[Amiwell]

thank you deadwood

[cdimauro]

I've finally managed to run FinalWriter using the AxRuntime on WSL2 (see attached screenshot).
It took sometime because I've messed-up my WSL2 configuration, and trying to find the root cause and fix it was a nightmare. Anyway, for Windows uses that want to use GUI Linux applications on WSL2, please just follow the below guidelines and do NOT try something else!
Run Linux GUI apps on the Windows Subsystem for Linux (preview)
Running WSL GUI Apps on Windows 10

However and I don't know if it's FinalWriter and/or AxRuntime, but it's quite unstable: it easily segfaults. Likely it's caused by my multimonitor system (I've two completely different monitors). In fact, the application opens on the left screen, but if I right-click with the mouse then the menu appears on the right one, and if I try to reach it... it segfauls:

Code: [Select]

[FWMouse] ms_setmouse(): IDCMP_MOUSEMOVE above correct word / no text!
[FinalWriter] ctm_DoEvent()
XError 3 (Major=15, Minor=0) task = Intuition menu handler
BadWindow (invalid Window parameter)
Segmentation fault (core dumped)But at least I was able to execute something.

[deadwood]

@cdimauro

Thanks a lot for doing these experiments! Greatly appreciated.

I think the most possible answer to stability issues you are having is "both". AxRuntime was not tested with dual screen setup and its possible I made some hardcodes there that assume single monitor. On the other hand, FinalWriter is still in beta and probably does have some issues still.

Could you make another test? Use MPlayer or WookieChat instead of FinalWriter as well we disconnect your second monitor?

[cdimauro]

Sure. Unfortunately there are the same stability issues, even using only a monitor. It happened with all applications: FinalWriter (checked again), MPlayer, and WookieChat.


Full logs for MPlayer:

Code: [Select]

cesare@Conan:~/MPlayer$ ./gmplayer
<<INFO>>: AxRT 41.2
<<INFO>>: Using absolute paths.
<<INFO>>: RUNTIME_ROOT: /usr/lib/x86_64-linux-gnu/axrt/4.0/
<<INFO>>: AXRTSYS     : ROOT:usr/lib/x86_64-linux-gnu/axrt/4.0/
<<INFO>>: USERSYS     : ROOT:home/cesare/.axrt/
Xlib:  extension "XFree86-VidModeExtension" missing on display "192.168.2.126:0".
<<INFO>>: CURRENT_DIR : ROOT:home/cesare/MPlayer/
<<INFO>>: PROGRAM DIR : ROOT:home/cesare/MPlayer/
<<INFO>>: PROGRAM NAME: gmplayer
AxRuntime does not support AllocAbs(nommu_AllocAbs)
MPlayer UNKNOWN-9 (C) 2000-2012 MPlayer Team
VO: [cgx_wpa] Preinit.
File not found: 'PROGDIR:conf/lastplaylist.pls'
Failed to open PROGDIR:conf/lastplaylist.pls.
Error while opening playlist file PROGDIR:conf/lastplaylist.pls: No such file or directory
XError 3 (Major=15, Minor=0) task = Intuition menu handler
BadWindow (invalid Window parameter)




MPlayer interrupted by signal 11 in module: unknown
- MPlayer crashed by bad usage of CPU/FPU/RAM.
  Recompile MPlayer with --enable-debug and make a 'gdb' backtrace and
  disassembly. Details in DOCS/HTML/en/bugreports_what.html#bugreports_crash.
- MPlayer crashed. This shouldn't happen.
  It can be a bug in the MPlayer code _or_ in your drivers _or_ in your
  gcc version. If you think it's MPlayer's fault, please read
  DOCS/HTML/en/bugreports.html and follow the instructions there. We can't and
  won't help unless you provide this information when reporting a possible bug.

and for WookieChat:

Code: [Select]

cesare@Conan:~/WookieChat$ ./WookieChat
<<INFO>>: AxRT 41.2
<<INFO>>: Using absolute paths.
<<INFO>>: RUNTIME_ROOT: /usr/lib/x86_64-linux-gnu/axrt/4.0/
<<INFO>>: AXRTSYS     : ROOT:usr/lib/x86_64-linux-gnu/axrt/4.0/
<<INFO>>: USERSYS     : ROOT:home/cesare/.axrt/
Xlib:  extension "XFree86-VidModeExtension" missing on display "192.168.2.126:0".
<<INFO>>: CURRENT_DIR : ROOT:home/cesare/WookieChat/
<<INFO>>: PROGRAM DIR : ROOT:home/cesare/WookieChat/
<<INFO>>: PROGRAM NAME: WookieChat
AxRuntime does not support AllocAbs(nommu_AllocAbs)




******************************************************************************
wookiechat.c (55) main() - WookieChat - Transmission begins...
XError 3 (Major=15, Minor=0) task = Intuition menu handler
BadWindow (invalid Window parameter)
Segmentation fault (core dumped)

Applications crashes as usual: when right-clicking with the mouse, and trying to use the menu.


AROS-Shell works, but it has no menu, so it doesn't crash.

[cdimauro]

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.