From mint-bounce@lists.fishpool.fi  Mon Apr 27 13:28:02 2009
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=domainkey-signature:mime-version:received:in-reply-to:references
         :date:message-id:subject:from:to:cc:content-type;
        bh=f0ObaH8olz1KdtGgmv5498mJuPA9piddwawljZ3j0lk=;
        b=i82Q7ruB4yt8L/3fQQyEgPOGO1EhOnAWAlOnuzBRo0MFwwjLpyFoJjfSD1iB/Bpk7n
         ief81YeuEuHTXODdHaCYZRcKlZ9gc8IglQqY/y9aMA86eO/kz3ANACwQ/tHkn5pWy+33
         R2/7oLkjhopNVlJfACbAtAgKJphYA9+LCGBHQ=
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :cc:content-type;
        b=poLLWXOWJ3vO+j6fvGhBstOhgh9iQkQnXaC2K/grX1wI0lAbdw2M/DmkDbWrS6ORYh
         tl5Vt41h5BjLcPqKodZ8MGdQcXpuR2OmN73LTcFEcKZ/gM5m64IBklrwSYUdP92yMo1T
         QZrjUMme99vik4YtAfHNCjf+eOQWx8EuFOIR8=
MIME-Version: 1.0
In-Reply-To: <Pine.GSO.4.63.0904271255520.16630@saltmine.radix.net>
References: <Pine.GSO.4.63.0904271255520.16630@saltmine.radix.net>
Date: Mon, 27 Apr 2009 19:24:50 +0200
Message-ID: <c6533ef60904271024w33e416f3gf74db208d7903380@mail.gmail.com>
Subject: Re: [MiNT] Possible MintLib FastRAM bug in TOS/MagiC? (Or My Own 
	Error...)
From: Miro Kropacek <miro.kropacek@gmail.com>
To: Keith Scroggins <kws@radix.net>
Cc: mint@fishpool.com
Content-Type: multipart/alternative; boundary=000e0cd246c6aa51b904688c9f76
X-ecartis-version: Ecartis v1.0.0
Sender: mint-bounce@lists.fishpool.fi
Errors-to: mint-bounce@lists.fishpool.fi
X-original-sender: miro.kropacek@gmail.com
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>

--000e0cd246c6aa51b904688c9f76
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

> Did any of this make sense, need more info?

Probably not much of help but -- are you aware of the fact you can't call
mxalloc in the TOS with that MiNT flag (bit 3) set? Because if you do, the
call will fail -- I remember to fail here when I was doing mxplay. Maybe
some of your / SDL code uses this with MiNT flag set.


-- 
MiKRO / Mystic Bytes
http://mikro.atari.org

--000e0cd246c6aa51b904688c9f76
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<br><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"b=
order-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; paddin=
g-left: 1ex;">Did any of this make sense, need more info?</blockquote>Proba=
bly not much of help but -- are you aware of the fact you can&#39;t call mx=
alloc in the TOS with that MiNT flag (bit 3) set? Because if you do, the ca=
ll will fail -- I remember to fail here when I was doing mxplay. Maybe some=
 of your / SDL code uses this with MiNT flag set.<br>
</div><br clear=3D"all"><br>-- <br>MiKRO / Mystic Bytes<br><a href=3D"http:=
//mikro.atari.org">http://mikro.atari.org</a><br>

--000e0cd246c6aa51b904688c9f76--