»

[Miloo]

Ive borrowed a 80 pin sca scsi drive with os3.9 with 060 libs etc installed.

There is a 68 to 80 pin adapter and i set the id to 0, when i go into the csppc scsi menu nothing is detected, the hd led does even light up but I can hear the hd spin up at turn on. And so i cant get it to boot.

What am I doing wrong?

[Reynolds]

Have you set termination to be active?
on the SCSI cabel is the CSPPC in the mid, or on the end? IIRC the board has to be not the first of any end of the cable as it has no termination option. some drives also has to be set with power on or motor start jumper, or something similar, don´t know yours.

Regards

[Miloo]

ive got on the scsi cable :

Terminator/CSPPC/HD/PLUG/CDRW/Terminator

[TrevorDick]

Your setup looks fine to me? I have the similar problem with my CS PPC SCSI setup. I have the right cable/termination and connectors and suspect my SCSI drive might be faulty? Should a SCSI drive attached to the CS SCSI interface be displayed in HDToolbox?

TrevorDick

[spirantho]

From what I remember you can enable and disable each unit on the CSPPC from the CSPPC early startup menu (hold down Escape isn't it?). Check all the units are enabled. Maybe set the settings to suboptimal, like asynchronous access and things like that.
You can use later versions of hdtoolbox such as in OS3.9 ok, just make sure you specify cybppc.device, i.e.

System3.9: > hdtoolbox cybppc.device

Alternatively use the software that came with your CSPPC as that's set up correctly out of the box, but it's a little more complex.

Perhaps also try jumpering the HDD to spin up immediately, or alternatively try jumpering to spin up only when accessed and see if it spins up correctly. Make sure the spin up delay isn't set otherwise it may not spin up in time. Also try with just Term->CSPPC->HD->Term. You made need to make sure something on the chain is supplying terminator power, there is possibly a TermPower jumper on your HD but there may not be as SCA disks such as yours are slightly different on termination issues I think.

[Bamiga2002]

Set your 68-->80pin adapter jumpers to "spin motor" and "motor start-up". Don't remember the correct names to the settings but check your adapter setup guide.

[Audun]

I have a similar problem on my 4k csppc (by p5). I just recently acquired an 18gb 10krpm scsi harddrive. I terminated it Term-->CSPPC-->HD-->Term, and first of all it takes me a zillion tries to actually get it to boot from floppy with the harddrive plugged onto the csppc, and when I do it only gets detected as a scsi device with no sectors. Thus I figure it detects the device itself but is unable to figure out what kind of device. I switched it with an IBM 36gb drive and that worked just fine. What teh hell ? Anyone know why / how to fix ? Any help is greatly appreciated!

[Dandy]

Audun wrote:

I have a similar problem on my 4k csppc (by p5). I just recently acquired an 18gb 10krpm scsi harddrive. I terminated it Term-->CSPPC-->HD-->Term, and first of all it takes me a zillion tries to actually get it to boot from floppy with the harddrive plugged onto the csppc, and when I do it only gets detected as a scsi device with no sectors.

If I understood you correctly, it shows no sectors.
Is the rest of the drive information there?
(like manufacturer, product name, heads, cylinders, capacity and so on)

If not, it might just be a bad RDB (rigid disk block).
Way back I had similar probs with my 160 gB IDE drive connected to the CSPPC UW-SCSI via ACARD UW-SCSI->IDE bridge.

Disk was reported to be there, but nothing else - no heads, sectors or cylinders or the like.

So I looked for the missing info on the web (HD manufactures pages) and with a tool from Aminet (can't remember the name ATM) I wrote an new RDB to the disk and it was accessible again.

Audun wrote:

Thus I figure it detects the device itself but is unable to figure out what kind of device. I switched it with an IBM 36gb drive and that worked just fine. What teh hell ? Anyone know why / how to fix ? Any help is greatly appreciated!

From what you write it really sounds like a bad RDB...

[Miloo]

Ive got the SCSI HD to work - There is a problem with the SCSI CDRW side.

When the HD is the only drive in the chain and terminated the machine boots up, with the CDRW connected the HD does not get reconised.

The CDRW has a 50 pin to 68 pin adaptor, it is terminated as its the last drive on the chain but still will not allow the HD to be reconised.

?

[Framiga]

you have to terminate the CDRW separately and it NOT must be the latest in the chain.

In the CSPPC manual, there are some useful schemes about.

CSPPC User Manual (page 52)

[Zac67]

If you terminate just the narrow part of the SCSI bus on the CDRW, the upper byte is not terminated correctly. Use a Wide SCSI terminator instead.

[Miloo]

@Zac67

What ive done is :

Terminator/CSPPC/HD/CDRW+terminator enabled/Terminator

The CDRW has a terminator built in the drive so i enabled that and on the last SCSI plug put a 68 pin terminator and now everything boots up.

Is that what you mean?

[Zac67]

I'm not sure I got you correctly - the CDRW as a narrow device just terminates the narrow half (lower byte) of the bus. If you use it to terminate the end of the bus, the upper half is not terminated at all. If you add (?) a wide terminator, you end up doubly terminating the lower byte, which isn't very good either (though it might work).

Deactivating the CDRW's terminator would be the best choice. If you'd had it that way before, there might have been a problem with term power: at least one device has to power the terminators, on a lenghty bus I usually set the end devices to provide term power.