"Bob Armstrong" <bob at jfcl.com> writes:
LAT is _NOT_ part of DECnet. LAT can be run without DECnet installed
or running. IIRC, LAT was licensed with VMS.
Yeah, but most (actually, "all" I think) of the DECservers required MOP to
download them. How did you do that without DECnet?
Or was it just an unwritten catch-22 that you had to have a DECnet node
somewhere to boot up your terminal server, even if it wasn't the node you
actually wanted to connect to ?
Yeah, that does move a rather dark and rainy cloud over the parade.
--
VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)ORG
Well I speak to machines with the voice of humanity.
LAT is _NOT_ part of DECnet. LAT can be run without DECnet installed
or running. IIRC, LAT was licensed with VMS.
Yeah, but most (actually, "all" I think) of the DECservers required MOP to
download them. How did you do that without DECnet?
Or was it just an unwritten catch-22 that you had to have a DECnet node
somewhere to boot up your terminal server, even if it wasn't the node you
actually wanted to connect to ?
Bob
hvlems at zonnet.nl writes:
Citeren "Brian Schenkenberger, VAXman-" <system at TMESIS.COM>:
"Cory Smelosky" <b4 at gewt.net> writes:
Is LAT supported on VMS 3.5 at all? If so, is it supported without the =
DECnet license? (I don't have a license kit for 3.x)
LAT is _NOT_ part of DECnet. LAT can be run without DECnet installed or
running. IIRC, LAT was licensed with VMS.
--
VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)ORG
Well I speak to machines with the voice of humanity.
LAT is a systemen integrated product without it' s won licentie. It
became availa stond vms 3.4 or 3.5.
Hans
OK. Then Cory needs to look in his system for LTDRIVER and LTPAD .EXEs
to be certain if his version had LAT.
--
VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)ORG
Well I speak to machines with the voice of humanity.
-----Original Message-----
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE]
On Behalf Of Mark Wickens
Sent: 07 April 2013 08:58
To: hecnet at Update.UU.SE
Subject: Re: [HECnet] Who was doing that HECnet mapping work?
On 07/04/2013 00:31, Rob Jarratt wrote:
What version of VMS are you running on the two machines you tried it
from?
Thanks
Rob
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE]
On Behalf Of Mark Wickens
Sent: 07 April 2013 00:13
To: hecnet at Update.UU.SE
Subject: Re: [HECnet] Who was doing that HECnet mapping work?
On 06/04/2013 23:54, Rob Jarratt wrote:
NCP TELL A5RTR SHOW KNOWN CIRCUITS
Had more success from SIMVAX:
$ MCR NCP TELL A5RTR SHOW KNOWN CIRCUITS
Known Circuit Volatile Summary as of 6-APR-2013 22:48:15
Circuit State Loopback Adjacent
Name Routing Node
eth2 on 5.8
psilo.update.uu.seon 1.13
psilo.update.uu.seon 1.15
psilo.update.uu.seon 62.637
psilo.update.uu.seon 59.11
psilo.update.uu.seon 42.1022
psilo.update.uu.seon 14.1
psilo.update.uu.seon 8.400
psilo.update.uu.seon 4.248
psilo.update.uu.seon 44.1023
psilo.update.uu.seon 19.41
psilo.update.uu.seon 28.41
psilo.update.uu.seon 47.556
psilo.update.uu.seon 11.2
psilo.update.uu.seon 2.1
Command completed.
Regards, Mark.
Hi Rob,
The VAX (SIMH, successful run) is running OpenVMS 7.3, the Alpha (first
run) is running OpenVMS 8.3
Regards, Mark.
Interesting. I think the other person who failed also runs OVMS 8.3, so it
looks like more modern OSs can't connect. I don't have 8.3, any chance you
could let me have a guest account on your 8.3 machine so I can test?
Thanks
Rob
On 07/04/2013 00:31, Rob Jarratt wrote:
What version of VMS are you running on the two machines you tried it from?
Thanks
Rob
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On Behalf Of Mark Wickens Sent: 07 April 2013 00:13 To: hecnet at Update.UU.SE Subject: Re: [HECnet] Who was doing that HECnet mapping work?
On 06/04/2013 23:54, Rob Jarratt wrote:
NCP TELL A5RTR SHOW KNOWN CIRCUITS
Had more success from SIMVAX: $ MCR NCP TELL A5RTR SHOW KNOWN CIRCUITS Known Circuit Volatile Summary as of 6-APR-2013 22:48:15 Circuit State Loopback Adjacent Name Routing Node eth2 on 5.8 psilo.update.uu.seon 1.13 psilo.update.uu.seon 1.15 psilo.update.uu.seon 62.637 psilo.update.uu.seon 59.11 psilo.update.uu.seon 42.1022 psilo.update.uu.seon 14.1 psilo.update.uu.seon 8.400 psilo.update.uu.seon 4.248 psilo.update.uu.seon 44.1023 psilo.update.uu.seon 19.41 psilo.update.uu.seon 28.41 psilo.update.uu.seon 47.556 psilo.update.uu.seon 11.2 psilo.update.uu.seon 2.1 Command completed. Regards, Mark.
Hi Rob,
The VAX (SIMH, successful run) is running OpenVMS 7.3, the Alpha (first run) is running OpenVMS 8.3
Regards, Mark.
Citeren "Brian Schenkenberger, VAXman-" <system at TMESIS.COM>:
"Cory Smelosky" <b4 at gewt.net> writes:
Is LAT supported on VMS 3.5 at all? If so, is it supported without the =
DECnet license? (I don't have a license kit for 3.x)
LAT is _NOT_ part of DECnet. LAT can be run without DECnet installed or
running. IIRC, LAT was licensed with VMS.
--
VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)ORG
Well I speak to machines with the voice of humanity.
LAT is a systemen integrated product without it' s won licentie. It became availa stond vms 3.4 or 3.5.
Hans
On Saturday, April 06, 2013 at 4:59 PM, Cory Smelosky wrote:
Hmmm, 3.5 has datecodes of 1982 and wikipedia states LAT wasn't until
1984...I wonder if it's in 3.6. VMS 4.6 (although it STILL identifies as VAX/VMS
KG when I boot it...) does have LAT OOTB however.
VAX/VMS KG will be set to the appropriate version (4.6) by installing the 'manditory update' which was part of the 4.6 install media.
On Saturday, April 06, 2013 at 1:30 PM, Cory Smelosky wrote:
On 6 Apr 2013, at 16:26, "Johnny Billquist" <bqt at softjar.se> wrote:
However, it is nice that simh now can associate a physical serial port with a
simulated one. How transparent is it? I mean, can you change the speed of
the physical serial port by doing the programming of the simulated one?
Actually, if the DZ device is set for 'modem control', modem enabled signaling, all aspects of the connection are dynamically under control of the simulated OS. This full signaling capability is part of an 'extended' API which the device simulation needs to be modified to support (the DZ was modified, the VH (aka DHV) was not). The VH can attach particular lines to host serial ports, but the line speed, etc. must be statically configured when the attachment is made.
ATTACH DZ has an option for specifying baud rate. I broke SIMH when I tried
to set it to 300 baud though. ;)
Please elaborate (offline) the details so whatever you saw broken can be fixed!
Thanks.
- Mark
On 04/06/2013 07:46 PM, Johnny Billquist wrote:
On 2013-04-07 01:40, Brian Schenkenberger, VAXman- wrote:
"Cory Smelosky" <b4 at gewt.net> writes:
On 04/06/2013 06:12 PM, Brian Schenkenberger, VAXman- wrote:
"Cory Smelosky" <b4 at gewt.net> writes:
On 6 Apr 2013, at 16:54, "Brian Schenkenberger, VAXman-" =
<system at TMESIS.COM> wrote:
=20
"Cory Smelosky" <b4 at gewt.net> writes:
=20
Is LAT supported on VMS 3.5 at all? If so, is it supported
without =
the =3D
DECnet license? (I don't have a license kit for 3.x)
=20
LAT is _NOT_ part of DECnet. LAT can be run without DECnet
installed =
or
running. IIRC, LAT was licensed with VMS.
Ah. So I just need to find the filename to start it then. ;)
It's changed since V3x days. Look for LTLOAD.COM in SYS$MANAGER.
The new names are LAT$STARTUP and LAT$SYSTARTUP but I think you'll
find LTLOAD.COM is the place to begin.
Hmmm. There is no LATCP.EXE, LAT$STARTUP.COM, or LTLOAD.COM it would
appear. Was it an add-on kit for VMS 3.5 or did I miss something rather
important? ;)
Though I lived it, recalling this history is not one of my strong points.
LAT showed up in VMS circa 1984/1985 time frame from my recollection. I
think you will need a newer version of VMS if you want LAT. Look around
for V4.7 (pre-SMP/V5.0) or later VMS. They should have LAT and DECnet
IV.
I'm trying to recall, but I might be wrong. But I thought I was atleast
using LAT with VMS V3.7 at the time. (I don't think I ever used any VMS
before that.) That should be somewhere around 1984.
Hmmm, 3.5 has datecodes of 1982 and wikipedia states LAT wasn't until 1984...I wonder if it's in 3.6. VMS 4.6 (although it STILL identifies as VAX/VMS KG when I boot it...) does have LAT OOTB however.
Johnny
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Experiments
Johnny Billquist <bqt at softjar.se> writes:
On 2013-04-07 01:40, Brian Schenkenberger, VAXman- wrote:
"Cory Smelosky" <b4 at gewt.net> writes:
On 04/06/2013 06:12 PM, Brian Schenkenberger, VAXman- wrote:
"Cory Smelosky" <b4 at gewt.net> writes:
On 6 Apr 2013, at 16:54, "Brian Schenkenberger, VAXman-" =
<system at TMESIS.COM> wrote:
=20
"Cory Smelosky" <b4 at gewt.net> writes:
=20
Is LAT supported on VMS 3.5 at all? If so, is it supported without =
the =3D
DECnet license? (I don't have a license kit for 3.x)
=20
LAT is _NOT_ part of DECnet. LAT can be run without DECnet installed =
or
running. IIRC, LAT was licensed with VMS.
Ah. So I just need to find the filename to start it then. ;)
It's changed since V3x days. Look for LTLOAD.COM in SYS$MANAGER.
The new names are LAT$STARTUP and LAT$SYSTARTUP but I think you'll
find LTLOAD.COM is the place to begin.
Hmmm. There is no LATCP.EXE, LAT$STARTUP.COM, or LTLOAD.COM it would
appear. Was it an add-on kit for VMS 3.5 or did I miss something rather
important? ;)
Though I lived it, recalling this history is not one of my strong points.
LAT showed up in VMS circa 1984/1985 time frame from my recollection. I
think you will need a newer version of VMS if you want LAT. Look around
for V4.7 (pre-SMP/V5.0) or later VMS. They should have LAT and DECnet IV.
I'm trying to recall, but I might be wrong. But I thought I was atleast
using LAT with VMS V3.7 at the time. (I don't think I ever used any VMS
before that.) That should be somewhere around 1984.
Recollection of V37 and V4.7 (key releases) always confuses me. However,
you may be right. A timeline that HP has on its site begins with V4.0. I
don't see any mention of LAT in the timeline until much later though but I
am pretty sure that is was available before the date mentioned in said time-
line.
I do still have my Orange Wall and Gray Wall but the Blue Wall was damaged
in a basement flood, so I don't have that documentation to reference.
--
VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)ORG
Well I speak to machines with the voice of humanity.
