Hopefully, this request is clear enough to be understood. Both the
software and the hardware portion of the questions are independently
important, so please answer one aspect even if you can't help with
the other.
Over the past 30 years of using PDP-11 software (RT-11 over 95%)
and hardware, I have never had occasion to use a Unibus system with
more than 256 KB of memory (such as a PDP-11/34).
I would appreciate help in understanding the Unibus Map hardware which
(if I understand its purpose correctly) is to convert 18 bit addresses given
to a Unibus controller into 22 bit addresses for real physical memory for
systems like a PDP-11/84 and perform DMA from / to the hard drive.
Also helpful would be an explanation of the related software used under
RT-11 along with exactly where the Unibus Map hardware is located
on a real DEC system (on the CPU board I presume) since the identical
CPU board is used for both the Qbus and the Unibus with both the
PDP-11/84 and the PDP-11/94.
-------------------------------------------------------------------------
DO NOT READ THE FOLLOWING if you don't use RT-11!!!!!!!
By way of context, I have successfully modified the HD0: device driver
originally written by John Wilson which obviously executes ONLY under
E11. Last week, John mentioned in a private e-mail that it is possible to
direct the HD0: "controller" (all references to hardware in quotes refers
to E11 software) to ignore the "Unibus Map hardware". Since I execute
under E11 using Qbus emulation in order to stay totally compatible with
the real DEC PDP-11/23, PDP-11/73 and PDP-11/83 systems (all Qbus
and all with 4 MB of physical memory) which I have available for comparison
testing, user buffers in physical memory above 256 KB are often a situation
which can't be avoided.
Consequently, it had always been a high priority to have a 22 bit device
driver
for HD0: under E11 BECAUSE HD0: is TWICE as fast as MSCP (DUX.SYS
device driver). In addition, I have also been able to write code that
avoids the
overhead of using the HD0: device driver which makes HD0: FOUR times as
fast as MSCP and also allows for direct access of 2 TB of disk space via a
32 bit block number. Since I have an immediate application for a data base
of 32 GB (I have a disk drive of 160 GB, so 32 GB is only 20% of its
capacity -
although under RT-11 15 years ago in 1992, 32 GB would have been only a
dream), the code which I have written will actually be used quite soon.
However, I would very much like the HD0: device driver to be able to execute
under both "Qbus" and "Unibus" hardware. And while I can test the code for
a "Qbus" and for a "Unibus" without a "Unibus Map", I am not clear about
what is required for a "Unibus" with a "Unibus Map" such as a PDP-11/84
running under RT-11.
Megan are you still watching the list? Allison, if you can't answer,
can anyone
but Megan help? Is anyone else familiar enough with the "Unibus Map" that
you can suggest what RT-11 actually needs to do with the "Unibus Map"?
A solution is to check the "hardware" configuration and refuse to allow the
HD0: device driver to LOAD or .Fetch if the modified version is not
executing under "Qbus hardware".
By the way, if anyone who is thinking of a controller for the Qbus which is
able to use SATA drives, I would be happy to modify an RT-11 device
driver to an HD0: type device that is able to handle drives up to 2 TB
in the same manner that DU(X).SYS can handle drives up to 8 GB.
Anyone interested??
Sincerely yours,
Jerome Fine
--
If you attempted to send a reply and the original e-mail
address has been discontinued due a high volume of junk
e-mail, then the semi-permanent e-mail address can be
obtained by replacing the four characters preceding the
'at' with the four digits of the current year.
I'm trying to use simh to create an RT-11 bootable RX50 disk and am
following some instructions posted by Megan Gentry a while ago. I've
created the disk image but am having trouble making it bootable. The
copy/boot command claims it can't find the RT-11 image but it is
clearly on the floppy (du0). Any idea what's going wrong?
.dir du0:
10-Apr-99
RT11XM.SYS 106P 20-Dec-85 DU .SYS 8P 20-Dec-85
TT .SYS 2P 20-Dec-85 PIP .SAV 30P 20-Dec-85
DUP .SAV 47P 20-Dec-85 DIR .SAV 19P 20-Dec-85
RESORC.SAV 25P 20-Dec-85 EDIT .SAV 19P 20-Dec-85
MACRO .SAV 61P 20-Dec-85 CREF .SAV 6P 20-Dec-85
LINK .SAV 49P 20-Dec-85 LIBR .SAV 24P 20-Dec-85
FILEX .SAV 22P 20-Dec-85 HELP .SAV 132P 20-Dec-85
BATCH .SAV 26P 20-Dec-85 FORMAT.SAV 24P 20-Dec-85
SETUP .SAV 41P 20-Dec-85 SPEED .SAV 4P 20-Dec-85
DATIME.SAV 4P 20-Dec-85 LET .SAV 5P 20-Dec-85
SPLIT .SAV 3P 20-Dec-85 CONFIG.SAV 7P 20-Dec-85
SWAP .SYS 27P 20-Dec-85
23 Files, 691 Blocks
95 Free blocks
.copy/boot du0:rt11xm.sys du0:
?DUP-F-File not found DU0:RT11XM.SYS
http://mysite.verizon.net/rtellason/pa020085.jpg
I haven't seen the inside of one for a while, but this may be for a Fortune-32
JAM or someone with a machine handy (Eric?) could confirm it.
There were different 'dash' configurations for the WD1001, according to the WD
catalog. The ones listed use ribbon cable connectors.
Roy, Al,
> http://mysite.verizon.net/rtellason/pa020085.jpg
>
> I haven't seen the inside of one for a while, but this may be for a Fortune-32
> JAM or someone with a machine handy (Eric?) could confirm it.
Yes, that's a hard disk controller for the Fortune 32:16 computer.
I would be happy to save it from going to the scrap heap.
James Markevitch
Hello,
The company I work for has approximately 15 HP 9000/300 computers
available. These are mainly the 310 models. There are a couple of other
models too. Most of them have the SRM boards installed. There is also a
HP9826 available. Also are keyboards and monitors. There are NO hard drives
or floppy drives.
We are going to do an renovation of the area they are stored in. They are
free for local pick up in Lexington KY or if you arrange for freight
pickup, we will put them on a pallet and wrap them. If there are no takers
in 30 days, they will be scrapped.
thanks
Max
> http://mysite.verizon.net/rtellason/pa020085.jpg
> I haven't seen the inside of one for a while, but this may be for a
> Fortune-32
> JAM or someone with a machine handy (Eric?) could confirm it.
Al - we have one of those machines here at the Personal Computer Museum
(pcmuseum.ca) - if you can give me a couple of days, I can confirm this if
nobody else has one handy.
I tend to look for the simpler explanations first.
If your keyboard was previously working,
the first place I would check is the MMJ
on the back of the terminal.
I've seen everything from malformed pins,
to corrosion, to spider webs, to dead bugs
inside RJ12 / RJ45 connectors.
Another point of failure is the?MMJ on the keyboard cable;
you can try removing that, and re-crimping it.
T
________________________________
Yo, Tony here (Sharkonwheels on VC)
Got any boards left? CPU board, ECB backplane, and (if ready) FDD/IDE board.
Tony
[snip]
-----REPLY-----
Hi Tony!
Thanks! Yes, I have several PCBs left. I have N8VEM SBCs, ECB backplanes,
and ECB bus monitor PCBs. I just received the ECB bus monitor PCBs and
haven't finished building mine yet. Some of the other builders are helping
out by taking the lead on the first ECB bus monitor for build and test phase
while I continue work on the Disk IO board.
The ECB backplanes are going fast which rather surprises me. I have only a
few left and am going to have to reorder. The builders who have ECB
backplanes seem to like them though.
The Disk IO prototype is working fine so I am writing up the schematic and
doing the PCB layout right now. I'll be posting the schematic and PCB
layout for some much appreciated peer review in the next few days. I am
still doing quality checking on them to make sure they are right. The IDE
portion looks OK but the FDC portion is complex and has me concerned. The
big difference between the prototype and the manufactured PCB will be
several option jumpers and a "feature" connector to help builders who want
8" drive support.
Thanks and have a nice day! Please contact me offline if you'd like some
PCBs. They are still $20 each plus shipping.
Andrew Lynch
Would anyone have a service manual for the Hazeltine 1410 terminal ?
I have a peculiar problem where several keys output a different
character. I found there's a pattern to this chaos. From looking at the
ascii data, bits 5 and 6 become swapped only for characters between 40h
and 5Fh. instead of an 'A' it displays a '!" and it continues like
this. I'm afraid the i8243 chip might be bad but I'm not completely
sure. I found the i8243 datasheet and currently trying to trace the
connections. I hear this chip is hard to come by. I only found one
supplier so far which I'm waiting to hear back on the rfq.
thanks
=Dan
--
[ Pittsburgh 250th --- http://www2.applegate.org/~ragooman/ ]