From mint-bounce@lists.fishpool.fi Thu Apr 29 15:42:33 2010 Content-Type: text/plain; charset=iso-8859-15; format=flowed; delsp=yes References: <0004cd7e.0184326223fe@smtp.wanadoo.fr> <201004292104.54898.jflemaire@skynet.be> Subject: Re: [MiNT] INI : File not found - The return! To: mint@lists.fishpool.fi Date: Thu, 29 Apr 2010 21:41:36 +0200 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit From: "Helmut Karlowski" Message-ID: In-Reply-To: <201004292104.54898.jflemaire@skynet.be> User-Agent: Opera Mail/10.52 (Win32) X-Antivirus: avast! (VPS 100429-1, 29.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: List-unsubscribe: List-Id: X-List-ID: List-subscribe: List-owner: List-post: Am 29.04.2010, 21:04 Uhr, schrieb Jean-François Lemaire : > > This is not a bug. Jo Even was right. Look up /etc/ttytab. You should see > there this line: > > console "/usr/bin/xaaes" tw52 on secure > > On my system, "/usr/bin/xaaes" is a symlink to "/c/mint/1-16- > cur/xaaes/xaloader.prg". In that case he XaAES wouldn't start. Is this the case? I would use a debug-kernel and try to catch the failing open from the debug-output. -- Helmut Karlowski