Sick SETI Cruncher - Help Troubleshoot Please

[xhale]

All power saving features are off (except monitor) in XP and bios.

CPU temp is 54C w/SETI Driver running

setiathome-3.03 is using 89-98%

seti driver is using 0%

 

[Wiz]

Ok, looks like you are crunching since the cpu % shows seti using most of the cycles.
The temp is a bit high, have you checked your other similar machines with MBM to see the cpu temp while crunching?
(my P3 @ 974mhz is running 48C under full seti load - this is at 1.9V, yours is stock 933 at stock voltage right?)
What is the AR of the current work unit?
How long has it been working on the current WU and what is the percent finished?

 

[Smoke]

What I suggest is ditching seti driver (my very favorite seti add on) and see if things go right merely with seti cli.

Execute the SETI cli with -proxy 192.168.123.184:5001 (e.g. seti.exe -proxy 192.168.123.184:5001).

I don't think Xhale has done this yet. He is reporting SetiDriver at 0 CPU usage. It shouldn't even be there if he turned it off and is only running the CLI Client.

Xhale, I know this is a pain in the arse but go ahead and follow Wiz's instructions. (If you already have, then just ignore me.)

/me now backs off again and watches/

 

[Wiz]

I suggest putting the seti cli in a new folder along with your user_info.sah file and making a shortcut to it. Edit the properties of the shorcut to add:
-proxy 192.168.123.184:5001

What is the temp of the other P3 933's while crunching?

54C is high, mine gets unstable right around there so I keep it down with extra cooling fans.

What is the voltage setting on this cpu?

 

[xhale]

This is strange. I just got in and have 2 WUs completed. I haven't made Wiz's recommended changes yet.

 

[Smoke]

As you can see it was 9 hours ago that Wiz was trying to give you a hand. He is off in some meetings right now but will return later in the evening. I'm sure he is going to look back in on this thread. We figured you had to go to work.

OK, so you have two completed WUs. Tell me more. Are they in the SetiDriver installation that is marked to NOT AUTO TRANSMIT and are they are pointed to the Berkeley server (meaning NO PROXY/SOCKS is selected)?

Or have you transmitted them and observed that you got credit in your S@H account?

 

[xhale]

Tell me more. Are they in the SetiDriver installation that is marked to NOT AUTO TRANSMIT and are they are pointed to the Berkeley server (meaning NO PROXY/SOCKS is selected)?

They are in the SetiDriver installation that is marked to NOT AUTO TRANSMIT, they are pointed to my SetiQueue.

Or have you transmitted them and observed that you got credit in your S@H account?

Transmited them and observed. Both accounted for!

BTW, when do you sleep?

 

[Smoke]

So for the moment you are good to go. :Q

Let's keep our eyes on that machine and see if it gives us any more trouble.

Sleep?

 

[Wiz]

hmmm what's different? what changed?

(me just got back from late late meetings)

 

[xhale]

hmmm what's different? what changed?

Dunno yet. Didn't change anything.