receiving data very slowly

[John Smith]

I'm running the cli version of seti under WinXP with setidriver and
the d/l of data is very slow.

It stays at 10K for about 5 minutes and then I get the 20K message and
so on. I know my internet connection is fine because I can d/l
normally. Another computer on the same network works fine.

Any idea why this is so slow? It used to work just fine.

Thanks.

[Michael D. Ober]

This sounds like either a configuration problem (not likely since other
programs don't appear to have this problem), network contention between you
and Berkeley, or noise on your phone line.

Mike Ober.

"John Smith" > wrote in message
om...
> I'm running the cli version of seti under WinXP with setidriver and
> the d/l of data is very slow.
>
> It stays at 10K for about 5 minutes and then I get the 20K message and
> so on. I know my internet connection is fine because I can d/l
> normally. Another computer on the same network works fine.
>
> Any idea why this is so slow? It used to work just fine.
>
> Thanks.

[Michael D. Ober]

This sounds like either a configuration problem (not likely since other
programs don't appear to have this problem), network contention between you
and Berkeley, or noise on your phone line.

Mike Ober.

"John Smith" > wrote in message
om...
> I'm running the cli version of seti under WinXP with setidriver and
> the d/l of data is very slow.
>
> It stays at 10K for about 5 minutes and then I get the 20K message and
> so on. I know my internet connection is fine because I can d/l
> normally. Another computer on the same network works fine.
>
> Any idea why this is so slow? It used to work just fine.
>
> Thanks.

[Michael D. Ober]

The message you're seeing is coming from the SETI CLI itself. Download the
CLI again to your desktop and use the SETI Driver "New Client" button to
install it.

Mike.

"John Smith" > wrote in message
. 241...
> "Michael D. Ober" > wrote in
> arthlink.net:
>
> > This sounds like either a configuration problem (not likely since
> > other programs don't appear to have this problem), network contention
> > between you and Berkeley, or noise on your phone line.
> >
> > Mike Ober.
> >
> > "John Smith" > wrote in message
> > om...
> >> I'm running the cli version of seti under WinXP with setidriver and
> >> the d/l of data is very slow.
> >>
> >> It stays at 10K for about 5 minutes and then I get the 20K message
> >> and so on. I know my internet connection is fine because I can d/l
> >> normally. Another computer on the same network works fine.
> >>
> >> Any idea why this is so slow? It used to work just fine.
> >>
> >> Thanks.
> >
> >
>
> Here is the full error message:
>
> Getting data - connecting to server.
> Receiving data: 10K
> Receiving data: 20K
> Receiving data: 30K
> Receiving data: 40K
> Receiving data: 50K
> recv fd=64 n=0, errno=2
> Can't connect to server; will retry in an hour.
>
> I'm also running seti on my other computer and that computer connects and
> d/l wu's with no problem. So it can't be between me and Berkeley.
>
> Any other suggestions.
>
> Thanks
>

[Michael D. Ober]

The message you're seeing is coming from the SETI CLI itself. Download the
CLI again to your desktop and use the SETI Driver "New Client" button to
install it.

Mike.

"John Smith" > wrote in message
. 241...
> "Michael D. Ober" > wrote in
> arthlink.net:
>
> > This sounds like either a configuration problem (not likely since
> > other programs don't appear to have this problem), network contention
> > between you and Berkeley, or noise on your phone line.
> >
> > Mike Ober.
> >
> > "John Smith" > wrote in message
> > om...
> >> I'm running the cli version of seti under WinXP with setidriver and
> >> the d/l of data is very slow.
> >>
> >> It stays at 10K for about 5 minutes and then I get the 20K message
> >> and so on. I know my internet connection is fine because I can d/l
> >> normally. Another computer on the same network works fine.
> >>
> >> Any idea why this is so slow? It used to work just fine.
> >>
> >> Thanks.
> >
> >
>
> Here is the full error message:
>
> Getting data - connecting to server.
> Receiving data: 10K
> Receiving data: 20K
> Receiving data: 30K
> Receiving data: 40K
> Receiving data: 50K
> recv fd=64 n=0, errno=2
> Can't connect to server; will retry in an hour.
>
> I'm also running seti on my other computer and that computer connects and
> d/l wu's with no problem. So it can't be between me and Berkeley.
>
> Any other suggestions.
>
> Thanks
>

[anonymous]

Matt Giwer > bedacht usenet onlangs met het bericht
m>, en maakte ons deelgenoot
van:

> Totally erase seti with one of those erase utilities (or delete and install
> something else or use it for a few days or download a meg of graphics) then
> reinstall it. If still a problem reinstall windows with a full reformat if that
> is an option, presuming it will reformat without the option. Do something to
> make certain the same sectors are not used on reinstall.
>
> Or switch out the modems, reinstall the modem driver, reconfigure the modem even
> if it is correct -- set it wrong then right again, anything else the might be
> related to what you are seeing short of windows reinstall.

Nonsense.
Chances are that your SETI Driver's priority is set to 'normal'. When downloading
WU's, you should try and set it temporarily to 'low'. Does that do the trick?
Take a look at this thread as well:
www.google.com/groups?threadm=3eccfabf%241%40websrv.net4all.be

--
Polar

My ol' grandaddy taught me to always
post in plain text,
quote only that portion to which you are replying,
post replies at the bottom,
use Google before asking dumb questions.

[anonymous]

Matt Giwer > bedacht usenet onlangs met het bericht
m>, en maakte ons deelgenoot
van:

> Totally erase seti with one of those erase utilities (or delete and install
> something else or use it for a few days or download a meg of graphics) then
> reinstall it. If still a problem reinstall windows with a full reformat if that
> is an option, presuming it will reformat without the option. Do something to
> make certain the same sectors are not used on reinstall.
>
> Or switch out the modems, reinstall the modem driver, reconfigure the modem even
> if it is correct -- set it wrong then right again, anything else the might be
> related to what you are seeing short of windows reinstall.

Nonsense.
Chances are that your SETI Driver's priority is set to 'normal'. When downloading
WU's, you should try and set it temporarily to 'low'. Does that do the trick?
Take a look at this thread as well:
www.google.com/groups?threadm=3eccfabf%241%40websrv.net4all.be

--
Polar

My ol' grandaddy taught me to always
post in plain text,
quote only that portion to which you are replying,
post replies at the bottom,
use Google before asking dumb questions.

[Michael D. Ober]

I fixed this problem over a year ago. After 30 seconds, SETI Driver flips
the transmitting WU to "High" priority. This doesn't impact other programs
too much because the bulk of the clock time a WU is transmitting is spent
waiting for the network and very little time is spent actually assembling
the WU.

Mike Ober.

>
> Nonsense.
> Chances are that your SETI Driver's priority is set to 'normal'. When
downloading
> WU's, you should try and set it temporarily to 'low'. Does that do the
trick?
> Take a look at this thread as well:
> www.google.com/groups?threadm=3eccfabf%241%40websrv.net4all.be
>

[Michael D. Ober]

I fixed this problem over a year ago. After 30 seconds, SETI Driver flips
the transmitting WU to "High" priority. This doesn't impact other programs
too much because the bulk of the clock time a WU is transmitting is spent
waiting for the network and very little time is spent actually assembling
the WU.

Mike Ober.

>
> Nonsense.
> Chances are that your SETI Driver's priority is set to 'normal'. When
downloading
> WU's, you should try and set it temporarily to 'low'. Does that do the
trick?
> Take a look at this thread as well:
> www.google.com/groups?threadm=3eccfabf%241%40websrv.net4all.be
>

[anonymous]

Michael D. Ober > bedacht usenet onlangs met
het bericht hlink.net>,
en maakte ons deelgenoot van:

> I fixed this problem over a year ago. After 30 seconds, SETI Driver
> flips the transmitting WU to "High" priority. This doesn't impact
> other programs too much because the bulk of the clock time a WU is
> transmitting is spent waiting for the network and very little time is
> spent actually assembling the WU.

Well, my SETI Driver v1.6.4.0 operating the CLI client v3.08 is still
showing the same symptoms, both on WinMe, WinXP, and Win2k.

--
Polar

[anonymous]

Michael D. Ober > bedacht usenet onlangs met
het bericht hlink.net>,
en maakte ons deelgenoot van:

> I fixed this problem over a year ago. After 30 seconds, SETI Driver
> flips the transmitting WU to "High" priority. This doesn't impact
> other programs too much because the bulk of the clock time a WU is
> transmitting is spent waiting for the network and very little time is
> spent actually assembling the WU.

Well, my SETI Driver v1.6.4.0 operating the CLI client v3.08 is still
showing the same symptoms, both on WinMe, WinXP, and Win2k.

--
Polar

[Matt Giwer]

anonymous wrote:
> Matt Giwer > bedacht usenet onlangs met het bericht
> m>, en maakte ons deelgenoot
> van:

>>Totally erase seti with one of those erase utilities (or delete and install
>>something else or use it for a few days or download a meg of graphics) then
>>reinstall it. If still a problem reinstall windows with a full reformat if that
>>is an option, presuming it will reformat without the option. Do something to
>>make certain the same sectors are not used on reinstall.
>>
>>Or switch out the modems, reinstall the modem driver, reconfigure the modem even
>>if it is correct -- set it wrong then right again, anything else the might be
>>related to what you are seeing short of windows reinstall.

> Nonsense.

This is not the place to pick fights. If there is something nonsensical in
desperation measures in dealing with any version of windows, I have yet to hear of
it. I got tired of doing such nonsensical things when I switched to linux some
three years ago. I will guarantee that everything I suggested did work at least once.

Linux does screw up but it is always tracable to something rational and a
learning experience.

--
In July 2003 a poll of Palestinian refugees found most did not
want to return to Israel. A week later a poll found most Israeli
squatters in the West Bank were willing to leave if compensated.
Both governments are out of touch with the people.
-- The Iron Webmaster, 2794

[Matt Giwer]

anonymous wrote:
> Matt Giwer > bedacht usenet onlangs met het bericht
> m>, en maakte ons deelgenoot
> van:

>>Totally erase seti with one of those erase utilities (or delete and install
>>something else or use it for a few days or download a meg of graphics) then
>>reinstall it. If still a problem reinstall windows with a full reformat if that
>>is an option, presuming it will reformat without the option. Do something to
>>make certain the same sectors are not used on reinstall.
>>
>>Or switch out the modems, reinstall the modem driver, reconfigure the modem even
>>if it is correct -- set it wrong then right again, anything else the might be
>>related to what you are seeing short of windows reinstall.

> Nonsense.

This is not the place to pick fights. If there is something nonsensical in
desperation measures in dealing with any version of windows, I have yet to hear of
it. I got tired of doing such nonsensical things when I switched to linux some
three years ago. I will guarantee that everything I suggested did work at least once.

Linux does screw up but it is always tracable to something rational and a
learning experience.

--
In July 2003 a poll of Palestinian refugees found most did not
want to return to Israel. A week later a poll found most Israeli
squatters in the West Bank were willing to leave if compensated.
Both governments are out of touch with the people.
-- The Iron Webmaster, 2794