old skool

[Ben Rogers]

ok...oc'd my xp1600 on a kt133a mobo i picked up for cheap.

got it at 156 * 10.5 at the mo with stock vcore & pc133, 100% stable but any higher, the pci bus limits it with hdd & gfx running out of spec. ram maxes out at 172 cas 3 & 163mhz cas 2.

anybody have any idea's why it takes 5 hours to do a seti unit?

my old pc chips m810 with stock xp1600 did an average unit in 4 hours 30! i didnt think the kt133a was this slow or is it? benchmarks exactly where it should in every benchmark ive ran on it but just doesnt seem to like seti!

btw, got via 4 in 1's installed. memorys running in cas 2.

the strangest thing is the kt133a performs a lot better in sisoft memory benchmark than the pc chips did, 700mb/s vs 1200mb/s.

dont get it!

[Ben Rogers]

.

[Mulda]

Need a touch more info...

OS?
CLI or GUI (3.03 or 3.08)?
AR of unit?

Most windows OSes will complete a 'standard' 0.417° AR unit using 3.03 CLI in around 4 hours on that setup.

Lower AR will take longer (particularly on Win9x) as will *NIX, GUI or 3.08.

[Ben Rogers]

thanks for the reply.

os is windows 2000 pro with clean install, just seti command line 3.03 & seti driver.

0.417 - xp1600 on pc chips m810 @ stock - 4:30

0.417 - xp1600 on kt133a @ stock - 5:08

0.417 - xp1600 on kt133a @ 10.5 * 156 (xp1900 speeds) - 4:37

[Zak33]

Dont think that the older mobo supports the full benefits of an XP chip. My old IWill KK266 didn't . I whacked an XP init, and it was no faster than a T bird.

Soon as you have a mobo with even the vaguest whiff of XP support (not just compatibility) then you start getting the benefits of an XP chip.