| Subject: Re: SETI Driver problem? |
| From: "~misfit~" <~misfit~@his_desk.com> |
| Date: 31/12/2003, 11:27 |
Michael D. Ober wrote:
One more possibility - you're checking the "Use Proxy Server" option,
but are you entering proxy server information?
Hi again Mike. No, I'm not entering proxy server info. I should have the "No
Proxy/Socks" checked instead?
Thanks,
--
~misfit~
"Michael D. Ober" <obermd.@.alum.mit.edu.nospam> wrote in message
news:nsoIb.26681$Pg1.5501@newsread1.news.pas.earthlink.net...
Two things.
First, download the current version of SETI Driver from
http://www.wakeassoc.com/setidriver. I have added true IDLE
processing as an option as well as cleaned up some of the code since
the version that Marcel is distributing (with my permission).
Second, I suspect you have a colon ":" in your proxy server name.
If so, this is still a known bug. If not, please email me your SETI
Driver.cfg file and I'll take a look.
Mike Ober.
"~misfit~" <~misfit~@his_desk.com> wrote in message
news:TsnIb.44970$VV6.976576@news.xtra.co.nz...
Hey y'all.
I finally got around to dumping the GUI version of SETI (probably
just in time for BOINC) and downloaded a package from:
http://members.home.nl/marcel.zuiderveld/
which did pretty much everything for me. Installed SETI Driver and
SETI Spy and uninstalled the GUI. It works like a charm, I'm
returning three times the units I was before as my machine is
working all day while I'm working, browsing, reading newsgroups and
gaming. I no longer feel obliged to leave it on at night now and
again just to get a few units. <g>. My CPU sits at around 50�C or
less all the time (Athlon XP1800+ Tbred B at 10.5 x 200FSB with a
0.15v over-volt and standard HSF with ducted outside-case air being
blown onto the CPU fan)
*However*, it's not automatically returning results and getting
units after a re-start. In SETI Driver, under the section
Proxy/Socks server, the 'proxy server' check-box is ticked and,
when I re-start, in the top field under host it has "-SETISPY".
If I remove that and click 'save configuration' then it transmits
and receives fine. However, upon re-start it's there again. It's no
biggie I guess but is there some way I can fix it?
I connect to the internet through a LAN via a dial-up machine which
is always on. No problem with anything else that uses the 'net.
--
~misfit~