| Author |
Multiple Terminals |
NeonJack
Member
Posts: 12
Joined: 30.03.10 |
| Posted on January 11 2013 00:25 |
|
|
FREEAXP has just the Operator's Console (on port 9000) and TTA0 (on port 9001). I would like to connect a virtual Multiplexer (I think that is what this device would be called), or some other similar, and hopefully free, software so that you could connect more virtual terminals to the emulator (e.g. TTA1:, TTA2: TTA3: etc.), probably using the software on TTA0: (9001). Then when you connect using Telnet/Putty/Keavt/Reflection or whatever, using port 9001, the multiplexor would give you a unique TT: number (and probably automatically assign you a unique internal port number (e.g. 12001 etc).
I have had a careful look in the forums but if this topic has been posted already then I've missed it, sorry!
I agree this is probably a certainty for entry into the "Wishing For The Moon" competition, but if anybody knows of a means whereby I can do this, I would be very grateful. |
|
|
| Author |
RE: Umm Telnet ? |
John Manger
Moderator
Posts: 63
Location: nr Heathrow, Middlesex, UK
Joined: 18.03.10 |
| Posted on January 15 2013 04:17 |
|
|
I expect I am missing something obvious :-) , but why not simply start another PuTTy and telnet to the emulator locally or do a similar thing remotely ?
Just my 2d/2c.
John M |
|
|
| Author |
RE: Multiple Terminals |
NeonJack
Member
Posts: 12
Joined: 30.03.10 |
| Posted on January 16 2013 04:37 |
|
|
if you start a second PuTTY you still need to give the same port number e.g. 9001. The second connection then puts you in wherever the first connection happens to be - this might be in the middle of an FMS form for example, if the first session happens to be using the FMS Editor. The second session won't see what has already been painted on the screen of the first session, so if the cursor is in the middle of the screen on the third or fourth field, say, you will just see the cursor in the middle of the screen, blinking away. If OTOH, you use say port 9002, the emulator is not listening on that so the PuTTY session will sit there, not connected and therefore doing not a lot.
It'd be nice if you could do what you suggest, John (and thank you for your reply), but I think if we could the Multiplexer device manufacturers in the real DEC world would have gone bust long ago...
 |
|
|
| Author |
RE: Install TCPIP |
fovea1959
Member
Posts: 5
Joined: 06.02.12 |
| Posted on January 16 2013 04:49 |
|
|
I installed TCPIP on my FreeAXP/OpenVMS 8.4, and my user uses ssh to get in when it's on the net. I have a user in on device "FTA2:" right now.
I'm going to stuff a 2nd virtual NIC into my OpenVMS attached to the Microsoft loopback adapter so that I can ssh into it from the host machine when I am "off-net". |
|
|
| Author |
RE: Multiple Terminals |
NeonJack
Member
Posts: 12
Joined: 30.03.10 |
| Posted on January 16 2013 05:20 |
|
|
|
fovea1959 wrote:
I installed TCPIP on my FreeAXP/OpenVMS 8.4, and my user uses ssh to get in when it's on the net. I have a user in on device "FTA2:" right now.
I'm going to stuff a 2nd virtual NIC into my OpenVMS attached to the Microsoft loopback adapter so that I can ssh into it from the host machine when I am "off-net".
I have TCP/IP installed on my FreeAXP/Open VMS 8.4 as well. When setting up SSH in the PuTTY client what settings do you use? |
|
|
| Author |
RE: Multiple Terminals |
NeonJack
Member
Posts: 12
Joined: 30.03.10 |
| Posted on January 24 2013 06:17 |
|
|
SSH is the way to go with this. You need to enable it by logging in as SYSTEM and running the TCPIP$CONFIG command procedure. Select the server option and install and get the SSH Server going. You do not need to worry about the SSH Clinet, because PuTTY is going to be that. Remember to do a @SYS$STARTUP:TCPIP$SSH_SHUTDOWN followed by a @SYS$STARTUP:TCPIP$SSH_STARTUP so that the changes will be put into effect. The first time you logon using PuTTY with ssh you will get a check saying the host's rsa key is not in your cache but if you are happy with it, you will then be able to connect. The terminal is set to "unknown" because, being a remote terminal, OpenVMS has no way of knowing what type of terminal it is. You can set it to be a vt400 by doing a SET TERM/DEV=VT400 and if you detect the terminal type in your LOGIN.COM file you can change it as you are logging in. My thanks to "fovea159" for making this brilliant suggestion (i set it up and ran 5 terminals straightaway!)
|
|
|
