Blizzard 1230 SCSI kit not working?

[Djdavemortis]

Hi All,

I've just succesfully configured my Sandisk 16GB CF card on my pc (installed os 3.9 without support for cd-rom drives)

But now on my real amiga 1200 with 1230 and SCSI kit (64 + 128 mb ram installed) i can't get my SCSI CD-rom to work.
Everything else works fine, but i have some original games i'd like to install & play.
I installed the latest Phase 5 SCSI diskette, but nothing happens when i insert a CD
The CD-ROM is on SCSI ID 4 and correctly terminated

Did i do something wrong?

Thanks

Dave from Belgium

[alewis]

Are there any other devices on the SCSI bus - and do they work?
Is the CD-ROM visible when scanning the SCSI bus, either in the SCSI BIOS (assuming the blizzard has this abillity) or when using a partition tool such as, um, can't remember names of C= partitioning tool!

[Djdavemortis]

Hi alewis, thanks for your reply!

I've just connected another SCSI CD-rom i had lying around (100% working Plextor 20 speed) and still no go...
I tried running the blizzard SCSI tools from the CLI to scan the SCSI bus and i'm getting following message:

No device V7 or higher found

Edit: no other SCSI devices ar connected, only one SCSI CD-rom and it's correctly terminated

Regards,
Dave

[Toni Wilen]

Ignore Blizzard tools (I think they are mostly for SCSI parameter setup, not for mounting CDs etc..) and simply edit Devs:mountlists/CD0

Device = 1230scsi.device
Unit = <scsi id>

EDIT: What does "version full 1230scsi.device" return?

[Djdavemortis]

Hi Toni,

I removed the SCSI card from my A1200 and gently pressed down on the SCSI bios chip, now i'm not getting the "No device V7 or higher found" message anymore

Edit: maprom is on, memory is at 60ns

In the blizzard SCSI software i can do a scan of the SCSI devices, but nothing is found

The version of 1230scsi.device is 8.5

I'll change the mountlist as described: Unit = <scsi id> , but do i need to type it like this or do i type Unit = 4 or Unit = <4> ?

Thanks,
Dave

[AmigaFriend]

Hi DJ

it is without the <>

Unit = 4

[Hungry Horace]

dunno if it makes a difference but i've always done it without the spaces

device=1230scsi.device
unit=4

and i've never had any problems with it.

[smoorke]

doesn't the memory speed jumper have to be on 70ns (or whatever the slower memory speed is) for the scsi kit to work?
Can't remember if the jumper is 50/60ns or 60/70ns. Anyway it should be on the higest number (=slowest mem speed)

[rkauer]

Can you try a different SCSI cable? SCSI cables are very fragile.

[Djdavemortis]

@smoorke: Hallo i can choose between 60/70ns, i've changed the speed to 70ns, but still no go... (the manual states that i need to put it on 70ns when using two SIMMS)

@Hungry Horace: i tried without the spaces, but still no drive detected

@rkauer: i even tried a different external SCSI cd-rom with different cable, but still nothing is detected.
And i don't have a spare internal Blizzard SCSI cable


What direction must the red stripe of the internal Blizzard SCSI cable face?
Currently it's pointing to the direction of the 2nd SIMM socket

Is there a program that can test if the SCSI card is responding? Sysinfo?

[alewis]

What device ID is the Blizzard SCSI card set to?
What device ID is the CD-ROM set to? They must be different
Is the cable terminated? fit an active terminator
If you dont have an active terminator, plug the CDROM into the last plug socket on the cable (which should be at the end), and ensure that the jumpers for termination are set. You may also want to set a jumper for supplying TERMPWR

If the cable is terminated, try removing it and plugging CDROM in last socket as above.

Have never used this SCSI kit, from the comment above does it use a standard 50pin SCSI interface, or an abortion 25pin?

Before worrying about what mountlist to use, I'd be concerned about getting the Blizzard to see the cd-rom as a device on the bus. If it doesnt see it, then no amount of devs will get it to work... it aint there at the hardware level!

Boes the blizzard have a "bios" in which you can set SCSI paramters such as what device IDs to scan?

[Hungry Horace]

Originally Posted by alewis

What device ID is the Blizzard SCSI card set to?

it doesnt have one

