Amiga.org
Amiga computer related discussion => Amiga Hardware Issues and discussion => Topic started by: dwezel on May 24, 2005, 05:43:54 PM
-
I have an Amiga 2000 I am working on with a Vector 030 accelerator in it. The SCSI hardware onboard the Vector uses a driver named IVS_SCSIvector.device. I am trying to put a new 4gig IBM SCSI drive in this unit but having absolutely no luck getting the drive preped. I have OS 3.1, 3.5 and 3.9 and would be willing to use any I can get to work. Currently I am trying to get OS 3.9 working. I have an emergency boot disk for 3.9 which I have copied the IVS_SCSIvector.device drive into the DEVS folder. Once I bootup and launch HDToolbox it lets me select the IVS_SCSIvector.device v4.14 and starts to scan the scsi bus. Problem is it locks up the computer with the message
Found Drive at IVS_SCSIvector.device address 0 LUN 0.
I have tried several time and it always locks up the system at this point. HELP!?!?!?! Please.
-
you should try with the HDToolbox of OS3.9BB2.
Have you tryed to set this Tooltype in HDTB icon?
SCSI_DEVICE_NAME=IVS_SCSIvector.device
-
Had a similar problem with CSPPC and a WD LVD SCSI drive. I had to set the drive to SE mode, no U160 because it wasn't communicating properly with the CSPPC SCSI ( HDToolbox would lock up ).
With 8 bit SCSI devices on the bus, I had to set the CSPPC boot menu settings to 8 bit.
With newer drives and old controllers, it seems that there can be some scsi negotiation issues. Of course you also need to ensure that termination and cable lengths are proper.
-
its quite obvious, that you have to force a LVD to SE!
About the 8 bit thing . . . mhhhh
-
Why do you have to copy IVS_SCSIvector.device to devs: isn't it in ROM? That could be your problem right there.
-
Try OS3.1's HDToolbox and set the tooltypes MAX_LUN and MAX_UNIT both to 0. Later versions don't respect these tooltypes.
Bye,
Thomas
-
The "8 bit thing" is only when my cd burner and cdrom are on the bus. Once I put a 68 bit active terminator on both ends of the bus, I can run reset the boot rom to 16 bit. Otherwise, hdtoolbox would lock up. Drove me nuts... ;)
:insane: :banana: :insane: :banana: :insane: :banana: :insane: :banana: