Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!samsung!noose.ecn.purdue.edu!en.ecn.purdue.edu!wwarner From: wwarner@en.ecn.purdue.edu (William A Warner) Newsgroups: comp.sys.amiga.hardware Subject: Re: Hardrives and the A3000 Message-ID: <1991Mar20.220547.4677@en.ecn.purdue.edu> Date: 20 Mar 91 22:05:47 GMT References: <1991Mar19.222827.16244@en.ecn.purdue.edu> <17727@crdgw1.crd.ge.com> Organization: Purdue University Engineering Computer Network Lines: 69 >Notice: This article contains what may seem to be a flame. As I >don't wish to alarm you, there is also an explanation of why the >flame started in the first place. I thought about deleting it >and just sending off the rational part, but it doesn't make the >point quite as plainly. Read with a grain (nay, a slab) of salt. >#define HARSH_WORDS_AHEAD >OK "Mr. I know troubleshooting procedures thoroughly", what's >the common denominator? If you have 25 cases, then you ought to Mr. "know-it-all" here to report that the 25 cases that I recieved included only the fact that they too were having the same proble with a 3000 and various 2nd HDrives. I realize that the more info that you have, the better you can diagnose the problem, but unfortunately I have only my own specs to give you. I will get them to you ASAP. I apologize if I seemed to be flaming, but I am just frustrated with the HD problem and some of the idiotic questions/suggestions that I have been receiving from some people. (ie. Did you format the drive?.....No, I just happen to be accessing/using it every other reboot through the mystery of trons!) Sorry, I digress. >have enough info to tell us that, and to solve the problem, >instead of griping about how Commodore has their heads wedged. >Have you at least sent this compilation of problems to >"bugs@cbmvax"? Yes, Yes and Yes. I have written them, called them (phone bill to prove it, and e-mailed them (several times over) and posted. I will have to say that they "seem" concerned. I got e-mail from 3 C= reps, including Dave H. They are aware of the problem and have been since the release of the 2091. >Are you, in fact, trying to solve this, or are >you just trying to be a squeaky wheel and make someone else do >the work? I have noticed that the squeaky wheel usually gets greased first. By your correspondence, this seems to hold true. Would you have responded, if you never heard it? >don't feel like doing the skull work yourself, pass it off to me >and I'll be glad to collate it and try to find the LCD. Just do >your cause a favor and stop screaming your head off without >providing any more useful info than "It's broken and those nasty >people at Commodore can't read my mind and my system config long >distance over the network and fix it!" >we need to apply a little less Chicken Little and a little more >scientific method to this problem. My 3000 specs will be "in the mail" to you ASAP. Again, I apologize for any apparent "flaming" on my part and we would appreciate any help that you could give us. Thank-you. PS: who knows....maybe even a "know-it-all" like myself can still learn a few tricks. BTW: Passeretti: I tried to e-mail you, but your address doesn't seem to work. I tried both addresses in your post. I hate posting something that could be e-mailed. -- Art Warner wwarner@en.ecn.purdue.edu Amiga makes it happen.......IBM, Mac, Sun, and Next make it expensive!