<html><head><style type="text/css"><!-- DIV {margin:0px;} --></style></head><body><div style="font-family:times new roman,new york,times,serif;font-size:12pt"><div>If you want to communicate between Windows host machine and SIMH, the easiest setup is Windows Loopback Adaptor (yes, with "o"). To avoid confusion by name, it is not an adapter that is associated with address 127.0.0.1, but a virtual Ethernet card driver that creates a subnet connected on one side to the Windows host machine, and on other side to applications, pretty much like TAP/TUN, but without the hassle.<br><br>Loopback Adaptor can be installed from Device Manager (on Windows 7, Action -> Add Legacy Hardware -> manually -> Network -> Microsoft -> Microsoft Loopback Adaptor, and there is similar sequence in XP).<br><br>Once the adapter is installed, assign its host-side address in Control Panel (something like 192.168.3.1/255.255.255.0), restart the machine to get PCAP to
recognize it, then bind it on SIMH side the usual way, just as you would bind a physical adapter, and configure it inside VMS.<br><br>Note that there is a bug in SIMH 3.8.1 autoconfigure that causes mis-assignment of QBus device vectors when there are two XQ devices present and that may cause some other devices such as DHV stop working. I forwarded the fix some time ago to Robert Supnik, so if you run into the problem perhaps he could advise how to obtain the codebase that incorporates the fix.<br></div><div style="font-family:times new roman, new york, times, serif;font-size:12pt"><br><div style="font-family:arial, helvetica, sans-serif;font-size:13px"><font face="Tahoma" size="2"><hr size="1"><b><span style="font-weight: bold;">From:</span></b> Timothe Litt <litt@ieee.org><br><b><span style="font-weight: bold;">To:</span></b> Stafford Winters <stafford.winters@gmail.com><br><b><span style="font-weight: bold;">Cc:</span></b>
simh@trailing-edge.com<br><b><span style="font-weight: bold;">Sent:</span></b> Wed, December 21, 2011 11:03:36 AM<br><b><span style="font-weight: bold;">Subject:</span></b> Re: [Simh] Network interfaces under Windows<br></font><br>
Your second interface probably doesn't have an IP address assigned (under<br>windoze); annoyingly, libpcap doesn't return interfaces without addresses.<br> <br>Be careful picking a subnet.<br><br>Alternatively, you don't actually need a dedicated interface. I use OpenVPN<br>(just install the TAP adapter & bridge it to your primary ethernet card).<br>You don't need the whole OpenVPN package. Don't forget to set the Media<br>Status of the TAP to Always Connected, and things just work.<br><br><br>---------------------------------------------------------<br>This communication may not represent my employer's views,<br>if any, on the matters discussed. <br> <br>-----Original Message-----<br>From: <a ymailto="mailto:simh-bounces@trailing-edge.com" href="mailto:simh-bounces@trailing-edge.com">simh-bounces@trailing-edge.com</a> [mailto:<a ymailto="mailto:simh-bounces@trailing-edge.com"
href="mailto:simh-bounces@trailing-edge.com">simh-bounces@trailing-edge.com</a>]<br>On Behalf Of Stafford Winters<br>Sent: Wednesday, December 21, 2011 13:48<br>To: <a ymailto="mailto:simh@trailing-edge.com" href="mailto:simh@trailing-edge.com">simh@trailing-edge.com</a><br>Subject: [Simh] Network interfaces under Windows<br><br>I've had SimH for several months, running VAX (including ethernet<br>support) with OpenVMS installed. (WinPcap is installed.) I decided I<br>wanted to add a second network card so that I could telnet in from the same<br>computer to the OpenVMS system. I had a Dynex DX-E102 available, so I stuck<br>it in the computer, but I don't see it as an available network interface<br>under SimH. The primary network interface is an integrated NVIDIA nForce<br>10/100/1000. To complicate matters, I have old VMware Player software<br>installed (version 1.0.2.xxxx) that allows me to run some necessary
software<br>for a client. The host computer is running Windows XP Professional x64<br>Edition. Under SimH:<br>sim> show xq eth<br>ETH devices:<br> 0 \Device\NPF_{4EBEA91C-BB4D-4EB4-A3D0-D44914480A2F} (Local Area<br>Connection)<br> 1 \Device\NPF_{237514F4-8533-43C8-A69E-E94618353E5F} (VMware Network<br>Adapter VMnet8)<br>sim><br>The Local Area Connection is the NVIDIA NIC. Am I not able to additional<br>network interfaces because of VMware, or is the Dynex NIC not usable for<br>this, or is it something else altogether?<br><br>I realize this is a bit on the fringe for SimH discussion, but I haven't<br>been able to find anything that seems promising in my internet searches.<br>Thanks for any pointers you can provide.<br>_______________________________________________<br>Simh mailing list<br><a ymailto="mailto:Simh@trailing-edge.com" href="mailto:Simh@trailing-edge.com">Simh@trailing-edge.com</a><br><span><a
target="_blank" href="http://mailman.trailing-edge.com/mailman/listinfo/simh">http://mailman.trailing-edge.com/mailman/listinfo/simh</a></span><br><br>_______________________________________________<br>Simh mailing list<br><a ymailto="mailto:Simh@trailing-edge.com" href="mailto:Simh@trailing-edge.com">Simh@trailing-edge.com</a><br><a href="http://mailman.trailing-edge.com/mailman/listinfo/simh" target="_blank">http://mailman.trailing-edge.com/mailman/listinfo/simh</a><br></div></div>
</div></body></html>