Quote:

Exactly.

So if everything works, all you have to do is click on the ADF or WB program and it does the rest? I can't remember even the emulation on AOS 4 being that simple :)

AmiBridge is a quite complex beast. It basically does these things:

1. integrate ADF files when they are run for the first time, creating a uarec file for them to feed Janus-UAE. Once assimilated, an ADF file can run straightforward.

2. provide a reliable, pre-configured AROS M68K environment to run Workench applications in coherency mode (68K contents in X86 AROS windows) or in fullescreen.

3. provide the necessary scripting tools to customize the behavior of 68K environment

4. let the user integrate AmigaOS 3.x system files from Amiga Forever or other sources, and automatically reconfigure them to act as much as possible like AROS M68K in point 2 and 3.

I think I misunderstood how Amibridge work. Sorry about that guys :)

Quote:

That's what AmiBridge does for ADF files.

Oh, I did not know that you could do that ln janus-UAE as well. You learn something every day :)

@Yasu:
I perhaps misunderstand you, if so then i'm sorry.

If you take a look at those adf scripts, you will see that each one has an accompanied uae configuration file.

That file is needed because the game you want to start (using the project icon) requires a specific amiga (OCS/ECS/AGA kick such, memory so, etc).

The iconX scripts feeds that uae settings file to janus/uae and 'put' the disk into the emulator and tries to boot from it.

So, in the end the reason for those different configurations is because each and every program/game/etc requires a specific amiga.

There is nothing we can do about that.

Ofcourse, there are several specific amiga-setups that are very common and those uae-settings that match them could be re-used. In that regards it is no different then starting f.e. winUAE or FS-UAE and running your favourite games/program.

Nevertheless, we need some type of detection to know if a program requires f.e. a basic amiga 500 with kickstart 1.2 or an amiga 1200 with memory expansions (just to name a few specific things).

For you and me it might be obvious that Deluxe Galaga AGA is not ment for a basic A500, but how to 'detect' this automatically so that an enduser does not have to worry about that ?

At this moment this is done by providing an uae configuration file that at least 'provide' that information to uae. So in the real scheme of things, there is still 'something' changing the JanusUAE settings for every game (or program if you like).

Ok, I meant that as long as these "scripts" are available, everyone could change them according to need and use them over and over again instead of having to change the settings of UAE every time you change program.

Quote:

Yes that's why i wrote:
Quote:
And doing so for each and every 68k program (and filetype) out there (even if you would make 1 emulation-environment containing all needed programs) takes a while

In practise you would want to approach it in a more generic way, so that not every little quirk concerning a 68k program has to be addresed individually. Again a lot of work.

In order to see what all those hurdles are, just go nuts and try. If you know how to configure UAE properly you can test it yourself. There is no wizardry here, everone should be able to do so. The adf scripts which are distributed by Icaros Desktop are a nice starting-point and you can really go nuts with Icon-X

I see. But wouldn't it be possible to let an icon point to a script that start the emulator and has all the specifics needed for that particilar program?