<?xml version="1.0" encoding="UTF-8" ?>
<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
  "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd">
<book lang="en">
<!-- generated by DCL filter dwhtm, Ver 4.1 m210 h293 -->

<appendix>
<title>Technical support for <emphasis>Mif2Go</emphasis></title>
<para>Omni Systems can provide effective technical support for <emphasis>Mif2Go</emphasis>
when you provide complete, concise information. We always do our best
to help; when you do your part, we can do our part more quickly and effectively.
Topics include:</para>
<simplelist>
<member><xref
 linkend="z20Dx1175164"></xref></member>
<member><xref
 linkend="z20Dx1039529"></xref></member>
<member><xref
 linkend="z20Dx1035585"></xref>  </member>
</simplelist>
<simplesect>
<title xml:id="z20Dx1037428"><emphasis>Zip your files!</emphasis></title>
<para><emphasis>Do not send unzipped FrameMaker files to Omni Systems.
 Do not send files larger than 1 MB.</emphasis></para>
</simplesect>
<sect1>
<title xml:id="z20Dx1175164">Evaluation version is different</title>
<para>If you are using the evaluation version of <emphasis>Mif2Go</emphasis>,
and the problem you see is that some of the text in your output has been
replaced by nonsense, <emphasis>this is intentional</emphasis>:</para>
<simplelist>
<member><xref
 linkend="z20Dx1175186"></xref></member>
<member><xref
 linkend="z20Dx1175198"></xref></member>
<member><xref
 linkend="z20Dx1175204"></xref></member>
<member><xref
 linkend="z20Dx1175214"></xref></member>
</simplelist>
<simplesect>
<title xml:id="z20Dx1175186">Evaluation version alters text</title>
<para>The evaluation version of <emphasis>Mif2Go</emphasis> replaces
some of your text with excerpts from Lewis Carroll’s poem “Jabberwocky”.
This ensures that you can evaluate <emphasis>Mif2Go</emphasis> without
restrictions on the size or complexity of your project, yet you cannot
produce commercially usable output until you actually purchase a license.
For additional information about using the evaluation version, see <literal>readme.txt</literal>
in <literal>%OMSYSHOME%\m2g\zip</literal>.</para>
</simplesect>
<simplesect>
<title xml:id="z20Dx1175198">Get the latest release</title>
<para>If you encounter some other problem with the evaluation version,
first download the newest <literal>samp</literal><emphasis>XX</emphasis><literal>u</literal><emphasis>YY</emphasis><literal>.zip</literal>
file, and reinstall; then try the conversion again. To obtain the latest
release of the evaluation version, download file <literal>samp</literal><emphasis>XX</emphasis><literal>u</literal><emphasis>YY</emphasis><literal>.zip</literal>
from the following location:</para>
<simplelist>
<member><ulink
 url="http://mif2go.com"><phrase>http://mif2go.com</phrase></ulink></member>
</simplelist>
</simplesect>
<simplesect>
<title xml:id="z20Dx1175204">Get a license</title>
<para>To purchase a license for <emphasis>Mif2Go</emphasis>, see:</para>
<simplelist>
<member><ulink
 url="http://mif2go.com"><phrase>http://mif2go.com</phrase></ulink></member>
</simplelist>
</simplesect>
<simplesect>
<title xml:id="z20Dx1175214">Delete evaluation components if necessary</title>
<para>Once you have installed a licensed copy of <emphasis>Mif2Go</emphasis>,
you should no longer see any of your text replaced by excerpts from Jabberwocky.
However, if you are still seeing these excerpts, some components of the
evaluation version are still present on your system; and one of them,
<literal>drmif.dll</literal>, is located in a directory that is earlier
on your system <literal>PATH</literal> than the licensed version. The
evaluation version of this file is larger than the production version.
Use Windows Explorer to search your hard disk for <literal>drmif.dll</literal>,
and delete any copies of this file that are 320K in size rather than
317K.</para>
</simplesect>
</sect1>
<sect1>
<title xml:id="z20Dx1039529">Things to check first</title>
<para>Before you holler for help, try the following:</para>
<simplelist>
<member><xref
 linkend="z20Dx1023350"></xref></member>
<member><xref
 linkend="z20Dx1064252"></xref></member>
<member><xref
 linkend="z20Dx1175396"></xref></member>
<member><xref
 linkend="z20Dx1100709"></xref></member>
<member><xref
 linkend="z20Dx1021175"></xref></member>
<member><xref
 linkend="z20Dx1175488"></xref></member>
<member><xref
 linkend="z20Dx1175532"></xref></member>
<member><xref
 linkend="z20Dx1175573"></xref></member>
<member><xref
 linkend="z20Dx1019799"></xref></member>
<member><xref
 linkend="z20Dx1175722"></xref></member>
</simplelist>
<sect2>
<title xml:id="z20Dx1023350">Examine your conversion log file</title>
<para>By default, <emphasis>Mif2Go</emphasis> writes conversion errors
and warnings to a log file in your project directory. If the information
in the log file does not reveal the cause of the problem, try changing
the log options to capture more information. See <xref
 linkend="zzzc1666358"></xref>.</para>
<para><emphasis>No log errors or warnings?</emphasis> Next: <xref
 linkend="z20Dx1064252"></xref></para>
</sect2>
<sect2>
<title xml:id="z20Dx1064252">Check your <emphasis>Mif2Go</emphasis>
installation</title>
<para>Sometimes supporting files are not where they need to be. See if
you are getting one of these error messages:</para>
<simplelist>
<member><xref
 linkend="z20Dx1175284"></xref></member>
