ahogan Posted April 11, 2011 Report Share Posted April 11, 2011 Using: Immunet 3.0. I use Adobe's Framemaker in a Windows 7 SP1 VM. Framemaker has a system of creating a lock file when ever you have a file open. If you open a file for which a lock file exists, it warns you. Lock files also prevent a lot of automatic operations like generating a table of contents or updating references by preventing Framemaker from opening those files. When I run Immunet I get multiple errors from Framemaker, as if the files I'm using were open and locked. I turned off Immunet and tested again, and didn't have the problem. I was able to recreate this, and then fixed it by adding an exception for Documents\*\*.fm as well as Documents\*\*.book. Link to comment Share on other sites More sharing options...
This topic is now archived and is closed to further replies.