DOCUMENT:Q173500  01-JUL-1998  [msnetwork]
TITLE   :Error Message: MSN Failed to Load Folcom.dll
PRODUCT :The Microsoft Network
PROD/VER:WINDOWS:2.5
OPER/SYS:WINDOWS
KEYWORDS:kbenv kberrmsg kbfile msnconnect kbmsn

======================================================================
---------------------------------------------------------------------
The information in this article applies to:

 - The Microsoft Network version 2.5
---------------------------------------------------------------------

SYMPTOMS
========

When you connect to MSN, The Microsoft Network, you may receive the
following error message:

   MSN failed to load Folcom.dll.

If you click Setup or Help, you may receive the following error message:

   Msn.ini file badly formed. Please contact Product Support.

CAUSE
=====

This issue can occur if the Wsock32.dll file is damaged or missing.

RESOLUTION
==========

To resolve this issue, replace the Wsock32.dll file.  To do so, use the
following steps:

1. Click Start, click Shut Down, click "Restart the computer in MS-DOS
   mode," and then click Yes.

2. At the MS-DOS prompt, type the following command, and then press ENTER

      <drive>:

   where <drive> is the letter of the drive on which Windows is installed.
   For example, if Windows is installed on drive C, type the following:

      c:

3. Type the following commands, pressing ENTER after each command:

      cd\windows\system
      ren wsock32.dll wsock32.old
      exit

4. Extract a new copy of the Wsock32.dll file to the Windows\System
   folder. You can extract the Wsock32.dll file from the following
   locations:

    - The Win95_11.cab cabinet file on the Windows 95 CD-ROM
    - The Win95_12.cab cabinet file on the original Windows 95 DMF disks
    - The Win95_19.cab cabinet file on the original Windows 95 non-DMF
      disks
    - The Win95_18.cab cabinet file on the Windows 95 OEM Service Release
      2 CD-ROM

   If you are using Microsoft Windows 98, you can extract the Wsock32.dll
   file from the following location:

    - The Precopy1.cab cabinet file on the Windows 98 CD-ROM.

For information about how to use the Extract tool, please see the
following article in the Microsoft Knowledge Base:

   ARTICLE-ID: Q129605
   TITLE     : How to Extract Original Compressed Windows Files

5. Restart your computer normally.

MORE INFORMATION
================

This issue may also occur if you run RegClean, version 3.0 or 4.0, on
your computer, and then attempt to run Visual Basic for Applications code
that uses Automation to control another program. The issue occurs because
RegClean 3.0 or 4.0 removes the keys that are required to use Automation.

NOTE: The RegClean utility has been updated.

To resolve this issue, download and install a custom registry file that
replaces keys that are removed by RegClean.

The following file is available for download from the Microsoft Software
Library:

 ~ Idisp.exe   (16 KB)

For more information about downloading files from the Microsoft Software
Library, please see the following article in the Microsoft Knowledge Base:

   ARTICLE-ID: Q119591
   TITLE     : How to Obtain Microsoft Support Files from Online Services

You can also download an updated version of RegClean 4.1. The updated
version of RegClean prevents the problem from occurring. RegClean 4.1 does
NOT remove the keys that are required to use Automation.

For more information about RegClean 4.1, please see the following articles
in the Microsoft Knowledge Base:

   ARTICLE-ID: Q147769
   TITLE     : Updated Version of RegClean 4.1 Available

Additional query words: 2.50 msnet msnetwork microsoft-net m.s.n.
======================================================================
Keywords          : kbenv kberrmsg kbfile msnconnect kbmsn 
Version           : WINDOWS:2.5
Platform          : WINDOWS
Issue type        : kbprb

=============================================================================

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS
PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND.  MICROSOFT DISCLAIMS
ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES
OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.  IN NO
EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR
ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL,
CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF
MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE
POSSIBILITY OF SUCH DAMAGES.  SOME STATES DO NOT ALLOW THE EXCLUSION
OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES
SO THE FOREGOING LIMITATION MAY NOT APPLY.

Copyright Microsoft Corporation 1998.