<member><xref
 linkend="z20Dx1175299"></xref></member>
<member><xref
 linkend="z20Dx1175336"></xref></member>
<member><xref
 linkend="z20Dx1175367"></xref></member>
<member><xref
 linkend="z20Dx1175382"></xref></member>
</simplelist>
<simplesect>
<title xml:id="z20Dx1175284">DCL NT console driver has stopped
working</title>
<para>Check whether: </para>
<itemizedlist>
<listitem>
<para><literal>%OMSYSHOME%</literal> is defined as a System environment variable</para>
</listitem>
<listitem>
<para><literal>%OMSYSHOME%\common\bin</literal> is on your System (not User)
execution PATH.</para>
</listitem>
</itemizedlist>
<para>See <xref
 linkend="z101x999156"></xref>.</para>
</simplesect>
<simplesect>
<title xml:id="z20Dx1175299">Error processing m2rbook...</title>
<para>If you get an error message such as the following when you run
<emphasis>Mif2Go</emphasis> from the FrameMaker File menu:</para>
<programlisting>
Error Processing m2rbook command
</programlisting>
<para>Generally this indicates one of the following problems:</para>
<itemizedlist>
<listitem>
<para>A corrupted <emphasis>Mif2Go</emphasis> project (<literal>.prj</literal>)
file; see <xref
 linkend="z20Cx1238350"></xref>. You can try deleting your existing <literal>.prj</literal>
file, and then restarting FrameMaker. However, if your FrameMaker book
file is on a network server, you might need to work with a local copy.
Update it from the network copy when you start, and copy back changes
when you are finished, assuming others also need to work on the same
book.</para>
</listitem>
<listitem>
<para>A missing document file, if you get the error while <emphasis>Mif2Go</emphasis>
is checking links.</para>
</listitem>
<listitem>
<para>A problem with the file system where your FrameMaker book is located;
this happens mostly with network server file systems; it seems to be
an intermittent problem of FrameMaker not getting write access to the
directory that contains the book file. This is more a FrameMaker problem
than a <emphasis>Mif2Go</emphasis> problem, and might also manifest as
trouble saving files, or trouble with graphics.</para>
</listitem>
</itemizedlist>
<para>Other, similar error messages include the following:</para>
<programlisting>
Error initializing m2rbook.
</programlisting>
<programlisting>
Error processing m2rbook notification.
</programlisting>
<programlisting>
Error processing m2rbook hypertext command.
</programlisting>
<programlisting>
Error processing m2rbook dialog event.
</programlisting>
<para>Each message is issued under a different condition, usually as a result
of an internal problem in FrameMaker, but sometimes as a result of a
<emphasis>Mif2Go</emphasis> problem. If you can get the error message
to display consistently, send a test case, prepared as described in <xref
 linkend="z20Dx1035585"></xref>.</para>
</simplesect>
<simplesect>
<title xml:id="z20Dx1175336">Could not run DCL filter...</title>
<para>If the FrameMaker Console reports an error such as the following:</para>
<programlisting>
Mif2go failed for file: G:\HTML\First.htm
</programlisting>
<programlisting>
type 1, code 2, at: Thu Jul 25 10:07:37 2012
</programlisting>
<programlisting>
Could not run DCL filter or other program.
</programlisting>
<programlisting>
File not found.
</programlisting>
<para>This is an installation problem: <emphasis>Mif2Go</emphasis> could not
find one or more executable files. This error usually means that the
<literal>PATH</literal> environment variable is not set to include <literal>%OMSYSHOME%\common\bin</literal>,
where the DLLs <emphasis>Mif2Go</emphasis> is looking for reside. You
must set the <literal>SYSTEM PATH</literal>, not the <literal>USER PATH</literal>;
see <xref
 linkend="installm2g"></xref>. Another
possibility is that <literal>%OMSYSHOME%</literal> is not set as a <literal>SYSTEM</literal>
(not <literal>USER</literal>) environment variable, or is not set to
the path where you actually installed the executables.</para>
<note>
<para>After you make environment settings, you must reboot Windows before
they take effect.</para>
</note>
<para>Make sure your zip program did not put an extra directory name in the
path when you unpacked the distribution archive. For example, if <literal>%OMSYSHOME%</literal>
is defined as <literal>C:\omsys</literal>, make sure the executables
are in <literal>C:\omsys\common\bin</literal>, and not in <literal>C:\omsys\m2g_full_54\common\bin</literal>.</para>
<para>If files are all present in the right places, look at them in Windows
Explorer. Right-click each DLL, choose <guilabel>Properties</guilabel>,
and look at the <guilabel>Security</guilabel> tab. Make sure that everyone
has permission to execute, preferably “full control”. Windows “security”
often disables whatever came from a downloaded <literal>.zip</literal>
file by limiting permissions for any executables.</para>
</simplesect>
<simplesect>
<title xml:id="z20Dx1175367">Arguments unacceptable</title>
<para>If the FrameMaker Console reports an error such as the following:</para>
<programlisting>
Mif2go failed for file: G:\HTML\Test.htm
</programlisting>
<programlisting>
code 1 at: Wed Aug 17 15:05:57 2012
</programlisting>
<programlisting>
Arguments unacceptable.
</programlisting>
<para>This usually means that one or more required DLL files are not installed
where Windows can find it; see <xref
 linkend="z101x999156"></xref>. Sometimes this error occurs when an administrator
