From mint-bounce@lists.fishpool.fi  Sun Jan 10 15:00:25 2010
Message-ID: <4B4A3168.3070209@online.no>
Date: Sun, 10 Jan 2010 20:58:32 +0100
From: Jo Even Skarstein <joska@online.no>
User-Agent: Thunderbird 2.0.0.23 (X11/20090817)
MIME-Version: 1.0
To: "mint@lists.fishpool.fi" <mint@lists.fishpool.fi>
Subject: Re: [MiNT] XaAES+nvdi-et400
References: <BIEHKLLGMNEPEMKHDPAIIEHGEMAA.mintlist@mr2.net> <4B4A1AC2.3040003@online.no> <op.u6b1jujlofd6j1@descaro.cpe.ish>
In-Reply-To: <op.u6b1jujlofd6j1@descaro.cpe.ish>
Content-Type: text/plain; charset=ISO-8859-15
Content-Transfer-Encoding: 7bit
X-ecartis-version: Ecartis v1.0.0
Sender: mint-bounce@lists.fishpool.fi
Errors-to: mint-bounce@lists.fishpool.fi
X-original-sender: joska@online.no
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>

Helmut Karlowski wrote:

>> normally, we know that this is indeed possible. We could even trace
>> N.AES to see what it does when opening the physical workstation.
> 
> How is it started? Do you write INIT=N.AES or GEM=N.AES in mint.cnf?

When I had a TT I always started N.AES using GEM= in mint.cnf. There
were no problems with NVDI ET4000.

Jo Even