Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 12 Aug 1999 17:24:13 -0500 (CDT)
From:      David Scheidt <dscheidt@enteract.com>
To:        Peter Jeremy <jeremyp@gsmx07.alcatel.com.au>
Cc:        hackers@FreeBSD.ORG
Subject:   Re: SETI@home bug?
Message-ID:  <Pine.NEB.3.96.990812172206.6865B-100000@shell-3.enteract.com>
In-Reply-To: <99Aug13.075021est.40332@border.alcanet.com.au>

next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 13 Aug 1999, Peter Jeremy wrote:

> I've been attempting to run SETI@home on -current.  Has anyone else
> found that both setiathome-1.1.i386-unknown-freebsd4.0 and
> setiathome-1.2.i386-unknown-freebsd3.2 fail with the following
> message after downloading a work unit:
> 
> Scanning data file
> Error reading data: -23
> Bad file header
> 
> The same work unit works with setiathome-1.3.i386-unknown-freebsd2.2.8.

You are working through a proxy?  Versions prior to 1.3 didn't deal well
with some proxies.  I don't know the details, but some proxies re-write data
in a form that Seti@home  won't deal with.

David



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.NEB.3.96.990812172206.6865B-100000>