well, the second step of the emulation is replace the kernel and the os using aros replacement. at least afaik.

but it seems that this post is about integration. just to make it transparent, without the kernel/os issue atm.

kind regards,

I dont see why the rom dependency have to be removed at this point. At least the original rom files could be used in the initial face to get things working fast. Most Aros users probably already have these rom files anyway. I think this bounty is very important. It would bring thousands of games and applications (perhaps old but still very useful) running directly under Aros.

Is'nt it a good idea to integrate some compatibility settings in the icon files? So you can change the UAE settings for each application just by right clicking the icon. That would make it possible to run games like Moonstone on an A500 config and FinalWriter97 with a A4000+ RTG config integrated with the desktop? It is a much better solution than the one used in MorphOS which only gives limited backwards compatibility with applications written in a very system friendly way...

Quote:
item 3 is available for winuae...

Bounty #1:

1. Double click on 68k icon to run application with UAE - emulation running in one window and one UAE task

2. seemless integration by integration of UAE sources in Aros main tree to allow further expansion

3. Shared clipboard.

4. Global Prefs program; default prefs shall be adequate for most applications

5. easy setup for needed amiga system files (how far can AfA replace original files?)

6. Able to kill emulation.


Bounty #2:

1. Applications must be able to open their windows on the Wanderer

2. possibility to set special prefs for each app

3. replacement of ROM by wrapping to the Aros native versions; used by default; possibility to set original ROM files for each app in special prefs as compatibility mode

4. TCP/IP wrapper (emulated bsdsocket.library)



Part #3 would be Bounty #23 "Kickstart ROM Replacement (Phase I)" then: replacing Amiga system files with Aros 68k ones. Maybe the current UAE bounty money could be split up..

Quote:

Just made some some suggestions as I would like to see it, with steps 6 and 7 as some kind bounty #2.
The bounty gouls should be defined better, I agree.

What about..


Bounty #1:

1. Double click on 68k icon to run application with UAE - emulation running in one window/one UAE task

2. easy setup for needed amiga system files (how far can AfA replace original files?)

3. Shared clipboard.

5. Global Prefs program

6. Able to kill emulation.

7. TCP/IP Wrapper (emulated bsdsocket.library on UAE side)


Bounty #2:

1. Applications must be able to open their windows on the Wanderer

2. possibility to set special prefs for each app

7. replacement of ROM/System files (or wrapping to the Aros native Versions as possible so far)




Just collecting some ideas..

Quote:

AFAIK GLUAE only covers item 1.

Quote:
Agreed.

But perhaps the bounty description should be more explicit about what _is_ required. In particular, "a seamless integration of UAE and AROS" should be defined more rigorously.

Your list of requirements above differ from what is stated in bounty #7. In particular, items 2, 6 and 7 from above are not included in the bounty #7 requirements as currently listed at http://thenostromo.com/teamaros2/?number=7.

It would be possible to interpret "seamless integration" as not requiring your items 2 and 7 above. For example, the emulation could operate in its own window and make use of an AmigaOS 3.1 ROM image and AmigaOS 3.1 disk-based libraries/commands and could still reasonably be regarded as "seamless".

Cheers,
Rich

If it providesthe funcionality I don't see how not... but it seems it doesn't

Quote:

Indeed, it?s not really a seemless integration within the os which would allow easy expansion, connection to native environment.


1. Double click on 68k icon to run application with UAE

2. Applications must be able to open their windows on the Wanderer

3. Shared clipboard.

4. Global Prefs program, easy handling; possibility to set special prefs for each app

5. Able to kill emulation.

-----

6. TCP/IP Wrapper (connection to bsdsocket.library)

7. raplacement of ROM/System files (or wrapping to the Aros native Versions as possible so far)



..long way to go, but making some scripts isnt worth 572$.

Quote:


Yeah, I thought this was a good Idea too. The author had quite a good chat with some of the devs on the mailing list about whether it actually suits the current UAE bounty. After a bit of discussion, it was deemed not to cover the bounty - something to do with the fact that it was script based (as in cli scripts ?).

Anyhow, I got the feeling that its even money on whether he will do it for AROS.