HECnet

hecnet@lists.dfupdate.se

1 participants
15560 discussions

by drb＠msu.edu

Seems like our link to SG1 has been down for weeks. I don't recall seeing anything on list. Anybody know what's up? Or perhaps I should ask if I need to do some local troubleshooting. :) De

9 years, 11 months

old problem with 11/34 solved

by mcguire＠neurotica.com

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 -- Dave McGuire, AK4HZ New Kensington, PA

9 years, 11 months

STSC APL*PLUS System for VAX VMS User's & Reference Manual

by mark＠wickensonline.co.uk

Kind reader 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 format. 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? Regards, Mark.

9 years, 11 months

RSX question

by mcguire＠neurotica.com

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 within RSX11M-Plus? Thanks, -Dave -- Dave McGuire, AK4HZ New Kensington, PA

9 years, 11 months

[Simh] Announcing TCP/IP for RSX-11M-PLUS

by bqt＠softjar.se

Aw, chucks. After reading the other day about someone who was talking about VMS and the wish for DHCP, I actually decided that it was time that BQTCP/IP also got DHCP. So, without further ado - I cut a new release. One bugfix for a bug in the TCP state machine, which could get stuck, but otherwise the big reason is that DHCP is now implemented. Read the documentation, or ask me questions. The IPGEN procedure will create installation files for use with DHCP, but if you are upgrading from a previous version, you might want to make comparisons with the new command files, and merge any new stuff in, if you want to use DHCP. If you don't care about DHCP, then nothing needs to change in the current configs. DHCP tries to be clever, and handle some different options, but there are parts that I do not use myself, that I have not tested, or sometimes implemented. In such cases you might see some messages on the console. Pass such information on to me, and I can improve things. DHCP is written in PDP-11 C. If you do not have that compiler, you will not be able to recompile the code. Sources are provided, along with a binary that runs, and do not depend on any shared libraries. The DHCP code also makes use of some functions and interfaces to the IP stack and the interface drivers that others might find useful to reference to if they are interested in doing low level stuff with TCP/IP. (Such as reading/writing interface configs and routing tables.) As usual, the distribution is available from: ftp://madame.update.uu.se/bqtcp.dsk ftp://madame.update.uu.se/bqtcp.tap ftp://ftp.update.uu.se/pub/pdp11/rsx/tcpip/tcpip.dsk The documentation is also available through ftp on Madame, or also at http://madame.update.uu.se/tcpipdoc I hope people will find this latest release useful, and my next project right now is telnet (this time really...). Johnny On 2015-06-08 19:03, Johnny Billquist wrote: > About three months since I last announced anything. There have been > various development since, and I figured I should encourage people who > are using BQTCP/IP for RSX to upgrade to the latest release. > > A short list of changes: > ICMP: > . ICMP packets accidentally lost the source IP address informaton when > returning information to a program. - Fixed. > > TCP: > . User timers on TCP sockets could erroneously stop. - Fixed. > . User timers now reset on completed reads, so that you do > not get a timeout if you are constantly completing reads. > . Sockets in Fin-Wait-2 could sometimes get stuck in that state. > - Fixed. > . If a TCP session got an RST, it could get into a bad state. - Fixed. > . Added the ability to send URGENT data in TCP. (Receive ignores any > URGENT flags.) > . Added a special I/O function to read from TCP without formatting. > > DNS: > . Improved stability of DNS client daemon code. > > FTP: > . FTP client and server performance improved. > . FTP server logging added. > . Improvements in FTP server and client for handling files with implicit > CFLF. > . Implemented primitive handling of Unix file paths implemented in FTP > server. This allows most web browsers to access FTP repositories > under RSX. > > I also did some performance testing using FTP. > > FTP from a modern Unix system of BQTCP.DSK in binary mode to both RSX > and 2.11BSD, running under simh on the same physical machine: > 2.11BSD: 210s > RSX: 141s > > From RSX (E11) to the same machines: > 2.11BSD: 240s > RSX: 137s > > I honestly do not know why transfer from RSX to 2.11BSD took longer than > from Unix, but transfer from RSX to RSX was faster compared to Unix to > RSX. I would have expected both to be slower or faster. But the numbers > are interesting, and show that the RSX TCP implementation is doing > fairly well, even through it goes through the DECnet ethernet driver, as > compared to 2.11BSD which runs TCP/IP more "native". > > As usual, the distribution is available from: > ftp://madame.update.uu.se/bqtcp.dsk > ftp://madame.update.uu.se/bqtcp.tap > ftp://ftp.update.uu.se/pub/pdp11/rsx/tcpip/tcpip.dsk > > The documentation is also available through ftp on Madame, or also at > http://madame.update.uu.se/tcpipdoc > > I hope people will find this latest release useful, and my next project > right now is telnet. > > Johnny > > On 2015-01-16 04:47, Johnny Billquist wrote: >> There have been lots of positive comments, and obviously some people >> have even tested using the software. >> >> Of course, a bug was also found. A really weird corner case with >> severely loading the network stack and having a socket in listen state >> programatically could trigger a corruption of kernel memory. >> >> So I've cut a new release with the bug fixed. >> >> While I'm at it I also realize that I forgot to mention that included in >> the distribution is also a simple IRC client as well as a simple IRC >> robot. >> >> I've also taken a little time to slightly improve the documentation, and >> the documentation is now also available directly by ftp from >> Madame.Update.UU.SE, so you do not need to get the whole distribution >> and unpack it to just read something. >> >> So - same as before. Disk image and tape image are available at >> Madame.Update.UU.SE. Use anonymous ftp. >> Disk image is also available at >> ftp://ftp.update.uu.se/pub/pdp11/rsx/tcpip. >> The disk image is a virtual RL02 disk. Can be used with any emulator, or >> also directly inside RSX if you have virtual devices available. >> >> Happy hacking. >> >> Johnny >> >> >> On 2015-01-14 00:40, Johnny Billquist wrote: >>> Well, it's been a long time project, but I'm happy to finally announce a >>> more public initial release of TCP/IP for RSX-11M-PLUS. >>> >>> This is the result of over 20 years of development. Needless to say, >>> I've been doing a lot of things over the years, and this code have been >>> through four reimplementations over the years. >>> What I now release is something that I believe is a nice and useful >>> piece of software. I am aware of the fact that most people do not use >>> these machines any longer, but if someone actually wants to talk to me >>> about support for this or other RSX software, let me know. >>> >>> Also, feel free to spread this information to anyone who might be >>> interested, anywhere. >>> >>> So - what is in this release? >>> It is a complete implementation of ARP, IP, UDP, and TCP for >>> RSX-11M-PLUS. It has been tested on RSX-11M-PLUS V4.6, but should work >>> on any V4 release. There might be some small tweaks or fixes required, >>> but nothing major. >>> It do require a system with split I/D-space, or else at least the TCP >>> part will not fit. >>> For Unibus machines, it should be possible to run without any additional >>> software except what is in a base RSX distribution. >>> For Q-bus machines, DECnet is required for ethernet networking. >>> The TCP/IP stack can co-exist with DECnet. >>> Some utilities also utilize RMS for file access. >>> >>> A bunch of tools, utilities and libraries are also included. These >>> include: >>> . IFCONFIG network configuration tool. >>> . NETSTAT network information tool. >>> . PING >>> . TRACEROUTE >>> >>> . DNS client >>> . FTP daemon >>> . FTP client >>> . HTTP server >>> . TELNET client (rudimentary) >>> . TFTP client >>> . TFTP server >>> . INET server that can do SINK, ECHO, DAYTIME, QUOTE, and IDENT >>> . NTP client >>> . LPR client that sits in the queue manager (rudimentary) >>> >>> . FORTRAN-77 library >>> . BASIC+2 library >>> . PDP-11 C library >>> >>> The implementation fulfills most of the requirements put forth in RFC >>> 1122. There are a few limitations because of restrictions in the PDP-11, >>> but none of them should really cause any problems. >>> >>> Documentation is still on the thin side, but example configs are also >>> provided, along with installation scripts. >>> >>> A bunch of test programs and example programs are also included, as well >>> as the sources of all tools and libraries. >>> >>> The TCP/IP stack itself only comes in binary form. >>> >>> All tools are also included precompiled in the distribution, so an >>> installation only have to build the stack itself for your system, and >>> then you should be ready to go. >>> >>> The API only have a slight resemblance to the Unix sockets API. However, >>> if someone sits down to write code to use TCP/IP under RSX, I'm sure >>> they will discover that it is extremely easy to use the libraries, or >>> the basic functions. >>> >>> The TCP/IP implementation is mostly written as device drivers. This also >>> have some other interesting implications, such as it is possible to >>> access TCP as a normal file. You can, for instance do something similar >>> to the Unix netcat command by issuing the MCR command: >>> >>> > PIP TI:=TC:"foo.com";4711 >>> >>> which would open a connection to foo.com, on port 4711, and any data >>> sent from that machine will be shown on the terminal. >>> >>> The resources used by TCP/IP are modest. A memory area (size selectable >>> at generation/startup) is used internally. The amount of memory in the >>> private pool limits the amount of data that can be buffered. Normal pool >>> is used in a small quantity for each TCP port that is open. >>> >>> People are welcome to play around with this, and make improvements. >>> Contributions of code is most welcome. >>> >>> There are still lots of things to do. The programs marked as rudimentary >>> should be rewritten. >>> The most obvious thing still missing is a telnet daemon, which probably >>> is my next step. >>> >>> However, the reason for now announcing the release is that it can >>> finally be distributed natively from an RSX host. >>> >>> The main locations to download the TCP/IP for RSX are: >>> >>> Madame.Update.UU.SE (anonymous ftp). >>> >>> This is one of my development systems for this software. It runs under >>> E11, and if things are down, I blame E11. :-) >>> When connected, you are already in the right directory. There is both an >>> RL02 disk image there, which can be downloaded by anyone. If you happen >>> to have an RSX system which you are conneting from, you can also try >>> getting the BQTCP.TAP tape image. Such an image will not transport >>> cleanly to a non-RSX system, however. Sorry. >>> >>> ftp.Update.UU.SE (anonymous ftp) - /pub/pdp11/rsx/tcpip >>> The disk image is normally duplicated to ftp.update.uu.se as well, so >>> the same file can be found there. >>> >>> I hope some people will find this useful/amusing. :-) >>> >>> Johnny Billquist >>> >> >> > > _______________________________________________ > Simh mailing list > Simh at trailing-edge.com > http://mailman.trailing-edge.com/mailman/listinfo/simh

