Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!usc!zaphod.mps.ohio-state.edu!mips!daver!bungi.com!news
From: eyal@echo.canberra.edu.au (Eyal Lebedinsky)
Newsgroups: comp.sys.nsc.32k
Subject: some problems bringing the pc532 up.
Message-ID: <9011040317.AA13912@echo.canberra.edu.au>
Date: 4 Nov 90 07:17:46 GMT
Sender: news@daver.bungi.com
Lines: 39
Approved: news@daver.bungi.com

Hello,

The machine seems to work. The PI program was downloaded and run with no
problems - but the disk wont respond.

The monitor is dated July 14, 1990.

I get scsi select timeouts. I traced the signals and found that there is no
activity on conn1. Then I found that the SELECT output of the ICU goes low
on first disk i/o and stays low forever. This seems to select /scsi1 at the
scsi pal, but the disk is on scsi0 (that's where it belong, correct?). The only
time I see SELECT high is after machine reset until first read/write.

The disk will just spin up, front led go green, a short burst of what sounds
like head movement, then the thing goes silent. The front led is dark with a
faint blink  (at say 3Hz) and an on-board bright green led flickeres madly (
the disk is a 9380S).

Also, I dont recall seeing a monitor man, was there one?

The baud command does not affect the rate: I did 'baud 19200' which should
have altered the consol speed but it did not.

What should 'scsi_adr' be set to? I hope the default '0' will work the native
disk (conn1). I tried 1 and 2 with no noticable change.

Last, J1 and J2 do not have pinput numbers in the layout (I assume 1-2-3 top
to bottom) and no indication which jumper for 1M/4M (I assumed 2-3 for 1M,
1-2 for 4M).

BTW, the scsi pal definition says 'select = 0 will select scsi 0' but it does
not seem to do this (unless 0 is high).




-- 
Regards
	Eyal