From fnaumann@mail.cs.uni-magdeburg.de Thu Jul 22 13:08:15 2004 Date: Thu, 22 Jul 2004 13:03:41 +0200 From: mikro To: mint@fishpool.com Subject: Re: [MiNT] freemint 1.16.0b stability Message-ID: <20040722110341.GA3154@hysteria.sk> References: <20040722083449.GA22919@hysteria.sk> <004301c46fd0$2c2eecd0$480f63d9@blaszak> <20040722101829.GB15521@hysteria.sk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2i X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on onyx.hysteria.sk X-Spam-Status: No, hits=-4.9 required=5.0 X-Virus-Scanned: by amavisd-new-20030616-p7 (Debian) at fishpool.fi Delivered-To: mint@fishpool.com Delivered-To: mint@lists.fishpool.fi X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: mikro@hysteria.sk Precedence: bulk List-help: List-unsubscribe: List-ID: X-List-ID: X-Milter: ClamAV 0.70/0.70kjel X-Milter: ClamAV 0.70/0.70kjel > You know that this is heavily overclocked and that especially the 'full' > 68060 have problems with such heavy overclocking? As you use PMMU I assume > that you have a 'full' 68060. > but this is the last revision, which R.Czuba sent to all developers who were interested.. so for this version is normal operating speed, didier went even over 110 mhz :) And yes, full 060. > That's don't mean much if you don't run an intensive memory test for > example. > i can do it, but i doubt it will fail... remember NOONE of these problems appeared on 1.15.12! > It's possible that you run for testing the CPU at the normal clock speed > (of 66 MHz) and see if the problems remain? Just to be sure that it's not > the hardware. > eh... ok, but only for your satisfaction ;-) -- --------------------------------------------------------------------------- MiKRO Atari XE/XL/Mega STE/Falcon060 http://mikro.atari.org ---------------------------------------------------------------------------