19 Jun
2014
19 Jun
'14
5:42 p.m.
Does anyone have RT-11 actually running with two MSCP disk controllers?
My 11/83 has a CMD CQD220A/TM at 172150, and an RQDX3 at 160334. The rqdx3 has an rx33
floppy drive, and is set for starting LUN 4.
No matter what I do, RT-11 simply won't see the floppy. I've run sysgen, specified
the addresses of both controllers, nothing works.
So, if anyone actually has a running system with dual controllers, I would love to see the
SET DEVICE stuff that makes it work.
Thanks for any advice.
20 Jun
20 Jun
8:08 a.m.
At one point I had my 11/73 running with a Webster WQESD/4 ESDI controller driving the HD,
and a RQDX3 running the floppies. I *believe* that's how it's setup now, except
I'm using a Viking QDT SCSI adapter instead of the Webster board. Originally running
RT-11 v5.3, now I think it's either v5.4 or v5.7 depending on which of the removable
SCSI HD's I boot from.
Zane
On Jun 19, 2014, at 5:42 PM, "Peterson, Roe (LAI)" <roe at
liveblockauctions.com> wrote:
Does anyone have RT-11 actually running with two MSCP
disk controllers?
My 11/83 has a CMD CQD220A/TM at 172150, and an RQDX3 at 160334. The rqdx3 has an rx33
floppy drive, and is set for starting LUN 4.
No matter what I do, RT-11 simply won't see the floppy. I've run sysgen,
specified the addresses of both controllers, nothing works.
So, if anyone actually has a running system with dual controllers, I would love to see
the SET DEVICE stuff that makes it work.
Thanks for any advice.
--
healyzh at aracnet.com
http://blog.zanesphotography.com
http://www.flickr.com/photos/zanes-photography/
8:44 a.m.
So did it "just work"? The key question is: what did you do to configure RT-11
for the RQDX3?
On Jun 20, 2014, at 9:10 AM, "Zane Healy"
<healyzh at aracnet.com> wrote:
At one point I had my 11/73 running with a Webster WQESD/4 ESDI controller driving the
HD, and a RQDX3 running the floppies. I *believe* that's how it's setup now,
except I'm using a Viking QDT SCSI adapter instead of the Webster board. Originally
running RT-11 v5.3, now I think it's either v5.4 or v5.7 depending on which of the
removable SCSI HD's I boot from.
Zane
On Jun 19, 2014, at 5:42 PM, "Peterson, Roe
(LAI)" <roe at liveblockauctions.com> wrote:
Does anyone have RT-11 actually running with two MSCP disk controllers?
My 11/83 has a CMD CQD220A/TM at 172150, and an RQDX3 at 160334. The rqdx3 has an rx33
floppy drive, and is set for starting LUN 4.
No matter what I do, RT-11 simply won't see the floppy. I've run sysgen,
specified the addresses of both controllers, nothing works.
So, if anyone actually has a running system with dual controllers, I would love to see
the SET DEVICE stuff that makes it work.
Thanks for any advice.
--
healyzh at aracnet.com
http://blog.zanesphotography.com
http://www.flickr.com/photos/zanes-photography/
9:18 a.m.
Peterson, Roe (LAI) wrote:
Does anyone have RT-11 actually running with two MSCP
disk controllers?
My 11/83 has a CMD CQD220A/TM at 172150, and an RQDX3 at 160334. The rqdx3 has an rx33
floppy drive, and is set for starting LUN 4.
No matter what I do, RT-11 simply won't see the floppy. I've run sysgen, specified
the addresses of both controllers, nothing works.
So, if anyone actually has a running system with dual controllers, I would love to see the
SET DEVICE stuff that makes it work.
Thanks for any advice.
While you have provided insufficient detail of which
version of RT-11 you are using, along with a Mapped
or UnMapped Monitor, I can guess a bit.
For your information, I have FIVE MSCP controllers:
DU(X).SYS - Standard CSR / VECTOR
QR(X).SYS - RQDX3 (Q for a dual board)
VR(X).SYS - RQDX2 (V for a quad board)
SE(X),SYS - Dual ESDI controller for Seagate Hard Drives
HI(X).SYS - Sigma RQD11-EC (Quad ESDI controller) for
Hitachi Hard Drives
I also have a CMD CQD220 / TM which is often used with the
DU(X).SYS device driver for SCSI interface drives.
If you "merely" made a copy of DU(X).SYS to SC(X).SYS,
then critical values were not modified. In addition, if you
SYSGENed an extended device driver which supports more
than EIGHT physical units, there is one additional word which
requires alteration.
Unfortunately, DEC neglected to provide the command:
SET SC NAME
which would fix all of those other values when the NAME
of the device driver is changed to support a second controller
at a different CSR / VECTOR pair. But then, even though
RT-11 is VERY comprehensive for a VERY simple operating
system, there are still many enhancements that were omitted.
If you are using an UnMapped Monitor (RT11FB) with ONLY
a maximum of EIGHT physical units, then search for (use SIPP)
the value ^rDU (16110) and change it to ^rSC (73470 - or
whatever you have named your CQD220A/TM device driver).
If you are using a Mapped Monitor, the names are a bit different.
That will be in addition to:
SET SC CSR=160334
SET SC VECTOR=150 (did you forget to change the VECTOR?)
As far as I understand, you may be able to get by with just the above
two SET commands without changing the ^rDU values if you just
use the RQDX3 controller for the RX33 floppy as a data device.
Please let me know what you find that fixes the problem or if you
need more help.
Jerome Fine
2:44 p.m.
On 20/06/2014 01:42, Peterson, Roe (LAI) wrote:
Does anyone have RT-11 actually running with two MSCP
disk
controllers?
My 11/83 has a CMD CQD220A/TM at 172150, and an RQDX3 at 160334. The
rqdx3 has an rx33 floppy drive, and is set for starting LUN 4.
No matter what I do, RT-11 simply won't see the floppy.
I think but am not 100% sure I've run RT-11 with two MSCP controllers,
but I do know that the RT-11 DU: driver before 5.2 (or was 5.2 the last
broken one?) is broken and doesn't recognise an RQDX3 properly. I spend
a week once, tracking that down and making a patch for it. In essence,
the earlier drivers assumed a status register would be zero after
initialisation (which it is on RQDX1 and RQDX2), and checked for that
instead of checking the specific bits the MSCP spec calls for. One of
the other bits is non-zero on an RQDX3.
--
Pete Peter Turnbull
Network Manager
University of York
23 Jun
23 Jun
4:28 a.m.
Pete Turnbull wrote:
On 20/06/2014 01:42, Peterson, Roe (LAI) wrote:
Which is why I asked Roe for the details of which version
of RT-11 and which monitor (Mapped or UnMapped) was
being used.
The real problem, as I mentioned in passing, was that DEC
never provided the feature:
SET device: NAME
to support multiple controllers so that:
COPY SY:DU(X).SYS SY:SC(X).SYS
SET SC: NAME (this command does NOT exist)
SET SC: CSR=160334 (this command does exist)
SET SC: VECTOR=130 (this command does exist)
could be used to set up additional device drivers for other
CSR / VECTOR pairs.
Another feature that was also missing until V05.06 was the
code to boot a non-zero partition. Prior to V05.06 of RT-11
(starting with V05.03 of RT-11 when partitions were first
supported for the MSCP device driver), all DEC versions
of the MSCP device driver supported non-zero partitions
as DATA ONLY.
And finally, even with V05.05 to V05.07 of RT-11, for
the DEC version of the MSCP device driver, ONLY the
first eight logical device names (DU0: to DU7:) can be
booted in any case even though with extended device
driver support, 64 partitions are available (D00: to D77:)
to be used starting with V05.05 of RT-11. The extra
code to support booting from all 64 partitions is not
difficult. What I found impossible was to support more
than one controller and still fit the code, and especially
the SET tables, within the single boot block allowed for
the device driver. The end result was just (with zero
words left over) able to fit, and even then the unit table
within the boot block had to be reduced to byte entries
Does anyone have RT-11 actually running with two
MSCP disk
controllers?
My 11/83 has a CMD CQD220A/TM at 172150, and an RQDX3 at 160334. The
rqdx3 has an rx33 floppy drive, and is set for starting LUN 4.
No matter what I do, RT-11 simply won't see the floppy.
I think but am not 100% sure I've run RT-11 with two MSCP controllers,
but I do know that the RT-11 DU: driver before 5.2 (or was 5.2 the last
broken one?) is broken and doesn't recognise an RQDX3 properly. I spend
a week once, tracking that down and making a patch for it. In essence,
the earlier drivers assumed a status register would be zero after
initialisation (which it is on RQDX1 and RQDX2), and checked for that
instead of checking the specific bits the MSCP spec calls for. One of
the other bits is non-zero on an RQDX3.
from the standard word entries in the other tables in
the
device driver.
At the time, I had not yet managed to think of the feature:
SET device: NAME
so an additional tiny file of parameters was used at
SYSGEN time to change the values that the NAME
feature would modify. MANY years later, I found I
needed the NAME feature again when I modified John
Wilson's code for HD.MAC and wanted a substitute
for the VM(X).SYS device driver which would be faster
and MUCH larger than is possible using real DEC
hardware and just a 4 MB memory as opposed to
the GB memory available now under current Windoze
hardware when Ersatz-11 is used to run RT-11 as
opposed to real DEC hardware. Of course, SimH
could also support an HD: device, but I have never
had the urge to figure out the needed code.
Even real DEC hardware could also have a custom
controller to support an HD: device, but since I am
not a hardware individual, I have never even considered
the possibility. Has anyone else? I ask a hardware
question so rarely, so perhaps when I do, one of
the really clever individuals who knows hardware
quite well could make a modest effort to determine
what might be needed to support an interface to
a current SATA hard drive of a TB which would
be able to interface a Qbus on a PDP-11. A bit
of overkill, obviously, considering what DEC ever
supported on a PDP-11.
Jerome Fine
3616
days inactive
3619
days old
5 comments
4 participants
participants (4)
-
healyzh＠aracnet.com -
jhfinedp3k＠compsys.to -
pete＠dunnington.plus.com -
roe＠liveblockauctions.com