Silicon Investor (SI) -- The First Internet Community

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Technology Stocks : Rambus (RMBS) - Eagle or Penguin -- Ignore unavailable to you. Want to Upgrade?

To: JimLeo who wrote (27286)	8/20/1999 1:19:00 AM
From: Dan3	Read Replies (3) \| Respond to of 93625

Re: You can't use benchmarks using overclocked CPU's The systems were overclocked only in the sense that the CPU hadn't been certified to run at 133. If it had crashed, you could have blamed it on overclocking. It didn't. It was just faster on PC133. And it demonstrated that, unlike rambus 800, there are advantages to using PC133 over PC100. Dan By the way, I have an older server (running Winframe) that used to blue screen every week to 10 days. It had an intel board with a Pentium 233 on it. I swaped out the motherboard for an ASUS P5 and an AMD k6-400. Same drives, same installation of the OS, just swaped out the mainboard - hasn't blue screened since. Now, my guess is that I had an intermittent sim, since, in my experience, Intel CPUs and mainboards are usually pretty good, but moving to the AMD/ASUS board solution was what solved this particular problem. (The move was made for performance - Winframe isn't the most stable OS, a weekly (or nightly) reboot is often used in Winframe installations. The elimination of the blue screens was an unexpected bonus.