“cleans up” system directories and removes an essential file (such
as <literal>msvcrt40.dll</literal>, the Microsoft C run-time library
for Visual C++ 4.x). Make sure all DLLs are in the required places.</para>
<para>You can get an “Arguments unacceptable” error message if compilation
fails when you are generating WinHelp or HTML Help, and you set <literal>CompileHelp=Yes</literal>
(or you check <guilabel>Compile Help</guilabel> on the <emphasis>Export</emphasis>
dialog); <emphasis>Mif2Go</emphasis> runs the compiler after converting
your document. Try compiling directly from Help Workshop to see if that
is where the problem lies.</para>
</simplesect>
<simplesect>
<title xml:id="z20Dx1175382">OmniHelp Loading...</title>
<para>If you use <emphasis>Mif2Go</emphasis> to generate OmniHelp, then
when you load <literal>_myproj</literal><literal>.htm</literal> the browser
displays only this message, and nothing else happens:</para>
<simplelist>
<member><emphasis>OmniHelp Loading...</emphasis></member>
</simplelist>
<para>This usually means the OmniHelp viewer files or control files are not
in the same directory as the HTML files; see <xref
 linkend="z109x1058444"></xref>.</para>
<para><emphasis>Everything where it belongs?</emphasis> Next: <xref
 linkend="z20Dx1175396"></xref>.</para>
</simplesect>
</sect2>
<sect2>
<title xml:id="z20Dx1175396">Check for missing Microsoft components</title>
<para>If FrameMaker crashes when you browse for a <guilabel>Path</guilabel>
in the <emphasis>Choose Project </emphasis>dialog, check to make sure
you have a copy of library file <literal>msvcp60.dll</literal> in your
Windows system directory. If this file is not present, or is dated before
29 August 2000, download a copy from:</para>
<simplelist>
<member><ulink
 url="http://dl.dropbox.com/u/1868997/msvcp60.dll"><phrase>http://dl.dropbox.com/u/1868997/msvcp60.dll</phrase></ulink></member>
</simplelist>
<para>Place this file in your Windows system directory (<literal>\windows\system32</literal>
or, for 64-bit systems, <literal>\windows\SysWOW64</literal>) before
you start FrameMaker again.</para>
<para><emphasis>Microsoft components present?</emphasis> Next: <xref
 linkend="z20Dx1100709"></xref>.</para>
</sect2>
<sect2>
<title xml:id="z20Dx1100709">Check the <emphasis>Mif2Go</emphasis>
User’s Guide</title>
<para>Quickest way: use the <guilabel>Search</guilabel> feature of the
HTML Help version, which is installed with <emphasis>Mif2Go</emphasis>.
Search for words likely to relate to the problem; you might be able to
solve it yourself. </para>
<para><emphasis>No luck?</emphasis> Next: <xref
 linkend="z20Dx1021175"></xref>.</para>
</sect2>
<sect2>
<title xml:id="z20Dx1021175">Check path names, file names, and
drive location</title>
<para>If the name of any path or file involved in the conversion contains
<emphasis>any</emphasis> characters other than letters and numbers (such
as spaces, dashes, or underscores), rename the path or move the file
to eliminate them; see <xref
 linkend="z101x998726"></xref>.
FrameMaker does not handle spaces in file names very well; <emphasis>Mif2Go</emphasis>
does not care.</para>
<para>If all file and path names are free of non-alphanumeric characters
and your conversion is still not producing any output, check whether
your <literal>%OMSYSHOME%</literal> directory or any of your FrameMaker
files are on a network drive. FrameMaker is noted for not running properly
when files are on a network drive. </para>
<para>Another issue is “latency”, where a large and unpredictable
delay occurs between a program's file request and the server's response.
So you can get a “race” condition, where one instance of <emphasis>Mif2Go</emphasis>
closes a file, and the next instance opens the same file. If the close
is not completed, which involves numerous internal updates on the server,
the open may be denied. The result will be broken links. You may get
other results for other such race conditions.</para>
<para>If you are using a network drive, move your files to a local drive
and try running the same conversion there before asking for support.
</para>
<para><emphasis>File names and paths valid, and the problem still exists?</emphasis>
Next: <xref
 linkend="z20Dx1175488"></xref>.</para>
</sect2>
<sect2>
<title xml:id="z20Dx1175488">Check for file corruption</title>
<para>A slightly corrupted FrameMaker file might cause hard-to-trace
problems with <emphasis>Mif2Go</emphasis>. To rule out this possibility,
try cleaning out any corruption by saving the offending file as MIF and
replacing the binary version with the MIF version. <emphasis>Mif2Go</emphasis>
can do this for you (even in the evaluation version), and report the
results in the FrameMaker console window.</para>
<simplesect>
<title xml:id="z20Dx1175496">Clean a single file</title>
<para>To clean a FrameMaker binary file: with the file open and active,
on the FrameMaker <guilabel>File</guilabel> menu choose <guilabel>Wash
Via MIF</guilabel>. <emphasis>Mif2Go</emphasis> does the following:</para>
<orderedlist>
<listitem xml:id="z20Dx1175505">
<para>Saves the file as MIF with extension <literal>.tmb</literal> (for Temporary
MIF Backup), to avoid conflict with any existing MIF file of the same
name.</para>
</listitem>
<listitem xml:id="z20Dx1175506">
<para>Closes the file without saving.</para>
</listitem>
<listitem xml:id="z20Dx1175508">
<para>Opens the <literal>.tmb</literal> MIF file.</para>
</listitem>
<listitem xml:id="z20Dx1175509">
<para>Saves the <literal>.tmb</literal> MIF file as <literal>.fm</literal>,
overwriting the original file.</para>
</listitem>
<listitem xml:id="z20Dx1175510">
<para>Deletes the <literal>.tmb</literal> MIF file.</para>
</listitem>
</orderedlist>
<note>
<para>FrameMaker version 11 seems to get as far as <xref
 linkend="z20Dx1175508"></xref> and then stop;
