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

<< Prev | Next >>

> D Technical support for Mif2Go > D.2 Things to check first > D.2.2 Check your Mif2Go installation

### D.2.2 Check your Mif2Go installation

Sometimes supporting files are not where they need to be. See if you are getting one of these error messages:

DCL NT console driver has stopped working

Error processing m2rbook...

Could not run DCL filter...

Arguments unacceptable

OmniHelp Loading...

DCL NT console driver has stopped working

Check whether:

• %OMSYSHOME% is defined as a System environment variable

• %OMSYSHOME%\common\bin is on your System (not User) execution PATH.

See §1.3.1 Set up a framework for Omni Systems applications.

Error processing m2rbook...

If you get an error message such as the following when you run Mif2Go from the FrameMaker File menu:

Error Processing m2rbook command

Generally this indicates one of the following problems:

• A corrupted Mif2Go project (.prj) file; see §C.1 Locating document and conversion files. You can try deleting your existing .prj 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.

• A missing document file, if you get the error while Mif2Go is checking links.

• 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 Mif2Go problem, and might also manifest as trouble saving files, or trouble with graphics.

Other, similar error messages include the following:

Error initializing m2rbook.

Error processing m2rbook notification.

Error processing m2rbook hypertext command.

Error processing m2rbook dialog event.

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 Mif2Go problem. If you can get the error message to display consistently, send a test case, prepared as described in §D.3 How to request help.

Could not run DCL filter...

If the FrameMaker Console reports an error such as the following:

Mif2go failed for file: G:\HTML\First.htm

type 1, code 2, at: Thu Jul 25 10:07:37 2012

Could not run DCL filter or other program.

File not found.

This is an installation problem: Mif2Go could not find one or more executable files. This error usually means that the PATH environment variable is not set to include %OMSYSHOME%\common\bin, where the DLLs Mif2Go is looking for reside. You must set the SYSTEM PATH, not the USER PATH; see §1.3.3 Install Mif2Go. Another possibility is that %OMSYSHOME% is not set as a SYSTEM (not USER) environment variable, or is not set to the path where you actually installed the executables.

Note: After you make environment settings, you must reboot Windows before they take effect.

Make sure your zip program did not put an extra directory name in the path when you unpacked the distribution archive. For example, if %OMSYSHOME% is defined as C:\omsys, make sure the executables are in C:\omsys\common\bin, and not in C:\omsys\m2g_full_54\common\bin.

If files are all present in the right places, look at them in Windows Explorer. Right-click each DLL, choose Properties, and look at the Security tab. Make sure that everyone has permission to execute, preferably “full control”. Windows “security” often disables whatever came from a downloaded .zip file by limiting permissions for any executables.

Arguments unacceptable

If the FrameMaker Console reports an error such as the following:

Mif2go failed for file: G:\HTML\Test.htm

code 1 at: Wed Aug 17 15:05:57 2012

Arguments unacceptable.

This usually means that one or more required DLL files are not installed where Windows can find it; see §1.3.1 Set up a framework for Omni Systems applications. Sometimes this error occurs when an administrator “cleans up” system directories and removes an essential file (such as msvcrt40.dll, the Microsoft C run-time library for Visual C++ 4.x). Make sure all DLLs are in the required places.

You can get an “Arguments unacceptable” error message if compilation fails when you are generating WinHelp or HTML Help, and you set CompileHelp=Yes (or you check Compile Help on the Export dialog); Mif2Go runs the compiler after converting your document. Try compiling directly from Help Workshop to see if that is where the problem lies.

OmniHelp Loading...

If you use Mif2Go to generate OmniHelp, then when you load _myproj.htm the browser displays only this message, and nothing else happens:

OmniHelp Loading...

This usually means the OmniHelp viewer files or control files are not in the same directory as the HTML files; see §10.2 Setting up OmniHelp viewer control files.

Everything where it belongs? Next: Check for missing Microsoft components.