BlizzardSCSI problems..

[Leifern]

Well, no i've just about had it.. I bought a bunch of nice stuff for my Amiga (Mediator, Voodoo3, Networkcard and E/Box tower). But now nothings working... Again...!

Before removing everything from my CRAPPY InfinitivTower i managed to mess up my 3.9 installation by fiddling around with my filesystem and maxtransfer-settings. However, the evertrusty EmergencyDisk always fixes those thing with a nice fresh installation, so i didn't think any more of it.

I took everything out and put it into my new tower (the MB, ZIV, 1260&SCSI, PIV&Concierto) And set out to boot from my EmDisk. But i got this wierd error saying: Can't open "1230scsi.device" unit 1. Which would be my CD-rom. I have no idea what this means, so i figured that there was either something wrong with my disk or with my SCSI controller (which seams wierd). But none of the SCSI devices show up in the BOOTmenu or when booting from any Wokbench. However the RAM is always there.. Both the ram connected to the 1260 and the SCSI controller.

Other then that i got a "Vector" Keyboard interface that i can't get to work either. Not with a PC or an A2000 keyboard. Anyone have one of these?

I really hope someone can help me, because i've just about had it with this constant "What just happened!??"

All the best,
Leifern

[Chain]

I took everything out and put it into my new tower (the MB, ZIV, 1260&SCSI, PIV&Concierto) And set out to boot from my EmDisk. But i got this wierd error saying: Can't open "1230scsi.device" unit 1. Which would be my CD-rom. I have no idea what this means, so i figured that there was either something wrong with my disk or with my SCSI controller (which seams wierd). But none of the SCSI devices show up in the BOOTmenu or when booting from any Wokbench. However the RAM is always there.. Both the ram connected to the 1260 and the SCSI controller.

looks like bad connection between blizzard and scsi kit

[Angus]

Hang on in there if you can.  

I had a lot of trouble getting my Mediator etc all working, but when it does, its worth all the hassle. As stated, connections are a common issue. In my situation I pay a certain amount of attention to the chips on the Mediator itself as well as where it interfaces with the 1200 and accelerator. I take the lid off my tower, get plenty of light in the room, power off, have a little tweak/push on a connection, power on, and repeat. But try not to lose your cool and break anything if things aren't going well. Its easy - I know.  

All the best with it.

[Leifern]

Thanks for the reply.. I'll try to check the connections, but if it was a connection-problem wound't the RAM on the SCSI controller be gone as well? :-?


EDIT:

I was also thinking: Since it's unit 1 thats not found (allthough i can't see any evidence that it's found unit 0)
Couldn't there be something wrong with the SCSI chain? I don't know SCSI all that well so if there any essentials that would seem obvious, please share. Also if unit 0 (The HD) is messed up, wouldn't it have problems finding unit 1?

[Matt_H]

Type 'version 1230scsi.device' in a shell. Does it return anything? If so, then I suspect either:

Your CD drive is broken
Your SCSI chain is not terminated properly
Your CD mountlist or drive is misconfigured

It's trying to mount your CD drive, configured as unit 1, from the SCSI Kit. If the drive isn't jumpered as unit 1, then the problems you've reported are to be expected.

EDIT: Is your hard drive on the internal IDE bus or the SCSI bus?

[rockape]

Hi,  

I seem to remeber that if you upgraded to a higher CPU accelerator the SCSI device had to be changed to 1240scsi.device

Regards, Michael

aka rockape

[Matt_H]

I seem to remeber that if you upgraded to a higher CPU accelerator the SCSI device had to be changed to 1240scsi.device

Not so. At least, not with the version of the SCSI Kit that I used. It was still 1230scsi.device on my Blizz1260.

[Leifern]

Hi,

The drive is on the SCSI bus. I think the chain is terminated correctly, as it worked before, and i haven't changed anything. I am unable to test anything that needs a keyb. right now as the keyboard adapter doesn't work. I will try some more stuff today.

[Leifern]

I've checked which SCSI-ID it's jumpered as and it was set to 1. Also, would i be able to see it or the HD in the Boot menu? And would i see the HD still if the CDRom didn't work?
And if the SCSI-controller works, will i see it in the BootMenu, or is the accellerator and SCSI controller considered as ONE expansion? The accellerator seems to be working correctly, and the ram on the controller is there when i boot with my 3.1 disk. But none of the SCSI devices are accesable through workbench. Wouldn't the HD partitions be if the controller worked properly?

[rockape]

Hi Matt_H

Thanks for pointing that out.

I seemed to remeber having to re-name the device from years ago,

Prhaps tis a SCSI ROM version that caused it ?

Regards, Michael

aka rockape

[Leifern]

By the way, the error message is given by "Cache CDFS". Don't know if it matters. I've tried using only the CDrom and setting the "terminator" jumper on the cdrom to on. So that if it wasn't terminated before, it is now, but it didn't help at all..

[Matt_H]

Prhaps tis a SCSI ROM version that caused it ?

That seems possible, as I have seen references to 1240scsi.device and 1260scsi.device in some very old documention. I had previously thought it to be a mistake.

[LawlessPPC]

at a guess i think its a problem with the tooltype settings check that these settings are correct ie correct
device = scsi1230.device
Unit = 1


etc

[Leifern]

How do i check this?

[Leifern]

I just booted from 3.1 and installed the SCSI software to the ramdisk. Tried to scan for SCSI devices using unitconfig (or something). But it didn't find the HD or the CDRom. Could this meen i have to replace the cable? Wierd that it should brake though. But once again, find it hard to believe that the SCSI-Controller is broken as long as the ram attached to it works properly.