Desperate for immediate help with Win95 IP stack

From: Kai Kaltenbach <kaikal_at_MICROSOFT.com>
Date: Tue Jun 22 12:44:15 1999

Despite your best efforts to keep me from helping you by dissing Microsoft
in your help request :), here is the solution to your problem from the MS
KnowledgeBase
(http://support.microsoft.com/support/kb/articles/q191/0/64.asp)

Kai


Error Messages When Running TCP/IP-Based Utilities or Programs[win95x]
ID: Q191064 CREATED: 06-AUG-1998 MODIFIED: 28-MAY-1999
WINDOWS:95
WINDOWS
PUBLIC | kberrmsg kbtool win95

\* Security : PUBLIC
======================================================================
----------------------------------------------------------------------------

---
The information in this article applies to:
 - Microsoft Windows 95 
----------------------------------------------------------------------------
---
SYMPTOMS
========
You may experience the following symptoms when you attempt to use a
Transmission
Control Protocol/Internet Protocol-based (TCP/IP-based) utility or program:
 - When you attempt to use the Winipcfg utility, you receive the following
error
   message:
   Fatal Error! Cannot read IP configuration.
 - When you attempt to ping a Web site name or TCP/IP address using the Ping
   utility, you receive either of the following error messages:
       - Bad IP address <Web address>
       - PING: transmit failed, error code 10091
 - When you attempt to load a Web page using Internet Explorer, you receive
the
   following error message:
   Internet Explorer cannot open the Internet site <Web address>. A
   connection with the server could not be established.
 - When you try to uninstall Microsoft Personal Web Server 4.0, you receive
the
   following error message:
   WINSOCK2 is required to run this setup utility. Please click OK to exit
   setup.
CAUSE
=====
This behavior can occur if you attempt to uninstall the Winsock 2.0 update
for
Windows 95, but it is not uninstalled completely.
RESOLUTION
==========
To resolve this behavior, follow these steps:
1. Click Start, point to Programs, and then click MS-DOS Prompt.
2. At the command prompt, type the following commands, pressing ENTER after
each
   command
   cd\<windows>\ws2bakup
   ws2bakup.bat
   exit
   where <windows> is the folder in which Windows is installed.
   NOTE: If you are prompted to abort, retry, or fail the operation, press
A.
   This causes the Ws2bakup.bat to continue restoring up all the necessary
   files.
   NOTE: If you receive sharing violation error messages when you run the
   Ws2bakup.bat file, continue with step 3.
3. Click Start, click Shut Down, click "Restart in MS-DOS mode," and then
click
   OK.
4. Repeat step 2.
   NOTE: If you receive error messages when you run the Ws2bakup.bat file
stating
   that some programs cannot be run outside of Windows 95, disregard them.
MORE INFORMATION
================
For more information about the Winsock 2.0 update for Windows 95, please see
the
following article in the Microsoft Knowledge Base:
   Q182108 Availability of Windows Sockets 2.0 for Windows 95
Additional query words: wsock
======================================================================
Keywords          : kberrmsg kbtool win95 
Version           : WINDOWS:95
Platform          : WINDOWS
Issue type        : kbprb
\* Edit Status    : Published
\* Tech Status    : Reviewed
-----Original Message-----
From: Sellam Ismail [mailto:dastar_at_ncal.verio.com]
Sent: Monday, June 21, 1999 11:15 PM
To: Discussion re-collecting of classic computers
Subject: OT: Desperate for immediate help with Win95 IP stack
I would normally not post such a lame question to this list but I need
help desparately and don't have time to go wading through a haystack for a
needle.  Its bad enough I have to keep re-visiting this problem of windows
deciding to kill itself every few months for the joy of it.
My IP stack is hosed on my Win95 machine.  When I try to ping any host I
get "Transmit failed, error code 10091".  If I try to run WINIPCFG I get
"Fatal error: cannot read IP configuration".
Since MS is fucked and doesn't have any sort of technical documentation
anywhere useful that would list these errors I must now try to go
searching for what this bullshit means.  Unless you already have the
answer?
This started to happen after I had to re-install windows over the existing
install, because it all of a sudden started coming up with a "Windows
exception" during boot and would not boot any further.
TIA.
Sellam                                    Alternate e-mail:
dastar_at_siconic.com
----------------------------------------------------------------------------
--
Don't rub the lamp if you don't want the genie to come out.
             Coming this October 2-3: Vintage Computer Festival 3.0!
                   See http://www.vintage.org/vcf for details!
                        [Last web site update: 05/25/99]

Received on Tue Jun 22 1999 - 12:44:15 BST