Reasons for Failure of SetRestartDir

Last reviewed: July 23, 1997
Article ID: Q113187
3.10 WINDOWS kbtool

The information in this article applies to:

  • Microsoft Windows Software Development Kit (SDK) for Windows version 3.1

SUMMARY

The SetRestartDir subroutine from the Setup Toolkit will return 0 (zero) for any of the following reasons:

  • The restart directory has already been set by an earlier call to SetRestartDir from the setup script.
  • The value of the STF_CWDDIR symbol is an empty string or it is not a valid directory.
  • _MSSETUP.EXE is not in the STF_CWDDIR directory. This is true if MSSETUP.EXE is not included in the [Files] section of the SETUP.LST file.
  • _MSSETUP.EXE cannot be copied from the STF_CWDDIR directory to the restart directory.
  • _MSSETUP._Q_, a temporary file created in the temporary directory specified in SETUP.LST by SETUP.EXE, cannot be copied to the restart directory.
  • The restart directory specified is invalid. The syntax for the directory name is:

          drive:\[dir[\subdir...][\]]
    


Additional reference words: 3.10 mssetup
KBCategory: kbtool
KBSubcategory: TlsMss
Keywords : kb16bitonly


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: July 23, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.