HECnet October 2020

hecnet@lists.dfupdate.se

29 participants
22 discussions

by tim＠sneddon.id.au

For all those who have tunnels to my Cisco 1841, I have switched ISPs and as such my static IP address has changed. In my configuration I have the following endpoints configured: David Moylan (Area 35) Tomas Prybil (Area 34) Supratim Sanyal (Area 31) Brian Hechinger (Area 52) Ian McLaughlin (Area 42) Cory Smelosky (Area 9) Dave McGuire (Area 61) Peter Lothberg (Area 59) Mark Darvill (Area 22) Mark G Thomas (Area 23) If you are on that list could you please update your tunnel to use my new address, which is 163.47.57.118. Mark Berryman, my IPv6 address is unchanged, for the moment. Regards, Tim.

3 years, 10 months

DECnet for Linux Bug Fixes

by john＠forecast.name

Recently I have found, and fixed, a number of bugs in the DECnet for Linux kernel module. Some of these bugs may be relevant for members of this mailing list who are using DECnet for Linux, especially on a Raspberry Pi. Major bugs fixed: - Ethernet Listen Timer was not implemented In addition, the check for an address change for the designated router (DR) was missing although there was a check if the DR?s priority had changed. Note: this code changes the format of /proc/net/decnet_dev to include the listen timer value. nml/nml2 needs to be rebuilt to understand the changed format. - System panic when using the loopback device (lo) The DECnet code was missing a destructor routine which is used to avoid data copying. - The neighbour (adjacent node) code could be broken by kernel changes The code made use of a now deprecated feature (zero length array at the end of a structure) in order to access data in a surrounding structure. This happened to work ?by chance? until kernel 5.4.42 on 32-bit processors. - Interrupt message flow control was broken The flow control was a mixture of using the SEND/DONTSEND status of the data subchannel and a message count. This seems to work between Linux systems but is broken when communicating with other systems - during the life of a logical link, the remote system could only send a single interrupt message while the Linux system could pretty much send as many interrupts as it wanted possibly overrunning the remote systems buffers. - Optional data on received connect confirm message was corrupted The code was getting the optional data from the wrong offset in the message. - Next hop cache problem 30 seconds after a logical link was taken down, the next hop cache entry was deleted. As part of this deletion, the link was taken ?down? which caused a neighbour entry to be created for the same node address but accessed via the loopback device. Sometimes this would cause the designated router to become accessible via the loopback device and subsequent connections would fail. - Intra-ethernet bit ignored The intra-ethernet bit in the routing flags is ignored on inbound traffic. If there was a neighbour entry for the remote node at connection time, everything would work correctly. If there wad no entry, all outbound traffic would be sent through the designated router for the duration of the logical link. - Promiscuous mode alters DECnet behaviour If the ethernet NIC used for DECnet had promiscuous mode enabled (e.g. using tcpdump for traffic tracing), the DECnet code would start seeing endnode hello?s, populating neighbour structures and causing the problems described above for the intra-ethernet bit to go away. New programs: DECnet Test Send and DECnet Test Receiver (DTS/DTR) Test programs created via reverse engineering the protocol exchanges. Used to find a number of the bugs described above. NML2 New implementation of the Network Management Listener. Supports SUMMARY, STATUS and CHARACTERISTICS for NODES, CIRCUITS and AREAS. It does not support LINKS and OBJECTS which were in the old version but are system specific operations which were only visible from DECnet-VMS systems. The old version is still the default during installation. The new version can be installed by: cd dnprogs/nml2 make sudo make install which will overwrite the installed executable and man page. OS Support: As of 06/29/2020 the code has been tested with: Raspbian 2020-05-27 release with kernels 4.19.126 and 5.4.44 (32-bit only) Pi OS 2020-05-27 32-bit release with kernel 4.19.126 and 5.4.44 pI OS 2020-05-27 (fully updated on 06/26/2020) with kernel 5.4.49 The source code and installation instructions are available at: <https://github.com/JohnForecast/RaspbianDECnet <https://github.com/JohnForecast/RaspbianDECnet>> John.

4 years

Guest access to a VMS IA64 server on HECnet?

by Keith.Halewood＠pitbulluk.org

Hi, Are there any owners of IA64-based VMS servers on HECnet with either some sort of guest access, or willing to give/loan me a guest account so that I can compile a pascal program or two? I'm interested in the sort of code produced (PASCAL/LIST/MACHINE_CODE) and also more generally interested in the 'feel' of VMS running on such a beast anyway. I go to say or type O___VMS but it seems that only the VMS bit makes it out. Regards Keith

