Home · Articles · Downloads · Hobby Wear · Forums · Web Links · News CategoriesFriday, March 29, 2024
Navigation
Home
Articles
Downloads
Hobby Wear
FAQ
Forums
Web Links
News Categories
Contact Us
Photo Gallery
OpenVMS Bigot
Search
Users Online
Guests Online: 5
No Members Online

Registered Members: 7,708
Newest Member: nifseg
Sponsors
Island Computer
View Thread
OpenVMS Hobbyist Program | Alpha Systems Forums | FreeAXP
Author FreeAXP on VirtualBox Windows10 on OSX - NIC problem
gremlin
Member

Posts: 22
Joined: 19.04.10
Posted on November 06 2017 16:24
I suppose this may be a VirtualBox/FreeAXP problem...

On an OSX 10.13.1 host, I have installed VirtualBox and created a VM with two NICs and loaded Windows10 into the VM; then installed FreeAXP on that. Within Windows10, one of the NICs has all Windows clients removed in Properties.

Windows sees and can use both NICs; FreeAXP cannot "see" either NIC. Choosing Bridged or NAT within VirtualBox makes no difference. The only option for connecting the DE500 is "Dummy Network".

Would appreciate some help please smiley
Author RE: FreeAXP on VirtualBox Windows10 on OSX - NIC problem
Bruce Claremont
Moderator

Posts: 623
Joined: 07.01.10
Posted on November 07 2017 02:38
What version of FreeAXP is installed?

Best I can suggest at the moment is re-install FreeAXP and see if it picks up the NICs.
Author RE: FreeAXP on VirtualBox Windows10 on OSX - NIC problem
gremlin
Member

Posts: 22
Joined: 19.04.10
Posted on November 07 2017 10:05
FreeAXP was downloaded three days ago, so current version I guess - 3.0.0.614

I have uninstalled, rebooted and reinstalled twice, and it still doesn't pick up any adapter. I have also bridged the two NICs, on the off chance that it will pick up the bridge adapter...it doesn't smiley
Author RE: FreeAXP on VirtualBox Windows10 on OSX - NIC problem
Bruce Claremont
Moderator

Posts: 623
Joined: 07.01.10
Posted on November 08 2017 02:30
Try FreeAXP 598 and see if it sees the NICs. If not, I am stumped at present.
Author RE: FreeAXP on VirtualBox Windows10 on OSX - NIC problem
gremlin
Member

Posts: 22
Joined: 19.04.10
Posted on November 08 2017 11:00
Uninstalled 614, rebooted windows, installed 598, rebooted windows, ran 598 and...didn't detect any adapter. Both VirtualBox adapters happily talking to other devices on the local network and also out to the internet... smiley

The two choices in the NIC interface dropdown are "dummy network" and " Invalid adapter: ask".
Author RE: FreeAXP on VirtualBox Windows10 on OSX - NIC problem
Bruce Claremont
Moderator

Posts: 623
Joined: 07.01.10
Posted on November 09 2017 02:20
Two questions:

1) Is this 32 or 64-bit Windows 10?

2) Can you test on an older version of Windows?
Author RE: FreeAXP on VirtualBox Windows10 on OSX - NIC problem
gremlin
Member

Posts: 22
Joined: 19.04.10
Posted on November 09 2017 11:06
1 - unsure...64bit VirtualBox container, W10 says 32bit on 64bit CPU.

2 - same behaviour with Win8.1 on VirtualBox where W8.1 says 32bit on 64bit CPU.

Despite multiple installs, can't get a Windows install on VirtualBox to say 64bit on 64bit CPU, despite having install DVD that contains both media...
Author RE: FreeAXP on VirtualBox Windows10 on OSX - NIC problem
Bruce Claremont
Moderator

Posts: 623
Joined: 07.01.10
Posted on November 10 2017 02:45
My next suggestion was going to be try a 64-bit version of Windows. Have you tested under Bootcamp?
Author RE: FreeAXP on VirtualBox Windows10 on OSX - NIC problem
gremlin
Member

Posts: 22
Joined: 19.04.10
Posted on November 10 2017 10:36
I am not prepared to install Bootcamp, for a variety of reasons.

I guess that there is just something odd happening, I can use the emulator but without any network functionality smiley
Author RE: FreeAXP on VirtualBox Windows10 on OSX - NIC problem
Bruce Claremont
Moderator

Posts: 623
Joined: 07.01.10
Posted on November 13 2017 05:56
FreeAXP filters the network adapter list before presenting it to the end user. Our best guess at this point is that something in the way Virtualbox is presenting the adapters is causing the filter to reject them from the usable list.

Under Start> All Programs> Accessories> System Tools you will find the System Information application. Open System Information and drill down to Components> Network> Adapter. Please post the contents of the Adapter page.
Edited by Bruce Claremont on November 13 2017 05:58
Author RE: FreeAXP on VirtualBox Windows10 on OSX - NIC problem
gremlin
Member

Posts: 22
Joined: 19.04.10
Posted on November 13 2017 12:00
Tried to include a screen snapshot - can't seem to...

Intel(R) PRO/1000 MT Desktop Adapter
Intel(R) PRO/1000 MT Desktop Adapter #2
Microsoft Networtk Adapter Multiplexor Driver
WAN Miniport (IKEv2)
WAN Miniport (IP)
WAN Miniport (IPv6)
WAN Miniport (L2TP)
WAN Miniport (Network Monitor)
WAN Miniport (PPOE)
WAN Miniport (PPTP)
WAN Miniport (SSTP)
Author RE: FreeAXP on VirtualBox Windows10 on OSX - NIC problem
Bruce Claremont
Moderator

