From mint-bounce@lists.fishpool.fi  Thu Dec 31 15:48:36 2009
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=domainkey-signature:mime-version:received:in-reply-to:references
         :date:message-id:subject:from:to:content-type
         :content-transfer-encoding;
        bh=zu4RbRXFefr95GdmmgSBEXPcUrn0dLDEvr1meVGUaxI=;
        b=SKxZVBRg2r96kw65Q4syhpPDLGbSmJJPv/Vsnd+JSwQLij50E4IjKioTIe5rYRyF0s
         iy4F3dVEfvLzezK4BfhhVQTFfmID84wNID09bkh73R3DKuix3CZKQG+c0C9Urwd5k02L
         r60wbSyxJhdUVoj/3dJ0QSsu5KDjIscFMFwN4=
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type:content-transfer-encoding;
        b=FDQqstAj/IS7iLdT39DS891MKrSqaOs1Zm8juTd7h0mCQeQ5EVFpU5NzpIhpQiTClQ
         BnBAF6rUGtAQCI3tfyvinM1fz6dyPy5TTl38vPnJkpcnS9pLGcGHIqsB9BAOd6y1QJX5
         uyANN7kfo1JPCDENymwlRp5p7xsHSFmv5UXbk=
MIME-Version: 1.0
In-Reply-To: <BIEHKLLGMNEPEMKHDPAIGECMEMAA.mintlist@mr2.net>
References: <BIEHKLLGMNEPEMKHDPAIGECMEMAA.mintlist@mr2.net>
Date: Fri, 1 Jan 2010 07:46:08 +1100
Message-ID: <11a6f2b10912311246o491d7a0xa880e8a0990c8449@mail.gmail.com>
Subject: Re: [MiNT] Problem with xaaes/nvdi+video card
From: Paul Wratt <paul.wratt@gmail.com>
To: mint <mint@lists.fishpool.fi>
Content-Type: text/plain; charset=ISO-8859-1
X-ecartis-version: Ecartis v1.0.0
Sender: mint-bounce@lists.fishpool.fi
Errors-to: mint-bounce@lists.fishpool.fi
X-original-sender: paul.wratt@gmail.com
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>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by mail.sparemint.org id nBVKmZmu007788

On Fri, Jan 1, 2010 at 12:56 AM, Mark Nias <mintlist@mr2.net> wrote:
>
>  >
>  > > I'm sure there's no issue with NVDI itself as it works fine
>  > under mint in
>  > > many other senarios. I think it's some problem with NVDIs resolution
>  > > selection app SLCT_DEV.PRG
>  >
>  > You cannot always blame the one or the other if something doesn't work.
>  >
>  > > Would there be any scope in someone debugging XAAES and SLCT_DEV.PRG
>  > > together?
>  >
>  > What do you mean?
>
> well from using nvdi.prg with cd2_mana.prg WITHOUT using slct_dev.prg means
> slct_dev is not doing something specific with nvdi but with the aes/vdi. So
> it could potentially be engineered so xaaes or some new app does whats
> needed instead.
>
> Or looking into why slct_dev causes xaaes to fail in the first place, but
> thats not something i can do myself i'm afraid.
>
> mark
>
Helmut is the current "man on the job" and because of the setups,
should be able to do debug related stuff "no problem". You will
probably have to help out with running debug versions if your CD and
his are not identical, but thats not the same as using a debugger, so
you should be able to handle it (also) "no problem".

There was some other related discussion to NVDI and ET4000, I cant
remember exactly what, it may have been VDI related (with Johan and
fVDI), but there was a percieved need to update NVDI for some reason,
related to video.. It may have been in relation to CTPCI

A question for Helmut, what is the mint folder in your auto folder?
for mint prg's? And what are the other TT specific XaAES issues that
need addressing.

Paul