Nope that didn't do it. I got up this morning to find the Linux box sitting there not crapped out, but just waiting for a WU. Also one of my Win98 boxes was the same way. SetiQ just seems to not want to download any WU's! Here's the output SetiQ had:
Seti Queue. Revision .78b Courtesy of: Ken Reneris
9/25 Mon 10:52am INI result_log=log
9/25 Mon 10:52am INI report_stats=yes
9/25 Mon 10:52am INI work_unit_adjust=1
9/25 Mon 10:52am INI min_limit=3
9/25 Mon 10:52am INI max_limit=8
9/25 Mon 10:52am INI max=8
9/25 Mon 10:52am INI sync_hour=3:30
9/25 Mon 10:52am INI queue_depth=4 days
9/25 Mon 10:52am INI max_poll=20 minutes
9/25 Mon 10:52am INI log_filesetiq.log hours=1
9/25 Mon 10:52am ave 192.168.0.2 23h03m15s
9/25 Mon 10:52am wu (rpd=1) Min:1 Max:8 Queued:0
9/25 Mon 10:52am SRV connecting to seti@home server
9/25 Mon 10:52am SRV get user_info
9/25 Mon 10:52am sah ME WuAdjust: 2
9/25 Mon 10:52am sah ME -> qresult.7 31h40m38s
9/25 Mon 10:52am sah ME <- user_info
9/25 Mon 10:52am sah wake srv
9/25 Mon 10:52am sah duplicate result ignored
9/25 Mon 10:52am sah ME <- user_info
9/25 Mon 10:52am sah wake srv
It always seems to just sit there on "wake srv" if some system has tried to request a WU or if it has yet it to it sits there at "get user_info." Again both of my Wsockhk.txt's have all the lines commented out (the one in \Seti@home and \Seti@home\setiq) and here is my qseti.txt below:
# work_unit_adjust sets the number of
seti@home.exe client apps
# that are processing work units. This number is used to determine
# how many work units are really outstanding (which is the # in
# the queue, plus the number of clients working on work units)
work_unit_adjust=1
# sync_hour is the hour to connect the seti server to send all
# outstanding results, and to acquire new work units. By default the queuing
# app picks the minute of the hour at random. (The hour is picked
# at randmon as well if the following line is commented out)
sync_hour=3
#sync_min=0
# setting autoconnect to 'no' will stop setiq from attempting to
# automatically contact the seti server. To connect you must use
# sq.exe tools. E.g: sq local connect
autoconnect=yes
# startupconnect causes setiq to transfer work when first started.
# Setting this value to 'no' will disable this.
startupconnect=yes
# max_poll is the longest amount of time to wait when polling the
# setiserver. This value is in minutes. If setiqueue can not connect
# to seti server, it retries in 1 second and doubles that amount
# each time the connection fails, up to max_poll. This value
# may be set from 5 to 2880.
max_poll=20
# if there are abort_retry_count *consecutive* failures in trying
# to perform an operation to seti server, setiq will disconnect
# and disable autoconnecting either permanently or until the
# next sync time as determined by the retry_at_sync_time flag.
#abort_retry_count=8
#retry_at_sync_time=no
# queue_depth is the number of days worth of work units to queue.
# the min is 1, the max is 30. This number to queue fluctuates a bit
# as min & max are computed by the rpd (result per day) which is
# tallied as the number of results submitted to the queuing app
# over the last 24 hours.
queue_depth=4
# ave_over is the number of days to average the results over
# to determine the number of work units being completed per day.
# This setting must be within the number of days setiq has been
# running.
ave_over=1
# min_limit limits the minimum queue threshold.
# max_limit limits the maxumum queue threshold. These are used if
# for some reason the queuing app is downloading too many work units.
# This allows an override to reduce the numbers.
min_limit=3
max_limit=8
# This setting will increase the upper limit of the queue size
# to be at least 'max'. The maximum value for this setting is 200.
max=8
# response_delay sets a delay in seconds that setiqueue will wait
# before responding to receiving a new result from a client. Set
# this value to 5 if you are using the seti monitor app. This will
# give the app enough time to see the result.sah file.
# response_delay=5
# result_log provides the location to keep a copy of all results
# ever completed. The file result.log (in the setiqueue directory)
# can be used to see which local machine completed which result.
# Comment this line out if you do not wish to keep a logged copy
# of all results sent. Note the results are logged when clients
# complete, not when they are sent to the seti server
result_log=log
# report_stats disables the reporting of statistics to setiq server.
# At some point I will put a link to get setiq stats on my website, but
# have not completed the web site code to do this yet. The stats also
# are useful when I send mail to s@h to indicate how many seti users
# are using/depending on setiq. And finaly I can send update notices
# to active users whom are reporting statistics when a change is
# made to setiq.exe
#report_stats=no
# After stats are reported an optional local job can be dispatched
# with job=
#job=C:\W2K\system32\cmd.exe /c e:\backup\backup
# log_file sets a filename where setiq output should be logged.
# log_days indicates how many hours to keep in the log before starting a new one
log_file=setiq.log
log_hours=1
# proxy_server is used if the non-queued clients normally work
# through a proxy server. By supplying proxy_server the connection
# setiqueue makes will be through the proxy server & port
# information.
#
# Note: This setting is under testing.
#
#proxy_server=204.248.217.6
#proxy_port=80
The computer is ALWAYS connected via dialup networking. I almost NEVER get kicked off and at all these times I was testing I was connected.
Help?