<!doctype html public "-//W3C//DTD W3 HTML//EN">
<html><head><style type="text/css"><!--
blockquote, dl, ul, ol, li { padding-top: 0 ; padding-bottom: 0 }
--></style><title>Re: [DuoList] Duo 2300c
Overclocking</title></head><body>
<blockquote type="cite" cite>But everything was working on the
2300c?</blockquote>
<blockquote type="cite" cite><br></blockquote>
<blockquote type="cite" cite>I overclocked a PowerBook 3400c once to
165mhz and everything still worked.</blockquote>
<blockquote type="cite" cite><br></blockquote>
<blockquote type="cite" cite>I was hoping perhaps getting my 2300c to
around 120mhz.</blockquote>
<blockquote type="cite" cite><br></blockquote>
<blockquote type="cite" cite>On Feb 23, 2006, at 7:48 AM, <a
href="mailto:ElBrio@aol.com">ElBrio@aol.com</a> wrote:</blockquote>
<blockquote type="cite" cite><br>
<blockquote type="cite" cite> I had a clock chip oscillator here
I was using for a special app...think it was 37.333 or 37.5 mhz.
Just swapped the stock 33.33mhz osc. chip with the 37 mhz part.
Everything worked, but it really didn't add that much to the
processing speed. Like MadDog says, the processor ratio needs to
be changed, and that was hardwired, IIRC. Any time you mess with
bus speed, the chance of something not working increases. At 42
mhz, my old 280C would run, but crash on occasion....but the modem
would not work, ext. SCSI would not be reliable (bus speed affects the
onboard SCSI interface chip, even tho externally it self-clocks) and
the floppy would not work at all.</blockquote>
<blockquote type="cite" cite> </blockquote>
<blockquote type="cite" cite>Hey, but it was fun!<br>
</blockquote>
</blockquote>
<div><br></div>
<div>Everything worked fine. I took the precaution of replacing
the apple gap pad with a superior one I ordered from digikey.</div>
<div><br></div>
<div>Mad Dog</div>
</body>
</html>