A500 + SupraXP hdd problem

[mrtabaka]

Hello,
I have problem with my SupraXP connected to A500. With FAST all is ok, in early starup (I tried ROM 2.04 and 3.1) all is Working and OK, in WB when I try HDTOOLBOX wit suprascsi.device I have to wait long time and later I see some device an ALL ID and LUN..?..HDD is ok,I checked on PC..what is wrong?
Regards

[c64_d0c]

hd slowly dying...
________
Lovely Wendie

[mrtabaka]

It's old Quantum 110mb, I tried with other old Qunatum 40mb and the same. But on PC hdd is working good? I will try other hdd maybe..

[Xanxi]

Look like SCSI termination trouble.

[mrtabaka]

I use external termitor which I think is good (I tested it),maybe I have to find SupraHDTool, because hdtoolbox don't like it?

[Ral-Clan]

Check and see what version of the ROM you have installed in the Supra controller card in the 500XP.  You have to look for a sticker on the ROM chip which will say AMAB#.  The old versions of the ROM have problems with other hard-drives and newer versions of Workbench.  You need the latest version (there was someone on Ebay selling the latest ROMs for $15US about 6 months ago, I bought mine then and am now running WB2.1 no problem).  I think the drive installed is a 105MB Quantum.  Before the new ROM was installed, it would not recognise all the partitions, now it does. With the AMAB6 ROM chip installed, I can use the HDtools included in Workbench 2.1 without problems.

The chip is IC9 located under the internal hard drive.

The new ROM also helps with using multiple SCSI devices, CD-ROMs and processor cards.  I wouldn't be surprised if you have version AMAB4, which could possibly also give trouble with later versions of Workbench (beyond 1.3).

http://amiga.resource.cx/exp/supra500xp

From and old message on Usenet:

"If the rom is labeled AmaB6 the supra controller will support large hard drives and Cd-Rom drives. If it is labeled AmaB5 there is no Cd-Rom drive support and if it is labeled AmaB4 or earlier there is no large hard drive support.

and from another:

"According to the Supra Faxback Document 1501 dated 4/24/96, the current version of the autoboot ROM is "AMAB6". The document also says that the "AMAB6" ROM is required for use with Workbench 2.0x and above."

Let us know which version you have.

[keropi]

Can someone please provide an image of the AMAB6 ROM

[mrtabaka]

I have AMAB6 Rom, I used checkrom from supra floppy and version is AMAB6, autoboot 3.8, all is ok, but when I try suprahdtool there is nothing:(((

No device found:(

[mrtabaka]

I have AMAB6 Rom, I used checkrom from supra floppy and version is AMAB6, autoboot 3.8, all is ok, but when I try suprahdtool there is nothing:(((

No device found:(

[Tenacious]

I've had probs with the new versions of HDtoolBox.  Can't remember the details.  Try several versions of the utility.

[AmiGuille]

I think the problem is not the terminator. In a SCSI system, HDToolBox looking for 8 possible attached devices. If the controller is slow, then HDToolBox can need a lot of time to checks all IDs.

[mrtabaka]

In HDTool box after loong time I have HDD on every ID and LUN!,but I can't format it etc. SupraHDTool doesn't see HD:(

ON PC HD works.

[alewis]

What ID is the HD set to?  Check it is NOT set to 7 (the Supra controller is /probably/ set to that.

Assuming you only have the hard disk on the controller, check that the drive itself is terminated, and remove the external terminator. Ensure that the controller is supplying term power. If the docs do not state that it does, set the TERMPWR jumper on the drive. If both controller and drive are supplying term power, this shouldnt be a problem.

ISTR the Supra uses a 25pin external "SCSI" connector. This is an abortion of a connector, and is non-standard: for example, it ties most of the ground pins together... allegedly.

Check the controller itself is terminated. This is NOT the external terminator on the rear port, but should be inside the case itself. A SCSI bus must be terminated at each end.

Check cabling is fully inserted into the sockets on both the controller, and the drive. Have a good gander at the cable, and check for any damage, check sockets for bent pins, and reseat cable.

On the Amiga, double check the spelling of the device driver in device= in the supra software .info file, and check this matches the device driver in Devs:

Hard boot, and post results; eliminate potential issues from the wire up.