From mint-bounce@lists.fishpool.fi Mon Jul 26 12:18:44 2010 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:subject:mime-version :content-type:from:in-reply-to:date:cc:content-transfer-encoding :message-id:references:to:x-mailer; bh=159Zz0VPkT6APy6ZfEfLF8U9SpJ/RRCgi3HsgcRBuXs=; b=Hy/IaEf55Szv+tc1xRkh9Ze2g5mPO6PGWcemWU3KuCz0WqYrR6W5BdyADGjAjv+/1z E6u9OHyX6aA7DJfia15frenpyysQTcgJRFIv+qIkNQwUst9pNsppimokQx+wpdfqDgjI mZHPJ/H6GA9Ot+IVE/Zqkp2zvaXAAA6wtGcnQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; b=otX/yDAu7N8IqUHmDabotVHB1u2cLVwvTnsBex2do7WafxncokXRyDCH6iw/isGw/d UdjDi6naAmi/SWJPi8gsZRlfT+xF5Mkmjj2UMCsjTr45pzs1kr6fA//NFZ4mbBPbjaoe c/fOnqiJnmCym8iw8uJbV8Rak70Hq6Yi2Ahb0= Subject: Re: [MiNT] "pid 80 (conholio) : unifs: couldn't match a drive with a directory" Mime-Version: 1.0 (Apple Message framework v1081) Content-Type: text/plain; charset=iso-8859-1 From: Peter Persson In-Reply-To: <4C4DB3C9.4050104@freesbee.fr> Date: Mon, 26 Jul 2010 18:16:56 +0200 Cc: mint@lists.fishpool.fi Message-Id: References: <4C4DB3C9.4050104@freesbee.fr> To: =?iso-8859-1?Q?Vincent_Rivi=E8re?= X-Mailer: Apple Mail (2.1081) X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: pep.fishmoose@gmail.com 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 o6QGIh7U024256 26 jul 2010 kl. 18.11 skrev Vincent Rivière: > Peter Persson wrote: > I have already reported that recently. > It happens with any software built with a recent MiNTLib and run with an old kernel. It happens when the program is run from a specific drive (i.e. C:\) but not from U:\. That explains it! > Alan answered we should not run new programs with old kernels, but we should at least investigate that to understand what is going on. "we should not run new programs with old kernels"? I take it this is a joke? In this case, "old kernel" == 1-16 (and this is an official release unlike 1-17). -- PeP