GPL,Win98 and D.U.N.-problem

I have a peer-to-peer network which uses TCP/IP. This setup worked fine for GPL until I "upgraded" my main machine to Win 98 (the other still has Win 95). Every time I tried to link in GPL, the Win98 machine would lock (as joiner or host). After three fingering to get out of this, I noticed that the Dial-up Networking connect window was opened underneath all of this. To fix this temporarily, I removed my modem driver and then it would work fine. The bad part is that I want to be able to receive calls either direct or internet to join GPL games. So, could someone tell me how to prevent GPL from bringing up the DUN window (or is something else causing my problem)? Thanks, Martin Fay

Never heard it put quite that way, but take two fingers out and it evokes the proper image. :-) Hmmm. You must have "alternate_ip_addr_lookup" set to 1 in core.ini. If your peer-to-peer IP addresses are assigned statically, you should be able to remove this line from core.ini. If they are assigned dynamically, then the line must be there. If this is the case, I believe there is a setting somewhere in the control panel maze that says "Automatically connect to the Internet when needed". If you can get away with not having this enabled, disable it. (Note that your dialup IP address will be found, regardless of the core.ini setting, whether the dialup IP address is either static or dynamic.) Randy

Randy, Thanks for the reply. I (you) solved the problem but read on because there's an interesting question at the bottom. >>Hmmm. You must have "alternate_ip_addr_lookup" set to 1 in core.ini. I don't actually. I have the 84/3 internet core or modem-to-modem core only. They are statically assigned. I found the check box under Internet settings in the control panel (I was looking in the DUN menus -wrong place) although it was still a little cryptic. I changed to connect to the internet over LAN instead of modem and this fixed my problem. Now for the interesting question: Is there a way to make a multi-purpose core.ini? For some strange reason, I can't get IPX working (stuck with TCP/IP for now) so on my network I would like to use the fast core.ini (net_use_mdm_bandwidth_for_tcp_ip = 0) for the peer-to-peer yet still have people join over my dial-up IP using the 84/3 core (or the modem-to-modem core: the assumedmodemconnectspeed dealy). In other words, can I have multiple listings in the core.ini file and direct them towards their specific IP addresses? My guess is I can't but I had to know for sure because this would help out quite a bit. Thanks, Martin

Quoted text (20 lines)

> > After three fingering to get out of this > Never heard it put quite that way, but take two fingers out and it > evokes the proper image. :-) > > I noticed that the Dial-up Networking connect window was opened > > underneath all of this. To fix this temporarily, I removed my modem > > driver and then it would work fine. > Hmmm. You must have "alternate_ip_addr_lookup" set to 1 in core.ini. > If your peer-to-peer IP addresses are assigned statically, you should > be able to remove this line from core.ini. If they are assigned > dynamically, then the line must be there. If this is the case, I > believe there is a setting somewhere in the control panel maze that > says "Automatically connect to the Internet when needed". If you can > get away with not having this enabled, disable it. (Note that your > dialup IP address will be found, regardless of the core.ini setting, > whether the dialup IP address is either static or dynamic.) > Randy

I had this with the demo. I renamed my dialup network, started GPL, closed GPL, and renamed my dialup back. Chuck

Cool. The net_use_mdm_bandwidth_for_tcp_ip setting was put in to reign in bandwidth usage for TCP/IP because of "funky" network connections like cable modems. From simple inspection, GPL can only determine whether a particular TCP/IP connection on your machine is a "normal" Windows dial-up networking connection, or some other type of connection. In the dial-up case, GPL will use the net_mdm_*_send_* bandwidth settings, regardless of whether net_use_mdm_bandwidth_for_tcp_ip is on or off. So, if all of your TCP/IP connections are either (a) standard dial-up connections, or (b) LAN connections, you should be able to turn off net_use_mdm_bandwidth_for_tcp_ip and achieve what you're trying to do. Your server will then feed dial-up clients using the net_mdm_*_send_* bandwidth settings, and will feed LAN clients using the net_lan_*_send_* values. Just be sure to have all your LAN clients turn this setting off, too, otherwise they will still be treating their TCP/IP LAN connections as mdm_bandwidth. This setting is only used when you use GPL's modem-to-modem connections. It in no way affects (or is affected by) the net_* settings. Randy