"Dr.White" <> wrote in message
news:POOdnc5fEr-...
>
> "~misfit~" <> wrote in message
> news:ffhr47$ihd$...
>> Hi folks,
>>
>> I've tried to search the group's archives (Google) but aren't sure what
>> string to put in. I need advice..
>>
>> I'm looking at getting a low-cost (i.e. *Not* Striker Extreme. <g>) Asus
>> or Gigabyte (they're about the only boards that seem to be stocked much
>> here in NZ) 775 mobo that I'll be able to OC my E4500 in. Any advice
>> appreciated. Oh, integrated graphics (or an AGP slot) would be good as I
>> won't be able to purchase a PCI-e card for a while
>>
>> TYVMIA. :-)
>> --
>> Shaun.
>>
>> (Thinking I might have to go the Asrock way instead...)
>>
>
> Have a quick look at my observations on 'PC support network' thread. I've
> worked out the quirks of said board and well... I'll let you have a look.
>
> Cheers Shaun,
>
> Dr.White.
AHA! Further to my earlier post in the "PC support network" thread - After
further experimentation, I have good news regarding that unflinching PC3200
memory of yours. The ASRock's BIOS has a veritable plethora of options for
the memory, but quite simply, I forced it into thinking that my DDR-400 was
indeed DDR-333. Running as I do on a FSB of 285, CPU-Z is now showing an
FSB

RAM ratio of 8:5, and shows my memory frequency to be 178.3MHz (*2),
and latency has lowered. Does this impact performance? We shall see...
Sisoft Sandra- Memory banwidth benchmark takes a hit exactly in line with
memory frequency, but all arithmetic, multimedia, etc are unchanged.
Aquamark 3 - Hmmm, took a dive from 92,000 to 84,500. Maybe I should run it
dual channel - the matching stick is in my Dad's machine.
SuperPi - it's taking a hit. For the 1M calculation, it's taking 30.5
seconds instead of 27.
FPS on UT2004 demo is down 5%.
But - all that lost performance can be clawed back by upping the FSB, now
that it's looking like your RAM isn't gonna be such a brick wall hinderance.
When this exact same RAM was in my Athlon XP machine, an increase of 1MHz
caused errors on Prime95, but perhaps something else was the problem.
I'll keep you updated,
Dr.White.