4 years

Announcing RPM, a software packet manager for RSX-11M-PLUS

by bqt＠softjar.se

There is SLIP... ;-) I have never tried the SLIP code, but I did write it. It could be an interesting test... (I also have the skeleton of PPP, but I have not completed that one...) But anything on a beaglebone or whatever will not really help. You need some kind of interface on the PDP-11 side either way. Ethernet is the obvious first choice, but serial lines is (I guess) the next best thing. Serial DECnet or serial IP don't make much difference, except I think you'd find serial IP more useful in the long run. Once you have even that, you could run DECnet over IP if you wanted to join in a DECnet sense. Johnny On 2020-10-25 18:24, Chris Zach wrote: > I *really* need to find a DEQNA and get tcp/ip running on my 11/83. This > system is feeling lonely. Unless.... Is there a Decnet to TCP/IP > beaglebone code out there that I could use to peer up to MAGICA? > > CZ > > On 10/24/2020 1:40 PM, Johnny Billquist wrote: >> RPM is a packet manager for RSX (it has nothing to do with the Red Hat >> Packet Manager, except the name). >> >> I don't post regularly about this software, nor about updates to the >> list of available packages, but enough work have been done, and a long >> enough time have passed since the initial announcement that an update >> can be useful for various people. >> >> >> Since the initial release of RPM, a lot of improvements have been done >> to it, and a lot of packages have been updated or added. For anyone >> running RSX-11M-PLUS, I would really recommend installing RPM, and using >> it to get the latest version of various software. >> >> For information on how to install and use it, see >> http://mim.update.uu.se/rpm.htm >> >> >> The current list of packages: >> >> In? Pkg??????? Ver???? Desc >> ?? --? ---??????? ---???? ---- >> ?????? RPM??????? Y0.27?? The RSX Packet Manager >> ?????? MKE??????? V1.31?? The Unix-like make tool >> ?????? TCPIP????? V2.5??? TCP/IP for RSX-11M-PLUS >> ?????? C????????? 000012? PDP-11 C compiler >> ?????? CRTL?????? V1.2??? PDP-11 C runtime library >> ?????? F77??????? T5.4??? FORTRAN-77 compiler >> ?????? F77RTL???? V5.4??? FORTRAN-77 runtime library >> ?????? BP2??????? V2.7C?? BASIC+2 compiler and interactive environment >> ?????? BP2RTL???? V2.7C?? BASIC-PLUS-2 runtime library >> ?????? C81??????? V3.1??? COBOL-81 compiler >> ?????? C81RTL???? V3.1??? COBOL-81 runtime library >> ?????? BCPL?????? BCPL04? The DECUS BCPL compiler >> ?????? FORTH????? V1.3.3? FORTH language for RSX-11M-PLUS >> ?????? SORT?????? V3.0??? SORT/MERGE for RSX >> ?????? DBG??????? T2.2.1? PDP-11 Symbolic Debugger >> ?????? DTR??????? V03.03? DATATRIEVE-11 for RSX >> ?????? FMS??????? V02.2?? FMS-11 for RSX >> ?????? NEMA?????? Y0.32?? The small portable Emacs-compatible editor >> ?????? TECO?????? V40.00? The Text Editor and COrrector (and language) >> ?????? TIN??????? V1.7??? Task INformation tool >> ?????? ATT??????? V01???? File attribute manipulation tool >> ?????? GREP?????? 000007? Tool to search through text files >> ?????? MORE?????? 2.17??? Interactive text file viewer (VTL) >> ?????? NTAIL????? X0.2??? Text file tail printout >> ?????? ERR??????? X0.2??? Display error messages based on codes >> ?????? USH??????? X0.2??? Unix shell like pipes >> ?????? KERMIT???? T3.63?? The KERMIT file transfer program >> ?????? RNO??????? 2000.1? The BONNER Lab RUNOFF document processor >> ?????? SRD??????? 6.9.2?? The DECUS directory maintenance tool >> ?????? COD??????? V1.5??? File encoder/decoder >> ?????? SWATCH???? V01.01? Stop watch for commands >> ?????? SYM??????? V1.1??? Examine symbols in OBJ and STB files >> ?????? VTL??????? V01.0?? Virtual Terminal Log utility >> ?????? ORCAM????? V01.7?? Object file disassembler >> ?????? DOB??????? V2.2??? Object file disassembler >> ?????? CLEACD???? V7.12?? The Command Line Editor ACD >> ?????? CCL??????? V9.3??? User configurable Command Line Interpreter >> ?????? CURSES???? X0.1??? A Unix compatible curses library for PDP-11 C >> ?????? ZEMU?????? V1.24?? The Z-machine emulator >> ?????? DUNGEON??? V3.2C?? The classic dungeon >> ?????? ADVENT???? 03MAR?? The classic adventure game >> ?????? MILLE????? V1.5??? The Mille Bournes card game >> >> >> Yes, this now includes various layered software from DEC, prebuilt for >> M+ I/D systems. I have lots of more software that I intend to add, but >> this is already starting to become a significant list. >> >> ????Johnny >> -- Johnny Billquist || "I'm on a bus || on a psychedelic trip email: bqt at softjar.se || Reading murder books pdp is alive! || tryin' to stay hip" - B. Idol

