Does anybody know what the status of any types of drivers for DECnet or
LAT on Windows 7 or above?
I have the CD's from HP for Windows 2000, but I'll be darned if I can
lay hands on them.? So I have a Windows 2000 laptop that has LAT on it
and I can use that to run Kermit, which has been useful when I have
really destroyed things.
However, I just got a new Windows 10 machine and I'd like to put DECnet
on it.? So is that bring your wallet?? Anybody know anything about
PuTTY??? That would be straightforward to adapt to NRT and (maybe) LAT.?
One assumes CTERM would be more effort.
I have the latd package on one of my Linux hosts and that works great.?
Right into the 20.? I have to scrounge up another Ethernet adapter
before I reconfigure the whole thing for DECnet because of some
connectivity issues.
Johnny Billquist <bqt at softjar.se> wrote:
> > 2. MCB; what was developed on it past your snapshot (Phase II).
>
> I can't even remember, or realize what MCB stands for now. :-)
Multi-Communication-Base comes to mind.
--Johnny (the other one)
Hi,
Is anybody running the NPTD functionality in Multinet 5.5 on VAX VMS 7.3 (under SIMH)? If so, how did you get it to work. I switched it on with a simple NTP.CONF and tried to query it. The logfile doesn't change much and I/O counts go up slowly. My attempts to query it usually result in a traceback. I'm a bit concerned by the lack of an NTPDATE command mentioned in the documentation, despite having done a full install. The timezone facility is a bit primitive too.
I'm thinking of giving up with it. I have local TCP services on the machines hosting SIMH instances. One of them returns a local time string in VMS format, so I may make use of that in an RDATE-like fashion.
Keith
Anybody else out there running DECnet on Linux? I recently upgraded from
the 4.4.0-148 kernel to 4.4.0-151 and find that DECnet does not work with
the latter. Connections always seem to hang at minimum, and frequently
cause kernel panics. Has anybody found a fix for this, or is this the end
of the road?
BTW, 4.4.0-151 was released recently to fix the TCP SACK kernel panic
problem.
Bob
Anyone familiar with the timeline for renewing Hobbyist licenses lately?
I registered on the HPE site.
In the past the turnaround was very quick, but it's been several days and nothing; so curious if this is the new timeline.
thanks
Mike
Time for a new release announcement of TCP/IP for RSX-11M-PLUS.
Highlights:
This release have some rather significant work done on the mail system.
There have also been some minor improvements on TCP, HTTPD, FTP and
libraries.
Detailed information on things that have been done since the last release:
TCP:
. Improved retransmission handling at Fin Wait 2.
. Correct keepalive handling at Fin Wait 2.
. Improved processing at socket close. TCP sockets should do keepalives,
and not probes when in Fin Wait 2.
Libraries:
. Corrected program section attributes on some modules in BQTLIB, so
that they work correctly also on overlaid programs.
. Bugfix in BQTC library. Recent changes to quadtime to string
conversion had introduced a potential buffer overflow error.
FTPD:
. Change FTPD read command processing to avoid a race condition.
HTTPD:
. Reworked logging routines to fix some performance issues.
. Bugfix in IND forms library for CGI scripts.
MAILD:
. Changed mailbox format for better performance.
. Changed location for mail spool file.
. Added checking for /NOBRO for new mail announcements.
. Increased stack size since the task sometimes ran out of stack.
. Reduced static data memory use.
. Changed overlay scheme to make more memory available.
. Added various error checks in the code.
. Changed usage so all queue operations requires a user with privileges.
. Added label handling for mails.
. Added copying of sent mails to self.
. Improved error mail generation in MAILD.
. Added mail size information to mails.
. Added conversion tool for old mailboxes.
*** Important notice about MAILD ***
The changes to MAILD are not seamless. When installing the new version,
the mailbox update program should be run, in order to upgrade all user
mailboxes to the new mailbox format. The task for this is MBXUPD.TSK.
There are no issues with running this task several times. A mailbox that
has already been updates will not be modified anymore by the update task.
The location of the mail queue file have moved. After installation, you
could just move the mail queue file over to the new place, or else
re-initialize the mail system.
The mail queue file name is MAILQUEUE.DAT, and it was previously located
at MAIL$:, but it should be moved to LB:[1,7] instead.
Once the mailboxes have been updated, and the mail queue file have been
moved/recreated, the mail system have been updated, and you are ready to
use the new mail system.
*** Important notice about MAILD ***
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
I hope people find this update useful. While there are no really
critical issues that have been solved, I still recommend people to
update, since this new version do contain improvements that are
beneficial and as far as I know there are no issues or problems updating
to this newest version.
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
Hi,
Just a quick question - has anybody (else) approached the Living Computers Museum and Labs (in Seattle) with regard to getting their VAX (Rosie) and/or other DECnet-capable kit onto HECnet? Not so long ago, they 'hid' their systems behind a ssh gateway because of the number of attacks they were suffering via telnet. It makes it rather difficult to move code onto Rosie... well, perhaps more inconvenient than difficult, especially if all I want to copy are binaries.
Just asking...
Keith
So, I added this command to the startup.cmd: @LB:[IPNET]INS.CMD.
I didn't modify the file yet. I wanted to see what it would do
The result after rebooting was this:
>INS LB:[IPNET]MLTCOM/UIC=[1,54]/PRO=[RW,RW,,]
>INS LB:[IPNET]MLTNET
>INS LB:[IPNET]MLTCFG
>NCP SET PROC IP TOP
NCP -- Set failed, unrecognized component, Process
>NCP SET LIN IP-0-* ALL
NCP -- Set failed, invalid identification format, Line
>MNC SHO VER
Initialize common
NT.IP not found. Exiting...
>MNC SET CIR IP-0-0 TCA HOST MIM.UPDATE.UU.SE:7705 PORT 0
Initialize common
NT.IP not found. Exiting...
>NCP SET CIR IP-0-0 STA ON
NCP -- Set failed, invalid identification format, Circuit
There are lots of errors, so I am not sure where to start.
Any advice would be appreciated.
Kurt
I wasn't sure where to post this question, so I thought I would start here.
I have two simh vax3900 machines. Larry and Moe. Larry is the HECNet
router for Moe.
When I send email from Larry (via SMTP), the *return *email address is
correct (SYSTEM at LARRY.MYDOMAIN.COM.
When I send email from Moe (to LARRY::SMTP%"user at domain.com"), the return
email address is: SYSTEM at SCSSYSTEMID.MYDOMAIN.COM.
Why is Moe using the SCSSYSTEMID instead of the system name?
*I am missing something.*
*Kurt*