15 Jul
2019
15 Jul
'19
2:52 p.m.
Johnny Billquist <bqt at softjar.se> wrote:
My experience with latd in Linux is that it sucks. It
sortof works if
you are lucky, but there are problems in it, which makes it undesirable
to use with RSX at least.
My experience is that for connecting to a Tops-[12]0 system it works,
even if the thing, as you say, sucks in several ways. Considering
myself lucky then.
--Johnny (the other one)
15 Jul
15 Jul
9:50 p.m.
Hi All,
Tried to install Pathworks 32 7.4 on both Windows 7 Home Premium and
Windows 8.1 PCs. (No Windows 10 machine to test with.)
CD installer doesn't function but navigated to the window2k(sp?) folder and
ran setup. Process completed after a few complaints about unrecognized
drivers. Used default location C:\PW32.
Seemed to work...but no mention of Pathworks on any of the Control Panel
dialogs.
Ran NCP (located in the C:\PW32 folder) in a DOS window. Returns error
"Failed to find NCP parse table file ncptab.bin" even though the file
exists in the same folder as ncp.
aslpass (Password Assistant) and nftw32 (DECnet File Transfer) programs
run, but nothing to connect to.
Any ideas, or is the software too old and incompatible with newer Windows
releases?
On the good side, the excellent PowerTerm 525 emulator installs and runs
perfectly. Far superior to putty. (I use a newer, paid version of PowerTerm
Pro every day for my OpenVMS systems.)
Thank you,
Jason
On Mon, Jul 15, 2019 at 3:53 AM Johnny Eriksson <bygg at cafax.se> wrote:
Johnny Billquist <bqt at softjar.se> wrote:
My experience with latd in Linux is that it
sucks. It sortof works if
you are lucky, but there are problems in it, which makes it undesirable
to use with RSX at least.
My experience is that for connecting to a Tops-[12]0 system it works,
even if the thing, as you say, sucks in several ways. Considering
myself lucky then.
--Johnny (the other one)
10:28 p.m.
Jason,
I tried it on Windows/10 64 bit. It fails to find network adaptors to use.
Dave
From: owner-hecnet at Update.UU.SE <owner-hecnet at Update.UU.SE> On Behalf Of Jason
Brady
Sent: 15 July 2019 20:51
To: hecnet at update.uu.se
Subject: Re: [HECnet] Windows 10 DECnet?
Hi All,
Tried to install Pathworks 32 7.4 on both Windows 7 Home Premium and Windows 8.1 PCs. (No
Windows 10 machine to test with.)
CD installer doesn't function but navigated to the window2k(sp?) folder and ran setup.
Process completed after a few complaints about unrecognized drivers. Used default location
C:\PW32.
Seemed to work...but no mention of Pathworks on any of the Control Panel dialogs.
Ran NCP (located in the C:\PW32 folder) in a DOS window. Returns error "Failed to
find NCP parse table file ncptab.bin" even though the file exists in the same folder
as ncp.
aslpass (Password Assistant) and nftw32 (DECnet File Transfer) programs run, but nothing
to connect to.
Any ideas, or is the software too old and incompatible with newer Windows releases?
On the good side, the excellent PowerTerm 525 emulator installs and runs perfectly. Far
superior to putty. (I use a newer, paid version of PowerTerm Pro every day for my OpenVMS
systems.)
Thank you,
Jason
On Mon, Jul 15, 2019 at 3:53 AM Johnny Eriksson <bygg at cafax.se <mailto:bygg at
cafax.se> > wrote:
Johnny Billquist <bqt at softjar.se <mailto:bqt at softjar.se> > wrote:
My experience with latd in Linux is that it sucks. It
sortof works if
you are lucky, but there are problems in it, which makes it undesirable
to use with RSX at least.
My experience is that for connecting to a Tops-[12]0 system it works,
even if the thing, as you say, sucks in several ways. Considering
myself lucky then.
--Johnny (the other one)
16 Jul
16 Jul
1:38 a.m.
On 2019-07-15 12:52, Johnny Eriksson wrote:
Johnny Billquist <bqt at softjar.se> wrote:
There is some protocol bug in Linux latd. And unfortunately, that bug in
turn triggers a bug in RSX LAT, so that not only are connections
dropped, but memory is lost on the RSX side. So after a while, the
system becomes unusable.
latd was developed by people just trying to reverse engineer LAT by
looking at traffic between a VMS host and a DECserver. And the code is
an ugly C++ hack. Someone should rewrite it. Especially as the protocol
specs are now available.
I have been thinking about it, but have not had any time to even do a
serious attempt.
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
My experience with latd in Linux is that it
sucks. It sortof works if
you are lucky, but there are problems in it, which makes it undesirable
to use with RSX at least.
My experience is that for connecting to a Tops-[12]0 system it works,
even if the thing, as you say, sucks in several ways. Considering
myself lucky then. 
4:21 a.m.
On 7/15/19 7:38 PM, Johnny Billquist wrote:
latd was developed by people just trying to reverse
engineer LAT by
looking at traffic between a VMS host and a DECserver. And the code is
an ugly C++ hack. Someone should rewrite it. Especially as the protocol
specs are now available.
I have been thinking about it, but have not had any time to even do a
serious attempt.
I'm sure we'd all love it if you did..
-Dave
--
Dave McGuire, AK4HZ
New Kensington, PA
1986
days inactive
1987
days old
4 comments
5 participants
participants (5)
-
bqt＠softjar.se -
bygg＠cafax.se -
dave.g4ugm＠gmail.com -
jrbrady65＠gmail.com -
mcguire＠neurotica.com