From mint-bounce@lists.fishpool.fi Thu Apr 29 14:44:08 2010 X-ME-UUID: 20100429184023754.B81B670006C9@mwinf2812.orange.fr To: From: Jean-Luc CECCOLI Subject: Re: [MiNT] INI : File not found - The return! X-Mailer: MyMAIL Rev:1.94.13761 (Atari/(STiK/STinG/GlueSTiK)) X-Hardware: Atari FalCT60 96 MHz / 526 Mo / 20 Go MIME-Version: 1.0 Date: Thu, 29 Apr 2010 20:45:50 +0200 (EET) Content-Type: text/plain; charset="iso-8859-15" X-Priority: 3 X-MSMail-Priority: Normal Message-Id: <0004cd7e.0184326223fe@smtp.wanadoo.fr> References: In-Reply-To: DED501562E3B4FA585EA393FCC6E889A@mercatus.local X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: Jean-Luc.Ceccoli@wanadoo.fr Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: List-subscribe: List-owner: List-post: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by mail.sparemint.org id o3TIi3G8027853 On Thu, 29 Apr 2010 08:05:34 , "Jo Even Skarstein" wrote: > > -------------------------------------------------- > From: "Helmut Karlowski" > Sent: Wednesday, April 28, 2010 10:17 PM > To: > Subject: Re: [MiNT] INI : File not found - The return! > > > Am 28.04.2010, 21:32 Uhr, schrieb Jean-Luc CECCOLI > > : > > > >>> Post your mint.cnf and mint.ini-files here, I'm quite sure that we'll > >>> find the answer there :-) > >>> > >> Hello, > >> > >> Here are the files. > > > > Nothing found - maybe its gluestik? > > > > Or does init issue the message? > > This looks like an EasyMiNT install. My guess is that init is looking for > xaloader.prg in the 1.16-folder. Have a look in /etc/ttytab (IIRC, I'm not > familiar with this unix-stuff anymore) and see if the path to xaloader is > hardcoded to the system-folder. > Hello, I search the whole data through and couldn't find any place where it could be told to go and search for anything elsewhere than in 1-17-cur folder. I found 2 folders into the boot folder in my MiNT partition (Q:\) which contain different versions of the kernel and some modules. I moved them so I can retrieve them quickly if necessary. So, I only can see 2 places where it could be told to go to 1-16 : 1- into the kernel itself (or one of its modules), or 2- in some cache that wouldn't be erased. Anyway, I think this bug will be hard to fix... Regards, J.-Luc