What device ID is the CD-ROM set to? They must be different
Is the cable terminated? fit an active terminator
....
If the cable is terminated, try removing it and plugging CDROM in last socket as above.

all answered in the first post

Have never used this SCSI kit, from the comment above does it use a standard 50pin SCSI interface, or an abortion 25pin?

25-pin.

Boes the blizzard have a "bios" in which you can set SCSI paramters such as what device IDs to scan?

no, it doesnt.

@ Djdavemortis

as i recall, the scsi-connector ribbon cable wont fit if you try to put it the 'wrong way round', the board itself would get in the way. (i think, although i havent checked) ... this would mean you dont need to worry about the 'red strip'

[Calgor]

The Blizzard SCSI Kit Controller has a SCSI ID of 7.
When the cable is folded, pin 1 (red line) should be closer to the board (also the simm).

See manual for SCSI Kit which has this info (maybe you have a different manual):
http://amiga.resource.cx/manual/BlizzardSCSI4.pdf

I think you can use the Blizzard SCSI Kit boot disk (i.e. the Blizzard tools) to set stuff such as Syncronous/Asynchronous for each SCSI Device/ID, but not sure if these will affect anything, as my SCSI Kit has always worked for me without problems so I have not needed to adjust these. I think a CDROM may not be as flexible in these settings as a hard disk. Just a thought.

[Hungry Horace]

Originally Posted by Calgor

The Blizzard SCSI Kit Controller has a SCSI ID of 7.

blimey. over ten years i've used that thing, and since you cant change it, i'd always assumed the controller didnt need one!

silly Horace.

[Djdavemortis]

I did some more testing, formatted another CF card (1GB) but this time installed OS3.1 and installed the Blizzard SCSI tools, still the same problem, nothing is detected... could the CF2IDE adapter be conflicting with the Blizzard SCSI controller?
Because In HDtoolbox the CF card is detected as SCSI device 0 ?
I think the CF2IDE is using scsi.device and the SCSI kit is using 1230scsi.device ?

[smoorke]

that's commodore for you. The IDE port is addressed with scsi.device
And yes the 1230scsi.device is for your scsi kit.

Perhaps you could post what 'showconfig' tells you to help determine the problem

[alewis]

Originally Posted by Hungry Horace

it doesnt have one

all answered in the first post

25-pin.


no, it doesnt.

@ Djdavemortis

as i recall, the scsi-connector ribbon cable wont fit if you try to put it the 'wrong way round', the board itself would get in the way. (i think, although i havent checked) ... this would mean you dont need to worry about the 'red strip'

No, its not, bar the ID question. The SCSI card *MUST* have an ID, it cannot operate without one. Most often to ID7.

OP doesn't state how the chain is terminated, just "correctly terminated". If the CD *and* the cable are terminated, this *can* (not will, just 'can') lead to problems.

Given it's a 25-50pin adapter, its difficult to eliminate cabling problems; The 25pin abortion lead sacrifices almost all ground connections... and can be temperamental over device/active/passive termination.

It is unclear if the CD-ROM can be seen at a hardware level by the Blizzard SCSI controller.

Assuming that the blizzard boot disk is correctly configured to scan the Blizzard SCSI controller, remove the CF adapter, and boot from the disk. Boot the necessary SCSI software, and scan the SCSI bus for devices. You might like the check the tooltype for what scsi.device it is using (scsi.device, blizzardscsi.device or whatever).

[Hungry Horace]

Originally Posted by alewis

The SCSI card *MUST* have an ID, it cannot operate without one. Most often to ID7.

my comment afterwards mentioned my own mistake there

[rkauer]

Originally Posted by Djdavemortis

I did some more testing, formatted another CF card (1GB) but this time installed OS3.1 and installed the Blizzard SCSI tools, still the same problem, nothing is detected... could the CF2IDE adapter be conflicting with the Blizzard SCSI controller?
Because In HDtoolbox the CF card is detected as SCSI device 0 ?
I think the CF2IDE is using scsi.device and the SCSI kit is using 1230scsi.device ?

Try to run the HDToolbox or HDinstTools from a CLI (Amiga DOS shell = Command Line Interface) and type "1230scsi" after the command. The used tool will recognize the device, even if it is not an HD (will show as "unknown").