From mint-bounce@lists.fishpool.fi  Wed Apr 28 05:14:17 2010
Message-ID: <964437.262245582-sendEmail@descaro>
From: "Helmut Karlowski" <helmut.karlowski@ish.de>
To: "Peter Slegg" <mint@lists.fishpool.fi>
Cc: "helmut.karlowski@ish.de" <helmut.karlowski@ish.de>
Subject: Re: [MiNT] XaAES:Singletask-mode
Date: Wed, 28 Apr 2010 09:12:48 +0000
X-Mailer: sendEmail-1.55
MIME-Version: 1.0
Content-Type: multipart/related; boundary="----MIME delimiter for sendEmail-852677.392614172"
X-Antivirus: avast! (VPS 100427-1, 27.04.2010), Outbound message
X-Antivirus-Status: Clean
X-ecartis-version: Ecartis v1.0.0
Sender: mint-bounce@lists.fishpool.fi
Errors-to: mint-bounce@lists.fishpool.fi
X-original-sender: helmut.karlowski@ish.de
Precedence: bulk
List-help: <mailto:ecartis@lists.fishpool.fi?Subject=help>
List-unsubscribe: <mailto:mint-request@lists.fishpool.fi?Subject=unsubscribe>
List-Id: <mint.lists.fishpool.fi>
X-List-ID: <mint.lists.fishpool.fi>
List-subscribe: <mailto:mint-request@lists.fishpool.fi?Subject=subscribe>
List-owner: <mailto:tjhukkan@fishpool.fi>
List-post: <mailto:mint@lists.fishpool.fi>

This is a multi-part message in MIME format. To properly display this message you need a MIME-Version 1.0 compliant Email program.

------MIME delimiter for sendEmail-852677.392614172
Content-Type: text/plain;
  charset="iso-8859-1"
  Content-Transfer-Encoding: quoted-printable

> 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.

> adi_load: done
> Creating XaAES kernel thread
> k_main:SEMCREATE
> Installed 'nAES' cookie in readable memory at 123C000
> k_init: videomode=3D0
> nvdi version =3D 503
> could not determine fvdi version
> 1st v_opnvwk
> ->0, wh=3D1976/12374 3 colors
> k_init:vdo=3D40000 vm=3D0 video=3D0
> Default screenmode
> Screenmode is: 1
> k_init: v_opnwk() mode=3D1
> k_init: v_opnwk() handle=3D2
> Physical work station opened: 2
> Virtual work station opened: 3
> lookup-support:0, planes:16

I still wonder where the 1st wk comes from and what it does.

> Loading system resource file 'xaaes.rsc'
> xaaes_sysfile: check if '\c\MINT\1-17-CUR\XAAES\xaaes.rsc' exists - return =3D 0
> system resource =3D 7B5C004 (\c\MINT\1-17-CUR\XAAES\xaaes.rsc)
> xaaes_sysfile: check if '\c\MINT\1-17-CUR\XAAES\xa_xtobj.rsc' exists - return =3D 0
> xaaes_sysfile: check if '\c\MINT\1-17-CUR\XAAES\img\hc\dbox.img' exists - return =3D -33
> xaaes_sysfile: check if '\c\MINT\1-17-CUR\XAAES\img\hc\popbkg.img' exists - return =3D -33

..

You'll get a faster start if you rename img.


-Helmut



------MIME delimiter for sendEmail-852677.392614172--