[Coco] Hard drive trouble

[Bob Devries]

Byte $22 is part of the descriptor name. The last byte of the name always 
has its high bit set, so "1" == $31 becomes $B1

One thing to be aware of is that the names of the settings in the descriptor 
as printed by DMODE may *NOT* be what the driver uses them for. A DNS 
setting for a hard drive is fairly meaningless, so I suspect it is actually 
used for something else.

Questions come to mind:
1. Which driver are you using? (eg, name etc)
2. Do you know that the driver supports multiple drives?
3. Do you have any kind of documentation to help you set it up?

--
Regards, Bob Devries, Dalby, Queensland, Australia

Isaiah 50:4 The sovereign Lord has given me
the capacity to be his spokesman,
so that I know how to help the weary.

website: http://www.home.gil.com.au/~bdevasl
my blog: http://bdevries.invigorated.org/

----- Original Message ----- 
From: "George Ramsower" <georgeramsower at gmail.com>
To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>
Sent: Sunday, April 06, 2008 12:22 PM
Subject: Re: [Coco] Hard drive trouble


> This question is directed to anyone that can help.
>
> I played with this problem for a while, day before yesterday. I created 
> another new boot disk, wth older device descriptors and the result was the 
> same.
> So I compared the device descriptors from various iterations that I have 
> of OS9 in different directories and they all match exactly as they should.
>
> Finally, want to show you a cmp of the h0 and h1 descriptors to see if 
> anyone has a suggestion as to why they both access the same drive. I've 
> tried this on two drives with the same result. I jumpered each drive as 
> h0.... well actually removed the jumper to make them h0. Only one drive in 
> the system each time.
> This is the Kenton SCSI card, Kenton driver. I don't remember where I got 
> the descriptors, but they used to work. I used both drive on this machine 
> and used /h1 as a backup. If I made changes, I don't remember doing so.
>
> Here's a cmp of the descriptors..
>
> OS9[t3]:cmp h0.dd.scsi h1.dd.scsi
>
> Differences
>
> byte      #1 #2
> ========  == ==
> 00000013  00 01
> 00000016  80 81
> 00000022  B0 B1
> 0000002E  03 5C
> 0000002F  C5 D1
> 00000030  D0 B4
>
> Bytes compared:   00000031
> Bytes different:  00000006
>
> Is this the way they are supposed to be?
>
> In byte 016, the 81 gets changed to 80 in operation because it won't work 
> with an 81. That's the DNS setting.
> I'm pretty sure byte 013 is the actual SCSI ID. I have no idea what byte 
> 022 is.
> The last three, I think are CRC stuff. Yes?
>
> George
>
> From: "richec"
>> On Monday 31 March 2008 23:51:09 George Ramsower wrote:
>>> ----- Original Message -----
>>> From: "Christopher Hawks"
>>>
>>> > George Ramsower said the following on 03/31/2008 09:38 PM:
>>> >> Does anyone have an idea why my ST-138N responds to both /h0 and /h1
>>> >> accesses?
>>> >>
>>> >> I was hoping that it was something in my bootfile, so I generated a
>>> >> totally new one and the problem persists.
>>> >
>>> > Check the device descriptors. dmode /h0 and dmode /h1 should give 2
>>> > different drive numbers.
>>>
>>>  That's the reason I made a new boot disk, to see if there was someting 
>>> in
>>> the DD that could have done this. Dmode shows two drives, 0 and 1 so I'm 
>>> at
>>> a loss at this time.
>>
>> This is exactly the same thing I am trying to resolve. I hope to get it
>> resolved at the Fest if not sooner. I am using TC3 with a Cloud-9 SCSI
>> controller. I am currently in discussion with Mark about this.
>>
>
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco