I have moved my cluster to running under VMware Fusion and W7 64 bit.
So the configuration now is:
Two VMware Fusion VMs on a MacBook Pro.
1. Windows 7 64 bit VM with 4 NICs. Two NICs dedicated to Windows,
and two NICs dedicated to VMS.
1. Ubuntu Linux VM with 4 NICS. Again, two NICs dedicated to SimH.
One of the Windows NICs is set to NAT or can be set to bridged to allow external access to the windows system. The other is set to "HOST" only for a private LAN.
One of the LINUX NICs is set to bridged and the other to "HOST" only.
And the VMS systems are configured the same way, so that all four systems can communicate on a private bus. At least that was the theory.
The actual fun is that since Microsoft windows could not reach the public internet on the "host" only network, it basically put up some sort of block on all network traffic. I could ping out, but not ping in to either the Windows system or the VMS emulated system.
Windows Help and knowledge base said to just click on the network to change the type. However that option is disabled for that unknown network type. So you can only override the network types of networks that Windows was able to guess the type.
A Google search showed a several options starting with a registry hack and to delete the devices and let windows re-discover them. That wasted a lot of time, as the registry keys mentioned do not exist in 64 bit windows 7, and nothing worked.
It turns out that you need to use the local security policy editor to change the classification of unidentified networks from public to private.
Apparently the default is now that networks that do not have access to the Internet are secured more tightly than office networks.
I have noticed that when I close the Macbook, and open it in a new location, that I usually have to shutdown the FreeAXP program and restart it, or VMS will not communicate over one or both of the NICs that have been dedicated to it.
I also have noticed messages on the console overnight that cluster communications were lost and restored.
And today, I saw one of those messages on the VAX console, yet it did not immediately recover. It occurred when the W7 VM blanked its screen.
The rest of the VM should have stayed powered up. On clicking on that VM, I found the FreeAXP system generating a machine dump.
The file machinechk.dmp is in my scratch directory on Encompasserve for a short period of time if anyone wants to look at it.
malmberg December 12 2017 HPE only makes the most current version of OpenVMS Alpha / IA64 /VAX available to hobbyists. When I had access to the Alliance 1 program it was the same. No public downloads are allowed by HPE.
nmbonao December 08 2017 Is anybody knows OpenVMS 8.2 version downloadable version? or CD copy? Thank you very much
aarommes December 02 2017 Bitcoin and Blockchain enthusiasts ( plus distributed computing ) please connec / reply: http://www.openvmshobbyis t.com/forum/viewthread.ph p?forum_id=130&thread_id= 2991
malmberg September 10 2017 https://sourceforge.net/p /vms-ports/wiki/VMSInstal lation/ For the most part just use VMS 6.1 media instead of 7.3. But why run the older release?
DoeveR August 07 2017 Where can I find the write up on running VMS 6.1 using the simh emulator?
Bart March 20 2017 Happy to have found my password again!