Hi!
I'm hoping a guru here can help! I'm trying to setup a couple of SCSI HDD's for a friend, I'm not great with SCSI but I said I'd try and help as they've not been to get them up and running.
Of the two drives the first is an UW SCSI Drive, 68pin so ideal to hook up to a CSMkIII. If I add this drive to my SCSI chain my Amiga 4000 wont boot any more, it gets stuck in a reboot loop trying to boot from this drive and I can't even access the early startup menu (holding two mouse buttons does nothing)
I have tried setting an IDE device (on the A4000 IDE) and my other SCSI drive to a higher priority so they boot first but then it boots up with Dos errors and cannot load Workbench. I find it weird how a drive can corrupt other drives? If I disconnect it my other drives work fine :dry:
I've checked that the ID isn't conflicting and even tried other ID's and my SCSI chain is correctly terminated, I have Active terminators before the MkIII and at the end of the chain.
Any idea's?
The second drive is a 50gb Seagate Baracuda with 80pin connector. I have used an 80pin to UW SCSI connector and my system boots as normal and I can see it in HDToolBox as 'Unknown' but HDTools tells me it cannot handle this drive type, the same story with HDInstTools. I checked ID jumpers again to no avail? Also this drive makes some nasty clunking noises when spinning up so maybe it's actually faulty? Or maybe there is a problem or special setting I need on the on the adapter?
Any Idea's?
I was able to successfully configure one of my own spare UW SCSI Drives for my friend so all isn't lost, they're still getting a fully working drive for their A4000 but I'm just stumped by these two.
When I connected my own drive as the second SCSI drive I was able to prepare it in HDToolBox with SFS no problems and install CWB3.9 from a System.zip I created, in fact it was really fast to setup from my Deneb USB! Almost WinUAE speeds
So I guess I'm doing right so maybe these other drives are just faulty?
Thanks in advance!
Steve.
I'm hoping a guru here can help! I'm trying to setup a couple of SCSI HDD's for a friend, I'm not great with SCSI but I said I'd try and help as they've not been to get them up and running.
Of the two drives the first is an UW SCSI Drive, 68pin so ideal to hook up to a CSMkIII. If I add this drive to my SCSI chain my Amiga 4000 wont boot any more, it gets stuck in a reboot loop trying to boot from this drive and I can't even access the early startup menu (holding two mouse buttons does nothing)
I have tried setting an IDE device (on the A4000 IDE) and my other SCSI drive to a higher priority so they boot first but then it boots up with Dos errors and cannot load Workbench. I find it weird how a drive can corrupt other drives? If I disconnect it my other drives work fine :dry:
I've checked that the ID isn't conflicting and even tried other ID's and my SCSI chain is correctly terminated, I have Active terminators before the MkIII and at the end of the chain.
Any idea's?
The second drive is a 50gb Seagate Baracuda with 80pin connector. I have used an 80pin to UW SCSI connector and my system boots as normal and I can see it in HDToolBox as 'Unknown' but HDTools tells me it cannot handle this drive type, the same story with HDInstTools. I checked ID jumpers again to no avail? Also this drive makes some nasty clunking noises when spinning up so maybe it's actually faulty? Or maybe there is a problem or special setting I need on the on the adapter?
Any Idea's?
I was able to successfully configure one of my own spare UW SCSI Drives for my friend so all isn't lost, they're still getting a fully working drive for their A4000 but I'm just stumped by these two.
When I connected my own drive as the second SCSI drive I was able to prepare it in HDToolBox with SFS no problems and install CWB3.9 from a System.zip I created, in fact it was really fast to setup from my Deneb USB! Almost WinUAE speeds
So I guess I'm doing right so maybe these other drives are just faulty?
Thanks in advance!
Steve.