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:
'InstallMif2Go.bat' is not recognized...
'InstallMif2Go.bat' is not recognized...
If you get this error message the first time you try to install Mif2Go with a .bat file, the reason might be that your .bat file actually is named something like InstallMif2Go.bat.txt. This can happen when you save a file from Notepad (or another text editor), if Windows is set to hide common file extensions.
To restore the correct extension:
1. Open a Command Prompt window: Start > All Programs > Accessories > Command Prompt.
2. cd to your Mif2Go installation folder.
3. Type dir, then press Enter; all files in the folder are listed.
4. Look for InstallMif2Go.bat.
5. If the file is actually named InstallMif2Go.bat.txt, in the Command Prompt window type the following and press Enter:
ren InstallMif2Go.bat.txt InstallMif2Go.bat
Now you should be able to run InstallMif2Go.bat successfully.
Hiding file extensions on Windows creates a security problem. This is how viruses named (for example) joke.jpg.exe are able to infect a system; a person sees only the name joke.jpg in Windows Explorer, double-clicks the file, and wonders why Microsoft Paint does not start...
To make Windows reveal common file extensions:
1. In Windows Explorer, go to Tools > Folder Options....
2. On the View tab, under Files and Folders, uncheck Hide extensions for known file types.
If you get an error message such as the following when you try to set up or start Mif2Go from the FrameMaker File menu:
Error Processing m2rbook command
Generally this indicates either a corrupted Mif2Go project (.prj) file (see §C.1 Locating document and conversion files), or 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 folder 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.
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.
Other, similar error messages include the following:
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.
If the FrameMaker Console reports an error such as the following:
MIF2HTM failed for file: G:\HTML\First.htm
type 1, code 2, at: Thu Jul 25 10:07:37 2002
Could not run DCL filter or other program.
This means that Mif2Go executable files were not installed in the correct folders. See §1.4.1 Install Mif2Go.
If the FrameMaker Console reports an error such as the following:
MIF2HTM failed for file: G:\HTML\Test.htm
code 1 at: Wed Aug 17 15:05:57 2005
This usually means that one or more required DLL files are not installed in the Windows system folder; see Table 1-1 Where to place Mif2Go executable files. Sometimes this error occurs when an administrator "cleans up" system folders 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.
If you use Mif2Go to generate OmniHelp, then when you load _myproj.htm the browser displays only this message, and nothing else happens:
This usually means the OmniHelp viewer files or control files are not in the same folder as the HTML files; see §9.2 Setting up OmniHelp viewer control files.
Everything where it belongs? Next: Check the Mif2Go User's Guide.
> D Technical support for Mif2Go > D.2 Things to check first > D.2.2 Check your Mif2Go installation