That's fantastic news! Thank you for your excellent work. Just a question, does this driver work on AROS 64bit or is it just for 32bit version?

Today I discovered how to correctly load WHDLoad files directly from the script without using the Amiberry GUI. It was a chance discovery, something really strange that only happens with LHA archives of WHDload games. Among other things, as you may have noticed, in the method used in the video, WHLoad games were run from AROS 68k ROMs. This is because no configuration could be used by the script for WHDLoad games. Now, however, WHDLoad games use Kickstart 3.1, which is an important difference. Kickstart 3.1 seems to speed up game loading considerably. A new video will follow.

The atheros5000.device wireless network driver has been updated to support some additional Atheros chipsets. It now supports 802.11n-capable devices based on the following chips (but only at 802.11g speeds): AR5416, AR5418, AR9160, AR9280, AR9281 and AR9285. It also now supports additional radio chips that may be used in some non-802.11n-capable devices: AR2316 and AR2317. This may allow additional AR5212-based devices to work. A 32-bit beta of the new version is attached below. A bugfixed version of WirelessManager is also included. Feedback is very welcome as I have only been able to test AR9285 support so far.

I spent a few days developing a script (a small GUI to be launched from an icon) that, through a set of commands, can select (multiple choice) and execute ADF, DMS, OCS/ECS and AGA files, as well as WHDLoad and CD/ISO files for CD32 emulation. Particular work has been done for WHD (WHDLoad) and CD32, where it is currently not possible to launch a WHDLoad game or an ISO file by name. The script I created now allows you to launch ADF and DMS OCS floppy images, whether they are ECS or AGA, from the same script, while for WHDLoad and CD32, the files must be imported later from the Amiberry GUI. The script also does a specific job. For example, if we first launch an OCS/ECS ADF, the script will first copy an Amiga 500 setting as the default setting. If we then decide to launch an AGA ADF, the script will replace the default A500 setting with the A1200 setting. For WHD and CD32, the procedure is different. WHDLoad does not need a config, so the script will delete the default setting, while for CD32, the script will copy a basic CD32 config. With this procedure, launching OS3 programmes and games on AROS will be easier than ever, and above all, you will always remain in the AMiGA/AROS environment. https://youtu.be/YwOLxeiD53s

Created on AROS One 64Bit, the ADF and DMS descriptors and related Def_ADF.info and Def_DMS.info icons. Now all ADF and DMS image files will be recognised by Wanderer and automatically executed by Amiberry integrated on AROS One. https://youtu.be/Nq1YQX5s8jU

[quote name=retrofaza post=10484]@retrofaza However, my tests so far show that booting via whdboot is not yet stable. Sometimes I get crashes.[/quote] That's what I was trying to do. I have no problem starting a single LHA, but thank you anyway.

Okay, I see what the problem is. Make a small modification to the script, first go to the directory, then call amiberry: [code] .K file/F cd sys:extras/emu/amiberry amiberry "<file>" [/code] However, my tests so far show that booting via whdboot is not yet stable. Sometimes I get crashes.

I have no problems running individual WHDLoad games. I would like to launch them from def icons using the method you showed in the video. If it works for you, please send me your script so I can compare it. Thank you.

What error are you getting? You don't need to specify any configuration for whdboot, the idea is that whdboot automatically uses the appropriate configuration for the game (but you can override it for each game separately if you want). Run “amiberry path/to/file.lha” without specifying the .uae file.

[quote name=retrofaza post=10454]@retrofaza - You can make the same script as for adf. I just don't know how to distinguish between lha for zunearc and lha for amiberry. Have you figured out how to do it with descriptors?[/quote] One solution would be to rename the archives from .lha to .whd, thus creating the def_WHD.info descriptor, and that's it. The only problem is that I tried to run the LHA archives using your method, but I get an error. If it works for you, could you attach the script and configuration you used for WHDLoad? Thank you. If I want, I can also create the descriptor for the Slave files, but I don't know if Amiberri will s

Okay, sorted. I recreated the configuration and now the WDLoad games are working. Thank you.

I had already renamed KickStarts to Roms, I'm probably doing something wrong in the Amiberry configuration, I get a message saying that the file ‘boot-data.zip’ is read-only! Can you attach the .uae config you use for WHDload and the Amiberry.conf file, please?

No, you don't need to extract the boot-data.zip file. In the amiberry directory, you have a directory called “kickstarts” (where all your kickstarts are located). Rename it to “roms” and whdboot will work. You don't need to do anything in the “whdboot” directory.

Are you referring to the Kickstart directory included in the boot-data.zip archive? I can find the kickstarts even without renaming them. Does boot-data.zip need to be unzipped? The ZIP archives are identical, they have the same internal PK acronym. We need to understand whether it is a format created with a compressor other than ZIP, or whether it is a corrupted compression. We should try other Zip archives used by Amiberry.

WHDBoot works. You just need to rename the “kickstarts” directory to “roms”. Then run: amiberry pathto/gamename.lha You can make the same script as for adf. I just don't know how to distinguish between lha for zunearc and lha for amiberry. Have you figured out how to do it with descriptors?

OK, retrofaza, that works, even though Toltypes would be the best solution (see flag problem). The ADF file has the ‘S’ flag, which makes it executable. This flag will be removed from the ISO/DVD file system, and as a result, ADF files cannot be executed from the ISO or DVD. Regarding installation on the hard drive, the ‘S’ flag can be restored using a command in User-startup. Have you tried with LHA files (WHDload)? The boot-data.zip file on AROS is not unpacked correctly (missing files), whereas on Windows it unpacks correctly with no missing files.

But this method launches every adf file. You don't need to create a separate iconx for each file. There is only one iconx script (you can create it in the amiberry directory). Then, clicking on any adf file will launch amiberry with that file. I recorded a second video, see how it works. https://www.youtube.com/watch?v=3b81zOm_yQM Of course, if there was support in tooltype, it would be even more elegant, but for now, amiberry doesn't have it.

retrofaza, I have already used a script like the one you described, see my previous videos. What I want to do is run ‘any’ ADF, DMS, LHA (WHDLoad) simply by clicking on its ‘Project’ icon (not IconX). Basically no script, just parameters set by the Icon Tooltypes. I am attaching a video showing what I would like to do. By clicking on the icon, the configuration is detected by default, while the ADF, DMS, etc. file could probably be resolved with WBXCLI, which does not exist on AROS 64Bit v11. I am also experimenting with a small GUI/request that allows you to launch any ADF or DMS. You can see it in the attached video! https://youtu.be/hVR_LFwNzVM

@AMIGASYSTEM Something like this? [url]https://www.youtube.com/watch?v=wVLjsjTHvmk[/url] Directs def_icon to the iconx file: .K file/F SYS:Extras/Emu/Amiberry/amiberry -f SYS:Extras/Emu/Amiberry/conf/A500.uae -0 "<file>"

@Deremon I created the Datatypes Descriptors for ADF, DMS and Slave, with the respective def_Icons where I associated Amiberry. Everything works, but the ADF, DMS, etc. files are not launched by Amiberry. Is there a way via Tootypes that allows Amiberry to launch these files?