From owner-freebsd-questions Mon May 10 10:57:17 1999 Delivered-To: freebsd-questions@freebsd.org Received: from fw2.roguewave.com (fw2.roguewave.com [208.151.233.2]) by hub.freebsd.org (Postfix) with ESMTP id F3B6D158DF for ; Mon, 10 May 1999 10:57:05 -0700 (PDT) (envelope-from carey@roguewave.com) Received: by fw2.roguewave.com; id KAA27733; Mon, 10 May 1999 10:50:28 -0700 (PDT) Received: from cvo1.cvo.roguewave.com(10.68.4.36) via SMTP by hub.FreeBSD.ORG, id smtpd027724; Mon May 10 10:50:26 1999 Received: by cvo1.cvo.roguewave.com with Internet Mail Service (5.5.1960.3) id ; Mon, 10 May 1999 10:57:40 -0700 Message-ID: From: Woody Carey To: "'Rivendell'" , freebsd-questions@FreeBSD.ORG Subject: RE: not able to install thru a dos partiton (3.1-Release) Date: Mon, 10 May 1999 10:57:37 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.1960.3) Content-Type: text/plain Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This does not have to do with your immediate problem, but may be useful to you and others on the list. From listening to the problems and solutions of the gentlemen on the beowulf mailing list, I have come to the understanding that overclocking is risky, and when it does cause problems, it causes very hard-to-track-down problems. Time and time again I watched as someone wrote: "I have been having [network | reboot | disk i/o | ...] problems", try everything they could think of for a week, and then someone asked: "Are the machines o/c'ed?" Voila! Problem solved. Moral: Overclocking can cause hard-to-track problems. [snip] > tech specs of system > celeron 300a(o/c to 450mhz, i'm sure o/c-ing has NOTHING to > do with the > problem) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message