From owner-freebsd-hackers Thu Aug 12 15:24:35 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from pop3-3.enteract.com (pop3-3.enteract.com [207.229.143.32]) by hub.freebsd.org (Postfix) with SMTP id 36CF314D48 for ; Thu, 12 Aug 1999 15:24:31 -0700 (PDT) (envelope-from dscheidt@enteract.com) Received: (qmail 89458 invoked from network); 12 Aug 1999 22:24:13 -0000 Received: from shell-3.enteract.com (dscheidt@207.229.143.42) by pop3-3.enteract.com with SMTP; 12 Aug 1999 22:24:13 -0000 Date: Thu, 12 Aug 1999 17:24:13 -0500 (CDT) From: David Scheidt To: Peter Jeremy Cc: hackers@FreeBSD.ORG Subject: Re: SETI@home bug? In-Reply-To: <99Aug13.075021est.40332@border.alcanet.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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