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.
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...
Generally this indicates either a corrupted Mif2Go project (.prj) file (see §C.1 ), 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.
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 .
This means that Mif2Go executable files were not installed in the correct folders. See §1.4.1 .
This usually means that one or more required DLL files are not installed in the Windows system folder; see Table 1-1 . 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.
This usually means the OmniHelp viewer files or control files are not in the same folder as the HTML files; see §9.2 .