Using VMware and these Quake clients is problematic

[sschm]

This is not a problem for most people, because "most people" do not have VMware installed on their Windows OS.

VMware creates a few "virtual" network adapters that I have noticed ProQuake and Qrack incorrectly handle. When I try to connect to a server with the VMware adapters enabled, these clients will ALWAYS select the wrong IP address that belongs to a "virtual" device associated with VMware. Is there a command (startup or console) that enables you to select which IP/adapter you want to use for network activity?

Here is a screenshot of the problem: MEGAUPLOAD - The leading online storage and file delivery service

Notice that it is automatically selecting the last adapter on the list (IP #2), which belongs to a virtual VMware device, and therefore is not suitable for network activity with Quake.

The only solution I know for this is to temporarily disable the virtual VMware adapters before launching Quake.

[Baker]

-ip xxx.xxx.xxx.xxx command line parameter in ProQuake (works in Qrack too I bet).

Yes, NetQuake's network code is quite outdated. Some NQ engines like notably DarkPlaces don't have the issue.

[rev]

the virtual adapters created by VMware aren't capable of network activity anyway, correct?

[rev]

it just occurred to me, my previous post is your entire point. you're trying to direct the quake clients to use your literal adapter, right? disabling the adapters in your other environments should do the trick though also.