Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!pacbell.com!ucsd!mvb.saic.com!ncr-sd!serene!cbmami!jason From: jason@cbmami.UUCP (Jason Goldberg) Newsgroups: comp.sys.amiga.hardware Subject: Re: Hardrives and the A3000 Message-ID: <18de57f0.ARN0f78@cbmami.UUCP> Date: 22 Mar 91 22:44:48 GMT References: <1991Mar19.222827.16244@en.ecn.purdue.edu> <17727@crdgw1.crd.ge.com> <1991Mar20.220547.4677@en.ecn.purdue.edu> <20023@cbmvax.commodore.com> Reply-To: jason@cbmami.UUCP Followup-To: comp.sys.amiga.hardware Lines: 62 In article <20023@cbmvax.commodore.com>, Dave Haynie writes: > In article <1991Mar20.220547.4677@en.ecn.purdue.edu> wwarner@en.ecn.purdue.edu (William A Warner) writes: > > >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. > > "The problem", which has been around since the A2091 or so, is a conflict > between the scsi.device and the WC33C93A SCSI controller chip, which causes > reselection to fail. There also seems to be some interrupt timing conflict > in one release of the A2091 ROM; I don't believe that has ever been an issue > on the A3000 release of the scsi.device. [stuff deleted] > -- > Dave Haynie Commodore-Amiga (Amiga 3000) "The Crew That Never Rests" > {uunet|pyramid|rutgers}!cbmvax!daveh PLINK: hazy BIX: hazy > "What works for me might work for you" -Jimmy Buffett Dave, There has to be more to the problems, I have had lockup problems with my A2091 since I first exchanged my slow Segates for Quantums. I definately have reselection turned off on all drives and have proper termination, I can reliable cause the drive to lock-up with either 5.92 ROMS or 6.1 ROMS. There is currently no latter ROM available to dealers! To cause a lockup I need only open two Shells and execute "dir dh0: all" in one and "dir fh0: all" in the other. There is a 50/50 chance this will lock up the system, if it doesn't then repeating the procedure a second time does. After reading your post I replaced my 5.92 ROMS with 6.1 and it made no difference (well actuall it didn't mess up memory location zero any more, but it still locks up). What should I try next? I really want to get this thing working since I have always been happy with CBM products in the past and because I would like to be able to run Unix (which would be a pain if I upgrade to the GVP controller). By whole system is: A2000 rev 4.4 (small upgrade to work with A2630). A2091 WD "A" Proto chip, 5.92 (and 6.1) ROMS A2058 2 Megs A2630 2 Megs A2320 The A2091 has a Quantum 40P on the card and a Quantum105 in the 5 1/4" bay. Everything is properly terminated and I have reselection turned off on both drives (yes, I am sure). Is there something else I should try. Is there someone I can write to, in order to prompt someone to work on this? Should I upgrade to a GVP and hope that GVP writes a driver to link with v2.0 of Unix (the current release will not support external links!). Thanks for any suggestions, keep up the great work! P.S. Which drives/ROMS/WD/etc... do you have in your A2500? -Jason- --------------------------------------------------------------------------- Jason Goldberg UUCP: ucsd!serene!cbmami!jason Del Mar, CA