and fails to process chapter files when run on a book.</para>
</note>
</simplesect>
<simplesect>
<title xml:id="z20Dx1175515">Clean all files in a book</title>
<para>To clean all files in a FrameMaker book: with the book file active,
hold down the Shift key, and on the FrameMaker <guilabel>File</guilabel>
menu choose <guilabel>Wash All Files in Book Via MIF</guilabel>. <emphasis>Mif2Go</emphasis>
processes each file in the book as described for <guilabel>Wash Via MIF</guilabel>,
afterward closing any file that was not open in the first place.</para>
</simplesect>
<simplesect>
<title xml:id="z20Dx1175520">Back-up copies are saved first</title>
<para>If you have set up FrameMaker to save back-up files, when you “wash”
files via MIF, <emphasis>Mif2Go</emphasis> saves the previous <literal>.fm</literal>
or <literal>.book</literal> file as <literal>filename</literal><literal>.backup.fm</literal>
or <literal>filename</literal><literal>.backup.book</literal>. </para>
<para><emphasis>File(s) decontaminated, and the problem still exists?</emphasis>
Next: <xref
 linkend="z20Dx1175532"></xref>.</para>
</simplesect>
</sect2>
<sect2>
<title xml:id="z20Dx1175532">Check for broken links (HTML or XML
output)</title>
<para>When you produce HTML or XML output from a FrameMaker book with
<literal>CheckLinks=Yes</literal> (see <xref
 linkend="zzzc2704858"></xref>), you might get an error message about
broken links. If <emphasis>Mif2Go</emphasis> is unable to resolve any
interfile links in your document, you will see a FrameMaker Book Error
Log at the end of processing, and the FrameMaker console report will
list the number of broken links.</para>
<simplesect>
<title xml:id="z20Dx1175540">Check ObjectIDs setting</title>
<para>Assuming you were able to successfully update the book before starting
<emphasis>Mif2Go</emphasis>, one possible problem might be the following
setting:</para>
<programlisting>
[HTMLOptions]
</programlisting>
<programlisting>
ObjectIDs = Referenced
</programlisting>
<para>If this setting is included in your project configuration file or in a
referenced configuration template, change or override the setting as
follows:</para>
<programlisting>
[HTMLOptions]
</programlisting>
<programlisting>
ObjectIDs = All
</programlisting>
<para>See <xref
 linkend="objectidlinks"></xref>. If you are converting generated files,
see also <xref
 linkend="z112x2369814"></xref>.</para>
</simplesect>
<simplesect>
<title xml:id="z20Dx1175557">Convert again, retaining .ref files</title>
<para>In a few situations you might have to run a conversion twice (<emphasis>without</emphasis>
deleting <literal>.ref</literal> files in between runs) before all links
are resolved. The first pass creates or updates the necessary <literal>.ref</literal>
files, and the second pass accesses the link information in those files.
See <xref
 linkend="z20Cx1240359"></xref>.</para>
</simplesect>
<simplesect>
<title xml:id="z20Dx1175562">Check for relative vs. absolute paths</title>
<para>If links work locally but not when you move all the output files
to another location, check whether your project includes any <literal>[XrefFiles]</literal>
settings that specify absolute paths. These settings must specify relative
paths; otherwise the links work only on the system where you ran the
conversion. See <xref
 linkend="z118x1236328"></xref>.</para>
<para><emphasis>No broken links, and the problem still exists?</emphasis>
Next: <xref
 linkend="z20Dx1175573"></xref>.</para>
</simplesect>
</sect2>
<sect2>
<title xml:id="z20Dx1175573">Restart FrameMaker, reboot system</title>
<para>Do you close and then reopen FrameMaker between <emphasis>Mif2Go</emphasis>
runs? This should be standard operating procedure; see <xref
 linkend="z102x999602"></xref>.</para>
<para>If you are using Windows 9<emphasis>x</emphasis> or Windows ME,
also try rebooting the system.</para>
<para><emphasis>The problem persists?</emphasis> Next: <xref
 linkend="z20Dx1019799"></xref>.</para>
</sect2>
<sect2>
<title xml:id="z20Dx1019799">Check your version of <emphasis>Mif2Go</emphasis></title>
<para>If you are using the evaluation version of <emphasis>Mif2Go</emphasis>,
see <xref
 linkend="z20Dx1175164"></xref>.
