CompuServe Thread

2090A & Quantum 105S

8 messages in this thread
#109869From: Sam ReynoldsJun 24, 1990 12:59 PM
Anyone, HHHHHEEEEELLLLPPPP!!!!! I just bought a Quantum Pro Drive 105S and I already have a 2090A controller card and I'm having trouble making them talk. The controller doesn't seem to recognize the drive. I've tried several different configurations for the mountlist entry but none seem to work. Th either fails immediately or fails after about a minute (with the rive light barely flickering) I hooked the drive up to a 2091 and preped, partitioned and formatted it with no prob, but with my 2090A its just not happening. It's the only drive I have hooked up to the board but I'm at the end of my rope . BTW the jumpers on the drive (bot that I know what they mean…) are set to the following: S E W A A A S P S 2 1 0 : I : I I : Any assistance would be GREATLY appriciated!!!!! Sam Reynolds
#110050From: John GagerJun 25, 1990 11:56 PM
Sam, you might upload your Mountlist and I will take a look at it for you. When I received my 105S I had a heck of a time getting it to work with my 2090 until I changed the Unit number in my Mountlist entry to 9. Apparently it came from the factory set up as unit 7 in a SCSI chain. John Gager
#110089From: Sam ReynoldsJun 26, 1990 7:28 AM
John, Thanks for the help. The drive is set to SCSI ID 0 no Parity (ie ALl jumpers on the drive are off). Heres My MountList: RES2: Device = hddisk.device Unit = 2 Flags = 0 Surfaces = 6 BlocksPerTrack = 32 Reserved = 2 LowCyl = 0 ; HighCyl = 1 Buffers = 1 BufMemType = 0 # P2: Device = hddisk.device Unit = 2 Flags = 0 Surfaces = 6 BlocksPerTrack = 32 FileSystem = l:FastFileSystem Reserved = 2 LowCyl = 2 HighCyl = 1018 Buffers = 30 GlobVec = -1 BuffMemType = 0 DosType=0x444F5301 # Any further help you would be able to offer would be greatly appriciated!!! (BTW: I don;t know if it was clear from my first message, but the drive won't even PREP) :^( -Sam
#110163From: John GagerJun 27, 1990 12:37 AM
Sam, probably the major problem in not getting your drive to Prep was using a Unit number of 2 in your mountlist. SCSI drives use unit numbers of 3-9 while ST-506 drives use unit numbers of 1 and 2. Also in the AmigaDos 1.3 manual it states that the first partition must be a auto-mounted normal file system partition (DH2:). Here is the mountlist that I would try: RES2: Device = hddisk.device Unit = 3 Flags = 0 Surfaces = 6 BlocksPerTrack = 32 Reserved = 2 Interleave = 0 LowCyl = 0 ; HighCyl = 1 Buffers = 1 BufMemType = 0 # DH2: Device = hddisk.device Unit = 3 Flags = 0 Surfaces = 6 BlocksPerTrack = 32 Reserved = 2 Interleave = 0 LowCyl = 2 ; HighCyl = 3 Buffers = 1 BufMemType = 0 # P2: Device = hddisk.device Unit = 3 Flags = 0 Surfaces = 6 BlocksPerTrack = 32 FileSystem = l:FastFileSystem Reserved = 2 Interleave = 0 LowCyl = 4 ; HighCyl = 1018 Buffers = 30 Stacksize = 4000 GlobVec = -1 BufMemType = 0 DosType=0x444F5301 # Hope this helps out and gets you up and running! John Gager
#110053From: Don Curtis/SYSOPJun 26, 1990 12:16 AM
Sam, Try removing all the jumpers. The EP jumper is "Enable Parity" and the 2090 series can't handle this. Also, the first drive should be SCSI ID of 0 (although that's not absolutly necessary…it's a good idea) so the 'A' jumpers should all be out. Don
#110054From: Don Curtis/SYSOPJun 26, 1990 12:18 AM
Sam, Oh…by the way, on the A2090, SCSI ID 0 would be UNIT 2. Don
#110090From: Sam ReynoldsJun 26, 1990 7:30 AM
DOn, I tried what you said and it still doesn't work. I left my MountList in a message reply to #110050 from John Gager. If you could take a look and see if anything looks wrong I'd appriciate it! Thanks! -Sam
#110149From: Don Curtis/SYSOPJun 26, 1990 11:53 PM
Sam, Well…the next thing to check is the cable…this presumes the drive is known to be a good drive. Make sure the cable is properly oriented (pin 1 is going to the right place) and properly connected. Don