Jon...

[e_storm]

My 8KHA+ has a regular TBird in it and is clocked at 1.6GHz with 160MHz on the FSB and it averages 3:45

You posted this in another thread. I looked at your farm page and it looks like you have the same system as me (#3 of your farm, system #1 in my sig). Are you getting under 4 hour times with your system #3? It takes me about 5.5 -6 hours per WU. Granted, Im only 1.4@.1477 and running the screen saver, but what else have you done to get those times so low?

[TC]

I don't know about Jon, but I'm running several 8KHA+'s and 8K7A's with XP's clocked between 1660 and 1700. I use the CLC and all of mine average around 3 hours flat. XP's crunch a good bit faster than tbirds, plus the screensaver will kill your times.

[Sir-Epix]

Ditch the screen saver and go with CLC with seti driver...by far the best crunching around.

[e_storm]

I have the screen saver set to go blank after 1 min and SETI generally runs for 10 hours straight until I get home. I know the screen saver is slower, but 2-3 hours?

Also, Jons rig was an 8K7A with a 1.4 T-bird (not an XP), which is what i have also. I was wondering how he got them so fast with the antiquated Tbird. He is running it at 1.6, which obviously gives him a major advantage over what I'm running, but I wouldn't think on the order of 2.5 hours. Thought he might have some tricks I could learn to speed it up.

[Jon]

At the time my 8K7A+ was running on a 166MHZ bus and I was getting sub 4 hour times on the CLC. I've since changed it back to stock 133MHz since I burnt out a DDR module. Clock speed is still the same, minus 60MHz, at 1.6GHz. I get 4h20m averages in WIn2K with it now and 4h45m averages in Linux, which I'm running on it now.

The screen saver is that much slower whether you have it go blank or not.

As far as tweaks go, nothing special. ALways agressive memory timings in the BIOS and turn off all shadowing. Other than that, everything else is normal.

[SpeeDj]

Give Jon a day or so, if that doesn't work drop him a PM and ask him that way. He usually stops in or so I have seen more towards nighttime anyway. Hope you get some good tips :cool:

Or just wait for him to respond above me LOL, Thanks Jon!

J

[Jon]

Haha, I'm always here. You Easterners are just up while it's still too early for us on the West coast.

I'm off today anyway so I got to sleep in :D

[SpeeDj]

LOL Sounds like a rough life you lead there :D Teasing, thanks again Jon for the speedy response

J

[e_storm]

Originally posted by Jon
At the time my 8K7A+ was running on a 166MHZ bus and I was getting sub 4 hour times on the CLC. I've since changed it back to stock 133MHz since I burnt out a DDR module. Clock speed is still the same, minus 60MHz, at 1.6GHz. I get 4h20m averages in WIn2K with it now and 4h45m averages in Linux, which I'm running on it now.

The screen saver is that much slower whether you have it go blank or not.

As far as tweaks go, nothing special. ALways agressive memory timings in the BIOS and turn off all shadowing. Other than that, everything else is normal.

ok cool....I've known about the value of increasing memory timings for some time now, but never did it out of a desire for stability on this system :rolleyes: . Never did know about shadowing though. I guess its about time though...I'll try both when I get home. thanks man :)

[Jon]

Turning off shadowing and video/BIOS RAM caching used to help when systems had low amounts of memory. It probably doesn't make any difference now since the smallest amount of memory most machines here carry is about 256MB.

I just turn it all off out of habit anymore. Play around and you'll find what works for your system.

[Sir-Epix]

Originally posted by Jon
Turning off shadowing and video/BIOS RAM caching used to help when systems had low amounts of memory. It probably doesn't make any difference now since the smallest amount of memory most machines here carry is about 256MB.

I just turn it all off out of habit anymore. Play around and you'll find what works for your system.

I find the shadowing to RAM helps improve my Celeron seti times. I guess it depends on the system...btw it has 160mb of Ram. So it is not in short supply.

[e_storm]

well, I aggressively times the memory settings last nite...it looked like it was moving much faster, but I'll see how fast once i get home tonite. From the looks of it though it should be 1/2 hour or so faster. I should be in the 5 hour range now.

[e_storm]

Originally posted by e_storm
well, I aggressively times the memory settings last nite...it looked like it was moving much faster, but I'll see how fast once i get home tonite. From the looks of it though it should be 1/2 hour or so faster. I should be in the 5 hour range now.

*update*

well, the aggressive memory setting did help on the old version of Seti, but I had to clock down back to stock speed to get it to work in Cas2, so some of my gains were erased.

I also upgraded to the most recent Seti version, and I'm at about 6 hours now. Based on reading the Seti page, the newest version is a bit slower, which proved true in my case.