HECnet

hecnet@lists.dfupdate.se

4 participants
15583 discussions

by system＠TMESIS.COM

Tony Blews <tonyblews at gmail.com> writes: >Hi > >I may have asked this before, but its bugging me again and I can't remember >the answer, or find a simple explanation online anywhere... > >Having just installed TARDIS again with OpenVMS7.3 everything seems to work >fine apart from mail over TCPIP. This throws up: > >%JBC-E-JOBQUEDIS, system job queue manager is not running >$ start/queue/manager >Message from user JOB_CONTROL on TARDIS >-RMS-E-FNF, file not found >%JBC-E-QMANNOTSTARTED, queue manager could not be started >$ > >Any ideas (and I promise I'll save the answer this time)? I have lots and lots of ideas. However, I'm sure you'd like to know how to start the queue manager over learning about my ideas. I'd suggest that you first create the queue manager before you try to start it. $ START/QUEUE/MANAGER/NEW_VERSION $ START/QUEUE/MANAGER You will then need to INITIALIZE/QUEUE to create your queues. FYI, "$ HELP" might answer your questions. -- VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)ORG I speak to machines with the voice of humanity.

7 years, 9 months

Stupid question about VMS queues again.

by tonyblews＠gmail.com

Hi I may have asked this before, but its bugging me again and I can't remember the answer, or find a simple explanation online anywhere... Having just installed TARDIS again with OpenVMS7.3 everything seems to work fine apart from mail over TCPIP. This throws up: %JBC-E-JOBQUEDIS, system job queue manager is not running $ start/queue/manager Message from user JOB_CONTROL on TARDIS -RMS-E-FNF, file not found %JBC-E-QMANNOTSTARTED, queue manager could not be started $ Any ideas (and I promise I'll save the answer this time)? Thanks, Tony.

7 years, 9 months

pdp-11/VAX racks and chassis free to good home

by Alastair.Boyanich＠au.fujitsu.com

G?day, Picked up a 11/73 several years past off Grog which came with a couple of the chest height DEC 19? Cab?s which housed the /73 and some RL02 and TS05. One I?m using with the /73 upstairs. The second is surplus to requirements. New car means I need to find a home for it. Item location is North Shore New South Wales (Australia). Price is free, and half-price on Tuesdays. Second rack is a little knee high one that the 11v03 (Yep it?s v03 not /03) came in. Faux wood and round bubble wheels. Also a bunch of Tru64 ops and dev manuals will need to be gone so anyone interested there Also please stick your hand up. The knee high rack is: http://ns4.reboot.net.au/pdp11-03/20150517_123020.jpg The chest high rack is the usual fare with rounded edges and black cladding sides. Would also suit standard 19? comms and rack servers I know. Nice to have period things. Any takers? I?d love these things to goto another home that would love them rather than a serious conversation with my reciprocal saw. ? Sadly. Best Wishes, Al Disclaimer The information in this e-mail is confidential and may contain content that is subject to copyright and/or is commercial-in-confidence and is intended only for the use of the above named addressee. If you are not the intended recipient, you are hereby notified that dissemination, copying or use of the information is strictly prohibited. If you have received this e-mail in error, please telephone Fujitsu Australia Limited on 02 9776 4555 or by reply e-mail to the sender and delete the document and all copies thereof. Whereas Fujitsu Australia Limited would not knowingly transmit a virus within an email communication, it is the receiver?s responsibility to scan all communication and any files attached for computer viruses and other defects. Fujitsu Australia Limited does not accept liability for any loss or damage (whether direct, indirect, consequential or economic) however caused, and whether by negligence or otherwise, which may result directly or indirectly from this communication or any files attached. If you do not wish to receive commercial and/or marketing email messages from Fujitsu Australia Limited, please email unsubscribe at au.fujitsu.com.

7 years, 9 months

DECnet Phase IV through Linux GRE Tunnel?

by nf6x＠nf6x.net

One of the suggestions that was posted here for how one might connect to HECnet was to create a GRE tunnel to a cooperative node, using either a Cisco router or an emulation of one. I don't have any experience with Cisco stuff, and I don't feel enthusiastic about going down that particular rabbit hole just yet if I can find another approach more in line with my experience and interests. I see that there is GRE support in Linux, at least for IP-in-IP tunneling. Do any of y'all know if Linux's GRE support can tunnel non-IP protocols such as DECnet Phase IV? So far I've only succeeded in finding documentation about how to set up IP-in-IP tunneling, and I don't understand what's going on under the hood yet. Since I want to keep my local DECnet traffic local, my current goal is to set up a VAX/OpenVMS simulation under SIMH to act as a DECnet area router (and provide other services to my real VAXen, too). I plan to use a SIMH emulation so I can leave it up all the time to maintain presence on HECnet without running up a big power bill. My real VAX-11/730 and other future vintage DECnet-speaking hardware would only graze on electrons infrequently, and mostly during colder weather.