</para>
<para>If you are using a licensed version of <emphasis>Mif2Go</emphasis>,
do the following:</para>
<orderedlist>
<listitem xml:id="z20Dx1020245">
<para>In a text editor, open an output file (<literal>.htm</literal> or <literal>.rtf</literal>
or <literal>.dita</literal> or <literal>.ent</literal>) that you created
with <emphasis>Mif2Go</emphasis>, and find a line near the top of the
file that shows the <emphasis>Mif2Go</emphasis> version and build numbers.
The line you want looks like this:</para>
<informaltable xml:id="z20Dx1020311">
<tgroup cols="2">
<colspec colnum="1" colname="col1" colwidth="63pt" />
<colspec colnum="2" colname="col2" colwidth="315pt" />
<tbody>
<row>
<entry colname="col1"><para><emphasis>HTML, DITA, or DocBook:</emphasis></para></entry>
<entry colname="col2"><programlisting>
&lt;!-- generated by DCL filter dwhtm, Ver 4.0 <emphasis>m199</emphasis><emphasis> </emphasis><emphasis>h280</emphasis> --&gt;
</programlisting>
</entry>
</row>
<row>
<entry colname="col1"><para><emphasis>RTF:</emphasis></para></entry>
<entry colname="col2"><programlisting>
{\info {\doccomm DCL filter dwrtf, Ver 4.0 <emphasis>m199</emphasis><emphasis> </emphasis><emphasis>r285</emphasis>}}
</programlisting>
</entry>
</row>
</tbody>
</tgroup>
</informaltable>

<para><xref
 linkend="z20Dx1020862"></xref> lists the build
numbers underlined in these examples. </para>
</listitem>
<listitem xml:id="z20Dx1175612">
<para>If you are running <emphasis>Mif2Go</emphasis> from inside FrameMaker,
check the build number of the <emphasis>Mif2Go</emphasis> plug-in, <literal>m2rbook.dll</literal>.
Look for keyword <literal>PluginVersion</literal> in the <literal>[Setup]</literal>
section of the project configuration file you were using when the problem
occurred. <emphasis>Mif2Go</emphasis> updates the value of <literal>PluginVersion</literal>
each time you run a conversion. For example:</para>
<programlisting>
[Setup]
</programlisting>
<programlisting>
PluginVersion=<emphasis>b112
</emphasis></programlisting>
<para><xref
 linkend="z20Dx1020862"></xref> lists the build
number shown in bold in this example.</para>
<para>To make sure you are using the most current build, check <literal>PluginVersion</literal>
value <literal>b</literal><emphasis>NNN</emphasis> against the version
of <literal>m2rbook</literal><emphasis>NNN</emphasis><literal>.zip</literal>
on the Omni Systems Web site:</para>
<simplelist>
<member><ulink
 url="http://mif2go.com"><phrase>http://mif2go.com</phrase></ulink></member>
</simplelist>
</listitem>
<listitem xml:id="z20Dx1018700">
<para>Go to the <emphasis>Mif2Go</emphasis> Web site:</para>
<simplelist>
<member><ulink
 url="http://mif2go.com"><phrase>http://mif2go.com</phrase></ulink></member>
</simplelist>
<para>Navigate to <guilabel>Downloads &gt; Registered Software &gt; Components</guilabel>,
and check the build numbers on the archived DLL files. For example: </para>
<informaltable xml:id="z20Dx1108290">
<tgroup cols="4">
<colspec colnum="1" colname="col1" colwidth="94pt" />
<colspec colnum="2" colname="col2" colwidth="40pt" />
<colspec colnum="3" colname="col3" colwidth="108pt" />
<colspec colnum="4" colname="col4" colwidth="67pt" />
<thead>
<row>
<entry colname="col1"><para>File</para></entry>
<entry colname="col2"><para>Size</para></entry>
<entry colname="col3"><para>Description</para></entry>
<entry colname="col4"><para>Last updated</para></entry>
</row>
</thead>
<tbody>
<row>
<entry colname="col1"><programlisting>
m2rbook<emphasis>112</emphasis>.zip
</programlisting>
</entry>
<entry colname="col2"><para>196k</para></entry>
<entry colname="col3"><para>Plugin main module</para></entry>
<entry colname="col4"><para>01-May-2012</para></entry>
</row>
<row>
<entry colname="col1"><programlisting>
drmif<emphasis>208</emphasis>.zip
</programlisting>
</entry>
<entry colname="col2"><para>177k</para></entry>
<entry colname="col3"><para>MIF input module</para></entry>
<entry colname="col4"><para>01-May-2012</para></entry>
</row>
<row>
<entry colname="col1"><programlisting>
dwrtf<emphasis>295</emphasis>.zip
</programlisting>
</entry>
<entry colname="col2"><para>251k</para></entry>
<entry colname="col3"><para>RTF output module</para></entry>
<entry colname="col4"><para>01-Jun-2010</para></entry>
</row>
<row>
<entry colname="col1"><programlisting>
dwhtm<emphasis>289</emphasis>.zip
</programlisting>
</entry>
<entry colname="col2"><para>421k</para></entry>
<entry colname="col3"><para>HTML/XML output module</para></entry>
<entry colname="col4"><para>01-Jun-2010</para></entry>
</row>
</tbody>
</tgroup>
</informaltable>

</listitem>
<listitem xml:id="z20Dx1097196">
<para>Compare the number on each DLL archive file with the build numbers you
found in your output, as shown in <xref
 linkend="z20Dx1020862"></xref>.</para>
