From owner-freebsd-hackers Mon Mar 20 22:20:52 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id WAA00909 for hackers-outgoing; Mon, 20 Mar 1995 22:20:52 -0800 Received: from goof.com (root@goof.com [198.82.204.15]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id WAA00903 for ; Mon, 20 Mar 1995 22:20:50 -0800 Received: (from mmead@localhost) by goof.com (8.6.11/8.6.9) id BAA03098; Tue, 21 Mar 1995 01:20:38 -0500 From: "matthew c. mead" Message-Id: <199503210620.BAA03098@goof.com> Subject: Re: 66 -> 80 To: rgrimes@gndrsh.aac.dev.com (Rodney W. Grimes) Date: Tue, 21 Mar 1995 01:20:38 -0500 (EST) Cc: hackers@FreeBSD.org In-Reply-To: <199503210602.WAA03875@gndrsh.aac.dev.com> from "Rodney W. Grimes" at Mar 20, 95 10:02:39 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 862 Sender: hackers-owner@FreeBSD.org Precedence: bulk Rodney W. Grimes wrote: > > Has anyone ever clocked a 486dx2/66 up to 80? I'm considering doing this > > on my FreeBSD box. > > Most of them crap out some place between 70 and 72 Mhz... > > You can also cause serious CPU chip damage by doing this if you try to > run it much beyond the crap out point. Hmm. Oh well, I was just being hopeful. > DO NOT attempt to run a 66Mhz part at 80Mhz, it will not work. I know several people that due just fine running their 66 chips at 80, but they'll probably end up replacing the CPUs soon... :-) -matt -- Matthew C. Mead -> Virginia Tech Center for Transportation Research - -> Multiple Platform System and Network Administration Work Related -> mmead@ctr.vt.edu | mmead@goof.com <- All Other ---- ------- WWW -> http://www.goof.com/~mmead --- -----