[Info-vax] Enabling network in the "student" kit...

Jan-Erik Söderholm jan-erik.soderholm at telia.com
Fri Jul 12 06:25:49 EDT 2019


Den 2019-07-11 kl. 17:14, skrev Jan-Erik Söderholm:
> Den 2019-07-11 kl. 11:27, skrev Hans Bachner:
>> Jan-Erik Söderholm schrieb am 10.07.2019 um 11:05:
>>> Den 2019-06-20 kl. 09:29, skrev Jan-Erik Söderholm:
>>>
>>>> My plan is to try with a spare laptop not used for anything else.
>>>
>>> Now tested on a Win10 Pro laptop with nothing particular running.
>>> I cannot see any network interface in the config tool. Apart from
>>> the "Dummy Network" and "Invalid adapter: ask". The network
>>> interfaces aren't seen by the config tool...
>>>
>>> Has *anyone* get the network running from the Student Kit?
>>>
>>> [...]
>>>
>>> Jan-Erik.
>>
>> Yes I did. As someone else suggested elsewhere in this thread, you need 
>> to download the latest "official" FreeAXP kit (3.0.0.620 at this time) 
>> from <http://www.migrationspecialties.com/FreeAXP.html#Kits> and install 
>> this. Then install the VSI student kit which will uninstall the FreeAXP 
>> kit and replace it with its newer version (3.1.0.627), but networking 
>> will be available at this point.
>>
>> This works fine on a Windows Server 2016, so I assume it will work on 
>> Windows 10 as well.
>>
>> Hope this helps,
>> Hans.
> 
> OK, installing the 3.0.0.620 kit and then reinstalling the VSI kit
> got the device to show up in the config tool. Just clicked "OK" both
> times to remove the other one. The device I selected in the config
> tool is called "WiFi", same name as ipconfig reports. The laptop
> is not wired.
> 
> Then I had to switch EWA0_MODE to FastFD (was some single duplex mode)
> and then the VMS environment is visible with PING at least. Both from
> the local Win10 laptop and from another laptop on the same subnet.
> 
> Then tried with SSH, Telnet and FTP but got could not connect, was
> disconnected with some "connection refused" message. Not sure where
> that message originated, nothing is logged on the VMS environment.
> Tried both from the local Win10 system and a remote Win10 system.
> 
> I have closed down the local Win10 firewall but that didn't help.
> 
> Aything else that have to be done to get the network traffic through?
> Is there any issues to share the same WiFi connection in this way
> between the local Win10 system and the VMS environment?
> 
> Does this has anything to do with those special drivers that also
> was discussed here a bit earlier?
> 
> Jan-Erik.

OK. Very few (anyone?) here seems to have got this kit running
including network support. I'll try to the VSI support and see
what that gives...



More information about the Info-vax mailing list