9 years, 11 months

time-critical, need RSX sysgen help

by mcguire＠neurotica.com

Hi folks. I am trying to do a sysgen of RSX11M v4.6 on a PDP-11/34A with two RL02s, from the RL distribution. I'm trying to get a system running before VCF-East, for which I'm loading my truck in two days. I also have a lot of other work to do for my exhibit, so the problems I'm having with this sysgen are causing me heartburn. This is real hardware, not an emulator. It is stopping at seemingly random points, the most recent being during RSXASM. At least I'm pretty sure it had stopped at different points the first two times I did it. I get 'Task "...MAC" terminated, T-bit trap or BPT execution' and a register dump. This is going to tank a big part of my exhibit. Can anyone help me get past this? I last did an RSX11M sysgen probably 25 years ago; I don't consider myself to be well-versed in this anymore. Thanks, -Dave -- Dave McGuire, AK4HZ New Kensington, PA

9 years, 12 months

Assigned areas and unassigned areas

by gregg.drwho8＠gmail.com

Hello! Does a list exist someplace of what areas were assigned, and to who? Versus of course those that are unassigned of course. A fellow I know, bythe name of Jason Stevens,wrote an interesting package, he called it: HecnetNT HECnet for Windows And described it in a blog post here: http://virtuallyfun.superglobalmegacorp.com/category/decnet He says here: "It?s a port of Johnny Billquist?s bridge program to Windows." He describes on that blog post what he accomplished and more importantly how he did it. So as you might expect I'm interested in that area list. I can't safely say that I'll get something up soon, nor will be as active as say all of the current locations that all of you discuss. ----- Gregg C Levine gregg.drwho8 at gmail.com "This signature fought the Time Wars, time and again."

