AMIGASYSTEMDistro MaintainerPosted
3 months agoI created this thread to discuss AROS One 64Bit v11!
I would like to inform you that on AROS 64Bit v11, Dopus4 has numerous problems, making it impossible to use it to its full potential. These are the problems encountered.
- It requires a floppy disk, otherwise it crashes (this problem is also present in the 32-bit version).
Solution:
- On AROS running in VM, this can be solved by enabled the floppy in the VM configuration, or if you are familiar with a hex editor, you can disable tackdisk.device from the binary
- On AROS Hosted Linux, the only way I know is to disable tackdisk.device from the binary with a hex editor
- On a native PC, the floppy problem should not occur even if the PC does not have a floppy drive
In addition to the aforementioned problem, on AROS 64Bit v11 Dopus4 cannot be configured (Guru). Among other things, you cannot use the mouse wheel, and you cannot use the ESC key, otherwise a Guru appears.
Dopus4 on AROS 64Bit v11 needs to be recompiled, perhaps with the latest version available.
AMIGASYSTEM attached the following image:
What exactly do you need for this: "on AROS 64Bit v11 Dopus4 cannot be configured (Guru). ". Can you make a small video showing the issue?
FYI: I started DOpus4 right after compiling it on hosted and it started propertly and didn't require trackdisk.device being present.
This build fixes crash with ESC and mouse wheel.
deadwood attached the following file:
AMIGASYSTEMDistro MaintainerPosted
3 months agoExcellent 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?
I don't have any issue with trackdisk.device with this build. There needs to be something else needed that is triggering this issue.
AMIGASYSTEMDistro MaintainerPosted
3 months agoI 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.
AMIGASYSTEM attached the following image:
AMIGASYSTEMDistro MaintainerPosted
3 months agoOn 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.
AMIGASYSTEM attached the following image:
Can you share the config you are using to make sure we have same environment?
AMIGASYSTEMDistro MaintainerPosted
3 months agoThe 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.
AMIGASYSTEM attached the following file:
AMIGASYSTEMDistro MaintainerPosted
3 months agoThe same Guru also appears with other DOS commands when executed via Dopus4 64bit, for example the Version command.
Please try this dopus.library. It solved problem of "Version" and possibly will solve problem with unpacking.
deadwood attached the following file:
AMIGASYSTEMDistro MaintainerPosted
2 months agoThanks 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.
AMIGASYSTEMDistro MaintainerPosted
2 months agoI 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.
AMIGASYSTEMDistro MaintainerPosted
21 days agoSince 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.
Edited by AMIGASYSTEM on 06-09-2025 12:58,
21 days ago
AMIGASYSTEM attached the following image:
AMIGASYSTEMDistro MaintainerPosted
19 days agoNuova versione di BeeBase 1.2 per AROS One 64Bit v11 e AROS One 32Bit !
AMIGASYSTEM attached the following image: