In order for your system to "see" the board, you must insure that none of it's 
addresses conflict with existing QBUS boards.

As I suggested in a previous Email, QBUS Vaxes have a "configure" command 
which can be used at the PROM prompt.

Type "configure", then "help" and you will get a list of devices that VAX is 
"familiar" with.  Then type: device,# for each device on the QBUS.  When you 
type "exit", you will be "told" what addresses to set each QBUS board in your 
system.

I do this for running OpenVMS and it has always worked well.  When I'm using a 
board which is not known by "configure", I merely use configure to do all the 
known boards, and then make sure whatever other board I am using does not 
conflict.

"configure" does not deal with "memory" issues - so you have to manually 
insure that any QBUS board's memory does not conflict (overlap) with another 
QBUS board.

Cheers,
Lyle

On Wednesday 04 June 2003 07:47, Jochen Kunz wrote:
> On 2003.06.04 16:25 M J Dowden wrote:
> >      I've tried several dip configurations, but the KFQSA never shows
> > up in "service" mode in a sho dev, as described in n.rieck's notes.
>
> Not "show dev", "show qbus" should give:
> 774420 KFQSA Service #0
>
> I have somthing in my mind that the assignment of "0" and "1" on the DIP
> switch description is inversed on that page. I had to fight with the dip
> switches for some time too.
>
> But bevore you start to fight with the KFQSA, try to regonfigure the
> CMD SCSI and boot of the NetBSD CDROM without the KFQSA. If this fails
> you don't need all that fiddling with the KFQSA and can proceed with
> a net-boot setup.

-- 
Lyle Bickley
Bickley Consulting West Inc.
Mountain View, CA 94040
"Black holes are where God is dividing by zero"