From fnaumann@mail.cs.uni-magdeburg.de Sat Jul 3 01:29:52 2004 Message-ID: <031901c4608b$bd4c4770$0a01a8c0@tonic> From: "Brian J. Roland" To: "MiNT" Subject: [MiNT] CT2b Saga Continues Date: Fri, 2 Jul 2004 18:24:35 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 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: bjr@localink4.com Precedence: bulk List-help: List-unsubscribe: List-ID: X-List-ID: X-Milter: ClamAV 0.70/0.70kjel X-Milter: milter-regex 1.5jel X-Milter: ClamAV 0.70/0.70kjel X-Milter: milter-regex 1.5jel The strangest thing just happened! I'm sure most of you have seen my venting about Falcon CT2b and mint problems...the saga continues, but this time there's good news. Today I took my CT2b out, did a full reinstall, and kept having the same problems. Next I put the CT2b board under a well lit magnifying glass, and discovered some crushed pins on the CPU. How they got this way, I haven't a clue. My guess is that a pair of the pins might have been 'touching'. So....I found a razor and added some space between the suspected pins there right carefully. I still get problems from time to time on boot...but not nearly as bad (today anyway). Here's the fun part! I took down all my MINT folder files and reinstalled these bits. While I was at it, decided I might as well try it with memory protection on. Alas, it's working! Right now at least....CAF is even playing a MIDI file as I type here. This is with the 1.15.12 kernal in Turbo Mode and EasyMiNT 1.4.1 distribution. Lets hope it stays together! Brian