[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [MiNT] patch:MiNT:KM_FREE



On Tue, Dec 15, 2009 at 7:09 AM, Peter Slegg <p.slegg@scubadivers.co.uk> wrote:
> On Mon, 14 Dec 2009 20:28:45 , "Helmut Karlowski" <helmut.karlowski@ish.de> wrote:
>> Am 14.12.2009, 08:00 Uhr, schrieb Paul Wratt <paul.wratt@gmail.com>:
>>
>> > Is it possible to allow for both KM reload, and specifically with
>> > reference to XaAES, to unload current KM, then load a new KM (with a
>> > different filename). Or is there some reason why this should be
>> > restricted to implementation in xa_loader.prg only.
>>
>> There is no restriction. It should be possible to load any km with
>> xaloader. Just use another argument on the commandline.
>> It should be possible to have more kms loaded at the same time, but only
>> one XaAES :)
>>
>
> One XaAES or one AES ?
>
> Peter
>
He means loading only 1 XaAES KM at a time.

I am interested in testing 2 AES at the same time, and later, the
possibility of a AES extension as a KM (for XaAES at least). I do not
think we will see MyAES as a KM, at least not until fVDI has better
coverage, and is also a KM. But it is the only (cool) AES to work on
standard TOS, and I dont see that support changing..

With AES binding programs as child processes, it may in fact be
possible to run two odf them, It will be interesting to see how
AVSERVER reacts to this, or can be accomodated. I have a raw AVSERVER
somewhere, of one of the uptodate ftps, it will probably work well in
this situation if loaded before and AES, as it does not have any
graphics stuff (desktop etc)..

Paul