Omni Systems, Inc. Mif2Go User's Guide, Version 55

<< Prev | Next >>

> D Technical support for Mif2Go > D.2 Things to check first > D.2.9 Check your version of Mif2Go

### 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 or .dita or .ent) that you created with Mif2Go, and find a line near the top of the file that shows the Mif2Go version and build numbers. The line you want looks like this:

HTML, DITA, or DocBook: | <!-- generated by DCL filter dwhtm, Ver 4.0 m199 h280 -->
RTF: | {\info {\doccomm DCL filter dwrtf, Ver 4.0 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=b112

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. Go to the Mif2Go Web site:

http://mif2go.com

Navigate to Downloads > Registered Software > Components, and check the build numbers on the archived DLL files. For example:

File | Size | Description | Last updated
m2rbook112.zip | 196k | Plugin main module | 01-May-2012
drmif208.zip | 177k | MIF input module | 01-May-2012
dwrtf295.zip | 251k | RTF output module | 01-Jun-2010
dwhtm289.zip | 421k | HTML/XML output module | 01-Jun-2010

4. Compare the number on each DLL archive file with the build numbers you found in your output, as shown in Table D-1.

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

Output type | DLL file | Build number: | Current?
Latest | Used
All | m2rbook.dll | 112 | b112 | Yes
drmif.dll | 208 | m208 | Yes
HTML | dwhtm.dll | 289 | h284 | No
RTF | dwrtf.dll | 295 | r295 | Yes

5. If the build number on a DLL archive 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 download an updated copy and unzip it in %OMSYSHOME%\common\bin.

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, and check the four-part numbers in the descriptions of the DLL files. The first two parts are the product version, third part the build number, and fourth is the beta version, zero for the released DLL, incremented for each beta build. For example:

File | Size | Description | Last updated
m2rbook.dll | 572k | Plugin main module, 4.0.112.0 | 01-May-2012
drmif.dll | 412k | MIF input module, 4.0.208.0 | 01-May-2012
dwrtf.dll | 588k | RTF output module, 4.0.297.2 | 02-Jun-2012
dwhtm.dll | 1052k | HTML/XML output module, 4.0.291.4 | 04-Jun-2012

8. Compare the third part of the number in each description with the build numbers you found in your output, as shown in Table D-1. If the fourth part is greater than zero, and 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.