4 years, 1 month

Third Release of Route20 User Mode DECnet Router

by robert.jarratt＠ntlworld.com

Hello Everyone, As some of you may be aware, I have been writing my own DECnet router. Since the last formal release a few years ago I have added a few things, the details are here https://github.com/rjarratt/Route20. These were all on the Dev branch, which I know a few people have tried. I have been running the Dev branch for a long time myself, so I am sure it is stable. All I have done really is make the current Dev branch "official" by merging it to the master branch. I know Paul has been much more active than me lately on this front, so I am probably a bit behind, but if anyone would like to take a look that would be great. Regards Rob

4 years, 1 month

Announcing RPM, a software packet manager for RSX-11M-PLUS

by bqt＠softjar.se

RPM is a packet manager for RSX (it has nothing to do with the Red Hat Packet Manager, except the name). I don't post regularly about this software, nor about updates to the list of available packages, but enough work have been done, and a long enough time have passed since the initial announcement that an update can be useful for various people. Since the initial release of RPM, a lot of improvements have been done to it, and a lot of packages have been updated or added. For anyone running RSX-11M-PLUS, I would really recommend installing RPM, and using it to get the latest version of various software. For information on how to install and use it, see http://mim.update.uu.se/rpm.htm The current list of packages: In Pkg Ver Desc -- --- --- ---- RPM Y0.27 The RSX Packet Manager MKE V1.31 The Unix-like make tool TCPIP V2.5 TCP/IP for RSX-11M-PLUS C 000012 PDP-11 C compiler CRTL V1.2 PDP-11 C runtime library F77 T5.4 FORTRAN-77 compiler F77RTL V5.4 FORTRAN-77 runtime library BP2 V2.7C BASIC+2 compiler and interactive environment BP2RTL V2.7C BASIC-PLUS-2 runtime library C81 V3.1 COBOL-81 compiler C81RTL V3.1 COBOL-81 runtime library BCPL BCPL04 The DECUS BCPL compiler FORTH V1.3.3 FORTH language for RSX-11M-PLUS SORT V3.0 SORT/MERGE for RSX DBG T2.2.1 PDP-11 Symbolic Debugger DTR V03.03 DATATRIEVE-11 for RSX FMS V02.2 FMS-11 for RSX NEMA Y0.32 The small portable Emacs-compatible editor TECO V40.00 The Text Editor and COrrector (and language) TIN V1.7 Task INformation tool ATT V01 File attribute manipulation tool GREP 000007 Tool to search through text files MORE 2.17 Interactive text file viewer (VTL) NTAIL X0.2 Text file tail printout ERR X0.2 Display error messages based on codes USH X0.2 Unix shell like pipes KERMIT T3.63 The KERMIT file transfer program RNO 2000.1 The BONNER Lab RUNOFF document processor SRD 6.9.2 The DECUS directory maintenance tool COD V1.5 File encoder/decoder SWATCH V01.01 Stop watch for commands SYM V1.1 Examine symbols in OBJ and STB files VTL V01.0 Virtual Terminal Log utility ORCAM V01.7 Object file disassembler DOB V2.2 Object file disassembler CLEACD V7.12 The Command Line Editor ACD CCL V9.3 User configurable Command Line Interpreter CURSES X0.1 A Unix compatible curses library for PDP-11 C ZEMU V1.24 The Z-machine emulator DUNGEON V3.2C The classic dungeon ADVENT 03MAR The classic adventure game MILLE V1.5 The Mille Bournes card game Yes, this now includes various layered software from DEC, prebuilt for M+ I/D systems. I have lots of more software that I intend to add, but this is already starting to become a significant list. Johnny -- Johnny Billquist || "I'm on a bus || on a psychedelic trip email: bqt at softjar.se || Reading murder books pdp is alive! || tryin' to stay hip" - B. Idol

