[Coco] Hard drive trouble

[Bob Devries]

I your second drive doesn't work, even though it appears to be selected 
(i.e. the select LED goes on), I'd say there's a hardware problem.

I'm going to assume the LED isn't always on, but just when you try to access 
the drive.

Do you have the termination resistors in the second drive when you're using 
it by itself?

If the second drive (H1) is the last drive when you're using the two 
together, then H0 should have no termination resistors.

Are the termination resistors installed the correct way 'round?

Have you changed the SCSI address on the drive when you try to use the 
drives separately, and do you have them set at two different addresses when 
you use them together?

My Quantum drives have three other jumpers, one of which is EP (Enable 
Parity). None of these are jumpered.

I have my H0 drive jumpered at SCSI address 0 and the H1 drive at SCSI 
address 1. That is, No jumpers on A0, A1, A2 on drive H0, and a jumper on A0 
on drive H1.

--
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 1:58 PM
Subject: Re: [Coco] Hard drive trouble


> As I was exploring around my hard drive and the floppies of this stuff, I 
> just discovered this fact about the same time this 'puter went DingDong on 
> your message.
> .
> I remember now that I'm using 512 byte sectors and the driver to do 
> so(SCSISYS). I believe that's what I did, replaced the KenTon driver with 
> the SCSISYS driver and set it all up for 512 byte sectors. It's "supposed" 
> to give more storage space, but I never needed it. I got greedy.
> Right now, I'm trying to find the source of SCSISYS. So far, I haven't.
>
> Anyway, can this make my problem appear several years later?
>
> I can't go back to 128 byte sectors until I can fix this problem I'm now 
> having.
>
> Like I said earlier, it used to work fine with two drives using everything 
> I'm now using unless I did something that I don't remember. I've been 
> using this setup for many years.
>
>
>
> ----- Original Message ----- 
> From: "Bob Devries"
>
>
>>I notice you're using SCSISYS. That driver should have a program with it 
>>to create the descriptors for you. (DescGen???) I have a disk image of the 
>>SCSISYS disk here somewhere, if you need it.
>> For this to work, the driver *MUST* be called SCSISYS
>
> It came with... I think.... ScsiSys  Scsidesc   Scsifmt
>
> I recall using those a LONG time ago.. Scsifmt is what I used to reformat 
> my second drive when I discovered it was broke.
> However, I'm not so sure it's really broke. I think something in my system 
> messed it up as there is that conflict with addressing the /h0 drive and 
> the /h1 drive at the same time.
> What's wierd is that my primary drive is working fine. No lost files or 
> problems at all. It's just that when I try to access /h1, the /h0 drive 
> appears in it's place, even if the second drive is on the cable.
> If I put the second drive online all by itself, it too responds to /h0 and 
> /h1, even though it doesn't work, the drive light still lights up.
>
>
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco