Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!zaphod.mps.ohio-state.edu!mips!apple!uokmax!servalan!epmooch!ben From: ben@epmooch.UUCP (Rev. Ben A. Mesander) Newsgroups: comp.sys.amiga.hardware Subject: Re: A2091 rev 6.6 ROM announcement Message-ID: Date: 26 Apr 91 17:25:39 GMT References: <8860@ucdavis.ucdavis.edu> Lines: 71 In article greg@travis.cica.indiana.edu (Gregory TRAVIS) writes: Mistaken attribution to: >In <8860@ucdavis.ucdavis.edu> jesup@cbmvax.cbm.commodore.com (Randell Jesup) writes: > >>[ This should get that one guy who keeps griping about his pair ] >>[ of hard drives locking up to quiet down. -Dan ] > >Don't know who you're referring to (could be me) but I think this statement >is totally inappropriate. A lot of loyal Commodore customers have >waited a long time for this. Many, like myself, have been waiting for over >a year for Commodore to fix the problem. Watching our A2091s go out of >warranty while the fix was always something that we "shouldn't worry about, >it'll be along RSN. Trust us." I suggest you unwedge your head from between your cheeks: If you had bothered to read this thread befor flaming, the attribution is mistakenly made to Randall Jesup. You also seem to be a bit paranoid - "They could be talking about me!", or perhaps you have an inflated sense of self worth. >We've waited through official stonewalling and comp.sys.amiga blacklisting. >Commodore didn't even completely 'fess up to the problem till January >of this year. What a way to treat your customers - make them feel >crazy about a problem and when they ask you about it, tell them they're >full of shit. I'm sure that's thier exact words. "You're full of shit." Listen smarty- pants, when I worked in the SCSI drive industry, for Imprimis, on the Wren 5/6/7 product line, we sometimes would get customers complaining about a lockup with our drives. We tried our best to duplicate the problems they had, and to figure out how to fix the problem, even if it was the host's problem, and not the drives. SCSI is a hell of an interface, with lots of strange edge cases. Sometimes we *could* *not* duplicate a customer's problem, no matter how we tried. Commodore has figured out what the problem is now. Who pissed dioxin in your post toasties and made you fly off like this over a mis-attribution? >We've had to put up with a lot of insecurity about who would pay for the >fix and if Commodore would ever come up with a fix. Sometimes it takes *months* of testing to ascertain what set of conditions on a SCSI bus causes a particular problem with what combination of equipment. It is neither trivial nor fast and easy to fix these things. >From the customer's point of view, it's not such a trivial matter to >desire multiple-drive support on the A2091, as was advertised. What's >next, customers "griping" their machines won't boot out of the >box? Apparrently due to a bug in the LSI, it's not such a trivial matter to implement multiple drive support on the A2091 *either*. It's a lot more trivial to "desire" something than to implement something. >Shame on Commodore for the unnecessary disclaimer listed above. This was >a serious problem with Commodore hardware and NOT the fault of the individual >purchasers - or would Commodore rather we just refer to them as >the whiners? You're a pot calling the kettle black. >Gregory R. Travis Indiana University, Bloomington IN 47405 -- | ben@epmooch.UUCP (Ben Mesander) | "Cash is more important than | | ben%servalan.UUCP@uokmax.ecn.uoknor.edu | your mother." - Al Shugart, | | !chinet!uokmax!servalan!epmooch!ben | CEO, Seagate Technologies |