KnowledgeBase Archive

An Archive of Early Microsoft KnowledgeBase Articles

View on GitHub

Q115214: PRB: Project Editor Gives "Invalid File Format" at Startup

Article: Q115214
Product(s): Miscellaneous Software Development Kits
Version(s): 2.0,2.0a
Operating System(s): 
Keyword(s): 
Last Modified: 12-NOV-1999

-------------------------------------------------------------------------------
The information in this article applies to:

- Microsoft Multimedia Viewer Publishing Toolkit, versions 2.0, 2.0a 
-------------------------------------------------------------------------------

SYMPTOMS
========

Upon starting the Viewer Project Editor, an "Invalid File Format" error is
displayed.

CAUSE
=====

Viewer located and attempted to use an older version of the CMDIALOG.VBX custom
control.

RESOLUTION
==========

Check the date and time of the CMDIALOG.VBX file located in the \WINDOWS\SYSTEM
directory. If the file is dated before 3/22/93, it will need to be replaced.
This file can be found on the Viewer CD in the \SYSTEM directory.

If the CMDIALOG.VBX file located in the \WINDOWS\SYSTEM directory has a date
later than 3/22/93, check the directories specified in your MS-DOS path
(especially those that precede the Windows directory) for the presence of a
duplicate. If one is found, keep only the most recent copy and delete the
others.

Additional query words: viewer 2.00 2.00a 2.0a invalid file format

======================================================================
Keywords          :  
Technology        : kbHomeProdSearch kbHomeMMsearch kbMMViewer200 kbMMViewer200a
Version           : :2.0,2.0a

=============================================================================

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.