4 years, 1 month

Announcing TCP/IP V2.5 for RSX-11M-PLUS

by bqt＠softjar.se

Time for a new release announcement of TCP/IP for RSX-11M-PLUS. Since I have now started to try and properly number releases, this is release V2.5 of BQTCP/IP. It's been five months since the last official update, and there been various smaller improvements. Highlights: . Improved startup scripts making the whole process more safe. . Performance improvements in many places. . Added LPR protocol to LPT symbiont spooler. Detailed information on things that have been done since the last release: Startup: . If CEX does not exist, try to load XE: driver automatically. If IPAPPL is executed but there is no IP: loaded, exit immediately. IP: . Added class broadcast address handling. TCP: . Added PU.ACK as an option on TCP ports. . Improved TCP ACK strategy. . Improved default TCP configuration. . Improved TCP push handling. Only set PSH on last packet of sequence of packets included in push. . Corrected reads from TCP. Under some circumstances, read could return IE.NLN on a closed socket, when it should have returned IE.EOF. . Improved TCP fast retransmit logic. . Bugfix in TCP. Make sure congestion window never goes below MSS. . Rewritten the TCP congestion avoidance and slow start logic. . Impoved TCP window update logic. . Reworked TCP MSS logic to better handle if MSS is asymetric. . Improve TCP retry logic in case of remote side constantly ACKing old data. Connection should eventually be closed. DNS: . Added handling of zero length domain names in DNS. FTP/FTPD: . Improved FTP and FTPD push strategy. . Added port number to host string in FTPD login message. . Changed FTP client to probe for RSX system to after login. (Some Linux ftp servers are broken, and gives multiple responses to commands given before logging in.) . Reworked FTP client ETA computation. . Added check in FTP if run from VT device, and disable progress bar. . Improved error handling in FTPD. . Bugfix in FTP. Under some circumstances, a successful GET could end up deleted the received file. (Reported by Ludwig Tauer) TELNET/TELNETD: . Modified telnet server to use PU.ACK. . Improved TELNET and TELNETD push strategy. . Bugfix in telnet client. It could loose input terminal characters in some circumstances. . Bugfix in telnet client. It could get into a state where it stopped reading from the terminal. LPT: . Added LPR protocol to LPT. MAIL: . Improved network reject error handling in MAIL11 sending. . Changed mail queue output format. . In MAIL, make sure addresses are properly reformatted when receiving mails over MAIL11. . In MAIL, when sending over SMTP, strip any DECnet part of destination address. Does not make sense to keep that. . Added SMTP Source domain logical name for outgoing mails. . Improved mail headers content. Some additional notes: As usual, I would recommend people to update as soon as possible. The changes are not critical, but will lead to a much better experience. For the RSX fixes to be applied, it is necessary to answer yes to the question about installing RSX patches. Otherwise those fixes will not be installed. This does not lead to any failures, but it might lead to some components running exactly the way you might be expecting (such as daemons running under the wrong user). As usual, the distribution is available from: ftp://mim.update.uu.se/bqtcp.dsk ftp://mim.update.uu.se/bqtcp.tap ftp://ftp.update.uu.se/pub/pdp11/rsx/tcpip/tcpip.dsk (As an additional note, I have become aware of that there is some device proxying access to the ftp service at Mim. This might lead to failure to transfer large files. If you observe such problems, try connecting to Mim at port 10021 instead, which is an alternative port for the ftp server, and which circumvents the proxy.) The documentation is also available through ftp on Mim, or also at http://mim.update.uu.se/tcpipdoc I hope people find this update useful. Johnny -- Johnny Billquist || "I'm on a bus || on a psychedelic trip email: bqt at softjar.se || Reading murder books pdp is alive! || tryin' to stay hip" - B. Idol

4 years, 1 month

[simh] Decnet8: Who has any knowledge about this product and has seen it actually working in whatever versions? Cross post from Hecnet --> @John

by R.Voorhorst＠swabhawat.com

