I have updated my website with the new logo and updated header, and now the 64-bit version is also listed.

https://sites.goo...ew/arosone

The AROS One logo has changed its look, it should now be more attractive, I hope you like it. I have created numerous variations for various purposes that you will find on the various GUIs. The logo is the result of imagination, a reconstruction with pieces recovered from the web and modified to have a personalised look for AROS One. Of course, I am not a graphic designer, everything is done manually, pixel by pixel.

Available on Aros Archive (attaching a link) Tutorial showing how to correctly install AROS One 64Bit on VMware. Naturally, other 64Bit distributions will also need to use the same procedure.

The tutorial includes numerous screenshots showing all the steps !

The tutorial is available in two languages, Italian and English. Although the screenshots are intuitive, if anyone would like to provide a correct translation into their own language, I could update this package. Thank you.

https://archives....-64bit.zip

Nuova versione di BeeBase 1.2 per AROS One 64Bit v11 e AROS One 32Bit !

Since there is no way to enable the bottom bar with folder information (Status Bar), I have created a script that will allow you to enable and disable the Status Bar automatically, see screenshot.
This script will be present on both Aros One 64 and AROS One 32Bit.

I was reading on a forum whether it was possible to mount a physical floppy disk with AROS One. The answer is yes, you can mount a floppy disk using the same procedure used on OS3, i.e. through a MountList (PC0).

This DOSDriver is not active on AROS One. To mount a floppy disk, simply open a Shell and type the command:

Mount PC0:

To view the floppy disk on Workbench, enter the command:

PC0:

To avoid the second command, simply add an icon and enter the following string in Tooltypes:

ACTIVATE=1

If you want automatic mounting, you will need to copy the DosDrivers ‘PC0’ and the icon ‘PC0.info’ to DEVS/DOSDRIVERS or WBStartup.

The same procedure also works with Floppy Images ‘Mounted’ on Virtual Machines such as V;Mware and VirtualBox.

The Grub Menu on AROS One 32/64Bit has been modified, so now you can run Dopus4 from Shell using ‘AROS Early Startup Control’. To get the Shell, just click on ‘Boot With No Startup-Sequence’ and type Dopus4.

Not all tools will work on Dopus4 for obvious reasons (no OS started), but you can perform many operations on files such as editing, renaming, deleting, unzipping, creating archives and much more!

Dopus4 64Bit v11 configuration complete!!!

Dopus4 64Bit v11 now has the same configuration as Dopus4 32Bit. Remember that the 32Bit configuration is not compatible with the 64Bit configuration, so I recreated the configuration for the 64Bit version from scratch!

From the screenshot, you can see the supported file types, except for a few where the data types do not exist on AROS 64Bit v11.

As for archives (all those shown in the screenshot are supported), you can unpack them with ‘Click-M-Click’ (highlight the file, left mouse button and click on the opposite window of Dopus4), or unpack them using the button.
Double-clicking on the archive file will display the contents of the archive.

With Dopus4, you can also create LHA and ZIP archives using the appropriate buttons, see screenshot

Created a small script for ‘Wildmidi’ for converting MIDI files to Wave files on 32 and 64Bit v11.

To convert, simply click on the ‘MidiToWave’ icon. This will open a file request window where you can select the MID or KAR file to convert. The Wave file will be saved in the same folder as ‘MidiToWave’.

If you wish, you can also choose to save it in a specific location, to do this, add the path to the script!

Thanks Deadwood, with this new library, the Guru has disappeared from all the applications that generated it!

It seems as perfect as the 32-bit version. I'm continuing to test it. I've only had one Guru with Multiview, but I need to check if it was just a one-off!

Given the latest improvements and the new conversions produced, I'll soon be doing an update to upgrade AROS One 64-bit.

Please try this dopus.library. It solved problem of "Version" and possibly will solve problem with unpacking.

The same Guru also appears with other DOS commands when executed via Dopus4 64bit, for example the Version command.

The problem persists even if you try to create an archive!

I am attaching my configuration (not yet complete). You can unzip the archives using the button or by Click-M-Click.

Can you share the config you are using to make sure we have same environment?

On the new Dopus4 64bit, a problem has been encountered when unpacking LHA, LZX, etc. archives.

If you try to unpack an archive, a Guru appears, see screenshot. It seems to be a problem with DopusRT.

I don't know, as you can see from the screenshot, with your new version, on VM, if the floppy drive is preset in the VM configuration, there is no problem; Dopus4 works perfectly.

With your new version, if no drive is set on VMware, no Guru appears, but Dopus4 does not open.

If I use Hex Editor to delete trackdisk.device (replacing it with 0) on the binary, everything works normally even without setting a floppy drive.

I don't have any issue with trackdisk.device with this build. There needs to be something else needed that is triggering this issue.

Excellent Deadwood, thank you for correcting Dopus4, now all the problems seem to have been resolved! Only the ‘tackdisk.device’ issue remains.

Now I have to configure everything, the 32-bit version configuration is not compatible, is there a way to convert it to 64-bit?

This build fixes crash with ESC and mouse wheel.

FYI: I started DOpus4 right after compiling it on hosted and it started propertly and didn't require trackdisk.device being present.