Hi Uniserver,
It is jumpered to 6. I also verified the SCSI number via SCSI Probe. If I use a normal 50 pin cable, the device mounts during start-up (via the SCSIProbe INIT). I can access it as if it were a hard disk (read/write no problems). However I cannot use it to boot the Mac (the driver does not load at start-up). This is not an issue with the device, but rather an issue with the early implementation of SCSI in the Mac Plus ROMs and compatibility with more "modern" SCSI drives. The advice given by the drive developer is to remove the RST function by cutting pin #40 (the problem as I understand it is "reset" is sent to the drive repeatedly before the drive can actually reset thus removing the signal eliminates the problem). However when I use the "modified" cable (wire leading to pin #40 is cut), the drive is no longer recognized. I suspect this is due to the cut wire not being grounded or terminated. If I go back to a normal cable, behavior is as before. So I was wondering if anyone had solved this problem using this device (or other modern drive having same problem).
It is jumpered to 6. I also verified the SCSI number via SCSI Probe. If I use a normal 50 pin cable, the device mounts during start-up (via the SCSIProbe INIT). I can access it as if it were a hard disk (read/write no problems). However I cannot use it to boot the Mac (the driver does not load at start-up). This is not an issue with the device, but rather an issue with the early implementation of SCSI in the Mac Plus ROMs and compatibility with more "modern" SCSI drives. The advice given by the drive developer is to remove the RST function by cutting pin #40 (the problem as I understand it is "reset" is sent to the drive repeatedly before the drive can actually reset thus removing the signal eliminates the problem). However when I use the "modified" cable (wire leading to pin #40 is cut), the drive is no longer recognized. I suspect this is due to the cut wire not being grounded or terminated. If I go back to a normal cable, behavior is as before. So I was wondering if anyone had solved this problem using this device (or other modern drive having same problem).