Newly installed HD not showing in Workbench

[vortexau]

Another potential problem (according to a text file with my Blizzard 2060's Partitioning Util) can exist with much older SCSI drives previously in use with older Amiga SCSI Controllers!

The concept is that MASK and MaxTransfer values used earlier won't match those that a more-modern SCSI Controller uses!!

BTW - the HDInstTools partitioning utility allows those values to be changed ..... and that SAVing the NEWer values (MASK and MaxTransfer) won't usually destroy your data.

 ° In fact, I linked up an older drive recently that had been partitioned with my earlier GVP G-Force 030 Accellerator, and tried to copy its contents over to another Hard Drive partitioned with my present Blizzard 2060 WITHOUT having reset the older drive's MASK and MaxTransfer values!

The result? About 2-5% of the larger graphic files were "rounded down" to 120 000 bytes, and lost their end-of-file markers!

The only way I could salvage some part (the TOP part) of those files was by loading each into The Art Department and Re-SAVing from there.

The values reccommended by HDInstTools were:
 MASK - 0xFFFFFFFF
 MaxTransfer - 0x00FFFFFF

The values that scsiconfig3 is ready to set are:
 MASK - 0xffffffff
 MaxTransfer - 0xffffff
(scsiconfig3 is supplied with the Blizzard 2060)  

[vortexau]

@ QuikSanz

Is your question relating to the use of a Hard Drive previously used on a different Amiga SCSI controller? That's the type of case where this option is the most relevant.

What happens with a drive NOT previously used on an Amiga when partitioning it with a utility such as HDInstTools is that utility gives the values for MASK and MaxTransfer that work best with your SCSI Controller. ie. these values are read FROM your controller.

So, these are the values matched to the controller itself.

When a drive HAS been used on an Amiga before - it already has RDB formatting with the information written to the MIDDLE of each partition - the Amiga Partitioning Tool in use READs the values that were used before (unless I'm wrong here ....? )

Don't go by the values that I quoted - those are the ones pertaining to the Blizzard 2060 Controller that I use!