@John Forecast: Hi John, The oddity is just the other way around ?. The release date of the primitive software, say Phase-I+ is dated at 8-april-1977. The Nip printout is dated 28-dec-1976 which aligns with your story. So why ship something clearly broken with an obvious simple bug that should have been easily catched with a minor level of release quality control. When the Pdp8 development was dropped around may-1977, why not release the current stuff instead? Some form of date editing in the software was clearly done on package level as the date 8-apr-77 appears all over the place, but why for a product at that time already 1-3 years ago? Best regards, Reindert From: simh at groups.io [mailto:simh at groups.io] On Behalf Of John Forecast Sent: Thursday, 22 October, 2020 17:23 To: simh at groups.io Subject: Re: [simh] Decnet8: Who has any knowledge about this product and has seen it actually working in whatever versions? Cross post from Hecnet On Oct 19, 2020, at 6:07 PM, R_Voorhorst <simh at swabhawat.com <mailto:simh at swabhawat.com> > wrote: The following oddities ? amongst more - can be seen: 1. The date is 28-dec-76, the various edit dates in the current software are all centered on april/may-77. 2. Ddcmp is dated 7-apr-77 with version 1A, the doc mentiones already 4B 3. KL8 ISR is versioned 3A while the current available version is 1A and dated at 8-apr-77 4. And then the Nip version V1 as documented is older than the V1C version of the internet release!! If these dates are correct it?s unlikely this code is Phase II. Phase II design was mostly done in 1976 (maybe late 1975) with protocol design along with prototype code running standalone on various PDP-11?s. In January 1977 a group was constituted in the Mill to develop networking products (mostly DECnet) for RSX-11M/S/D/IAS, RT-11 and the PDP-8 (I joined that group in late January 1977). In early May, there was an off-site meeting to finalize the API?s that the RSX systems would use - running code wasn?t available for another 4 or 5 months. Around that May timeframe the PDP-8 development was dropped, I don?t know if it was cancelled or transferred back to the OS group (as later happened with RT-11). As Johnny pointed out it?s more likely to be a snapshot of the Phase II development specs from late 1976 - bug fixes/changes were happening all through the summer of 1977. John. And there are a lot more things going on. So the bottom question remains: has anyone seen the internet versions working or is there a clobber up between an advanced laboratory (Phase-II??) version as documented (look at the Ddcmp versions) and a preleased or prior old Decnet version. And if so, can anything be retrieved or is it lost forever. Best regards, RV _._,_._,_ _____ Groups.io Links: You receive all messages sent to this group. View/Reply Online (#223) <https://groups.io/g/simh/message/223> | Reply To Group <mailto:simh at groups.io?subject=Re:%20Re%3A%20%5Bsimh%5D%20Decnet8%3A%20Who%20has%20any%20knowledge%20about%20this%20product%20and%20has%20seen%20it%20actually%20working%20in%20whatever%20versions%3F%20Cross%20post%20from%20Hecnet> | Reply To Sender <mailto:john at forecast.name?subject=Private:%20Re:%20Re%3A%20%5Bsimh%5D%20Decnet8%3A%20Who%20has%20any%20knowledge%20about%20this%20product%20and%20has%20seen%20it%20actually%20working%20in%20whatever%20versions%3F%20Cross%20post%20from%20Hecnet> | Mute This Topic <https://groups.io/mt/77669945/4811914> | New Topic <https://groups.io/g/simh/post> Your Subscription <https://groups.io/g/simh/editsub/4811914> | Contact Group Owner <mailto:simh+owner at groups.io> | Unsubscribe <https://groups.io/g/simh/leave/8621341/991916336/xyzzy> [simh at swabhawat.com] _._,_._,_

4 years, 1 month

Decnet8: Who has any knowledge about this product and has seen it actually working in whatever versions?

by R.Voorhorst＠swabhawat.com

L.S. Currently I am finishing testing for the release of the last member of the Pdp8 series computers: Simh Pdp8a with some new devices (and some from old not present in Ppd8). Current state of affairs is, that it is running Os8 V3S 128k monitor and the Kt8 diagnostics and is stable. Also F4 runs and basic Rts8 V2b and V3. The last hurdle is to activate Decnet8 as the last test station to really load a Pdp8 with some realistic real time work. However ?. Activating Decnet8 leads to a lot of funny but nasty surprises and is tedious at best. Basic software can be found on the internet with only 2 flavors of Nip and Nsp which differ only slightly. The setup, assembling and loading is easy enough, though Nip02 uses a thing that is only available in Rts8 V3 exec although it was released for V2b. That should be catched with prerelease testing. The initial point is already, that the Ddcmp lines are not starting up automatically. Looking in the code there are pointers to things with temp status or not implemented, like the STRTUP function code in Nsp which might be needed to startup the lines. There are quite some discrepancies between current available Decnet8 and the documentation in Decnet8.pdf as can be seen with the Nip report: According to the Decnet8 doc copyrighted in 1977, the example display of status looks as follows: 4.5 SAMPLE NIP PRINTOUT The following is a typical NIP printout: NETWORK INFORMATION PROGRAM V1 PHYSICAL LINE STATUS [DDCMP V4B] LINE NODNAM (#) STATE DRIVER VRSN UP SINCE 0 ACTON (3) ON-LINE KL8J 3A 8:03:35 28-DEC-76 1 MAYNRD (2) OFF-LINE DKC8 2B 2 CONCRD (5) STARTING LOCAL 15A LOGICAL LINK STATUS [NSP VllE] CHAN STATE LINE TASK SRCE-NAME[PPN] TYPE LINK DEST-NAME[PPN] TYPE LINK 1 IN-USE 0 12 TARZAN[6,0] 10 4 JANE [3,1] 7 6 2 WAKING 1 3 DONALD[2,2] 3 3 3 UNUSED 1 3 DUMMY [4,4] 29 14 4 BOOT 2 6 MASS [1,23] 3 44 PHYSICAL LINE ERROR STATUS LINE 0: 3 NAKS WITH HEADER CRC ERRORS 5 NAKS WITH DATA CRC ERRORS 83 NAKS WITH REP ERRORS 1 NAK WITH BUFFER UNAVAILABLE 2 NAKS WITH HEADER FORMAT ERRORS 192 NAKS WITH MESSAGES TOO LONG 100 MSGS WITH HEADER CRC ERRORS 1 MSG WITH REP ERROR 1 MSG WITH DATA OVERRUN 10 MSGS WITH HEADER FORMAT ERRORS 9 MSGS WITH MESSAGES TOO LONG LINE 1: NO ERRORS LINE 2: 3 NAKS WITH DATA OVERRUNS 1 MSG WITH REP ERROR A real printout on the current generated system is as follows: NETWORK INFORMATION PROGRAM V1C PHYSICAL LINE STATUS [DDCMP V1A] LINE NODNAM (#) STATE DRIVER VRSN UP SINCE 0 UNKNOWN***** OFF-LINE KL8J 1A LOGICAL LINK STATUS [NSP V1C] CHAN STATE LINE TASK SRCE-NAME[PPN] TYPE LINK DEST-NAME[PPN] TYPE LINK 1 UNUSED 0 36 TLK [1,2] 0 0 PHYSICAL LINE ERROR STATUS LINE 0: NO ERRORS 0 MESSAGES TRANSMITTED 0 MESSAGES RECEIVED The following oddities ? amongst more - can be seen: 1. The date is 28-dec-76, the various edit dates in the current software are all centered on april/may-77. 2. Ddcmp is dated 7-apr-77 with version 1A, the doc mentiones already 4B 3. KL8 ISR is versioned 3A while the current available version is 1A and dated at 8-apr-77 4. And then the Nip version V1 as documented is older than the V1C version of the internet release!! And there are a lot more things going on. So the bottom question remains: has anyone seen the internet versions working or is there a clobber up between an advanced laboratory (Phase-II??) version as documented (look at the Ddcmp versions) and a preleased or prior old Decnet version. And if so, can anything be retrieved or is it lost forever. Best regards, RV

4 years, 1 month

Pathworks for VMS V4.1 kit anywhere ?

by wboerhout＠gmail.com

Hi folks, I have become the proud owner of a VAXmate workstation, with a disk enclosure pizzabox attached. It is working in that it attempts to boot from disk (which fails), and then boots from the network, and I see a load request coming in on my VAX. Now I am looking for the supporting software. It looks like Pathworks V4.1 could be of use. I have tracked a kit PCSACLIENT041 (.A and .B), but it requires the PCSA041 server kit, of which, oddly enough, I do have .B but not .A Is the PCSA041 kit available on HECnet somewhere ? *Wilm*

4 years, 1 month

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

HECnet October 2020