Almost there, AROS One 2.7 if there are no unforeseen events will be released in the coming weeks.

In this new version I've set as default a ZUNE/MUI configuration with a "White marble" background that will be visible on all System Applications and most third party applications, 90% of the AROS One software makes use of ZUNE/MUI.

I write ZUNE/MUI because many applications have been ported from the Amiga and therefore always carry the MUI entry in the Menus.

Of course, as mentioned above, the user can replace this Zune configuration by simply clicking on a pre-configured Icon, where he can also choose to set the standard White default of Aros One, a native AROS Grey background, or a slightly striped White background.

For some Applications such as HDToolBox and others that you see in the screenshot the general Zune configuration change will not work because these Applications have a custom ZUNE/MUI configuration, to change this requires a special procedure, explained in the previous post.

From the screenshot you can see the change I made on the InstallAROS GUI and the AROS One Info GUI!

Besides being able to customise every single application, on the next version of AROS One also Wanderer will have its own default themes, I've created 4 "light" themes to make the Application windows more pleasant, to replace them just click on the icon and the script will do the rest, again no system reboot is necessary.

In the screenshot you can see the 4 themes created on Zune that will be used by default by all Applications, except those where the user has already chosen and saved the "custom" theme.

MUI/Zune works like this, if there is a preference the Application will ignore the system setting, furthermore customised Zune configurations for individual Applications can be edited and saved without any problems, while customising and saving Wanderer configurations is more complicated, to do this you first need to delete the configuration file in ENV and in ENVARC.

The creation of Skins for the various System and Third Party Applications continues, of course it is hard work to create the themes for all the Applications installed on AROs One, except those for which a White GUI remains the best choice, see the small GUIs that have only Buttons.

All the skins are based on the new type configurations I created for Zune, for the uninitiated, Zune as well as MUI, have a configuration program that allows you to create a general type configuration for all the Applications that use it, for example if we give a Red background to a window, all the Applications that use that window will see it as Red.

If, on the other hand, we want each application to have its own "unique" preferences, Zune, MUI saves will have to be made from the MUI/Zune settings of the programme; this can also be done for those applications that do not show this item in the preferences, in which case this function is activated by enabling the appropriate Gadget.

I enclose a screenshot that shows some skins that make some GUIs more attractive and modern, and others such as HDToolBox indispensible since a too light or too dark background would not allow a good reading of the texts since in the same GUI the texts are both White and Black.

AROS One by Default will have the usual White GUI, then each user will be able to choose the various configurations from those available for each Application, to do this just click on the Icon of the chosen Configuration and that configuration will be stored as the default setting of the programme.

Replacing Backgrounds and Buttons will not require a reboot, the icon will run a script that will delete the old settings from both ENV and ENVARC.

Thanks to ZUNE for the next version of AROS One I am creating "clothes" for all Applications that allow the change of Skins or Buttons.

Application users for each will be able to choose the background for the GUI or a set of available buttons by clicking on the appropriate Icon.

Advanced users will be able to add their own backgrounds or buttons by editing scripts and paths in the MUI/ZUNE configuration

I enclose a screenshot showing some skins already created for some Audio Players

If there are no Core updates in the short term, the new AROS One 2.7 or the update for those who don't want to install it from scratch will be released for Christmas, the update will be substantial given the many updates including the new OWB 2.0.

For the release of OWB 2.0 in addition to the new buttons created the past few days, I have also created some small backgrounds for the GUI that can be replaced with the usual script executed by Icona, you can see the Skins from the attached screenshot.

Legadon, ALB42 new Application for reading eBooks, for AROS One I created 4 sets of buttons, see scrennshot, the buttons are automatically replaced by clicking on the appropriate Icon as is the case with AmiFox and other customised AROS One Applications.

I created Datatypes Descriptors for the MKV and WEBM video formats and the M4A audio format

It was not so easy as the dentifier was far from the beginning of the file and in many cases changed slightly, in the end I found the solution for everyone.

MKV is Matroska Video, while WEBM is a Google-sponsored project dedicated to creating a free, royalty-free video format.

M4A is nothing more than an MPEG-4 Audio file