<para> </para>
<table xml:id="z20Dx1020862">
<caption>
<para>Examples of build numbers for <emphasis>Mif2Go</emphasis> DLL files</para>
</caption>
<tgroup cols="5">
<colspec colnum="1" colname="col1" colwidth="72pt" />
<colspec colnum="2" colname="col2" colwidth="81pt" />
<colspec colnum="3" colname="col3" colwidth="58pt" />
<colspec colnum="4" colname="col4" colwidth="58pt" />
<colspec colnum="5" colname="col5" colwidth="59pt" />
<thead>
<row>
<entry colname="col1" morerows="1"><para>Output type</para></entry>
<entry colname="col2" morerows="1"><para>DLL file</para></entry>
<entry namest="col3" nameend="col4"><para>Build number:</para></entry>
<entry colname="col5" morerows="1"><para>Current?</para></entry>
</row>
<row>
<entry colname="col3"><para>Latest</para></entry>
<entry colname="col4"><para>Used</para></entry>
</row>
</thead>
<tbody>
<row>
<entry colname="col1" morerows="1"><para>All</para></entry>
<entry colname="col2"><programlisting>
m2rbook.dll
</programlisting>
</entry>
<entry colname="col3"><programlisting>
112
</programlisting>
</entry>
<entry colname="col4"><programlisting>
b112
</programlisting>
</entry>
<entry colname="col5"><para>Yes</para></entry>
</row>
<row>
<entry colname="col2"><programlisting>
drmif.dll
</programlisting>
</entry>
<entry colname="col3"><programlisting>
208
</programlisting>
</entry>
<entry colname="col4"><programlisting>
m208
</programlisting>
</entry>
<entry colname="col5"><para>Yes</para></entry>
</row>
<row>
<entry colname="col1"><para>HTML</para></entry>
<entry colname="col2"><programlisting>
dwhtm.dll
</programlisting>
</entry>
<entry colname="col3"><programlisting>
289
</programlisting>
</entry>
<entry colname="col4"><programlisting>
h284
</programlisting>
</entry>
<entry colname="col5"><para><emphasis>No</emphasis></para></entry>
</row>
<row>
<entry colname="col1"><para>RTF</para></entry>
<entry colname="col2"><programlisting>
dwrtf.dll
</programlisting>
</entry>
<entry colname="col3"><programlisting>
295
</programlisting>
</entry>
<entry colname="col4"><programlisting>
r295
</programlisting>
</entry>
<entry colname="col5"><para>Yes</para></entry>
</row>
</tbody>
</tgroup>
</table>

</listitem>
<listitem xml:id="z20Dx1068032">
<para>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 <xref
 linkend="z101x1000067"></xref>.
Then try the conversion again.</para>
</listitem>
<listitem xml:id="z20Dx1068042">
<para>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 <literal>\windows\system</literal> or <literal>\windows\system32</literal>.
Find and delete the old copy, then download an updated copy and unzip
it in <literal>%OMSYSHOME%\common\bin</literal>. </para>
</listitem>
<listitem xml:id="z20Dx1097632">
<para>If you still encounter the problem, check whether later beta versions
of any DLLs are available on the <emphasis>Mif2Go</emphasis> Web site:</para>
<simplelist>
<member><ulink
 url="http://mif2go.com"><phrase>http://mif2go.com</phrase></ulink></member>
</simplelist>
<para>Navigate to <guilabel>Downloads &gt; Registered Software &gt; Beta Components</guilabel>,
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: </para>
<informaltable xml:id="z20Dx1110180">
<tgroup cols="4">
<colspec colnum="1" colname="col1" colwidth="63pt" />
<colspec colnum="2" colname="col2" colwidth="40pt" />
<colspec colnum="3" colname="col3" colwidth="184pt" />
<colspec colnum="4" colname="col4" colwidth="67pt" />
<thead>
<row>
<entry colname="col1"><para>File</para></entry>
<entry colname="col2"><para>Size</para></entry>
<entry colname="col3"><para>Description</para></entry>
<entry colname="col4"><para>Last updated</para></entry>
</row>
</thead>
<tbody>
<row>
<entry colname="col1"><programlisting>
m2rbook.dll
</programlisting>
</entry>
<entry colname="col2"><para>572k</para></entry>
<entry colname="col3"><para>Plugin main module, 4.0.112.0</para></entry>
<entry colname="col4"><para>01-May-2012</para></entry>
</row>
<row>
<entry colname="col1"><programlisting>
drmif.dll
</programlisting>
</entry>
<entry colname="col2"><para>412k</para></entry>
<entry colname="col3"><para>MIF input module, 4.0.208.0</para></entry>
<entry colname="col4"><para>01-May-2012</para></entry>
</row>
<row>
<entry colname="col1"><programlisting>
dwrtf.dll
</programlisting>
</entry>
<entry colname="col2"><para>588k</para></entry>
<entry colname="col3"><para>RTF output module, 4.0.<phrase>297</phrase>.2</para></entry>
<entry colname="col4"><para>02-Jun-2012</para></entry>
</row>
<row>
<entry colname="col1"><programlisting>
dwhtm.dll
</programlisting>
</entry>
<entry colname="col2"><para>1052k</para></entry>
<entry colname="col3"><para>HTML/XML output module, 4.0.<phrase>291</phrase>.4</para></entry>
<entry colname="col4"><para>04-Jun-2012</para></entry>
</row>
</tbody>
</tgroup>
</informaltable>

</listitem>
<listitem xml:id="z20Dx1110230">
<para>Compare the third part of the number in each description with the build
numbers you found in your output, as shown in <xref
 linkend="z20Dx1020862"></xref>. If the fourth
part is greater than zero, and the problem is due to a defect in <emphasis>Mif2Go</emphasis>,
the defect might have been corrected. See <xref
 linkend="z101x1000190"></xref>.</para>
</listitem>
</orderedlist>
<para><emphasis>All DLLs up to date, and the problem still exists?</emphasis>
Next: <xref
 linkend="z20Dx1175722"></xref>.</para>
