From owner-freebsd-questions Wed Aug 14 20:02:07 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id UAA17699 for questions-outgoing; Wed, 14 Aug 1996 20:02:07 -0700 (PDT) Received: from atlantis.nconnect.net (root@atlantis.nconnect.net [206.54.227.6]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id UAA17694 for ; Wed, 14 Aug 1996 20:02:04 -0700 (PDT) Received: from apollo.nconnect.net (dial190.nconnect.net [206.54.227.190]) by atlantis.nconnect.net (8.7.3/8.7.3) with ESMTP id WAA15571; Wed, 14 Aug 1996 22:00:02 -0500 (CDT) Message-Id: <199608150300.WAA15571@atlantis.nconnect.net> From: "Randall D. DuCharme" To: Cc: Subject: Re: Write failure on transfer! -1 bytes of 10240 bytes) Date: Wed, 14 Aug 1996 22:00:37 -0500 X-MSMail-Priority: Normal X-Priority: 3 X-Mailer: Microsoft Internet Mail 4.70.1141 MIME-Version: 1.0 Content-Type: text/plain; charset=Default Content-Transfer-Encoding: 7bit Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > From: shegonee@ix.netcom.com > To: questions@freebsd.org > Subject: Write failure on transfer! -1 bytes of 10240 bytes) > Date: Wednesday, August 14, 1996 8:41 PM > > What does that mean: > Write failure on transfer! -1 bytes of 10240 bytes) > I am trying to install FreeBSD from the Walnut Creek CD-Rom on a new > 1 gig drive on my Pentium. Ine install program creates the partions then > bombs out with this message when it start st unzip the files. > Can you give me a list of possible reasons why this might happen? > I look through the FAQ - a few people have reported this problem > but I couldn't any answers. > Thanks > Kirk :) > > Greetings, I've encountered this same problem on 3 different occasions, each time the cause was different. 1) Drive geometry problem a: corrected problem by first partitioning and formatting the disk with DOS, then b: installing from FBSD distribution, thus deleting the DOS partition 2) Bad Cache a: disable, remove, or replace cache memory 3) SCSI Termination a: I had incorrectly terminated my SCSI bus. Correcting this error corrected the problem. Hope this helps Randy