Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!nntp.coast.net!howland.erols.net!news.mathworks.com!uunet!in1.uu.net!fu-berlin.de!irz401!orion.sax.de!uriah.heep!news From: j@uriah.heep.sax.de (J Wunsch) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: Disk Image Error C:0 H:0 S:0 Date: 5 Oct 1996 17:16:59 GMT Organization: Private BSD site, Dresden Lines: 23 Message-ID: <53656b$ba@uriah.heep.sax.de> References: <324AC540.6C38@pressconnect.com> <32507BB1.3F54BC7E@freebsd.org> <52s72f$sdc@natasha.rmii.com> Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) NNTP-Posting-Host: localhost.heep.sax.de Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: knews 0.9.6 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E jon@xinside.com (Jon Trulson) wrote: > Interestingly enough, I too had this error. So I go over to a > linux box, dd the floppy into a file, format a new floppy, dd the > image onto the new one, and presto - no problemo. Seems strange > that at boot this is an error, yet from linux I can read the drive > just fine.. hmmmm. It's been on another drive. Remember, the boot happens using the BIOS. So your BIOS could not read the floppy on the failing machine. It is not unlikely that the error pattern for a floppy disk varies from drive to drive. In particular, if the Linux box has been the drive where the original floppy has been formatted and/or written, this drive will be the one with the least error probability for this particular floppy. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)