### D.2.9 Check your version of Mif2Go

If you are using the evaluation version of Mif2Go, see §D.1 Evaluation version is different.

If you are using a licensed version of Mif2Go, do the following:

1. In a text editor, open an output file (.htm or .rtf) that you created with Mif2Go, and search for the line that shows the Mif2Go version and build numbers. The line you want looks like this:

HTML: | <!-- generated by DCL filter dwhtm, Ver 3.3 m199 h280 -->
RTF: | {\info {\doccomm DCL filter dwrtf, Ver 3.3 m199 r285}}

Table D-1 lists the build numbers underlined in these examples.

2. If you are running Mif2Go from inside FrameMaker, check the build number of the Mif2Go plug-in, m2rbook.dll. Look for keyword PluginVersion in the [Setup] section of the project configuration file you were using when the problem occurred. Mif2Go updates the value of PluginVersion each time you run a conversion. For example:

[Setup]

PluginVersion=b103

Table D-1 lists the build number shown in bold in this example.

To make sure you are using the most current build, check PluginVersion value b NNN against the version of m2rbook NNN.zip on the Omni Systems Web site:

http://mif2go.com

3. Look for the latest revision history on the Mif2Go Web site:

http://mif2go.com

Navigate to Downloads > Basic Software > History, and download m2g_history_nn.txt; place this file in%OMSYSHOME%\common\docs.

4. Find the first entry in m2g_history_nn.txt that looks like the corresponding history entry in Table D-1, for MIF, and also for either HTML or RTF, whichever output type you are creating with Mif2Go.

Table D-1 Examples of build numbers for Mif2Go DLL files

Output type | First entry in history.txt | DLL file | Build | Current?
MIF | **For MIF (build 199) | drmif.dll | m199 | Yes
HTML | **For HTML (build 280) | dwhtm.dll | h274 | No
RTF | **For RTF (build 285) | dwrtf.dll | r285 | Yes
HTML or RTF | **For the plugin (m2rbook.dll, build 103) | m2rbook.dll | b103 | Yes

5. If the first build number in m2g_history_nn.txt is higher than the corresponding build number in your output file (or in the configuration file), obtain and install the current update; see §1.4 How to update Mif2Go. Then try the conversion again.

6. If you think you have all the latest DLLs, but a build number in the output file does not agree, there might be an old copy somewhere on your system, typically in \windows\system or \windows\system32. Find and delete the old copy, then replace it with an updated copy.

7. If you still encounter the problem, check whether later beta versions of any DLLs are available on the Mif2Go Web site:

http://mif2go.com

Navigate to Downloads > Registered Software > Beta Components. If the problem is due to a defect in Mif2Go, the defect might have been corrected. See §1.4.3 Try out Mif2Go beta executables.

All DLLs up to date, and the problem still exists? Next: Narrow down the problem.

| D.2.8 Restart FrameMaker, reboot system |  | D.2.10 Narrow down the problem |