[Simh] V3.10 VAX causes blue screen

[Mark Pizzolato]

I'm glad you've got it going.

The issue you had is already fixed for future versions.  Future
versions will only list LAN capable devices (as long as
WinPcap/libpcap provides such a differentiation).

- Mark

--- aceyem at cox.net wrote:
>   Thanks for all the suggestions Mark.
> I updated the 3com driver from a 5 year old driver to the
> latest driver which was only 4 years old.  Also I checked
> WINPCAP to make sure it was the latest release.  Finally I
> started up both the 3.10 and the 3.02 versions of SIMH-VAX and
> checked the configurations.  Alas when I entered 
> SHOW XQ ETH
> I discovered the problem.  The 3.10 version lists the network
> devices in reverse order.  My configuration file was attaching
> XQ to the NdisWAN device instead of the 3Com Network
> Interface.
> >From now on I'll have to make sure I'm attaching to a real
> NIC and not a VDD.  Thanks again for all the help and great
> job on the VAX emulator!!!!  I have a VAXCluster containing
> A 4300, 3100/30 and 3 SIMHs, it's impossible to tell the real
> VAXen from the simulated ones at the software level.
> 
> Anthony McCracken
> aceyem at cox.net
> 
> _______________________________________________
> Simh mailing list
> Simh at trailing-edge.com
> http://mailman.trailing-edge.com/mailman/listinfo/simh