jmarty@sagelink.com wrote: >> Any known problems with Trumpet Winsock 2 or 3. It doesn't pick >> up the assigned IP. and Steven P. Crain added: >I've seen a problem like you described. If the person had a static IP or >had 0.0.0.0 set in Winsock, it worked. Normally Winsock tries to get the >address it had before, and that seems to cause the problem. Adding >something like -ip=0.0.0.0 to the Winsock command line helped for our >customers. Trumpet Winsock "remembers" IPs between sessions unless the user closes (exits) Trumpet between sessions. What makes matters WORSE is that Trumpet (2.x, at least) will SAVE an IP in its *.ini file if the user opens up the settings window and clicks upon "Save". The forcing of the IP address to 0.0.0.0 is a way around this, but it still does not cover the case of multiple connect attempts in one invocation of Trumpet. If you have a large number of Trumpet Winsock users, you may want to consider messing about with a "standard" script to distribute to your customers. The key command that can overcome your problem is: load <variable> [<string variable> [<ini file>]] Trumpet 2.1F's help file says the following about the command: Returns <variable> which may be integer or string from <ini file>. Where <string variable> is the section name within the ini file and defaults to "default vars", and <ini file> is the name of the Winsock ini file and defaults to "trumpwsk.ini". Note that the file extension must be specified with the file name. The idea here would be to overtly load the default IP address (assumed to want to be "0.0.0.0") from the *.ini file each and every time before dialing. To overcome the possible inadvertent saving of a (dynamically assigned) IP address to the *.ini file, you may want to also use the "save" command: save <variable> [<string variable> [<ini file>]] One could do this with each and every parameter. To overwrite any bad values with proper ones, I would suggest that you first SAVE a literal string, then LOAD the SAVEed value from the *.ini file before dialing if you want 100% bullet-proof and idiot-proof operation. ...of course, every time I think I have something to the point of being "idiot-proof", someone goes out and invents a more idiotic idiot... It may be lonely at the top, but at least you eat better. james fischer jfischer@supercollider.com ++ Ascend Users Mailing List ++ To unsubscribe: send unsubscribe to ascend-users-request@bungi.com To get FAQ'd: <<A HREF="http://www.shore.net/~dreaming/ascend-faq">http://www.shore.net/~dreaming/ascend-faq</A>> or <<A HREF="ftp://ftp.shore.net/members/dreaming/ascend-faq.txt">ftp://ftp.shore.net/members/dreaming/ascend-faq.txt</A>> </PRE> <!--X-MsgBody-End--> <!--X-Follow-Ups--> <!--X-Follow-Ups-End--> <!--X-References--> <!--X-References-End--> <!--X-BotPNI--> <HR> <UL> <LI>Prev by Date: <STRONG><A HREF="msg04758.html">(ASCEND) CACHE-TOKEN and APP Server</A></STRONG> </LI> <LI>Next by Date: <STRONG><A HREF="msg04757.html">Re: (ASCEND) MAX-->CISCO ISDN connexion</A></STRONG> </LI> <LI>Prev by thread: <STRONG><A HREF="msg04759.html">RE: (ASCEND) CRC 4</A></STRONG> </LI> <LI>Next by thread: <STRONG><A HREF="msg04758.html">(ASCEND) CACHE-TOKEN and APP Server</A></STRONG> </LI> <LI>Index(es): <UL> <LI><A HREF="mail166.html#04760"><STRONG>Main</STRONG></A></LI> <LI><A HREF="thrd13.html#04760"><STRONG>Thread</STRONG></A></LI> </UL> </LI> </UL> <!--X-BotPNI-End--> <!--X-User-Footer--> <!--X-User-Footer-End--> </BODY> </HTML>