Amiga.org
Amiga computer related discussion => Amiga Hardware Issues and discussion => Topic started by: xaccrocheur on March 28, 2003, 11:02:15 AM
-
.. Or is it me ?
I only have one Zorro board in this A4K (Moe is her name) and the bootmenu (both mouse buttons @ startup), when I click on "Expansion Board Diagnostic", lists me two !
'Board #' 'Manuf.' 'Product' 'Status'
'1' '2017' '11' 'Working'
'2' '2017' '10' 'Working'
Weird, huh ? I *do* have a Board, a GVP HC+8 Ser. II Rev. II, I suppose it's this one, but why two ? Why the numbers 11 & 10 ?
It may have something to do 8-) with the problems I'm experiencing with this Scuzzy chain. Namely, I cannot get HDToolBox (the 3.9 version) to even consider my Seagate ST HAWK (http://www.seagate.com/cgi-bin/view.cgi?/scsi/st15230n.txt)
and I'm quite used to fiddle w/ Scuzzy LUNs and chain terminations. Just any combination have been tried.... Oh, and the disk *is* working, It comes from a SCO server who used it not very long, it was operating when I removed it.
The rest of the chain is fine, thanks, the Conner 500 Mg HD and the TEAC X16 CD-Rom work almost flawlessly, wether the chain is terminated (a jumper on the Teac) or NOT ! :-o :-? :-o
But what the heck with HDT ? Does it have to do with the fact that I did not install the BBags 1&2 yet ?
What does it mean "this type of drive cannot be handled by HDT", should I hunt for a 3rd-party driver ?
For a *hard drive* ? Or does it just mean that my SCSI chain sucks and it won't look at it until it's proper ? I'd rather that much better.
Please help me understand ! And finally *close* the 4000 case, opened since the ROM switch :-[ And I have *another* SCSI drive to add, not to mention the (well, possible) external chain !
pX
-
My bet is that scsi-controller and memory expansion on the card are handled as separate units and that's why it shows two boards. I had some older gvp scsi-controller with 2M memory and it did the same thing. Although I have never used it because it doesn't support rdb :P (but your card does).
To hd problem I can't say much... maybe it's just that old scsi-controller that it has some problems with bigger and newer devices or something :) SCSI-bus may work without termination with small amount of devices on it, but anyway it's best to use termination.
-
Hi
There is nothing wrong with your A4K or the boot menu !!
The GVP HC+8 is actually 2 Zorro cards in one,
One Hard disc controler and one Memory expansion
on one card...
Have fun..
-
OK, that makes sense.
The two units in one is a logical enough explaination for the bootmenu.
But what the HELL about HDT *refusing* to handle my Seagate drive ?? Huh ?
Another quick one : What is "mounter" for ? After scanning "devices", It currently lists me 7 units from 0 to 6, *all* identical exept for the ID # :
Type Media Status
0 Fixed Not Ready
All other collumns (product, rev. size) are empty.
If it's a SCSI listing utility, why does'nt it seen even the boot HD ?? And the CDR ?:-? :-o :-?
Thank you 4 your help
pX
-
Just asking: do you have gvpscsi.device or a later version entered into the Tooltypes of HDToolBox and Mounter?
My HDToolBox uses the VALUE NAME of SCSI_DEVICE_NAME=, and the version of Mounter I'm using for GVP uses the VALUE NAME of DEVICE=.
Some SCSI Controllers own Partitioning Apps may work better than HDToolBox with their own SCSI Standards. With my GVP ones with original ROMs I've used FaaastPrep, and I use scsiconfig3 with my Blizzard 2060.
As to Mounter, my own scanning my Blizzard 2060 Controller is shown....
(http://home.iprimus.com.au/vortexau/images2/Mounter.jpg)
As can be seen, both Removable Media and unused IDs show the same Status when no removable Disk/c is present.
In similar fashion, Media shows the same result for Fixed Media as for unused IDs.
-
It may have something to do with the problems I'm experiencing with this Scuzzy chain. Namely, I cannot get HDToolBox (the 3.9 version) to even consider my Seagate ST HAWK
and I'm quite used to fiddle w/ Scuzzy LUNs and chain terminations. Just any combination have been tried.... Oh, and the disk *is* working, It comes from a SCO server who used it not very long, it was operating when I removed it.
the HAWK was a nice drive... almost silent!!!