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: <1991Mar22.064048.12805@en.ecn.purdue.edu>
Date: 22 Mar 91 06:40:48 GMT
References: <17727@crdgw1.crd.ge.com> <1991Mar20.220547.4677@en.ecn.purdue.edu> <20023@cbmvax.commodore.com>
Organization: Purdue University Engineering Computer Network
Lines: 62

In article <20023@cbmvax.commodore.com> daveh@cbmvax.commodore.com (Dave Haynie) writes:
>
>Yes    - Got those unit numbers set properly?
>Yes	- Got termination only at the bus ends?  Realizing, of course, that
>	  early A3000s had termination on the motherboard, later ones didn't,
>	  so "I have termination on SCSI drives at either end of the bus" isn't
>	  necessarily the right answer.
>How?	- Got the "Segate" bit set, where appropriate?
>Yes	- Are you sure your cables work?  I probably destroy them more than
>	  the average person, since I'll plug one cable in over and over again
>	  in the lab during system development.  Makes me distrust an arbitrary
>	  cable.
>Maybe	- "SCSI black magic" issues?  I have run into SCSI strangeness, which 
>	  may just be based on the drive types.  Like I said, I'm not the SCSI
>	  wiz around here.  We have a Mac IIcx in the lab which is really testy
>	  about anything properly added or deleted from its SCSI bus.  I have a
>	  100Meg Conner drive that refuses to work together with any Quantum,
>	  but plays just fine with a Sony drive on the bus (well, it did until
>	  I dropped the Sony off my lab bench, the Sony now just makes grinding
>	  noises).  Anyway, there seems to be some bit of mystery (to me at 
>	  least) that's independent of the host adaptor involved.  Fortunately,
>	  it doesn't seem to show up very often.
>
>And for disk speed questions:
>
>Yes	- Got your MASK, MaxTransfer, and Memory Type values set up for the
>	  fastest transfers.
>No	- You aren't using Diskperf, are you!
>??	- You're not running out of Fast memory in that test, are you?

One small thing that I have noticed is that different types of reboots affect
the 2nd HD problem.  
Here are my current symptoms again:
  Cold boot-up:  No 2nd HD recognized.  Both HD's spinup no problem.
   1st warm rb:     2nd HD recognized.
   2nd  "   rb:  Not recognized  
   3rd  "   rb:        "  "
   4th  "   rb:  Not   "  "
   etc .......etc.......etc   forever and forever.......AMEN.

Now does this sound like a sporatic occurence to you?
A glitch?  A borerline timing problem?.....I didn't think so.
I am not saying that it can't be one of these, but it just seems too
coincidental to me.  It acts almost like a switch being turned on and off!

Also, I would like to add that when I reboot after being inside Amax or 
"HDtoolbox" an extra reboot is not required to see HD#2. 
Is this weird or what?
Now if anyone knows what AMY does different between these reboots, then we
might have figured out what our problem is.

Has anyone figured out yet why the 3000 flashes a yellow screen at you 
instead of automaticly rebooting after a crash?  This didn't start occuring
until I added more RAM.  Dave, is this occuring on any of your "maxed-out"
3000's????   Is anyone else having this symptom occur?  I went to the 
trouble of removing my extra memory just to verify this and sure enough
the yellow flashies went away. (it would then auto-reboot after any crash or
"kickreboot", nice pd program!, without yellow screen flashes)
-- 
Art Warner
wwarner@en.ecn.purdue.edu
Amiga makes it happen.......IBM, Mac, Sun, and Next make it expensive!