7 years, 9 months

Pathworks for Macintosh?

by supratim＠riseup.net

Hi Got OS X Lion running inside a VirtualBox - obviously the first thing I want to do is to see if it can talk DECnet. The forums mention a ?Pathworks for Macintosh? product. Does anyone know where to get a copy of it? Thanks Supratim

7 years, 9 months

Intro and New User Questions

by nf6x＠nf6x.net

Hi there, everybody! I'm a vintage computer collector in southern California, USA, and I'm interested in joining HECnet. I thought I'd introduce myself and then ask some questions on the mailing list before I ask to join the network. One of my favorite computers in my collection is a VAX-11/730 system with an R80, RL02, TU81 and DECwriter III. It has an ethernet card, and it came with OpenVMS 7.3 on the R80 and VMS 5.3 on an RL02 pack. I don't seem to have a single good TU58 tape, even after repairing the capstan rollers in the drives, but I can boot up the computer via tu58em. I've shared the boot-optimized console tape image I put together, as well as an image I created of the CRDPACK RL02 pack that came with the system: https://github.com/NF6X/VAX-11-730-Console-v57 It's been a couple years since I fired up that system, but I recently had another burst of interest and began setting up some VAX emulations in simh. I have a simulated VAX-11/785 running in simh on a BeagleBone Green (a little embedded computer board, similar to the Raspberry Pi). I plan to leave it running as a full-time VMS presence at home, so it can be up on HECnet all the time. It would be a natural host for any bridging or routing I need to do, and I plan to use it as my main bridge between my modern computers and anything I have speaking DECnet. I have TCP/IP set up on it so I can FTP files on and off of it from my modern systems. The 11/730 won't be powered up very often, and probably mostly during winter! I have plans to restore a heap of parts that I have into a working PDP-11/44 eventually, and I suppose it should be able to run RSX-11 and also visit HECnet? I expect that I'll probably get more DECnet-capable hardware in the future. I'd like to get a PDP-11/73 someday, and I'm curious about those little QBUS MicroVAXen. Maybe I should add a VAXstation to the mix, too? So now it's time for me to figure out how to join HECnet. I gather that my best options would be to either use the bridge program, or to set up my VAX-11/785 emulation to bridge things somehow. If I use the bridge program running on a Linux box, can I configure it to only bridge traffic to/from the rest of HECnet? I don't want the traffic between my local DECnet nodes to leave the house. If the bridge program forwards all DECnet packets that it sees, then maybe I should learn how to set up my emulated VAX-11/785 as a router instead? And now for the really tough question: Once I add my systems to HECnet, what can I *do*? I'd like to join HECnet just because it's there, but it would be swell if there's more fun stuff to do. -- Mark J. Blair, NF6X <nf6x at nf6x.net> http://www.nf6x.net/

7 years, 9 months

Swedish Pascal under RSX-11M-Plus?

by mcguire＠neurotica.com

Hey folks. I'm trying to get "Swedish" Pascal v6.3 running under RSX-11M-Plus v4.6, and have hit a problem. The created PAS.TSK crashes on invocation, and I suspect it may be due to a patch that gets applied to a library during the build process. This appears in PAS.BLD: ; ; The above GBLPAT statement patches a branch instruction ; into the system overlay autoload routine AUTO. ; The last few releases of most operating systems have had ; different versions of AUTO. The proper GBLPAT statement ; to use above depends on which AUTO routine you have on ; your system. You can identify which one you have by ; examining the object module ident of module AUTO in ; the system object library, SYSLIB. Use a command such as ; "LBR LB:[1,1]SYSLIB/FU" to do this. The GBLPAT statements ; to use with each AUTO routine are: ; ; AUTO ident GBLPAT statement ; ============ ================== ; ??early?? GBLPAT=ROOT:$AUTO+34:437 ; 08 GBLPAT=ROOT:$AUTO+34:435 ; 09.08 GBLPAT=ROOT:$AUTO+36:441 ; 10.02 GBLPAT=ROOT:$AUTO+36:431 ; The ident of AUTO in my system is 10.05, making that patch potentially land at the wrong address. However, that's just my suspicion. Has anyone gotten Swedish Pascal v6.3 running under RSX-11M-Plus v4.6? -Dave -- Dave McGuire, AK4HZ New Kensington, PA

