Return to BSD News archive
Newsgroups: comp.unix.bsd Path: sserve!manuel!munnari.oz.au!newsroom.utas.edu.au!bruny.cc.utas.edu.au!u906400 From: u906400@bruny.cc.utas.edu.au (Roger Scott) Subject: Re: Corrupt 386bsd files Message-ID: <u906400.711419185@bruny> Keywords: 386BSD binary corrupt Sender: news@newsroom.utas.edu.au Organization: University of Tasmania, Australia. References: <u906400.711393959@bruny> Distribution: aus Date: Sat, 18 Jul 1992 00:26:25 GMT Lines: 13 u906400@bruny.cc.utas.edu.au (Roger Scott) writes: >Has anybody else had trouble with bin01.16 and bin01.37? I have three >copies from two different sources (kirk.bu.oz.au & gatekeeper.dec.com) and >extract complains about them all being corrupt. I appear to have some sort of drive problems which newfs doesn't pick up. I had to rename the original copies on the HD so I could place the files on a different physical part of the disk. It appears to be going now, although I'm not sure what's going to happen when I hit the bad spots again. Roger.