</sect2>
<sect2>
<title xml:id="z20Dx1175722">Narrow down the problem</title>
<para>Make a copy of a FrameMaker file that produces the problem, then
split the copy in two parts, and see if the problem happens with only
one part. If so, keep splitting until you are down to a page or less;
you might find something questionable in the file that you can fix to
get it working. </para>
<para><emphasis>Still no luck?</emphasis> See <xref
 linkend="z20Dx1035585"></xref>.</para>
</sect2>
</sect1>
<sect1>
<title xml:id="z20Dx1035585">How to request help</title>
<simplesect>
<title xml:id="z20Dx1037721">Zip your files!</title>
<para><emphasis>Do not send unzipped FrameMaker files to Omni Systems.
 Do not send files larger than 1 MB.</emphasis></para>
<para>If you still encounter problems after following the steps in <xref
 linkend="z20Dx1039529"></xref>,
help us to help you, as follows:</para>
<simplelist>
<member><xref
 linkend="z20Dx1038662"></xref></member>
<member><xref
 linkend="z20Dx1037633"></xref></member>
<member><xref
 linkend="z20Dx1020061"></xref></member>
<member><xref
 linkend="z20Dx1018224"></xref></member>
<member><xref
 linkend="z20Dx1018250"></xref></member>
</simplelist>
</simplesect>
<sect2>
<title xml:id="z20Dx1038662">If the problem involves a crash</title>
<para>If you are getting a Windows error message such as the following:</para>
<simplelist>
<member><phrase>DCL NT console driver has encountered a problem and needs to
close.</phrase></member>
</simplelist>
<para>This means your <emphasis>Mif2Go</emphasis> conversion caused a crash.If
the crash happens when <emphasis>Mif2Go</emphasis> is converting a FrameMaker
index, see <xref
 linkend="zzzc2705850"></xref>;
you might need to add character formats to page numbers. Otherwise, try
the following debugging options:</para>
<programlisting>
[Options]
</programlisting>
<programlisting>
; NoNameDel = No (default),
</programlisting>
<programlisting>
;  or Yes (prevent deallocation of name memory)
</programlisting>
<programlisting>
NoNameDel=Yes
</programlisting>
<programlisting>
; NoMemDel = No (default) or Yes (prevent deallocation of all memory)
</programlisting>
<programlisting>
NoMemDel=Yes
</programlisting>
<para>First set <literal>NoNameDel=Yes</literal>. If the conversion still causes
a crash, try setting <literal>NoMemDel=Yes</literal>. Your conversion
might run to completion with one or the other of these options; in any
event, document the result, so Omni Systems programmers can investigate.</para>
<note>
<para>When you set either of these options to <literal>Yes</literal>, memory
deallocation is prevented only while <literal>dcl.exe</literal> is running;
at the end of that (usually brief) process, all memory used by <emphasis>Mif2Go</emphasis>
is always freed; no memory leaks occur.</para>
</note>
<para>Next: <xref
 linkend="z20Dx1037633"></xref>.</para>
</sect2>
<sect2>
<title xml:id="z20Dx1037633">Scope the problem</title>
<para>Use the Configuration Manager (see <xref
 linkend="z104x2160891"></xref>) to check the configurations in use. If any settings
in “local’ configuration files in <literal>%OMSYSHOME%\m2g\local</literal>
subdirectories might affect the test case, copy those settings into your
project configuration file, and see if that fixes the problem. Otherwise,
consider the following questions:</para>
<itemizedlist>
<listitem>
<para>Do you get the same result each time you try, or does the result vary?
</para>
</listitem>
<listitem>
<para>If you have machines with other operating-system versions available,
does the same thing happen on all of them?</para>
</listitem>
<listitem>
<para>Does it happen with all source files, or only some? If only some, do
the problem files have something in common that other files do not?</para>
</listitem>
</itemizedlist>
<para>Next: <xref
 linkend="z20Dx1020061"></xref>.</para>
</sect2>
<sect2>
<title xml:id="z20Dx1020061">Document the problem</title>
<para>Write an e-mail message that contains the following information:</para>
<itemizedlist>
<listitem>
<para>A brief description of the problem, including answers to questions in
<xref
 linkend="z20Dx1037633"></xref>.</para>
</listitem>
<listitem>
<para>Operating-system name and version; for example, Windows 7 X64.</para>
</listitem>
<listitem>
<para>Amount of memory on your machine; for example, 2 GB.</para>
</listitem>
<listitem>
<para>FrameMaker version (click <guilabel>Help &gt; About FrameMaker...</guilabel>);
for example, 5.5.6p145.</para>
</listitem>
<listitem>
<para>Browser name and version, if the problem occurs when you generate HTML;
for example, Firefox 3.5.</para>
</listitem>
</itemizedlist>
<para>If <emphasis>Mif2Go</emphasis> crashed, we also need to know just
what information was displayed, at the time of the crash, on the status
bar at the bottom of the book window or file window.</para>
<para>Next: <xref
 linkend="z20Dx1018224"></xref>.</para>
