BUG: Executable Error "<path> is not an object file"

 Last reviewed: April 24, 1997
Article ID: Q163933
The information in this article applies to:
  • Microsoft Visual FoxPro for Windows, versions 5.0, 5.0a

SYMPTOMS

If you run an executable installed from disk images created by the Visual FoxPro Setup Wizard, the following error message appears: 

   "<Path and file name to executable> is not an object file."
Note that the size of the executable installed on the destination machine is larger than the original.

RESOLUTION

There are two possible workarounds to this situation:

  1. Distribute an additional file that is named alphabetically first. For example, if there is only one file being distributed and it is named "myexe.exe," add an additional file named "a.txt."

  2. If possible, use the NetSetup images instead of diskette images created by the Setup Wizard.

STATUS

Microsoft has confirmed this to be a problem in the Microsoft products listed at the beginning of this article. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

MORE INFORMATION

The three criteria that cause this error are:

  • The .EXE to distribute must be large enough to have the Setup Wizard split it into separate files for distribution.
  • The split files must spread across more than one diskette image.
  • The .EXE file name must be the first file, alphabetically, of the files being distributed via the Setup Wizard.

Additional query words: grow grew increased bigger
Keywords : buglist5.00 FxtoolDk kbtool vfoxwin vfpbug5.0a kbbuglist
Version : 5.0a 5.0
Platform : WINDOWS
Issue type : kbbug

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