Re: [MiNT] XaAES:Singletask-mode

[Peter Slegg <p.slegg@scubadivers.co.uk>]

On Wed, 28 Apr 2010 09:12:48 , "Helmut Karlowski" <helmut.karlowski@ish.de> wrote:
> > This is the bootlog for that version:
> >
> > ~~~~~~~~~~~~ XaAES start up!! ~~~~~~~~~~~~~~~~
> > stack is long-aligned:7C405BC
> > loader:pgrp=3D91, pid=3D91
> > sysfile_exits: 'u:/c/mint/1-17-cur/moose.xdd'
> > sysfile_exits: 'u:/c/mint/1-17-cur/moose_w.adi'
> > sysfile_exits: 'u:/c/mint/1-17-cur/moose.adi'
> > home_path: '\c\MINT\1-17-CUR\XAAES\'
> > sysfile_exits: 'u:\c\MINT\1-17-CUR\XAAES\moose_w.adi'
> >   XaAES v0.999 Alpha
> > MultiTasking AES for MiNT
> > Part of freemint (http://sparemint.org).
> > Supports mouse wheels
> > Compile time switches enabled:
> >  - CTRL+ALT key-combo's
> >  - Client vector validation
> >  - Realtime (live) window scrolling, moving and sizing
> >
> > nkc_init ok!
> > Loading config \c\MINT\1-17-CUR\XAAES\xaaes.cnf
> > load adi modules
> > Loading AES Device Drivers:
> > load_adi: enter (0x7C29344, 0x7C29244, moose_w.adi)
> > load_adi: return 0
> > load_adi: enter (0x7C28494, 0x7C28394, moose.adi)
> > load_adi: return 0
>
> Mikro may be right: remove moose.adi. It seems it uses the last loaded
> one. They are loaded the other way round in my aranym.
>


I was wondering about this. Is it loading them in alphabetical
order or is it behaving like the AUTO folder and reading them
in "unsorted" order based on the last one written to the folder ?

I think the behaviour may have changed between 1.16 and 1.17
but as long as it is clear that only one is needed then everything
will be ok.

Peter