</sect2>
<sect2>
<title xml:id="z20Dx1018224">Package the problem</title>
<para>If you have placed settings in a file in <literal>%OMSYSHOME%\m2g\local\config\*</literal>,
copy those settings to your project configuration file before you do
the following.</para>
<para>Create a <literal>.zip</literal> file <emphasis>smaller than 1
MB</emphasis> that contains the following files:</para>
<informaltable xml:id="z20Dx1035896">
<tgroup cols="2">
<colspec colnum="1" colname="col1" colwidth="108pt" />
<colspec colnum="2" colname="col2" colwidth="270pt" />
<tbody>
<row>
<entry colname="col1"><para>FrameMaker file(s)</para></entry>
<entry colname="col2"><para>The smallest fragments that yield the problem;
see <xref
 linkend="z20Dx1175722"></xref> in <xref
 linkend="z20Dx1039529"></xref>.
<emphasis>No unzipped files.</emphasis></para></entry>
</row>
<row>
<entry colname="col1"><para>MIF file(s)</para></entry>
<entry colname="col2"><para>The <literal>.mif </literal>file(s) <emphasis>Mif2Go</emphasis>
creates from the above <literal>.fm</literal> file(s).</para></entry>
</row>
<row>
<entry colname="col1"><para>FrameMaker conversion template</para></entry>
<entry colname="col2"><para>If your project uses a conversion template,
and the problem is a display problem, include the conversion template.</para></entry>
</row>
<row>
<entry colname="col1"><para>Book file</para></entry>
<entry colname="col2"><para>If <emphasis>Mif2Go</emphasis> crashed while
you were converting a book.</para></entry>
</row>
<row>
<entry colname="col1"><para>Output file(s)</para></entry>
<entry colname="col2"><para>Whatever output (if any) shows the undesired
result.</para></entry>
</row>
<row>
<entry colname="col1"><para>Log file</para></entry>
<entry colname="col2"><para>Located by default in your project directory;
see <xref
 linkend="zzzc1666358"></xref>.</para></entry>
</row>
<row>
<entry colname="col1"><para>Configuration file(s)</para></entry>
<entry colname="col2"><para>Your project configuration file, plus any
chapter-specific configuration file used by the problem FrameMaker file.</para></entry>
</row>
<row>
<entry colname="col1"><para>Configuration templates</para></entry>
<entry colname="col2"><para>Include all configuration files and templates
in every chain that might affect the result, except the distribution
templates. However, if you have placed settings in a file in <literal>%OMSYSHOME%\m2g\local\config\*</literal>,
copy those settings to your project configuration file before you create
the package.</para></entry>
</row>
<row>
<entry colname="col1"><para>Macro libraries</para></entry>
<entry colname="col2"><para>If the problem file uses <emphasis>Mif2Go</emphasis>
macros located in library files.</para></entry>
</row>
<row>
<entry colname="col1"><para>CSS file(s)</para></entry>
<entry colname="col2"><para>If your project uses CSS (HTML output only),
and the problem is a display problem.</para></entry>
</row>
<row>
<entry colname="col1"><para><emphasis>Mif2Go</emphasis> project file</para></entry>
<entry colname="col2"><para><literal>MyDoc</literal><literal>.prj</literal>,
located in the input directory; see <xref
 linkend="z20Cx1238350"></xref>.</para></entry>
</row>
<row>
<entry colname="col1"><para><emphasis>Mif2Go</emphasis> FileID file</para></entry>
<entry colname="col2"><para><literal>mif2go.ini</literal>, located in
the input directory; see <xref
 linkend="z20Cx1238350"></xref>.</para></entry>
</row>
<row>
<entry colname="col1"><para>Help project file</para></entry>
<entry colname="col2"><para>If the problem occurs when you generate one
of the following:</para><itemizedlist>
<listitem>
<para>WinHelp: <literal>MyDoc</literal><literal>.hpj</literal>.</para></listitem>
<listitem>
<para>HTML Help: <literal>MyDoc</literal><literal>.hhp</literal>.</para></listitem>
<listitem>
<para>JavaHelp or Oracle Help for Java: <literal>MyDoc</literal><literal>.hs</literal>.</para></listitem>
</itemizedlist>
</entry>
</row>
<row>
<entry colname="col1"><para>Graphics files</para></entry>
<entry colname="col2"><para>Any external graphics referenced by the problem-file
fragment.</para></entry>
</row>
</tbody>
</tgroup>
</informaltable>

<simplesect>
<title xml:id="z20Dx1037387"><emphasis>Zip your files!</emphasis></title>
<para><emphasis>Do not send unzipped FrameMaker files; they are nearly
always corrupted in transit.</emphasis></para>
<para>We need to be able to unzip and run your test case at Omni Systems
with no further ado.</para>
<para>Finally: <xref
 linkend="z20Dx1018250"></xref>.</para>
</simplesect>
</sect2>
<sect2>
<title xml:id="z20Dx1018250">Send the package to Omni Systems</title>
<para>Attach the <literal>.zip</literal> file you created in <xref
 linkend="z20Dx1018224"></xref>
to the e-mail message you wrote in <xref
 linkend="z20Dx1020061"></xref>,
and send it to:</para>
<simplelist>
<member><ulink
 url="mailto:support@omsys.com"><phrase>support@omsys.com</phrase></ulink></member>
</simplelist>
<para>Generally you will receive a response within one business day; sometimes
within an hour. If you have not heard from Omni Systems after one business
day, send another e-mail message (<emphasis>without attachments</emphasis>)
to inquire.</para>
<simplesect>
<title xml:id="z20Dx1037762"><emphasis>Zip your files!</emphasis></title>
<para><emphasis>Do not send unzipped FrameMaker files to Omni Systems.
 Do not send files larger than 1 MB.</emphasis></para>

</simplesect>
</sect2>
</sect1>
</appendix>
</book>
