Setup Hangs on Second Disk When Copying Logo File

 Last reviewed: November 21, 1994
Article ID: Q63130
The information in this article applies to:
  • Microsoft Windows operating system versions 3.0, 3.0a

SYMPTOMS

The Microsoft Windows version 3.0 Setup program may stop responding (hang) on the second disk (or on the fourth disk if you use low density 360k disks). The status line displays the following: 

   Copying <filename>
where <filename is VGALOGO.LGO or another .LGO file.

CAUSE

This problem occurs because the program was not able to enter the Windows portion of Setup. This is the last file that is copied before the real-mode Windows version 3.0 portion of Setup is run. (This is not a problem with copying the .LGO file.)

WORKAROUND

Approach this type of problem as a failure to run real-mode Windows version 3.0, which is essentially what happens at this point in Setup. Examine all factors that could cause the failure of real-mode Windows, such as the following:

  1. Incorrect display driver selection and/or detection

  2. Incorrect network driver

  3. Incorrect mouse driver

  4. Problem with an older, incompatible, or improperly configured expanded-memory manager in the CONFIG.SYS while running Setup

  5. TSRs (terminate-and-stay-resident programs) or other drivers in the CONFIG.SYS and/or AUTOEXEC.BAT

  6. DASDDRVR.SYS not installed on PS/2 machines

  7. SHARE, APPEND, or SUBST commands

KBCategory: kbsetup kbdisplay
KBSubcategory: win30
Additional reference words: 3.0 3.00 3.0a 3.00a install disk disk2, 2
win30

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.