From owner-freebsd-hackers Thu Aug 12 15:13:38 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with SMTP id 4A366155D5 for ; Thu, 12 Aug 1999 15:13:22 -0700 (PDT) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <40332>; Fri, 13 Aug 1999 07:50:21 +1000 Date: Fri, 13 Aug 1999 08:09:47 +1000 From: Peter Jeremy Subject: SETI@home bug? To: hackers@FreeBSD.ORG Message-Id: <99Aug13.075021est.40332@border.alcanet.com.au> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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. (I've found a similar problem with the alpha-osf versions, so it seems to be a problem with the SETI@home server, rather than the FreeBSD client). Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message