Release Note
meiConfig

Description:
Use mpiAxisOriginGet /Set(...) and mpiAxisFlashOriginGet /Set(...) to save/restore the origin to a config file.

Description:
Log file field of Preferences Dialog box was accepting an invalid file name to save output text without displaying a warning message.

Now, if the user enters a file that cannot be opened and enables logging, an error message is displayed and logging is disabled.

Description:
The file meiConfig_lib\copyingFilter.txt version was obsolete. This file was corrected and the following measures taken to prevent it in the future:

1. Generate copyingFilter.txt automatically from the current MPI release
2. Added a test to assure that copyingFilter.txt file is valid
   
   

Description:
In previous versions, when a .DM file defined a drive param to have a minimum value equal to its maximum value, meiConfig would crash when the user views the drive params. This problem was fixed.

Description:
meiConfig would fail to run due to a missing system DLL. Several things have been changed to fix the problem:

1. MSVCP71.dll is now distributed in the MEI\bin\WinNT directory.
2. Missing DLLs that are known to be necessary are now reported.

The following error message will now be reported:

    meiConfig has failed to load a necessary module.
    One or more of the following files may be missing:
        {List of missing DLL files}
    Not found in any of these directories:
        {list PATH environment variable}

Description:
meiConfig crashes when an unrecognizable filter element is specified in the filter file.

Description:
When the input config file is more than two versions behind the current version, meiConfig may fail with an error message similar to the following:

MPI version mismatch: 03.04 (actual) != 03.01 (file)

Description:
When the user tells meiConfig to load a file that does not exist, the error message that it prints is "unknown url type." Something more coherent would be preferable. A more helpful message is now displayed.

Description:
meiConfig rounds the maximum value for a float data type, 3.402823466e+38, up to 3.40282347e+038. Since this is an invalid number, meiConfig displays an error when trying to load it. The user can work around the issue by manually fixing the values in the config file with a text editor (not meiConfigGui). This bug was fixed.