Search the FAQ Archives

3 - A - B - C - D - E - F - G - H - I - J - K - L - M
N - O - P - Q - R - S - T - U - V - W - X - Y - Z
faqs.org - Internet FAQ Archives

Win95 FAQ Part 8 of 14: Dial-up Networking
Section - 8.4. Using Trumpet (TM) and other TCP/IP stacks (Just don't!)

( Part1 - Part2 - Part3 - Part4 - Part5 - Part6 - Part7 - Part8 - Part9 - Part10 - Part11 - Part12 - Part13 - Part14 - Single Page )
[ Usenet FAQs | Web FAQs | Documents | RFC Index | Cities ]


Top Document: Win95 FAQ Part 8 of 14: Dial-up Networking
Previous Document: 8.3. How do I run my Winsock program?
Next Document: 8.5. How do I get dial-up networking to work with other stuff besides The Internet?
See reader questions & answers on this topic! - Help others by sharing your knowledge
   Yes they do work, as long as you don't have any Win95 networking
   components installed. Problem is, when you make a networking change,
   Setup might decide to re-copy the files over, and when it does it will
   happily over-write WINSOCK.DLL. Remember: Winsock was designed for
   other protocols too, not just TCP/IP, and it's a standard OS component
   now! So, either use Win95's networking and Win95's dialer, or use no
   Win95 networking and someone else's dialer.
   
   And yes, you can make 32-bit Winsock apps work with older stacks.
   There's a WSOCK32 "thunk" available that works with an existing Win
   3.1 dialer and their own WINSOCK.DLL. It's somewhere on
   www.windows95.com but I forgot where.
   
   You could also check out Trumpet's own 32-bit TCPMAN or TGV's
   replacement TCP/IP stack.

     * 8.4.1. Netscape 32 Personal Edition's Setup Wizard screws up
       TCP/IP 
       
   If you install Netscape Personal Edition for Windows 95 (whatever
   version) it presents you with a connection setup wizard similar to
   Microsoft's Internet Setup Wizard. DON'T USE IT.
   
   Known problems:
     * It will gladly install a second instance of TCP/IP without
       checking first
     * It skips components of Win95 dial-up networking
     * It goofs up your TAPI location properties, so that whenever you
       try to connect, Win95 presents you with "There was an error in
       your configuration. It has been fixed." without actually FIXING
       IT.
       
   You can only correct this goofup by removing and re-installing Dial-up
   Networking, and any instances of TCP/IP from Network Properties. You
   will also need to make sure you configure your modem and location
   properties in the Modems control panel. See the steps in section
   8.1.2 above.

     * 8.4.2. Obtaining Winsock 2.0 for Win95
       
   To allow for multiple TCP/IP connections or to support Winsock 2 apps,
   MS released Winsock 2.0 for Win95 at
   http://www.microsoft.com/windows/downloads/contents/Updates/W95So
   ckets2/default.asp. This update resolves a few nasty bugs (mostly
   revolving around Denial of Service attacks). This works with any net
   card or release of Dial-up Networking before DUN 1.3; DUN 1.3 includes
   Winsock 2.
   

User Contributions:

Comment about this article, ask questions, or add new information about this topic:

CAPTCHA




Top Document: Win95 FAQ Part 8 of 14: Dial-up Networking
Previous Document: 8.3. How do I run my Winsock program?
Next Document: 8.5. How do I get dial-up networking to work with other stuff besides The Internet?

Part1 - Part2 - Part3 - Part4 - Part5 - Part6 - Part7 - Part8 - Part9 - Part10 - Part11 - Part12 - Part13 - Part14 - Single Page

[ Usenet FAQs | Web FAQs | Documents | RFC Index ]

Send corrections/additions to the FAQ Maintainer:
gordonf@intouch.bc.ca





Last Update March 27 2014 @ 02:12 PM