home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!cis.ohio-state.edu!rutgers!cmcl2!acf3!chapman
- From: chapman@acf3.NYU.EDU (Gary W. Chapman, , , )
- Newsgroups: comp.unix.bsd
- Subject: Re: [386BSD] corrupt files
- Message-ID: <56750002@acf3.NYU.EDU>
- Date: 7 Jan 93 03:57:00 GMT
- References: <56750001@acf3.NYU.EDU>
- Sender: notes@cmcl2.nyu.edu (Notes Person)
- Organization: New York University
- Lines: 12
- Nntp-Posting-Host: acf3.nyu.edu
-
- >>bin01.02 is corrupt
- >>bin01.03 is corrupt
- >>
- >>when doing 'extract'. What can I do?
-
- > They may not actually be corrupt! I had this problem (with different
- > bin01.xx files) and it was caused by the kernel from dist.fs not
- > reporting errors on my ESDI drives. I resolved this problem by getting
-
- Yes, I believe that was it (although to tell you the truth I haven't
- bothered to figure out if I have ESDI, or other. It's a measy Hertz '386
- from about 1988 with ~80 mb drive). Many hours wasted!
-