Thread dedicated to AROS One v11 64 Bit Hosted Linux and AxRuntime experience !

First video dedicated to AROS One Hosted Linux, in the video it is possible to see AROS One 64Bit v11 hosted on "Linux Lite" based "Ubuntu", in the future a version of AROS One Hosted Linux is planned, but this will happen when a stable version of AROS 64Bit is available.

AXRuntime, the AROS One 64Bit Shell executed directly from the Linux Lite Desktop (Ubuntu based).

By running the Shell it is possible to execute Native AROS 64Bit Applications, practically like running the Shell from Wanderer (Workbench).

It is also possible to run normal AROS 64Bit executables from the Linux Desktop via the AROS Shell.

I enclose a Small Video showing the above.

This is a great video of AxRuntime in action. Thanks for bringing its vision to wider audience.

Thanks deadwood, today I wanted to do a little experiment, updating the "SYS" folder dedicated to AXRuntime, with the data from the AROS One "SYS", I ran it from the AROS One Shell, on Wanderer it seems that almost everything works fine, only with Zune Prefs I encountered a problem (Shell Closure).

The interesting thing is that Wanderer can also manage linux system folders

Also good speed as I still use Win7 64Bit on a DualCore PC now with 8GB RAM

I enclose a small video:

That's how it's supposed to work. Allow hiding Linux details and make the experience as Amiga-like as possible.

@deadwood

I was creating a version of AROS One Hosted Linux 64bit, but I noticed a serious error on the part of Dopus4. In many cases, files are copied from 0 bytes (doesn't always happen), see screenshot! This does not happen on native Wmare and native PC (it has never happened).

For Dopus4 to work on Linux Hosted, you need to disable the Trackdisk device, which I did using Hex Editor. This version that I modified works well on native AROS and native WMware, and the files are copied correctly.

Furthermore, on AROS Hos Linux Dopus4, when copying files from a shared folder, it goes into Guru mode. On native AROS, I solved this by increasing the stack on the Dopus icon.

EDTIT:

I would add that Dopus4 on Linux Hosted does not update the directories. For example, if you close AROS and add folders and files to AROS on the Linux side, Dopus4 will not see these new folders. This can be resolved by opening and closing AROS several times.

Are those files really having size of 0 bytes or is it just DOpus4 showing them as 0-bytes size?

I actually don't have to "remove" trackdisk.device from DOpus4. See screenshot - starts right after being built. I also never heard anyone else reporting trackidisk.device issues with DOpus4.

The issues that you report with DOpus4 not seeing directories added on host side -> are those directories visible in Wanderer and via dir command from shell?

I tried the following: Close AROS, add directory on host side, Open AROS, Open DOpus4. Each time the added directory was visible in DOpus4. I'm sorry, but as long as you are using a modified binary, we might simply be running into phantom issues.

@AMIGASYSTEM

Ok, I was able to replicate your crash thanks to Kalamatee. Please delete DEVS:trackdisk.device. This driver is only for native, it can't work correctly under hosted - that's why you are getting a crash.

Yes, it's true that a modified file could cause this strange behaviour. I suspected that too, but with Dopus4 32Bit Hosted Linux this doesn't happen. Dopus4 works fine and the folders are also updated.

Regarding the 0-byte files, they are real and checked on both Linux and Windows. Dopus4 does not see the updated folders, but Wanderer sees them fine, so there is no problem on the Wanderer side.

I would also like to point out that the copying of 0-byte files only happens when copying from a network share, and only with Dopus64Bit. It does not happen with Wanderer, nor does it happen with Dopus4 32Bit.

Is AROS hosted and native on Linux or via WMvare?

For native AROS, WMware allows you to add a floppy drive, while AROS on WMware Linux Hosted cannot manage this drive.

What procedures did you use to enable Dopus4 to have a floppy drive?

Ok, trackdisk.device has been removed from the system, and now Dopus4 starts up, but the ‘Copy’ problem remains, which in some cases creates Guru or Copiai files of 0 bytes. As mentioned, this does not always happen, but it is not advisable to use it without properly checking the copied files.