Posts: 623
Joined: 07.01.10
Posted on November 14 2017 02:53
There is a Print function under the File menu in the System Information tool. I need to see all of the details for each adapter. I'll PM you an email address to send the information to.
Author RE: FreeAXP on VirtualBox Windows10 on OSX - NIC problem
Bruce Claremont
Moderator

Posts: 623
Joined: 07.01.10
Posted on November 15 2017 02:01
Output received. Thanks. We'll have a look and see what we can figure out.
Author RE: FreeAXP on VirtualBox Windows10 on OSX - NIC problem
Bruce Claremont
Moderator

Posts: 623
Joined: 07.01.10
Posted on November 15 2017 03:17
It looks like you have teamed the NICs. I see a Microsoft Network Adapter Multiplexor Driver with an IP assigned while the Intel(R) PRO/1000 MT Desktop Adapters have no IP assigned.

Try this. Remove the Multiplexor. Allow all Windows default network functions on one of the Intel NICs. Re-install FreeAXP to force a refresh of the NIC list. See if both Intel NICs show up in the configuration utility NIC list.

FYI: Once you can see the NICs, it is sometimes necessary to treat virtual NICs like a wireless NIC. See sections 10.9 and 10.7 in the User Guide.
Author RE: FreeAXP on VirtualBox Windows10 on OSX - NIC problem
gremlin
Member

Posts: 22
Joined: 19.04.10
Posted on November 15 2017 10:49
I originally had the drives unbridged, as that didn't work, I found an article bout bridging them and trying to use the bridge adapter.

I have tried with both NICs in their default config, and one in default and the other with everything removed (MS client, IP4 and 6 etc.), but that didn't work either...
Author RE: FreeAXP on VirtualBox Windows10 on OSX - NIC problem
Bruce Claremont
Moderator

Posts: 623
Joined: 07.01.10
Posted on November 16 2017 01:53
Ok, we shall continue our research.
Author RE: FreeAXP on VirtualBox Windows10 on OSX - NIC problem
gremlin
Member

Posts: 22
Joined: 19.04.10
Posted on April 06 2018 02:10
[UPDATE]
The problem was almost certainly that the Windows installations were 32bit...even though I had "forced" a 64bit install.

So, I installed Windows Server 2016 64bit and - bingo - interface appears and can be configured.

And so now I have an additional/different problem...

The vAlpha has a fixed IP address of 192.168.56.10 on WE0 and it can ping itself and 127.0.0.1; the Windows host running on VirtualBox can also ping the VirtualBox LAN (vboxnet0) of 192.168.56.254 . The vAlpha can't ping any other IP address. Within the vAlpha, TCP is configured to use 192.168.56.254 as its router/gateway; there are no errors in startup.

The Windows host has two NICs, one is configured with all services (including TCPIP) unbound/unchecked and it is this NIC that is configured in FreeAXP as the DE500.

Clearly I am doing something wrong, but I can't figure out what it is...
Author RE: FreeAXP on VirtualBox Windows10 on OSX - NIC problem
Bruce Claremont
Moderator

Posts: 623
Joined: 07.01.10
Posted on April 06 2018 03:11
Take a look at sections 10.7, 10.9, and 10.10 in the User Guide. Also, you say IPV4 is enabled on the Windows side of the NIC used by FreeAXP. Make sure the IP address assigned on the Windows side does not conflict with the 192.168.56.10 address used by the FreeAXP system.
Jump to Forum:
Login
Username

Password



Not a member yet?
Click here to register.

Forgotten your password?
Request a new one here.
Member Poll
Are you going to OpenVMS Boot Camp 2016?

Yes

No

You must login to vote.
Shoutbox
You must login to post a message.

malmberg
August 04 2022
No more VAX hobbyist licenses. Community licenses for Alpha/IA64/X86_64 VMS Software Inc. Commercial VMS software licenses for VAX available from HPE.

ozboomer
July 20 2022
Just re-visiting.. No more hobbyist licenses? Is that from vmssoftware.com, no 'community' licenses?

valdirfranco
July 01 2022
No more hobbyist license...sad

mister_wavey
February 12 2022
I recall that the disks failed on the public access VMS systems that included Fafner

parwezw
January 03 2022
Anyone know what happened to FAFNER.DYNDS.ORG? I had a hobbyist account here but can longer access the site.

gtackett
October 27 2021
Make that DECdfs _2.1A_ for Vax

gtackett
October 27 2021
I'm looking for DECdfs V2.4A kit for VAX. Asking here just in case anyone is still listening.

MarkRLV
September 17 2021
At one time, didn't this web site have a job board? I would love to use my legacy skills one last time in my career.

malmberg
January 18 2021
New Hobbyist PAKs for VAX/VMS are no longer available according to reports. Only commercial licenses are reported to be for sale from HPE

dfilip
January 16 2021
Can someone please point me to hobbyist license pak? I'm looking for VAX/VMS 7.1, DECnet Phase IV, and UCX/TCPIP ... have the 7.1 media, need the license paks ... thanks!

Bart
October 16 2020
OpenVMS, and this website!

malmberg
September 05 2020
VSI community non-commercial licenses for AXP/IA64 are available now.

malmberg
September 05 2020
See the forum about licensing. Don't know if HPE hobby licenses still being issued. Commercial licenses still being sold.

silfox70
September 01 2020
I need the license for OpenVMS7.3. Where can I find them?

malmberg
August 29 2020
Eisner, which is currently being moved, got an SSH update and the keys were updated to more modern encryption standards.

Shoutbox Archive