I'm happy to announce a new release of TCP/IP for RSX-11M-PLUS.
Since I'm broadening the scope of the announcement slightly, a more
complete list of features is included, and not just what changed since
last. For anyone who is currently running TCP/IP for RSX, I strongly
encourage you to update to this latest version. Several improvements
have gone in in the last couple of weeks. Most important change is that
there now is telnet support, both client and server side.
The TCP/IP for RSX that I've written is sometimes referred to as
BQTCP/IP, just to make clear that it is a different product than Process
Software's TCPWARE, or JSA's TCP/IP.
BQTCP/IP is a rather feature rich TCP/IP implementation, which also
comes with libraries for various high level languages. The API is not
compatible, even at the source level, with Unix, but on the other hand,
if people write some code, they will see that it is a very easy API to
work with. The reasons for the incompatibilities are several, including
both resource concerns and differences between how RSX works and Unix
like operating systems.
BQTCP/IP has tried to comply with all relevant RFCs, but I'm sure there
are corners where it does not do things right. It also does not demand
much resources. It do require RSX-11M-PLUS with split I/D space, and it
has only been tested properly on RSX-11M-PLUS V4.6. It should work on
any version 4 release of RSX-11M-PLUS, but there might be a couple of
tweaks or fixes needed.
BQTCP/IP is distributed in binary form, so very little compilation is
required to get it up and running. However, pretty much all utilities do
come with sources. The actual TCP/IP stack sources are not included. I
do not have a good setup for distributing them in a sane way, and it has
had a low priority on my list of things to do. But I do not mind
distributing the sources as a general principle.
All that said, BQTCP/IP current supports the following protocols:
o Ethernet and loopback interfaces.
o ARP. BQTCP/IP can use Ethernet in co-existance with DECnet, or
standalone using the provided Unibus ethernet device driver.
o IP. The largest IP packets supported are approximately
o UDP. The largest UDP packets supported are approximately
o TCP. The window is approximately 8KB in size, and TCP do
manage out of order packets in an efficient way.
BQTCP/IP supports the following applications:
o DHCP. DHCP can be used to configure interface addresses, network
masks, default gateways, DNS servers and NTP servers dynamically.
o NTP. NTP can be used to set the local time.
o TELNET. The TELNET server hooks in to the standard TT: terminal
driver, and the number of terminals to create is configurable.
The TELNET client can be used to connect to other systems.
o FTP. The FTP server can serve all kind of files to other RSX
systems, and can serve text and binary files to any system.
The FTP client can retrieve RSX format files from RSX servers,
and text, binary and block format files from any system.
o TFTP. The TFTP server and client can be used for simpler file
o RWHOD. RWHOD is a program that reports current users and uptime
from RSX, for other systems to collect.
o IRC. IRC is a program to communicate with other users around
o IRCBOT. IRCBOT is a small example robot program connecting to IRC
and performing a service for IRC users.
o PCL. PCL is a protocol for printing, used by HP (and other) printers
over a network. The PCL implementation in BQTCP/IP appears as a
print symbiont, which you can create a printer queue for.
o WWW. WWW (or World Wide Web) is a service that can present hypertext
information to clients. The WWW server in BQTCP/IP also supports CGI,
which makes it possible to create dynamic content.
o DNS. BQTCP/IP have DNS implemented as an ACP, that anyone can query
to get translations between IP addresses and domain names. It also
supports different users using different name servers, or private
o SINK. A standard TCP service.
o ECHO. A standard TCP service.
o DAYTIME. A standard TCP service.
o QUOTD. A standard TCP service.
o IDENTD. A standard TCP service.
BQTCP/IP also have automatic IP spoof detection and prevention.
Additional tools are IFCONFIG, PING, TRACEROUTE, NETSTAT as well as two
new pages for RMD.
High level language libraries exists for BASIC+2, PDP-11 C and FORTRAN-77.
I'm sure I have forgotten a thing or three, but that's a fairly
The documentation is a weak point, but there is hopefully enough
documentation to get people running, and I am happy to answer any
questions, or give support if needed. BQTCP/IP is already running on the
internet, and have been for a while. People who are curious to check it
out can ether look at http://madame.update.uu.se/, or telnet to
telnet://madame.update.uu.se and login as user GUEST with password
GUEST, or use ftp against ftp://madame.update.uu.se. Anonymous ftp
As usual, the distribution is available from:
The .tap file is an RSX virtual tape. It is only possible to download
and use if you are using FTP from anther RSX system and fetch the file.
The .dsk files are virtual RL02 images that are useful both from within
RSX as well as through emulators.
The documentation is also available through ftp on Madame, or also at
Has anyone heard from Sampsa (Laine) lately?
All of my connections to him are "down" and after a good amount of time I
sent him an email, and received no response, but didn't receive a bounce.
Hopefully it isn't too bad a form to post this to the HECNet list, but I
figured most folks here would be the likely candidates to have heard from
Jim Carpenter <jim at deitygraveyard.com> writes:
>Does anyone here happen to have that SPL? I have it but my CD 5
>(AXPBINSEP085) has a scratch on the label side. I can only read about
>the first half. (
>Of course a newer SPL would work too. ;) I'd like to use OpenVMS 8.4
>but will I have problems using such an old SPL with it?
I'm certain I do. Send me a private email about it, and I'll pull it out of
my archives and make an image of it for you. I have to pickup my kid sister
at the airport today and deliver her to my mom's house, so I wouldn't be able
to do this until tomorrow.
VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)ORG
I speak to machines with the voice of humanity.
Hey folks. Remember when I was losing my mind trying to get my
PDP-11/34 up and running RSX-11M just before VCF-East in April, and it
kept crashing during sysgen?
Well...it turns out that my FP11-A board was flaky. It failed some of
its tests in XXDP. Then I ran some XXDP tests on the processor itself,
and it failed in a couple of places in the MMU tests. That explains why
it ran RT11 just fine, but not a more demanding-on-the-MMU OS like RSX.
So I replaced the FP11-A with one that passes its tests (no time to
troubleshoot it right now, and I have a few spares) and was about to
start working on the CPU, when I decided to re-run the MMU tests. Now
the MMU checks out fine. I put the originally flaky FP11-A board back,
and the MMU tests fail again...so somehow this FP11-A is wreaking havoc
with the MMU.
So now the machine is about midway through phase II of sysgen, running
great, and seems to be rock solid.
Dave McGuire, AK4HZ
New Kensington, PA
I have two manuals labelled STSC APL*PLUS System for VAX VMS: User's
Manual and Reference Manual which were sent to me a number of years ago
as paper copies - I now have the ability to easily scan these into PDF
Would these be of interest to anyone? There is a PC version archived
here http://www.math.uwaterloo.ca/apl_archives/apl/apl-plus/ that might
benefit from the additional documentation. I've contacted Lee about this.
I am interested if anyone has any history of this software (there are
some general references out there about the STSC Mainframe and later PC
versions) - and indeed if the software survived at all.
Was VAX/VMS APL based on this version?
Hey folks, can anyone here (Johnny maybe?) tell me if there's a
programmatic way to tell if a PDP-11/70 has an FP11-C installed, from
Dave McGuire, AK4HZ
New Kensington, PA