### D.2.5 Check path names, file names, and drive location

If the name of any path or file involved in the conversion contains any characters other than letters and numbers (such as spaces, dashes, or underscores), rename the path or move the file to eliminate them; see §1.1.2 File, directory, and path names. FrameMaker does not handle spaces in file names very well; Mif2Go does not care.

If all file and path names are free of non-alphanumeric characters and your conversion is still not producing any output, check whether your %OMSYSHOME% 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.

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 Mif2Go 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.

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.

File names and paths valid, and the problem still exists? Next: Check for file corruption.

| D.2.4 Check the Mif2Go User’s Guide |  | D.2.6 Check for file corruption |