After Failed WFWG Setup, Not Enough Space to Setup Again

 Last reviewed: November 21, 1994
Article ID: Q92872
The information in this article applies to:
  • Microsoft Windows for Workgroups versions 3.1, 3.11

SYMPTOMS

Microsoft Windows for Workgroups Setup does not perform an upgrade over Microsoft Windows version 3.1 if it does not detect enough free disk space. If Setup fails for some reason and you run Setup a second time, it may refuse to upgrade your system.

CAUSE

This problem occurs if Setup incorrectly detects insufficient free disk space. Setup assumes it is upgrading Windows 3.1 and does not account for the Windows for Workgroups files it has already transferred.

WORKAROUND

To work around this problem, delete some Windows for Workgroups files before you start Setup. The following are some files you can safely delete: 

   NETAPI.DLL
   PMSPL.DLL
   WIN386.EXE
You can also delete files with the extensions .BMP and .HLP. These files are copied again when you run Setup.

NOTE: Avoid deleting files with the extensions .INI and .GRP. Such files contain information about your custom Windows configuration.

MORE INFORMATION

Windows for Workgroups Setup uses WINVER.EXE to determine which version of Windows it is installing over. Unfortunately, WINVER.EXE is one of the last files to transfer. Often in a failed installation, WINVER.EXE does not get copied; therefore, Setup thinks that it is upgrading Windows 3.1.

KBCategory: kbsetup
KBSubcategory: wfw wfwg
Additional reference words: 3.10 3.11

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.

Last reviewed: November 21, 1994
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.