This is one of the few areas where AROS and OS4.1 make us look bad.
But then, I don't use UAE a great deal anyway.

Quote:

Eagleplayer is open source, instead of making it work as a hack it should be fixed to work on later OS's. Running common tasks such as a music replayer on UAE is just waste of precious CPU cycles IMO.

hooligan,
Quote:

And that kind of UAE hacking would need some serious hacking to provide all program functions public. I don't know how it's done in AROS, but I would at least want program's AREXX ports available for main system for example, and running program in UAE sandbox wouldn't provide those kinds of functions to main system by default I think. Music player, as well as many other programs, without AREXX would be useless for me.

@jim
Quote:

I wrote such a script about 6 years ago and included it in UAE bonus/ directory in my release archive... It allows to run 68k apps directly from ambient contextmenu, launching them in UAE (either by starting a new UAE instance, or using the already existing one).

As for ADFs, you just have to doubleclick them if you installed the right Ambient filetype (i also included an example for that in UAE).

Fab,
Quote:

Fabulous.
Sometimes you scare me.
BTW - Did I ever thank you for helping me get access to ISP email site?


[ Edited by Jim 27.02.2013 - 01:55 ]

Thanks! I have read that on a french MorphOs site. I always had the idea, that this would launch a window where I would find a WB something and the application that I started.

With Aros, you run a program and after that, Wanderer (ambient eqv) recognizes the 680x0 code and starts the UAE code in the background. In Aros it then takes centuries to start, but it works. Why not have ambient do such a thing natively. Sure, you will need to recognize 680x0 native code, but if by policy, all 680x0 code is fed to a uae proces, that would work, I suppose.

> Why not have ambient do such a thing natively.

Most programs that really benefit from Janus-UAE's coherence mode on AROS usually can be run in MorphOS' transparent m68k emulation. There are exceptions though, like Eagleplayer which you would like to run. I'm sure that Janus-UAE's coherence mode could be adapted for MorphOS' E-UAE as well but I'm not sure the benefit would be worth the effort.

> you will need to recognize 680x0 native code

That's done anyway in order to trigger the transparent m68k emulation that's built into MorphOS.

> if by policy, all 680x0 code is fed to a uae proces, that would work, I suppose.

That's a very bad idea in my opinion. I want my OS-friendly m68k programs run as if they were MorphOS-native like they do now, not inside UAE (hidden or not).

Oh yes, That is dead right.
We don't want to have to use UAE.
That defeats the purpose of much of MorphOS' design.
And it is less efficient.

I rarely use UAE.
While an X86 PC is powerful enough to brute force things into working well, our PPC processor are quite a bit less powerful.

Yet, when running OS friendly app, the fly under MorphOS.
And its less resource intense then UAE.

I get a big kick out of running native apps like OWB alongside OS friendly Amiga apps.
Its the kind of thing you can do with a modern PC that you can't do with a legacy Amiga.

> While an X86 PC is powerful enough to brute force things into working well,
> our PPC processor are quite a bit less powerful. Yet, when running OS friendly
> app, the fly under MorphOS. And its less resource intense then UAE.

For me it's more about the integrated look and feel (ARexx, MUI config etc.) than the speed alone.