[Info-vax] VSI Community License Program - x86

[fsword007 at gmail.com]

Yeah. I got access letter from VMS software inc. today  too.

I had a problem with DHCP settings.  I did applied static IP addresses instead so that my Verizon G3100 assigned new machines with new internal static IP addresses. 
When DHCP bugs is fixed, I will changed settings back to DHCP in future..

I successfully installed OpenVMS x86 with VirtualBox under Windows 11.  I set a bridged network adapter to ethernet driver like Killer E2500 driver and was now able access the Internet and HECnet outside.   With other drivers, it did not work.   There is no Jnet software available for x86 version so that I have to develop NJE driver from scratch or FujiNet to access BITNET network or IBM mainframes.

I installed C, C++ and Fortran compilers so far.  I am waiting for Pascal, Cobol and Basic right now. 

I found OpenVMS E9.2-1 install guide manual according to access letter email.  It said that E9.2-1  now supports AMD processor.  I will try it on my UDOO Bolt SBC board. 

I moved TSVMSA to TSVMSB for VAX version and assigned TSVMSA to x86 version on HECnet network.  I will not need TSVMST anymore. 
I removed Multinet and TCPware from old VAX version and installed TCPIP software. 

Is that possible to get Multinet and TCPware with VSI hobbyist paks?  I am waiting for Process, Inc for porting their TCP/IP software to x86 version.

Tim