Windows 3.1 Setup Asks for Disk 5

Last reviewed: November 21, 1994
Article ID: Q83385
The information in this article applies to:
  • Microsoft Windows operating system versions 3.1, 3.11

SUMMARY

When updating Windows version 3.0, the Windows version 3.1 Setup will ask for Disk 5 before asking for Disk 4, and without copying all the files from Disk 3.

This problem is caused by the Windows version 3.1 Setup program finding the Windows version 3.0 SETUP.EXE in the WINDOWS\SYSTEM directory.

Deleting SETUP.EXE from the WINDOWS\SYSTEM directory and restarting the Windows version 3.1 Setup from Disk 1 will successfully install Windows version 3.1.

MORE INFORMATION

When updating Windows version 3.0, the Windows version 3.1 Setup program will delete any SETUP.EXE file in the WINDOWS directory. However, if a SETUP.EXE exists in the WINDOWS\SYSTEM directory it will not be deleted. Because of this, when Windows Setup needs to reload itself it may load the Windows version 3.0 Setup instead.

There are two situations that will arise because of this problem:

  1. The Windows version 3.1 Setup will finish copying the files from Disk 2, then ask for Disk 5.

  2. The Windows version 3.1 Setup will copy some of the files from Disk 3, bring up Windows to complete the setup, and ask for Disk 5 without copying any additional files from Disk 3.

To successfully install Windows version 3.1, delete the SETUP.EXE from the WINDOWS\SYSTEM directory and restart the Windows version 3.1 Setup from Disk 1.

Microsoft is researching this problem and will post new information here as it becomes available.


KBCategory: kbsetup kbenv
KBSubcategory: win31
Additional reference words: 3.10


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.