Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!news.mira.net.au!news.netspace.net.au!news.mel.connect.com.au!munnari.OZ.AU!news.ecn.uoknor.edu!feed1.news.erols.com!worldnet.att.net!news.bbnplanet.com!cpk-news-hub1.bbnplanet.com!mindspring!uunet!in3.uu.net!192.233.85.167!shore!news From: Robert Withrow <witr@rwwa.com> Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: ATAPI CDROM -- Any progress made in 2.1.6 Date: Sun, 26 Jan 1997 17:39:19 -0500 Organization: R.W. Withrow Associates Lines: 25 Message-ID: <32EBDD17.41C67EA6@rwwa.com> References: <32EAB13C.41C67EA6@rwwa.com> NNTP-Posting-Host: rwwa.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.1.5-RELEASE i386) Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:34503 This was ``any progress made'' I've discovered an interresting new problem with ATAPI cdroms on my 2.1.5 P6-200 (VS440FX) system: Corrupted data when reading large files from CDROMS. I have tried two different CDROM drives (a Toshiba 4x and a Creative 8x) and both get, for example, MD5 checksum mismatches for the files on the 2.1.5 cdrom (and different values for the checksum each time I mount and dismount the cdrom). If I read the cdrom with W95 I get good data. I'm hesitant to blame the hardware, since I tried two different CDROMS with two different cables, and since both IDE channels are on the same chip, and FreeBSD isn't having any problems with the hard drives on the other channel, and since W95 can read the files (much faster than FreeBSD, btw). This smells like a bug in the driver code, or the file system. Any ideas? -- ----------------------------------------------------------------------------- Robert Withrow, Tel: +1 617 592 8935, Net: witr@rwwa.COM