This is a notice that we have discovered a conflict between WinPcap 4.1.3 and Avanti / FreeAXP. If WinPcap 4.1.3 is installed, it conflicts with the Avanti NDIS network driver, preventing it from launching. The problem causes both Avanti and the Avanti configuration utility to hang. We are working on resolving the issue.
There is no conflict with WinPcap 4.1.2. If installing a product that requires WinPcap, such as WireShark or SimH, use WinPcap 4.1.2 to avoid impacting Avanti.
FreeAXP 22.214.171.1244, Win 10 Pro 64 bit and WinPCAP 4.1.0, 4.1.1, 4.1.2, 4.1.3 doesn't work together.
If I remove WinPCAP at all FreeAXP works but of course other WinPCAP programs (Whireshark, SimH) don't. :-(
Host OS: Ubuntu 16.04 64 bit.
Oracle VirtualBox 5.1.0 + extension
Guest OS: Win10Pro.
FreeAXP 126.96.36.1994 first time was installed without its MSI network driver (PCAP) (unchecked in the option install window).
SimH VAX was started successfully.
In the W10's adapter properties there was a tick in front of Win10Pcap Packet Capture Driver.
FreeAXP was started successfully and there was no chooseable NIC (except Dummy driver). -> No network support.
I went back, removed the tick from Win10Ocap driver on the LAN adapter's properties and I modified the FreeAXP install with enabling its MSI capture driver installation.
The default situation:
SimH - Could't see any NIC at "sh xq eth', as usual without PCAP support.
FreeAXP - works like a charm.
The enabled Win10Pcap support scenario:
SimH - works with Win10Pcap.
FreeAXP accept this PCAP situation and I was able to start my OpenVMS 8.4!
I want to mention I haven't tested the OpenVMS networking, yet!
Under FreeAXP the TCP/IP (or DECNet/LAT) hasn't configured, yet. The bare OS is working.
SimH VAX - no OS was installed so I wasn't able to test the network. I just used "sh xq eth" command.
So it is a over virtualised system now but it seems working (I hope the network will work, too in VMS).
In a later time I will make a test with real Win10 with the above install trick!
The virtualized Win10 (as host for VAX and AXP) is reachable from both VMS (VAX - 7.3 and AXP - 8.4)
VAX and AXP can communicate to each other.
Traffic from real network doesn't come back. On the target machine I can see ARP requests and no answer arrives back to VMS machines. I don't know why.
VirtualBox (Win10Pro) can communicate both direction.
Today I try to test a much more simple situation. Only FreeAXP its MSI PCAP driver and SimH alone with NCAP 0.93 (or the newer 0.94). I think the problem is with NCAP.
A simplier test would be go back to the real Win10Pro with NCAP + SimH/FreeAXP.
I don't know what is the real problem because the operation is better than WinPCAP 4.1.x or Win10PCAP.
Oh I forgot to mention: DHCP is working! (both SimH and FreeAXP)
I got good IP address from the DHCP server which is situated on the real (wired) network!
When I got the IP I can't communicate (ping) the DHCP server. Strange...
TCPIP> sh arp
2: U 24 192.168.52.30 #0
TCPIP> sh interface/full
IP_Addr: 127.0.0.1 NETWRK: 255.0.0.0 BRDCST:
Flags: UP LOOP NOARP MCAST SMPX
Packets 51 51
Errors 0 0
.52.30 is the address of DHCP server.
OpenVMS 8.4, switched off NCAP drivers at LAN card properties dialog but not uninstalled. FreeAXP MSI driver installed, Win10 wasn't restarted.
Something very funny thing happened...
Without NCAP (uninstalled and the machine was rebooted) the situation is the same: DHCP OK and nothing more communication. On the Linux side there is answer for the VMS's ARP request but it doesn't reach Win10(?)/OpenVMS 8.4. :-(
I think the problem between Linux and Win.
I tested again networking. The result was better than last time.
I used: buit in NCAP driver, NPCAP, Win10Pcap.
The OpenVMS was V7.1-1H2. Network protocol: LAT.
Host OS: Ubuntu Linux 16.04.3 64 bit up-to-date.
Virtual system: VirtualBOX 5.1.28 r117968 in bridged mode. Bridge interface: br0. Emulated network card: Intel PRO/1000 MT Desktop
Guest OS in VirtualBOX: Win10 Pro 64 bit. Network is working!
FreeAXP 188.8.131.52. In pci11 there is a DE435 NIC for OpenVMS. EWA0 is online.
I tried to connect from an other Linux with LAT (llogin <service_name>.
llogin -d shows the service and available after OpenVMS starts.
When I try to connect to the service it becomes UNAVAILABLE! So the connection was unsuccessfull. In some seconds later the service becames AVAILABLE again checking with llogin -d command.
I think the VMS->real network works and the opposite direction doesn't.
The situation is the same with the other two PCAP driver (NPCAP and WIn10Pcap).
Using an other OpenVMS version (8.4) and TCPIP with VirtualBOX NAT networking, connection is better but it is an absolutelly different networking method, for example there isn't LAT to my real network.
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!