#A3000 & IBM Hard Disc.
4 messages in this thread
A3000 & IBM Hard disc problem
I have just been given an IBM WDS3100 100Mb SCSI hard drive by a friend.
The hard drive came from an IBM PS2, and has OS/2 installed on it. I
already have a Quantum LP52S in my A3000 and had a Quantum Pro 40 in the
second bay. I want to replace the Pro 40 with the IBM. I removed the
Pro 40. Rebooted and ran HDToolbox to inform the system of the removal
of the old drive. Set the IBM drive to SCSI ID 6 (the same as the old
Pro 40) and installed it. Restarted the machine, and when I run
HDToolbox, it locks up when trying to access SCSI ID 6. I have tried
various other SCSI IDs but if I choose anything other than 6 the machine
refuses to boot at all. I have also tried putting the two drives on the
two possible SCSI connectors and terminating one, the other and both with
no change whatsoever. I have looked at the Quantum drives and both have
two sets of jumper blocks, one marked A0, A1, A2 for the SCSI ID, and one
marked WS, EP, SS, which I have no idea of the function (both drives are
set on EP). The IBM drive has just one jumper block marked, X X M X 3 2
1. The 3,2,1 jumpers are for SCSI ID, The M jumper is default closed,
and if removed the drive doesn`t even power up, and the other three
(Marked X) are default open and I presume have no function.
Has anybody else encountered this problem or a similar one, or does
anyone currently have an IBM WDS3100 working in an A3000 ? If I am doing
something stupid I would appreciate any pointers to overcome this most
annoying problem.
Thanks in advance.
Paul Gregory.
Paul,
FYI
EP = Parity Checking. Off = disabled ON= Enabled
WS = Wait/Spin (Drive motor power is applied when system power is applied
to the computer.)
SS = Self Seek Test (factory use only) should be OFF
Christopher
Gregory
Not sure if this is exactly the same but I did have some experience last
year with another IBM PS/2 drive that acted like yours does. HD toolbox
was able to format those drives but we had great problems with them on GVP
controllers and some Amigas never could use them.
May not be something you are doing, just way the roms are programmed on
that drive. On GVP it helped us to disconnect and reconnect the drives on
some machines, might try that. I don't know the command on a 2091 CBM
controller like the 3000, it is "gvpscsicntrl -r 6 DCOFF" for a GVP
controller. Not much help, I know.
Tom
alternate: jonest@hfsi.com
I never met a man I didn't like…Will Rogers
Paul,
While I have no experience with the 3000, SCSI in general requires proper
termination to work right. A simple qeustion to ask is was this the only
device on the SCSI bus in your friends' machine? If so, then it has a
terminating resistor installed on it somewhere that should be removed.
The reason for this is that the A3K you have has several devices on it already.
One of them will have termination on it. The erratic behavior you described is
pretty typical for an incorrectly terminated SCSI bus. You probably have three
terminators with that new drive in place: Once on the controller card, one on
this drive and another on the last device on the SCSI bus.
You did right by changing the termination, but maybe a quick diagram of the
devices that were terminated in each case would help in figuring this out.
–Gabe