New update for Dopus4 Config on AROS One (32/64/68k) it is now possible to ‘automatically’ unpack an archive, LHALZH, LZX, ZIP, RAR, 7ZIP, TAR.BZ2, TAR.GZ, TAR.Z, CAB (MSCF), CAB (ISC) with a simple Double-Click (LMB), the data included in the archive will be unpacked in the same path as the archive, while with ‘Click-M-Click’ you can see the list of the archive contents., see attached video.

https://youtu.be/...

All 38 AROS One 64/32/68k themes have been modified. Now, the AROS One text on the top bar of Wanderer (Titlebar) is no longer text, but a PNG image positioned by (SBarLogo) on the left side of the bar. The title (TitleOffset) has also been moved forward to make room for the logo.

Now, with any video resolution, the AROS One logo (SBarLogo) and (Titlebar) will always remain in the same place, see screenshot

If you notice any imperfections in any theme, please report them!

Fixed the ‘ArosOne-Angled’ and ‘ArosOne-BlueWave’ themes that had a problem with the window bar text, which was shifted too far to the left, almost to the edge, see screenshot. Now the text is in the correct position.

If you encounter any other problems with any theme, please report them in this post and I will try to fix them.

Created two scripts that allow you to disable or enable TrackDisk and NTFS Filesystem. The scripts will be present on both AROS 0ne 64-bit and 32-bit.

Some laptops no longer support floppy drives, and AROS may not start or Dopus4 may not work.
The Disable button will remove TrackDisk.device from the DEVS system folder.
The Enable command will do the opposite, i.e. restore TrackDisk.device to Devs.

The NTFS file system may be necessary to share data from an NTFS-formatted hard disk.
The Enable button will make a simple copy of the ‘ntfs-handler’ file in the L folder and enable the use of the NTFS file system. The Disable will do the exact opposite, i.e. it will remove the ‘ntfs-handler’ file from the L folder.

I would like to point out that on AROS One 32Bit in Storage/NTFS there is also ‘ntfs3g-handler’ which, compared to ‘ntfs-handler’, allows not only reading but also writing to an NTFS-formatted hard disk.Be careful when using ‘ntfs3g-handler’ because it could allow you to delete files from Windows systems if you are using Dual-Boot with Windows systems.

The sources for ‘ntfs3g-handler’ exist, but I have not been able to convert it to 64-bit. I hope that the author will also compile the 64-bit AROS version in the next update.

Listen to MOD music on AROS One 1.2 64bit

If you want to listen to MOD files from Wanderer and Dopus4, you need to copy the ‘AmiPlayMOD’ player to the C (I forgot to do this)

You can find the ‘AmiPlayMOD’ player in the path Extras/DOS-Tools/Music/AmiPlayMOD.

‘AmiPlayMOD’ is a good “DOS” player, but in the Extras/Music folder you will find a script I wrote called ‘PlayMidi’ that will allow you to start multiple MOD files in a playlist.

The Dopus4 configuration has been updated, and it is now possible to run binaries from Dopus4 with a simple double-click.
Even with DualPNG icons, it is possible to manage the Icon Tooltypes with a simple double-click on the .info file. This feature is already included in AROS One v1.2. Another feature implemented is the display of data files (including text files). Now, simply click on them to view them using Multiview.

All updates to the Dopus4 configuration will also be available on AROS One 32Bit (next version 2.9).

Yesterday, theoasisbbs.com published a great review of the new Core and AROS One v1.2 64-bit!

https://theoasisb...t-support/

It is not necessary to modify the Zune configuration of OWB. To resolve the issue, simply delete the ‘OWB.1.prefs’ file located in Prefs/Env-Archive/Zune.

This will cause OWB to use the default setting ‘global.prefs’, where ‘Redraw: without clear’ is set by default.

To make the change immediately, without having to restart Aros, you must also delete the file ‘OWB.1.prefs’ located in RAM:ENV/Zune.

Okay, I'll change the setting to “without clear.” It's strange that the problem occurs only native, while on VM no.
I had noticed this problem, but I thought it was due to my old PC.

I don't think this problem existed with the previous build. I don't remember changing the settings on OWB recently.

@AMIGASYSTEM

Is there any reason why you set “Redraw: with clear” for Windows in the custom preferences for OWB?

It doesn't make much difference on virtual machines, but for some reason it runs very slowly on real hardware, see the video:
https://youtu.be/...

I recommend changing this setting to “Redraw: without clear”, then there is no problem on real hardware.

@retrofaza

In a few hours, the new version of AROS One 1.2 will be available, as well as the update from v1.1 to v1.2 (it wasn't planned, but I decided to distribute it).

I deleted FinalBurnNeo, only the folder icon remains (I forgot to delete it).

@AMIGASYSTEM

Please do not add this alpha version of my FinalBurnNeo port to AROSOne1.2. I want to release it only when it is finished.

The new AROS One 64bit v.1.2 is coming soon. Once testing is complete, it will be available for download.
There are lots of new features concerning the Core, software updates and fixes.

There will be no update for Aros One 1.1, as there is too much data and too many configurations to replace, in addition to the removal of software that is no longer necessary.

Before installing the new AROS One, users will need to back up their personal data and then copy it to the new Aros One.

Strange, it should work on Native. It even works on my laptops/netbook without a floppy drive. Perhaps the floppy drive is disabled or does not exist in your PC's BIOS?

In any case, on AROS One, both 32-bit and 64-bit, in the Dopus4 folder, you will also find a version called ‘Dopus4-No-Floppy’ that works even if there is no floppy drive (modified by me).

Another solution would be to move ‘trackdisk.device’ from the “Devs” folder to the ‘Storage’ folder.

Trying out AROS one 64-bit on my DELL Latitude D520 and seams to work good For Dopus4 to run I had to edit Grub.cfg
Floppy=disabled

Updated the manual (vmware-install-arosone-64bit) on ArosArchive. Due to popular demand, the tutorial is now also available in Spanish and German.

Made some minor changes to improve the understanding of certain passages.

In just a few days, the tutorial has been downloaded by 90 people! I hope it helps spread the use of AROS!

To replace RunInDOSBox, i created a script named ‘DOSBox-Play’ that allows you to choose the path, binary file or bat file MS-DOS and have them run automatically from DOSBox. See a short demonstration video.

This script runs from a appropriate icon and can be run from any location. It also works on AROS One 32Bit and Amiga OS3.

Thanks to Deremon, DOSBox has also been ported to 64-bit!

DOSBox has been successfully tested with the game Prince Of Persia 2, with music and audio working!

To simplify the use of DOSBox and automatically associate executables and bat files with DOSBox, RunInDOSBox would also need to be ported to 64-bit.

Strange, I see that VMware does not seem to recognise the VESA video card. I suppose that it does not support the native VMware video card either.

I also notice that it cannot find the network. AROS One already has the network configured and active, and you can also connect from the ISO.

Regarding the installation error, it is usually caused by either a hard disk with insufficient capacity or a hard disk that has not been initialised (Wipe Disk not performed). If possible, you should try formatting it and see if the formatting is successful.

If necessary, check the VirtualBox ISO or the new GUI for QUemu Kyvos.

https://ko-fi.com...C0C51LTQXL

Exact steps from pdf also same outcome on Ubuntu 24.4

I used the .iso from your website