
                          Frequently Asked Questions
                                       
     * When I start tshost, TwinSock doesn't minimise
     * When I start tshost, TwinSock minimises, but when I start
       applications nothing happens
     * I keep getting "Reentrant call to interrupt window" with Netscape
     * How do I use X Windows with TwinSock
     * Why doesn't DCC work with TwinSock
     * Is there a version of TwinSock for the MacIntosh
     * When I use TwinSock, my machine reboots or resets to a black
       screen
     * Does TwinSock work under OS/2
     * I've just upgraded Windows and TwinSock doesn't work anymore
     * Netscape 2.0B4 cannot connect
     * Internet Explorer 3.0 Incompatibility
     * Microsoft NetMeeting doesn't work
       
When I start tshost, TwinSock doesn't minimise

   This gets me all the time - make sure you're not running "screen" or
   "iscreen". These packages change the output of programs for efficiency
   reasons, and while the effect is transparent for visual work,
   protocols like those used by TwinSock get confused.
   
   This can also be caused by trying to start tshost with options which
   are unsuitable for your line. Try starting tshost without any options,
   and if that works, slowly proceed to better options until you find the
   best one that works.
   
When I start tshost, TwinSock minimises, but when I start applications nothing
happens

   This is usually caused by trying to start tshost with options which
   are unsuitable for your line. Try starting tshost without any options,
   and if that works, slowly proceed to better options until you find the
   best one that works.
   
I keep getting "Reentrant call to interrupt window" with Netscape

   This was caused by deviations from the Windows Sockets standard in
   TwinSock 1.0 to 1.4. This has been fixed in version 2.0.
   
How do I use X Windows with TwinSock

   My first reaction to this is that unless you are on a direct
   connection at more than 56000bps, don't - X Windows is painfully slow
   over a modem. However, for those inclined to punish themselves in this
   way, I'll tell you how to do it, but be warned that certain senators
   might want to have this censored on grounds of inciting people to
   violence:
   
   X Windows usually fails because somebody on the host is already using
   X Windows with the default display (:0.0). You can get around this by
   causing TwinSock to remap this display to another one, such as :1.0.
   
   To do this you will need to set up port remapping in the ".twinsock"
   file on your host. Refer to the TwinSock help file for more
   information.
   
   When you start your X Windows program with port remapping set up, a
   message will be displayed in your TwinSock window telling you how the
   port was remapped. As TwinSock will be an icon at this point, you will
   need to restore the TwinSock window.
   
        X Windows Display 0 remapped to X Windows Display 7

   or if you haven't given names to the ports:
        Port 6000 remapped to 6007

   You can then telnet to your host and start an xterm with the following
   command.
   
        xterm -display :7.0

   Note that it will take a while for the xterm to display. Be patient.
   
Why doesn't DCC work with TwinSock

   This was caused by a bug in versions 1.0 through to 1.4 when the host
   was using the Intel byte order. There should be no problems with DCC
   using TwinSock 2.0.
   
Is there a version of TwinSock for the MacIntosh

   No, but I am aware of one person who is considering doing this.
   Meanwhile, try SLiRP.
   
When I use TwinSock, my machine reboots or resets to a black screen

   This problem is somehow related to using the communications
   notification features of the Windows API. It only seems to occur in
   Windows 3.1 and 3.11, not Windows for Workgroups, Windows 95 or
   Windows NT. To fix the problem, add the line "UseNotify=0" to the
   "Config" section of TWINSOCK.INI in the Windows directory. This
   requires TwinSock 2.0.
   
   Update: Microsoft listed this as a bug in Windows 3.1 on April 4th
   1995. Refer to the KnowledgeBase article titled BUG: Extra
   N_RECEIVE/CN_TRANSMIT Events (PSS ID Number Q101420). This is several
   years after 3.1 was released, so at least I identified it faster than
   they did.
   
Does TwinSock work under OS/2

   Yes, but of course you will only be able to use the 16 bit version.
   
I've just upgraded Windows and TwinSock doesn't work anymore

   Windows 95 and Windows NT install files called "WINSOCK.DLL" and
   "WSOCK32.DLL". These files are used with the Microsoft TCP/IP which is
   included in these operating systems. The most common problem you will
   see when these files are installed is a "Network is down" message.
   
   To fix this, first find any WINSOCK.DLL and WSOCK32.DLL in your PATH,
   or in the WINDOWS or WINDOWS\SYSTEM directories and remove or rename
   them. Then copy the WINSOCK.DLL from the TwinSock distribution to the
   WINDOWS directory, and copy the WSOCK32.DLL from the TwinSock
   distribution to the WINDOWS\SYSTEM directory.
   
Netscape 2.0B4 cannot connect

   mross@escape.ca reports:
   
   For 32 bit Netscape, You need to go into the registry
   (Start...Run...REGEDIT.EXE) and edit the following:
   
   HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\AppsPath
   
   Delete the references to netscape.exe and naplayer.exe, this is a
   known fix.
   
   If you are Netscape 16 bit try renaming your netscape executable
   something other than netscape.exe.
   
Internet Explorer 3.0 Incompatibility

   This is due to the way TwinSock implements the "[sg]etsockopt" calls
   of Windows Sockets. There are two problems. The first is that some
   hosts fail [sg]etsockopt calls which the Windows Sockets standard
   requires to succeed. This is indicated by the "unexpected error"
   message. The second is that getsockopt blocks, which Internet Explorer
   3.0 doesn't like. The relevant areas of code are in "winsock.c".
   
Microsoft NetMeeting doesn't work

   No, it doesn't, does it? There are too many problems with this to go
   into, but the biggest is that TwinSock uses DDE to communicate between
   WINSOCK.DLL/WSOCK32.DLL and TWINSOCK.EXE/TWNSCK32.EXE. NetMeeting
   doesn't like this at all. The file in question (dde.c) needs to be
   replaced with something using WM_COPYDATA.