7 years, 11 months

Announcing TCP/IP for RSX-11M-PLUS

by bqt＠softjar.se

Time for a new release announcement of TCP/IP for RSX-11M-PLUS. This release contains a lot of fixes and improvements in many areas. There is one very serious bug in TCP that is fixed in this release which is why I really encourage people to upgrade. Highlights: - Stability and reliability improvements in TCP. - Improved SPOOF detection. - Improved stability. Detailed information on things that have been done since the last release: Installation process: - The IPGEN script now more smoothly handles updates to an existing installation. Ethernet driver: - Improved driver reset handling. - Implemented MTU backoff in ethernet driver, to handle unpatched DEC XU: driver. TCP: - At socket close time, if there were pending packets to process still in the socket, the system pool could become corrupted, causing a crash at some random later time. - Add more spoof processing for suspicious connections. FTPD: - Improved error handling for not logged in clients. HTTP: - Implemented spoof processing for connections which looks suspicious. MAILD: - Implemented spoof processing for connections which looks suspicious. Mail client: - Added basic hooks for extending mail to deal with several folders (still not complete). 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 The documentation is also available through ftp on Mim, or also at http://mim.update.uu.se/tcpipdoc The firewall for Mim have now been removed, so no need for the alternate ports, but Mim is still listening to the alternate ports as well. ftp: 10021 telnet: 10023 As a final word about this release. As always things progress with time, but I think it's safe to say by now that BQTCP is now a very stable TCP/IP with almost all features one can expect. There might always be some more work on the lower level protocols, but at this point, expect that most work and updates will be more and more on various daemons and clients. If there is anything in particular anyone is looking for, let me know. 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

8 years

Alphaserver 800 5/500 CPU Module B-cache error

by mholmes10＠hotmail.com

Before I go looking on Ebay, I thought I'd ask here first. My Alphaserver 800 5/500 wasn't responding when I came back from a business trip. And when I rebooted it, I heard the 1-2-4 beep codes and no screen. Found out it means "Backup cache error. Replace the CPU daughter board" And I found out in the manual that "The system can be operated with the B-cache disabled until a replacement CPU daughter board is available." After re-seating the CPU board and the memory it still got the error beeps and changed the J1 jumper and it booted up fine. Does anyone know the impact of running with the B-cache disabled? The text in the system manual said the jumper setting "Allows the system to run despite bad B-cache until a replacement CPU board is available." How long can the system be run in this mode? just curious so I know how much time I have to watch for a reasonable price 5/500 CPU module to show up on ebay (since there aren't many VAX/Alpha geeks in DC on craigslist). Thanks in advance Mike

8 years

Announcing TCP/IP for RSX-11M-PLUS

by bqt＠softjar.se

Time for a new release announcement of TCP/IP for RSX-11M-PLUS. This release contains a lot of fixes and improvements in many areas. I really encourage people to upgrade, as some of these changes can have a noticeable impact on stability. Highlights: - Distribution now includes the PDP-11 C and BASIC+2 resident libraries, so that various tools and utilities that are built against them can be installed even if the full language is not installed on a system. - Improved stability. Detailed information on things that have been done since the last release: Ethernet driver: - The ethernet driver could under some overload situations become deaf, and not receive any more packets. TCP: - TCP FIN handling. Under some circumstances, TCP could get into a state where both sides would be sending FIN packets, and not acknowledging the other sides FIN. - TCP sequence handling. Under some circumstances, TCP packets with bad sequence numbers could be accepted as valid packets. - IO.KIL function for normal TCP ports removed. It turned out that it was very undesirable to process IO.KIL for connected sockets. (A separate function with the same effect does exist.) - Added counted for rejected TCP SYN packets. - Improved task activation code for TCP daemons. HTTP: - Improved logging. MAILD: - Improved new mail notification handling. - Correct handling of EHLO/HELO for SMTP. - Implemented proper MAIL11 protocol, version 3. - Rewritten address rewrite logic to better process both SMTP and MAIL11 addresses. MAIL: - Simple mail client now exist. Libraries: - Unified user lookup functions. User lookups now happen both on lastname, UIC, SID and login directory. This is used both by MAIL, FTP and HTTP. 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 The documentation is also available through ftp on Mim, or also at http://mim.update.uu.se/tcpipdoc The firewall for Mim have now been removed, so no need for the alternate ports, but Mim is still listening to the alternate ports as well. ftp: 10021 telnet: 10023 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

8 years, 1 month

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

HECnet