Athlon Original 750 @ 900 8 hour WU standard??

[garkman]

Hey, check out my sys config below, just wondering if 8 hours was the usual for my setup, thanks for the input.

 

[Fardringle]

Is your RAM running at CAS 2 or CAS 3? Also, is that one stick of RAM or more than one. If it is more than one, enable SDRAM Bank Interleave in the BIOS. Are you able to raise the BUS speed any? That would help your times as it would speed up the entire system.

With your memory at CAS2 and everything else optimized, I would think you should be getting around 6-7 hours. Are you using the GUI screensaver or the command line client? If you are using the screensaver, make sure it it set to blank the screen. If you can, I would recommend using the command line client as it will generally cut about 10-15% or more off of your times compared to the screeensaver...

 

[garkman]

It's CAS2-one stick of generic stuff original athlon board-no bios tweaking (fsb, etc) so i'm basically stuck w/what i got there...i have blank screen turned on. Thanks for the input!

 

[Assimilator1]

Sounds to me as if your still running v2.xx ,are you? if so get the latest v3.0 client ,preferable the Cli version ,v3 is MUCH quicker on an Athlon system.
Here are some WU times on my fathers Athlon 700 Abit KA7 (133MHz RAM)
v2.4 CLi
9/18 Mon 8:44pm 39c670b2 qresult.257 6h50m44s COLIN
9/19 Tue 3:38am 39c6d1a1 qresult.258 6h53m33s COLIN
9/19 Tue 10:32am 39c732bb qresult.259 6h54m16s COLIN
9/19 Tue 5:27pm 39c793f1 qresult.260 6h54m44s COLIN
Switched to GUI v2.04 client
9/21 Thu 7:08pm 39ca4eb7 qresult.261 7h21m22s COLIN
9/23 Sat 3:45pm 39ccc225 qresult.262 7h58m53s COLIN
9/24 Sun 8:20pm 39ce5408 qresult.263 7h39m39s COLIN
9/26 Tue 12:34am 39cfe0ef qresult.264 7h52m25s COLIN
9/27 Wed 8:09pm 39d24601 qresult.265 8h09m17s COLIN
9/29 Fri 9:05pm 39d4f600 qresult.266 8h17m07s COLIN
10/02 Mon 6:36pm 39d8c78a qresult.267 9h08m15s COLIN
10/05 Thu 9:32pm 39dce568 qresult.268 8h14m59s COLIN
10/07 Sat 12:47am 39de647d qresult.269 7h47m42s COLIN
10/07 Sat 8:21am 39decef6 qresult.270 7h34m20s COLIN
10/08 Sun 9:41pm 39e0dc02 qresult.271 7h53m29s COLIN
10/12 Thu 9:26pm 39e61e85 qresult.272 8h15m47s COLIN
client changed to v3.0 GUI
10/14 Sat 8:57pm 39e8ba91 qresult.273 5h44m15s COLIN
10/15 Sun 11:03pm 39ea2996 qresult.274 5h42m30s COLIN
10/19 Thu 3:58pm 39ef0c2b qresult.274 6h57m58s COLIN
10/19 Thu 10:32pm 39ef685d qresult.275 5h16m34s COLIN
10/20 Fri 4:56am 39efc283 qresult.276 6h24m40s COLIN
10/20 Fri 11:23am 39f01d35 qresult.277 6h27m01s COLIN
10/20 Fri 5:36pm 39f0747e qresult.278 6h12m28s COLIN

I'm looking to switch that 1 over to Cli v3.0 soon

 

[garkman]

Hrm, interesting guys, i'm runnin standard 3.0 w/blank screen mode now...i can't stand Old Dos apps...instability & such...thanks for the input tho!!

 

[blade47]

garkman the seti cli isn't an old dos program. It's not even really a true dos program it'll only run in windows and is every bit as stable as the gui and is much faster.🙂

 

[garkman]

K, all i know is that it runs WinOldApp (MS-Dos compatability mode driver) within windows while it runs.

 

[xtreme2k]

i think it is written as a Old windows apps
apps more designed for 95 i think

 

[blade47]

The window is also easily hidden using setispy.🙂

 

[office boy]

The 3.0 CLI is SPECIFICALLY written to be run with WinNT, and is therefore ported to command line, for easy administration.

 

[Assimilator1]

Garkman

Your on v3 already? ,oh well maybe its the 1/3 (?)L2 divider thats holding things back?

Have you checked to see if SETI is getting 95-99% cpu time when little else is running? ,if you don't have a task manager to use, try this one ATM 🙂

 

[office boy]

N/M

 

[garkman]

Good call on the 1/3 L2...that's most definitely it, CPU usage for seti is about 90% (got the usual suspects running in the background)...thanks for everybody's input, u guys rock!