Path: utzoo!attcan!uunet!cs.utexas.edu!wuarchive!decwrl!shlump.nac.dec.com!mountn.dec.com!memit!shatara From: shatara@memit.enet.dec.com (Chris Shatara) Newsgroups: comp.sys.apple Subject: Re: GS/OS SCSI questions Message-ID: <1232@mountn.dec.com> Date: 12 Jan 90 14:03:44 GMT Sender: news@mountn.dec.com Organization: Digital Equipment Corporation Lines: 56 In article , joseph@elbereth.rutgers.edu (Seymour Joseph) writes... > > >I called Claris tech support today. I spoke with Ellen who made an >alarming statement: > >"Yes, we are having problems reported with some SCSI drives. There >are bugs in the current versions of the GS/OS SCSI manager that can >cause data corruption. We feel that it's not our problem, it's >Apple's They are working on a fix but we don't know when it will be >available." > I had similar problems. What I found was that I could copy AWGS using prosel and got a good copy and all worked fine. When I used the installer or finder, strange things would happen. I sent a set of disks to Dave Lyons at DTS with AWGS on them copied with PROSEL and Finder. The following represents the response I got from Dave this morning. This may help. I've had NO problems with AWGS since I copied it onto the hard disk with Prosel, and I've been using the all the modules quite hard. ----------------------- note from Dave Lyons ---------------------- From: MEMIT::DECWRL::"dlyons@apple.com" 12-JAN-1990 01:03:04.67 To: shatara@memit.enet.dec.com CC: Subj: damaged AppleWorks GS copies Chris, Thanks for your help in tracking down the problem with damaged copied files under GS/OS. It turns out there is a bug in the SCSI.Manager (in 5.0.2 and 5.0) that can show up in the following situation: a large write (but not a read) is being performed on more than 64K of data at a time, and the data includes one entire 64K bank plus some data in the next -and- previous banks. The bug will be fixed at our next opportunity; for now users can use the 4.0 SCSI.DRIVER for copying large files (or, of course, use any utility that does not seem affected by the bug). (Note that it's -not- a Finder bug...the APW Duplicate command can also create a bad copy, for example.) I haven't investigated why ProSel isn't affected; it may simply not read data in large enough chunks to get bitten. --Dave (dlyons@apple.com) ---------------------------- end of message ------------------------ ============================================================================= | Chris Shatara | Internet: shatara@memit.enet.dec.com | | Opinions expressed are | DEC Easynet: memit::shatara | | mine and mine only! | UUCP: ...!decwrl!memit!shatara | =============================================================================