I don't think that Compaq have any version of SSH for VMS om VAX, but I haven't checked if anything was shipped after 7.3.
There are other options, though. tcpware comes to mine.
I was thinking TCPWare too - seems to be the only reference I can find to SSH on 7.3.
Doesn't Multinet also provide SSH on VAX? It's definately there in the Alpha version.
Regards,
Peter Coghlan.
On 2011-07-04 19.30, Mark Benson wrote:
On 4 Jul 2011, at 08:43, Mark Wickens wrote:
On 04/07/11 00:27, Johnny Billquist wrote:
On 2011-07-04 01.22, Mark Benson wrote:
On 3 Jul 2011, at 21:33, Johnny Billquist wrote:
No need. As soon as you switch to X-windows, you also need to switch to some X-based application. As xterm exists, it should be the obvious choice, and it works correct straight out of the box, even on a Mac.
Weelll... it sorta works.
Most of the keypad keys either do something, make EVE bitch about them being unassigned, or do unexpected things. Also, I'm still not positive that the GOLD key thing is working, nor can I find the Do key in EVE. It's not in either place the OpenVMS manual says it should be.
I should probably point out that PF1 (Gold) is mapped to F1 on your keyboard. So it is not located at the same physical place as on a DEC terminal...
Try F2, to get some help perhaps?
Johnny
For 'Do' you can always use Ctrl-B as a fallback - that's what I do when I don't have the right keyboard connected.
Great - those were the two things I was missing!
Is there anything I can do to fix the 'Backspace returns ti the start of the line' niggle. Normally either backspace or delete work okay for backspacing 1 character at a time but in xterm neither works as expected.
That's because your options in xterm is wrong. :-)
You can configure xterm to send either BS or DEL when you hit that key above CR. You want it to send DEL. It's only nitwits who think that backspace should delete. :-)
Johnny
On 4 Jul 2011, at 08:43, Mark Wickens wrote:
On 04/07/11 00:27, Johnny Billquist wrote:
On 2011-07-04 01.22, Mark Benson wrote:
On 3 Jul 2011, at 21:33, Johnny Billquist wrote:
No need. As soon as you switch to X-windows, you also need to switch to some X-based application. As xterm exists, it should be the obvious choice, and it works correct straight out of the box, even on a Mac.
Weelll... it sorta works.
Most of the keypad keys either do something, make EVE bitch about them being unassigned, or do unexpected things. Also, I'm still not positive that the GOLD key thing is working, nor can I find the Do key in EVE. It's not in either place the OpenVMS manual says it should be.
I should probably point out that PF1 (Gold) is mapped to F1 on your keyboard. So it is not located at the same physical place as on a DEC terminal...
Try F2, to get some help perhaps?
Johnny
For 'Do' you can always use Ctrl-B as a fallback - that's what I do when I don't have the right keyboard connected.
Great - those were the two things I was missing!
Is there anything I can do to fix the 'Backspace returns ti the start of the line' niggle. Normally either backspace or delete work okay for backspacing 1 character at a time but in xterm neither works as expected.
--
Mark Benson
My Blog:
<http://markbenson.org/blog>
Follow me on Twitter:
http://twitter.com/mdbenson
"Never send a human to do a machine's job..."
On 04/07/11 00:27, Johnny Billquist wrote:
On 2011-07-04 01.22, Mark Benson wrote:
On 3 Jul 2011, at 21:33, Johnny Billquist wrote:
No need. As soon as you switch to X-windows, you also need to switch to some X-based application. As xterm exists, it should be the obvious choice, and it works correct straight out of the box, even on a Mac.
Weelll... it sorta works.
Most of the keypad keys either do something, make EVE bitch about them being unassigned, or do unexpected things. Also, I'm still not positive that the GOLD key thing is working, nor can I find the Do key in EVE. It's not in either place the OpenVMS manual says it should be.
I should probably point out that PF1 (Gold) is mapped to F1 on your keyboard. So it is not located at the same physical place as on a DEC terminal...
Try F2, to get some help perhaps?
Johnny
For 'Do' you can always use Ctrl-B as a fallback - that's what I do when I don't have the right keyboard connected.
Mark.
On 2011-07-04 01.22, Mark Benson wrote:
On 3 Jul 2011, at 21:33, Johnny Billquist wrote:
No need. As soon as you switch to X-windows, you also need to switch to some X-based application. As xterm exists, it should be the obvious choice, and it works correct straight out of the box, even on a Mac.
Weelll... it sorta works.
Most of the keypad keys either do something, make EVE bitch about them being unassigned, or do unexpected things. Also, I'm still not positive that the GOLD key thing is working, nor can I find the Do key in EVE. It's not in either place the OpenVMS manual says it should be.
I should probably point out that PF1 (Gold) is mapped to F1 on your keyboard. So it is not located at the same physical place as on a DEC terminal...
Try F2, to get some help perhaps?
Johnny
On 3 Jul 2011, at 21:33, Johnny Billquist wrote:
No need. As soon as you switch to X-windows, you also need to switch to some X-based application. As xterm exists, it should be the obvious choice, and it works correct straight out of the box, even on a Mac.
Weelll... it sorta works.
Most of the keypad keys either do something, make EVE bitch about them being unassigned, or do unexpected things. Also, I'm still not positive that the GOLD key thing is working, nor can I find the Do key in EVE. It's not in either place the OpenVMS manual says it should be.
--
Mark Benson
My Blog:
<http://markbenson.org/blog>
Follow me on Twitter:
http://twitter.com/mdbenson
"Never send a human to do a machine's job..."
On 2011-07-03 19.55, Zane H. Healy wrote:
At 12:51 PM +0100 7/3/11, Mark Benson wrote:
I use a Mac OS X machine and the native Terminal.app with telnet or
SSH to access my OpenVMS boxen. Fior the most par tit works fine with
a VT100 terminal emulation to the VMS terminal. I have a problem with
EVE however. Mac's do something silly with the numeric keypad, it's
locked to numbers (rather than scroll) and the Numlock key doesn't do
anything sensible. As a result using the 'GOLD' key and pretty much
all the action keys in EVE becomes impossible. Anyone got any
suggestions, or am I just going to have to wing it or use my Linux box?
Use X-Windows and modify your keybindings so that they match what VMS
expects. It's a lot harder to do on the Mac, but it is possible.
No need. As soon as you switch to X-windows, you also need to switch to some X-based application. As xterm exists, it should be the obvious choice, and it works correct straight out of the box, even on a Mac.
Johnny
On 2011-07-03 13.51, Mark Benson wrote:
Hi,
I use a Mac OS X machine and the native Terminal.app with telnet or SSH to access my OpenVMS boxen. Fior the most par tit works fine with a VT100 terminal emulation to the VMS terminal. I have a problem with EVE however. Mac's do something silly with the numeric keypad, it's locked to numbers (rather than scroll) and the Numlock key doesn't do anything sensible. As a result using the 'GOLD' key and pretty much all the action keys in EVE becomes impossible. Anyone got any suggestions, or am I just going to have to wing it or use my Linux box?
Skip iTerm, and run xterm instead. You'll get all keys working the way you would expect. (I do this all the time on my Macs.)
Johnny
At 12:51 PM +0100 7/3/11, Mark Benson wrote:
I use a Mac OS X machine and the native Terminal.app with telnet or SSH to access my OpenVMS boxen. Fior the most par tit works fine with a VT100 terminal emulation to the VMS terminal. I have a problem with EVE however. Mac's do something silly with the numeric keypad, it's locked to numbers (rather than scroll) and the Numlock key doesn't do anything sensible. As a result using the 'GOLD' key and pretty much all the action keys in EVE becomes impossible. Anyone got any suggestions, or am I just going to have to wing it or use my Linux box?
Use X-Windows and modify your keybindings so that they match what VMS expects. It's a lot harder to do on the Mac, but it is possible.
Zane
--
| Zane H. Healy | UNIX Systems Administrator |
| healyzh at aracnet.com | OpenVMS Enthusiast |
| | Photographer |
+----------------------------------+----------------------------+
| My flickr Photostream |
| http://www.flickr.com/photos/33848088 at N03/ |
On 2011-07-03 11.14, Mark Benson wrote:
On 2 Jul 2011, at 14:19, Johnny Billquist wrote:
Curiousity is good. The thing you emulate is the thing that is visible at the disk contoller layer. So anything beyond that will (probably) be different from the thing you emulate. When you emulate a uVAX with an RA92 disk, simh will present you with a emulated KDA-50, on which there appears to be an RA92 connected. In the real world, the KDA-50 runs some sort of microcode, and communicates with the disk over SDI, which is a serial protocol using four coaxial cables. And the SDI protocol defines how the KDA-50 gets the RA92 to do all kind of operations.
One of these days I want to have a good look at a real VAX, they are such a departure from anything I've used :) Interesting that they use a serial disk communication system - where've I seen that crop up recently? ;)
Yeah, SATA and SAS is just really DECs SDI warmed over, except DEC did it 30 years ago, and did it better. SDI was the low level between disk and controller. The controller in turn talked a very low-level agnostic protocol called MSCP that was designed to handle all kind of disks in the same way, with command queuing, reordering, possible bad block handling for disks that didn't do that, and I don't even know what else. Controllers that talk MSCP to the computer were implemented that has SDI as the back end, but also there are also those with MFM, SCSI, DSSI, CI, networks and probably some other interface used as the low level connection to disks as well. But all that is totally hidden from the computer, who only understands MSCP.
But none of that is emulated, and there is no real point in emulating it.
So essentially you are only emulating the minimum needed to keep the VAX microcode and after that OS happy and working 100%.
Not even that. Why emulate the VAX microcode? Instead you emulate the VAX instructions, with your own "microcode" that does not look like the microcode of any existing VAX, but which works best for the platform where you are running your emulator. Programs running on the VAX are not aware of the microcode either.
(Maybe you are confusing microcode with machine code?)
Good to hear things are working now.
As for telnet vs. ssh. Well, ssh is safer, in that people can't sniff passwords easily over the network. If you worry about people doing that, then you might want to not use it. However, if your network is secure, then telnet isn't really an issue.
Inside my own network that's not an issue. Accessing it from the internet, not such a good idea. I can SSH the NetBSD side though so I may just settle with using the 'local terminal' via screen and ssh when using the internet.
So, you just block telnet traffic from the rest of the world in a firewall, so that you need to ssh to an intermediate box you have control of, and then you can telnet from there to the simh VAX. Good enough.
Johnny