Dimenicavo, these file formats, like all others you will see in the video, will be recognised automatically by AROS One even if they do not have an extension, see video.

https://youtu.be/...

Created some new Skins for AmiFish, among them in the next version of AROS One you will find a Pawn Skin based on the AROS One Logo, see screenshot.

AmiFish is a nice Chess game updated to version 2.0, on AROS One there was already version 1.0.

AmiFish uses an external engine "Stockfish" currently maintained by a community of open-source programmers, since 2010 Stockfish has repeatedly occupied the top position in the main chess engine rankings !!!

Finished the AmiBridge function on AROS One x86, it was quite complicated to configure everything, but now it seems to be even more stable, I had to experiment, Janus-UAE is based on E-UAE sources, but for this purpose it turned out to be the best choice, on E-UAE in the GUI there are no Options to Configure AmiBridge.

The tricky thing will probably be for inexperienced users, AmiBridge only works if the Video Resolutions of AROS and OS3 are identical, which means that you have to install OS3 systems in RTG, which will be tricky for those who don't know how to fiddle with the Picasso 96 preference programme.

As for OS 1.3 and 2.1, since they cannot install Picasso96 they can be run in PAL mode on an AROS One window.

I attach a new video see running OS 3.0, 3.1, 3.2 and 3.9 with Amibridge and OS 1.3 and 2.1 in Window mode

https://www.youtu...e=youtu.be

Did some tests to integrate OS 3.9 and OS 3.2 as well!

Everything works fine, but if a Guru happens, Janus-UAE will always go to Guru, whenever you start an Amibridge configuration.

This is solved if you start the executable "JanusUAE" without any configuration. Once this is done, all Amibridge scripts will work fine again.

Unfortunately JanusUAE like E-UAE (with the new Core goes in Guru) are outdated and very far from WinUAE, after a while running 68k applications hangs, it is solved by exiting the emulation, see attached video.

Nornmal Emulations (no Amibridge) are much more stable

https://youtu.be/...

Nice!

Very nice work! I look forward to trying out the Hostbridge on AROS One.

Having some spare time, I studied and put into practice the Amibridge procedure shown HERE, which would then be the one used by IcarOS.

This is a not so simple procedure to do, Amibridge from IcarOS allows you to run OS3 software using AROS 68k or via AmigaForever.

My Idea instead is to create an Amibridge with all Standard Amiga OS's like OS 3.1, OS 3.9 and OS3.2
On AROS One there will only be the settings and the 68k files accompanying Janus-UAE, users will only have to copy the OS and KickStart into the appropriate folders.

To do this I am using JanusUAE as stated in the attached guide, but it should also work with E-UAE if it includes the "Coherency" " Wanderer Integration" functions.

At the moment I have experimented with OS3.1 and OS3.2 RTG and it worked perfectly, the RTG system is essential otherwise Amibridge will not work, the system must be light otherwise emulation would be slow, JanusUAE and E-UAE do not have the many functions and power of WinUAE which exploits the host hardware.

For OS 1.3, OS 2.1 systems, due to lack of RTG there will eventually be normal windowed emulations without integration on Wanderer.

As peromitted here is the video that shows how WHDLoad games will start on AROS One!

Of course on AROS One there will be no KickStart or Games, that's what the user will have to do:


Before running, the games carefully read "All" the specific Readme also found in each folder, all this to

facilitate step-by-step installations.


For WHDLoad games the first time you start with TinyLauncher you have to create the Games Menu,
Read the attached TinyLauncher Readme and follow the on-screen instructions.


First you need to copy KickStart 1.3 and KickStart 3.1 to the path and name below:

SYS:Extras/Amiga-Games/DH0/Devs/Kickstarts/

KickStart must be renamed Kick34005.A500 and Kick40068.A1200 respectively.


ADF games must be copied to the Games-ADF folder
WHDLoad games must be copied to the Games-WHD folder instead.

If desired, subfolders can be created for each individual game.

No operating system is required, of course you can also load
ADF, and WHDLoad to start Workbench 1.3 and Workbench 3.1.


This is the video showing the ease of execution in the AROS environment running JanusUAE, which in turn runs what I set up in the script!

