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/...

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.youtu...b81zOm_yQM

Of course, if there was support in tooltype, it would be even more elegant, but for now, amiberry doesn't have it.

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.

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?

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.

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.

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?

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

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

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.

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.

Okay, I see what the problem is. Make a small modification to the script, first go to the directory, then call amiberry:



However, my tests so far show that booting via whdboot is not yet stable. Sometimes I get crashes.

That's what I was trying to do. I have no problem starting a single LHA, but thank you anyway.

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/...

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/...

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.

As mentioned previously, here is the new video showing how WHDLoad games can be run directly from the GUI script I created without using the Amiberry GUI.

WHDLoad games, which are generally compressed in LHA format, are run by Amiberry using a special procedure that creates and launches a mini-system in a temporary folder unique to each game.

The presence of corrupted temporary files remaining in the mini-system will prevent WHDLoad games from starting, and even the presence of default configurations in the Amiberry folder will prevent WHDLoad games from working.

The GUI script I created before launching the WHDLoad game will automatically delete the temp folder and the default configuration file, if present.

Regarding WHDLoad games, I also discovered that they will not work from a Shell or from my script if the games are located in the Amiberry folder.

https://youtu.be/...

wow great job!

After a busy Christmas I've only just now had some time to play with this. Bit of a problem straight off; I've installed my 68k system to a different pratition to the Amiberry program but found in the paths panel I can't set the patition name as the string gadget doesn't recognise the shift key so I can't type ':'. I'll try copying Amiberry to the other partition and try again.

Cheers,
Nigel.

OK, up an running now. Booted into workbench with no errors and was able to start Pagerstream4; this is as far as the tests go so far but initial observations are:

• With JIT turned on it's fast
• RTG emulation works and I was able to run on a custom screen.
• Looks to be working fine with Amiga Forever roms and rom key.
• I was not able to use shift key again in hard-drive/drawer requester so again I was unable to set drawers in other particitons. Also I found that once an emulated partition was set you can't edit it; if you want to make any changes you have to delete the entry and cerate again from scratch.

Some questions:

• Will resolutions greater than 800 x 600 will be avaialble at some point?
• Is it possible to have more that 64MB of Z3 ram? In Janus I normally run with 512MB ram.
• Is it possible to bring up the Amiberry GUI from Exchanged rather than just remove the program.

Anyway, I'll test furter but looks like an incredibly strong relese for an alpha - really brilliant

Cheers,
Nigel.

P.S. tests ae on native 64 bit aros running an Intel i5 processor.