Amiwell79Distro Maintainer Posted
5 months agook deadwood try it for testing
AMIGASYSTEMDistro Maintainer Posted
5 months agoThanks deadwood, I'll get to work!
If I understand correctly, regarding your post "please delete", if you edit the post you should be able to delete the post, the "delete this post" appears
AMIGASYSTEMDistro Maintainer Posted
5 months agodeadwood in the software included in Extras has something changed? does everything have to be overwritten?
Edited by AMIGASYSTEM on 21-12-2023 12:12,
5 months agoThere were no functional changes in contrib, but all the software has been recompiled to use new C library. If you don't update the software, you will start getting errors about missing stdc.library etc.
AMIGASYSTEMDistro Maintainer Posted
5 months agodeadwood I have integrated 20211214-D01 on the new AROS One 2.4, at the moment everything is fine, I had to delete some Zune Libraries (.mcc/.mui) not included in your Build.
Noticed a problem on OWB (even with the default config), basically every time I start OWB in the folder where the Binary resides "empty" folders with strange names are created, see screenshot ! if I delete them on the next start a new folder is created, if I restart again a second strange folder is created !
EDIT
Question: Inside the Extras folder there is a folder called 'GNU', should this folder remain in Extras, or can I integrate everything in Development?รน
EDIT
There are duplicate catalogues 'catalonian' and 'catalan' (Spanish autonomous community)
EDIT
I noticed that there are Scalos configurations in the ISO, has it been updated?
You do not have access to view attachments
Amiwell79Distro Maintainer Posted
5 months agoon the reference iso I tried the software in my distribution and it works I have not tried odyssey yet, I get output from applications written in freepascal amitube when I close it it gives me error dopus5 works
Amiwell79Distro Maintainer Posted
5 months agoOK I'll try d01 I didn't understand
AMIGASYSTEMDistro Maintainer Posted
5 months agoI also have the same problem as you.
If you search for the video from Google and click on the image, the video gui opens and after a while you get the error you see in the screenshot, if you then go to the address bar and hit enter again, if it doesn't work you repeat it, this time the error doesn't appear. The video cannot be seen, but if you go with the cursor to the end of the video you will see the preview of the video image.
AmiTube is happy to download videos from YouTube!
You do not have access to view attachments
Amiwell79Distro Maintainer Posted
5 months agodeadwood i have tried and successfully installed the build in my acer aspire a110 native mode does not work vesa yes
Amiwell79Distro Maintainer Posted
5 months agoI encountered an error with owb during a third or fourth boot I don't remember now
You do not have access to view attachments
Amiwell79Distro Maintainer Posted
5 months agothe applications work however yes odyssey no longer plays videos and displays pages differently from the version running on the reference build
Amiwell79Distro Maintainer Posted
5 months agoafter an installation on my netbook I wanted to create a usb key installation was not possible with the reference iso is possible
I don't know if installation to USB should be possible from anything else than Live-CD.
What goes wrong in your case?
Hmm, seems my post disappeared. To recap:
For descriptors in DiskImage you can't use previous descriptors as they often rely on stdc.library. If you use them with new build then most likely there will be a silent fail which will lead to guru.
AMIGASYSTEMDistro Maintainer Posted
5 months agoI did numerous tests with all the old Descriptors and never had any GURU.
As said in the new Descriptors the important "CUE" is missing otherwise it is not possible to check in the ISO if there are Audio tracks !
With the Old Descriptors the "CUE" images are loaded correctly without any Guru.
On AROS One I am using "DiskImageGUI" from the new Build D01, I just replaced 'Diskimage.device'. which generated the GURU !
In practice, in order for 'DiskImageGUI' to work properly, the Descriptors must be in Devs/DOSDriver, so that all mounted devices appear in the GUI of 'DiskImageGUI'. With the old 'Diskimage.device' in system startup I never encountered Guru !