From mint-bounce@lists.fishpool.fi Sat Jan 9 04:09:31 2010 Message-ID: <4B48475A.4060304@online.no> Date: Sat, 09 Jan 2010 10:07:38 +0100 From: Jo Even Skarstein User-Agent: Thunderbird 2.0.0.23 (X11/20090817) MIME-Version: 1.0 To: "mint@lists.fishpool.fi" Subject: Re: [MiNT] XaAES+nvdi-et400 References: <11a6f2b11001081358x10630742i3f11a163e4908316@mail.gmail.com> <4B484259.70006@online.no> In-Reply-To: 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: List-unsubscribe: List-Id: X-List-ID: List-subscribe: List-owner: List-post: Helmut Karlowski wrote: >> N.AES works just fine with NVDI ET4000. Used it for years on my TT. >> N.AES is started directly by MiNT. However, I never got past 1.15 on >> the TT. > > What does MiNT > 1.15 do that makes any AES fail? I don't know if it does anything. But it means that I've never tested the kernel module XaAES on my TT, just Henk's version which worked fine with NVDI ET4000. However, I can't remember if I started it from the desktop or not. Btw. I'm using XBoot, which opens a physical workstation and runs before MiNT. Perhaps this is why N.AES worked with NVDI ET4000? I don't think I've booted without XBoot for almost 20 years, so I don't know what happens without it. Jo Even