https://youtu.be/...

Found the solution also to start WHDLoad Games from icon on Wanderer, I'll follow with an exhaustive video
The tool in question is "TinyLauncher" for OS3, perfect for the purpose, it doesn't need Libraries and System Files, it allows from the GUI to create menus for Games, Demos and Music, and you start it by simply clicking an icon from the Wanderer, pretty much the same way as ADF as shown above in the video.

For TinyLauncher I got in touch with its Developer Michael GIBS to be allowed to install it on AROS One, after a few hours I got the answer via email where he gladly allowed me to use it, he also told me that he is of a certain age and Amiga enthusiast since ever, in the past I tested another good software of his "Amiga Boot Selector".

Today I tried my hand at creating some Scripts to make it easier for all those users who are not Amiga Emulation experts.

Basically I've created some simple scripts in AmigaOS so that an Emulator would be started, with a typical configuration so that the user only has to add the Floppy (ADF).

The scripts should work on any "Amigosa" Platform of course depending on the platform you will choose the emulator that works best.

The scripts as well as starting the emulation will also load a config file which is universal, practically it should be compatible with all Emulators, the scripts created are 2 one for AGA games and the other for OCS/ECS games.

The two configs in addition to the settings for the two ChipSets also include a ROM and Floppy path, in the same path there is also the Emulator, all to keep all the data in one path.

I created a small video showing when mentioned, the system used in the video test is my AROS One, the emulator chosen was JanusUAE (more advanced and better working), also tested E-UAE and P-UAE, but they didn't satisfy me as much as JanusUAE.

The script once started will show the kick-start screen, the user will only have to run the emulator icon or use the function keys CTR-Alt+i and add the floppy, the emulator will do the rest, when the game will ask for more floppies you will have to redo the operation add floppy.

Video Tutorial: Emulator UAE Script
https://youtu.be/...

Created new Pointers for AROS One, the Pointers have as "Busy" the same arrow with a small circle that will indicate when the Pointer is Busy, these Pointers will be in addition to those created by me previously.

Since with CAB Archives it seems that it is not possible to unpack them from Wanderer, but only from Dos, I found a way to do it through a simple Icon from Wanderer using the magic WBXCLI command created by the good "magorium"

I would like to point out that there are 2 types of CAB Archives (there is also a third one which is not used much), not to be confused, one is the "cabinet" used by Microsoft, the other by "InstallShield cabinet", usually the files are named "_sys.cab", "data1.hdr", "data1.cab", "data2.cab".

Wander thanks to two of my descriptors will recognise both CAB formats and associate the correct tool to unpack them.

I remind you that Microsoft CABs can be unpacked with the "Cabextract" command while "InstallShield" CABs can be unpacked with the "Unshield" command

To unpack both CABs, simply double-click on the icon and the data will automatically be unpacked in RAM in a folder called "Unpacked".

The "Unpacked" folder does not have a physical Icon will be visible if "Show all files" is set, on AROS One this setting on the RAM Icon is set by default.

I enclose Video Tutorial showing how to unpack the two versions of CAB from Wanderer and Dops4 (Microsoft CAB only)

https://youtu.be/...

A few hours ago another video on AROS One 2.6 was posted, a user tested it in VM and was happy with it without encountering any problems, a nice video (168 views in 5 hours)

https://youtu.be/...

About ten days ago the Youtube Channel of InstallOS published a video on how to install AROS One, too bad it showed the old version of AROS One 2.5.

The Video is of Good workmanship, it lasted minimum the time to install AROS One, I liked a lot the commentary of course positive, the only thing that you can notice is that the author is not a connoisseur of Amiga/AROS you can notice it when he tries to use some Application.


I enclose a link to the Video Tutorial on how to install AROS One, but be careful in the tutorial he skipped the "Wipe Disk", fundamental when using Hardisik or other peripherals previously used for Windows, MAC or Linux installations.

Basically the "Wipe Disk" wipes any bootloader and writes the native Amiga RDB, in his case it was not necessary because he used a Virtual HardFile on VM, for the rest all the procedure is correct, here is the link of the video:

https://youtu.be/...