Switch bank:
S1-1 low ROM enable, OFF = disable lower 256 word 765000-765777
In my YD version that is some of the boot devices, some tests
S1-2 ON=POWER UP REBOOT ENABLE, OFF=no boot on power up
parallel to TP1; if OFF, only TP2 low (TP3=GND) will boot
S1-3 to S1-10 word address offset, boot address = 173000 + (S)<<1
normally OFF
Boot process:
perform some tests, infinite loop when fail
print some register contents (console)
prompt for command (console)
enter console emulator command (L adr, D data, E[xamine], S[tart]) or boot
device
code (PR paper tape, DK RK05, ... )
if boot device: further tests, then boot from device
My doc is up to YD version only; the difference is different supported
devices, I believe.
John G. Zabolitzky
Ok, this is a long shot.
Background: DSSI disk controller (KFQSA), two DSSI disks (RF71's), BA213
Chassis, with a three disk active control panel on the front. The control
panel has three "unit number" plug in keys. One labeled "0", one labeled
"1", and one blank. One RF71 is plugged into the top connector and one is
plugged into the middle connector. In this configuration the "ready" lights
under the UNIT1 and UNIT0 plugs light up on power up.
Symptom: The controller only sees one of the two drives. The drive it sees
is the one connected to the control port with plug id '0' in it. If I swap
the ID plugs, the drive that gets talked to also swaps.
Other Data: In the PARAMS program on these disks (or perhaps in the
controller I don't know which) there are several "MSCP" variables
associated with the drive. One of them is "UNITNUM" which defaults to 0.
Both disks initially had unit numbers in this field of 0. I set one of them
to have a UNITNUM of 1, wrote it with the WRITE command and power cycled.
Rerunning PARAMS shows it now thinks it is unit 1, but it doesn't respond
if it is connected to the control panel with the unit 1 plug in it.
There are a few other parameters that I can set one is called "FORCEUNI"
which defaults to 'true'. I've tried turning it off on one of the disks
(where I set the unitnum to 1, but to no avail).
Triva Challenge: One of my thoughts was that perhaps the ID plug was
incorrectly "customized". The "0" plug has one center plug on top and one
center plug on bottom. The "1" plug has the center and right leg in, and
the center leg on the bottom. I'm wondering if it is actually another unit
number.
Misc Note: With the #3 and #4 switches "on" on the KFQSA, the board shows
up both in the Qbus scan and in the SHOW DEV scan as disk controller 0.
Any help appreciated...
--Chuck
I have the manual and several of these controllers. It is actually a Model
650.It sounds like yours has the 655/656 ROMS in location L4 and K4 since it is
responding as a DM: (RK06/7). There is page after page of configuration tables
for jumper settings depending on what drive and RK to emulate.
Dan
-----Original Message-----
From: Jacob Ritorto <jritorto(a)nut.net>
To: Discussion re-collecting of classic computers <classiccmp(a)u.washington.edu>
Date: Tuesday, July 27, 1999 11:19 PM
Subject: xylogics smd interface for pdp11
>Would someone please provide docs or setup info for the following
>scantily-marked unibus SMD controller:
>
>Xylogics #300-101-600 rev B L6
>
>doc. pkg. no. 300-101-902 Rev G serial no. 1103
>
>A few hand-written and typed labels are still attached to the socketed
>chips (presumably geometry/emulation codes):
>[handles forward, components up, edge connector facing you]
>
>along the left side, column of 8 big chips.
>4th down: " 766/BU4 "
>6th down: " 768/BU4 "
>
>six inches in from left; four inches down from handles, by itself
>: " -173E "
>
>slightly right of center; starting three inches down; column of four chips
>: " 242D "
>: " 245C "
>: " 244C "
>: " 243C "
>
>just below those, group of six chips, most missing their labels but top
>right is still there and reads : "799HC "
>
>That's all I can glean. Seems to show up as DM: under rt, but I don't
>know what size/shape of drive it expects or what partitioning it's willing
>to perform...
>
>BTW, Thanks John if you're lurking here somewhere...
>
>TIA
>
>jake
Hi folks, this is not really on topic as the machine in question doesn't
fit the ten year rule. But the list is a way to make first contact with
this query though. Reply off-list if you please.
Assuming one or more of you on the list are well-versed or even expert with
the T4400C, I pose a question to a problem I would like some advice on. The
machine belongs to my uncle and I'm helping him solve the problem.
As you may know this is a 1992 vintage machine: 486DX, 25 MHz, 12 Mb RAM,
120 Mb hdd, VGA color LCD display plus a Toshiba Desk Station IV docking
station. He installed Windows 95 and a sound card and CD-ROM drive into the
Desk Sta. IV.
He got the laptop second-hand and of course the manual was missing. The
D.S. IV was new, fresh outta the box and has a manual. The sound card and
CD-ROM is a Reveal SC400 package he scrounged from an old machine. Driver
disks came with it at least.
Problem is that the CD-ROM drive is not interested in working with the
system. W95 does not see it.
The sound card has the IDE interface meant for the Panasonic CD-ROM (which
is model CR-563-B) and the CD drive is plugged into that. So, BIOS setup
for setting a second IDE device does not work in this case. Looks like
there's no provision in the BIOS for a second IDE (slave) device anyway.
Apparently (and be aware that this is the very first time I've ever fiddled
with a sound card/CD-ROM combination) the drivers for the CD-ROM are part
of the sound card drivers. Well, the drivers predate the release of W95 by
a couple of years and Windows 3.1 and DOS are of course the only operating
systems mentioned in the installation. One of the attempts at installation
seemed to let W95 know there's a CDROM and sound card but the CDROM was not
accessable and the "undocked" mode caused W95 to try to fuss with the
drivers, etc. to get itself running. The CDROM was correctly set to be
present in "docked" mode and not present in "undocked" mode. Same for the
sound card.
Has anybody installed a CDROM and sound card set into their Desk Station IV
and gotten it running okay under W95?
Has anyone even installed W95 onto their T4400C? Results?
Thanks for your experiences.
Regards, Chris
-- --
Christian Fandt, Electronic/Electrical Historian
Jamestown, NY USA cfandt(a)netsync.net
Member of Antique Wireless Association
Check our redesigned website!
URL: http://www.antiquewireless.org/
<>Quantum D540 is the RD52, 31mb and faster than either of the seagates.
<>Also the 251 has a lousy track record for reliability (heat and skimpy spi
<>bearings).
<
< The Q540 was spec'd at, I believe, 35ms...but the ST251-1 (not 251) was 2
<I do agree about the heat and spindle bearing issues, though, 100%. I hav
<*never* seen a '540 fail. And they made much cooler sounds. :-)
The 8 heads vs 4 makes up for the difference in access as you can see twice
the data before moving the head, in real use acess time averaged better for
the d540. That was especially tue after the 251 dies. Also the D540 is a
servo vs the 251s stepper positioner so that impact reliability. Never
format a cold 251... the tracks move.
< Hmm. I think I'll ask them about the prices. By the "yet", are you
<suggesting that someone is working on it? :-)
Maybe Megan but, not I.
Allison
I know of someone wanting to sell a Wang 2200MVP. Is anyone interested? I
don't know what he's asking for it..
Kevin
-------------------------------------------------------------------------------
"It's you isn't it? THE BASTARD OPERATOR FROM HELL!"
"In the flesh, on the phone and in your account..."
-- BOFH #3
Ok, a diagnostic puzzle.
I've got a uVAX with two RF71 DSSI disks in it, before I knew how to talk
to them properly I had netbooted NetBSD and saw that it reported both
RF71s. I tried to talk one of them and the fault light came on (did a
diskinfo kind of thing.)
At the time I figured it was just the lack of a terminator. Now I'm not so
sure.
The other RF71 (which still came up ready) has now been tested formatted
and mounted under netbsd indicating all is well with that part of the world.
So how can I figure out the fault on the other drive? Where to look? I'm
going to try playing around with the internal "DUP" stuff this after noon.
--Chuck
Larry Simonsen (LSimonsen(a)FLOWSERVE.COM) posted elsewhere:
We have a 3000/37 available.
It has 4 discs for a total of 1.65 Gig; 5 port boxes (8 ports per box); a
DDS 1300H, and an open reel tape drive 7974.
Anyone interested?
For collectors, an HP 3000 Series 37 is about the size of a desktop PC
(slightly heavier), and runs MPE V. (No, you can't run Linux on it.)
It's a CISC stack-based machine. The disk drives mentioned are all
external boxes of some kind, connected via HPIB (no, you can't use SCSI).
The machine is in Edmonton , Alberta, Canada.
If interested, contact Larry directly, not me.
Here's an update for the archives so that others might benefit from the
knowledge:
I have a uVAX 3900 (KA655 CPU) with a KFQSA controller in it, the software
didn't "see" it. I had heard that one of the switch settings controlled if
the controller grabbed an address or not, so I flipped the switches (there
are only 4) until I found it, the combination (1,2,4-off, 3-on) was successful.
This vax boots to the chevron (>>>) prompt when the console control switch
is set to the dot inside the circle icon. At the prompt two interesting
commands are your friend. The first is
>>> SHOW QBUS
which shows you the devices that the CPU sees. It will also identify those
it recognizes. At first mine did not "see" the KFQSA, after flipping some
switches it did, and then I could type:
>>> SET HOST/DUP/UQSSP/DISK 1
and it got into the DUP menu that had drive information. Now why DISK 1?
Because DISK 0 is having problems. There is an ID jumper on the disk
somewhere that tells the card what disk it thinks it is I believe.
After getting into DUP I did ERASE and the DRVTST and both seemed to work
so we're off to the races yet again...
--Chuck
Someone is asking me about an NEC 8012A. Anyone know
anything about this system?
-----
David Williams - Computer Packrat
dlw(a)trailingedge.com
http://www.trailingedge.com
