3 Apr
2008
3 Apr
'08
8:08 p.m.
On Apr 3, 2008, at 11:52 AM, John A. Dundas III wrote:
The .SIL I was running was generated with the DQ132 configured
with extended features enabled. That was probably why init disabled it.
It's moot at this point, though, because I can't get the damn
drive to work. The universe just doesn't want me to have tapes on my
PDP-11s, it seems.
-Dave
--
Dave McGuire
Port Charlotte, FL
Well that
was my thought...I've never used a 9-track drive on a
22-bit system running RSTS/E, so I was guessing a bit. I thought
perhaps the driver might implement bounce buffers if the board was
operating in 18-bit mode.
Later last night (in total screaming frustration trying to get
at least ONE of my five 9-track drives working) I discovered that
the driver identifies the board correctly and says "extended
features disabled" in the HA LI output, then init disables the
device.
Is _that_ particular device SYSGEN'd into the RSTS SIL you're
attempting to run? IIRC, the boot-time code (HA LI) will show all
the devices it successfully identifies on the bus, but the RSTS
image you try to run after that may not be (and usually isn't)
configured to support all devices. One good reason is because some
of the magtape controllers use the same CSR but are otherwise
incompatible. You may need to SYSGEN a new .SIL before you can
actually use the device.