10 years

Assigned areas and unassigned areas

by hvlems＠zonnet.nl

Right now we've got 46 areas in use, out of ?63 possible areas. Each area can have 1023 nodes and few areas will have as many right now. I use area 44 and own probably the most systems but even then I only really need 70 addresses. Which means that even then we could at least accommodate 63*15=945 "sites" Verzonden?vanaf?mijn?BlackBerry?10-smartphone. ? Origineel bericht ? Van: Pontus Pihlgren Verzonden: maandag 15 juni 2015 08:48 Aan: hecnet at Update.UU.SE Beantwoorden: hecnet at Update.UU.SE Onderwerp: Re: [HECnet] Assigned areas and unassigned areas On Mon, Jun 15, 2015 at 03:38:44AM +0200, Johnny Billquist wrote: > On 2015-06-15 03:29, Ian McLaughlin wrote: > >This is remarkably impressive for a dead protocol on dead computers :) > > > >What happens when we run out of ares? > > We'll have to start using areas a little more efficient. But we'll > start dealing with that when we get there. > What is the limit? /P

10 years

Announcing TCP/IP for RSX-11M-PLUS

by bqt＠softjar.se

About three months since I last announced anything. There have been various development since, and I figured I should encourage people who are using BQTCP/IP for RSX to upgrade to the latest release. A short list of changes: ICMP: . ICMP packets accidentally lost the source IP address informaton when returning information to a program. - Fixed. TCP: . User timers on TCP sockets could erroneously stop. - Fixed. . User timers now reset on completed reads, so that you do not get a timeout if you are constantly completing reads. . Sockets in Fin-Wait-2 could sometimes get stuck in that state. - Fixed. . If a TCP session got an RST, it could get into a bad state. - Fixed. . Added the ability to send URGENT data in TCP. (Receive ignores any URGENT flags.) . Added a special I/O function to read from TCP without formatting. DNS: . Improved stability of DNS client daemon code. FTP: . FTP client and server performance improved. . FTP server logging added. . Improvements in FTP server and client for handling files with implicit CFLF. . Implemented primitive handling of Unix file paths implemented in FTP server. This allows most web browsers to access FTP repositories under RSX. I also did some performance testing using FTP. FTP from a modern Unix system of BQTCP.DSK in binary mode to both RSX and 2.11BSD, running under simh on the same physical machine: 2.11BSD: 210s RSX: 141s From RSX (E11) to the same machines: 2.11BSD: 240s RSX: 137s I honestly do not know why transfer from RSX to 2.11BSD took longer than from Unix, but transfer from RSX to RSX was faster compared to Unix to RSX. I would have expected both to be slower or faster. But the numbers are interesting, and show that the RSX TCP implementation is doing fairly well, even through it goes through the DECnet ethernet driver, as compared to 2.11BSD which runs TCP/IP more "native". As usual, the distribution is available from: ftp://madame.update.uu.se/bqtcp.dsk ftp://madame.update.uu.se/bqtcp.tap ftp://ftp.update.uu.se/pub/pdp11/rsx/tcpip/tcpip.dsk The documentation is also available through ftp on Madame, or also at http://madame.update.uu.se/tcpipdoc I hope people will find this latest release useful, and my next project right now is telnet. Johnny On 2015-01-16 04:47, Johnny Billquist wrote: > There have been lots of positive comments, and obviously some people > have even tested using the software. > > Of course, a bug was also found. A really weird corner case with > severely loading the network stack and having a socket in listen state > programatically could trigger a corruption of kernel memory. > > So I've cut a new release with the bug fixed. > > While I'm at it I also realize that I forgot to mention that included in > the distribution is also a simple IRC client as well as a simple IRC robot. > > I've also taken a little time to slightly improve the documentation, and > the documentation is now also available directly by ftp from > Madame.Update.UU.SE, so you do not need to get the whole distribution > and unpack it to just read something. > > So - same as before. Disk image and tape image are available at > Madame.Update.UU.SE. Use anonymous ftp. > Disk image is also available at ftp://ftp.update.uu.se/pub/pdp11/rsx/tcpip. > The disk image is a virtual RL02 disk. Can be used with any emulator, or > also directly inside RSX if you have virtual devices available. > > Happy hacking. > > Johnny > > > On 2015-01-14 00:40, Johnny Billquist wrote: >> Well, it's been a long time project, but I'm happy to finally announce a >> more public initial release of TCP/IP for RSX-11M-PLUS. >> >> This is the result of over 20 years of development. Needless to say, >> I've been doing a lot of things over the years, and this code have been >> through four reimplementations over the years. >> What I now release is something that I believe is a nice and useful >> piece of software. I am aware of the fact that most people do not use >> these machines any longer, but if someone actually wants to talk to me >> about support for this or other RSX software, let me know. >> >> Also, feel free to spread this information to anyone who might be >> interested, anywhere. >> >> So - what is in this release? >> It is a complete implementation of ARP, IP, UDP, and TCP for >> RSX-11M-PLUS. It has been tested on RSX-11M-PLUS V4.6, but should work >> on any V4 release. There might be some small tweaks or fixes required, >> but nothing major. >> It do require a system with split I/D-space, or else at least the TCP >> part will not fit. >> For Unibus machines, it should be possible to run without any additional >> software except what is in a base RSX distribution. >> For Q-bus machines, DECnet is required for ethernet networking. >> The TCP/IP stack can co-exist with DECnet. >> Some utilities also utilize RMS for file access. >> >> A bunch of tools, utilities and libraries are also included. These >> include: >> . IFCONFIG network configuration tool. >> . NETSTAT network information tool. >> . PING >> . TRACEROUTE >> >> . DNS client >> . FTP daemon >> . FTP client >> . HTTP server >> . TELNET client (rudimentary) >> . TFTP client >> . TFTP server >> . INET server that can do SINK, ECHO, DAYTIME, QUOTE, and IDENT >> . NTP client >> . LPR client that sits in the queue manager (rudimentary) >> >> . FORTRAN-77 library >> . BASIC+2 library >> . PDP-11 C library >> >> The implementation fulfills most of the requirements put forth in RFC >> 1122. There are a few limitations because of restrictions in the PDP-11, >> but none of them should really cause any problems. >> >> Documentation is still on the thin side, but example configs are also >> provided, along with installation scripts. >> >> A bunch of test programs and example programs are also included, as well >> as the sources of all tools and libraries. >> >> The TCP/IP stack itself only comes in binary form. >> >> All tools are also included precompiled in the distribution, so an >> installation only have to build the stack itself for your system, and >> then you should be ready to go. >> >> The API only have a slight resemblance to the Unix sockets API. However, >> if someone sits down to write code to use TCP/IP under RSX, I'm sure >> they will discover that it is extremely easy to use the libraries, or >> the basic functions. >> >> The TCP/IP implementation is mostly written as device drivers. This also >> have some other interesting implications, such as it is possible to >> access TCP as a normal file. You can, for instance do something similar >> to the Unix netcat command by issuing the MCR command: >> >> > PIP TI:=TC:"foo.com";4711 >> >> which would open a connection to foo.com, on port 4711, and any data >> sent from that machine will be shown on the terminal. >> >> The resources used by TCP/IP are modest. A memory area (size selectable >> at generation/startup) is used internally. The amount of memory in the >> private pool limits the amount of data that can be buffered. Normal pool >> is used in a small quantity for each TCP port that is open. >> >> People are welcome to play around with this, and make improvements. >> Contributions of code is most welcome. >> >> There are still lots of things to do. The programs marked as rudimentary >> should be rewritten. >> The most obvious thing still missing is a telnet daemon, which probably >> is my next step. >> >> However, the reason for now announcing the release is that it can >> finally be distributed natively from an RSX host. >> >> The main locations to download the TCP/IP for RSX are: >> >> Madame.Update.UU.SE (anonymous ftp). >> >> This is one of my development systems for this software. It runs under >> E11, and if things are down, I blame E11. :-) >> When connected, you are already in the right directory. There is both an >> RL02 disk image there, which can be downloaded by anyone. If you happen >> to have an RSX system which you are conneting from, you can also try >> getting the BQTCP.TAP tape image. Such an image will not transport >> cleanly to a non-RSX system, however. Sorry. >> >> ftp.Update.UU.SE (anonymous ftp) - /pub/pdp11/rsx/tcpip >> The disk image is normally duplicated to ftp.update.uu.se as well, so >> the same file can be found there. >> >> I hope some people will find this useful/amusing. :-) >> >> Johnny Billquist >> > >

10 years

decuslib.com domain expired

by system＠TMESIS.COM

Jim Carpenter <jim at deitygraveyard.com> writes: >Anybody here know who owns this domain? It expired May 22nd. Thanks. I've just addressed this. I don't know how this slipped but it's now been renewed. -- VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)ORG I speak to machines with the voice of humanity.

10 years

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

HECnet