Yesterday through the [url=https://github.com/pbatard/rufus/issues/2468][b]Issue tracker [/b][/url] I reported to Rufus developer "Pete Batard" the incompatibility between Rufus 3.x and Rufus 4.x. Basically the USB images created by Rufus 3.x are incompatible with the new 4.x versions (they generate error at the end of writing), now I don't know if it is a Bug or an evolution of the program. As I had mentioned the new AROS One USB Images will be produced with the new 4.x version of Rufus, this is because Windows users with Win10 and Win11 are all using the newer 4.x version. The 3.x versions were the last to work on WinXP and Win7, but they work perfectly on Win10 as well. Today discussing with Pete Batard developer of Rufus on issue tracker to try to understand the icompatibility between Rufus v3.x and Rufus v4.x, which according to him should not be there, however he is analyzing the various logs to try to understand why Rufus v4.x does not write images created by Rufus 3.x correctly The discussion was interesting, Pete advised me not to create the USB Images in the VHD format and especially not to compress them to ZIP, where corruptions could occur on the Image, although no error will be shown during writing. Pete instead strongly advised me to use the VHDX format, although then once tested it gave me error in writing, this error however is a Bug that Pete knows and is fixing, it will probably be fixed for the next 4.5 version Some info on the VHDX Image format: One of the biggest advantages of VHDX over the old VHD format is the storage capacity of the virtual disk. Prior to Windows Server 2012, the limit for Hyper-V virtual hard drives was 2 TB. VHDX files have a capacity of 64 TB. VHDX are designed to work with today's modern hardware and have logical sector sizes of 4 KB, which improves performance over VHD files. VHDX also provides protection against file corruption related to power supply failures by continuously keeping track of metadata updates, a feature not available with the VHD format. Larger block sizes for dynamic disks that differ, as well as the ability to store custom metadata, also provide the new format with superiority in the comparison between VHD and VHDX

deadwood to me HippoPlayer works fine on both your latest Build and Build aros.org. Consider that Olaf uses Dopus Magellan as the Workbench ! HippoPlayer it also works well on my old AROS One 68k

Are you using ROMs from www.aros.org or my test builds? If you want to check some older builds, they are here: https://build.axrt.org/download/builds/AROS-M68K/

Olaf I didn't quite understand the problem, if you are referring to the Play, Stop etc buttons not being visible, I on Wanderer don't have that problem. If you are referring to the request then you are using an incompatible version of "HippoPlayer.group". If you have updated HippoPlayer, you need to update HippoPlayer.group as well, veify you don't have 2 HippoPlayer.group files, one in the HippoPlayer folder and one in the SYS:S cate

Hello, I can remember that this was solved and now it is here again and I do not know how to fix it. Buttons in this kind of dialogs are not shown but you can press on them and then they are painted. Perhaps someone knows what library is causing it and how I can fix it

I modified an entry of Dopus5 it is located in "system:dopus5/filetypes" I attach it to the post replace it and to create even tar files on the fly remove zunearc from the software without problems it will no longer be needed, the development tools must be installed!

Keeping your system up to date is as simple as having an extra partition for your files, games, documents etc.., every time a new release of Tiny Aros comes out just delete the root partition:)

the new version of Tiny Aros is available some software has been removed in the "extras/home/doc" section there are some issues of total amiga to consult, added all the demos in the archives and also some games in a few days I will publish a new site the distribution can be downloaded from the following link it is a file to be written with rufus on windows 10/11 https://www.adrive.com/public/5CBXSp/TnyAros_copy.vhd All the best, enjoy!

My athlonXP and celeron are 32-bit only CPU so no 64-bit on that :)

On 64-bit AROS you will not get accelerated 3D on nVidia cards for now, so currently the only accelerated 3D is on hostgl unfortunatelly.

@ Deadwood @ Olaf @ AMIGASYSTEM thanks for the help 😊

I cannot test Adoom3 on athlonXP (crash) I think CPU is missing some fundamental instruction, I have another motherboard with a celeron I'll try there to test it on my Geforce 6600GT AGP

FYI, the fix for SDL has been made, but it was a more general fix to how includes are generated. In order to apply it, please update AROS sources and rebuild AROS and contrib. There is no need to rebuild toolchain.

mattson62, AROS Vision does not use Wanderer but Dopus5 Magellan, so most of the "Workbench" configurations are handled by Magellan ! As on AMiGA Dopus5 Magellan as Scalos were substitutes for the Workbench

Hello Matts, you find that in Settings->Environment->Backgrounds in the context menu

Edit: neverming, wront information

I just installed Aros Vision on winuae and this is embrassing but i have tried to change the backdrop and can't find the settings.,I'm used to right clicking on a picture and select "save as background''LOL i know i overlooked it somewhere :) thanks

I have to make a new website currently there are no new build releases from deadwood

I had to do a long hospital stay but I decided to treat myself at home I am quite well I have to take a lot of medicine but I am used to it, many thanks

Salvo, Thank you for what you do for AROS. Take care of your health. It's important.