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...
Rob.T Posted April 11, 2011 Report Share Posted April 11, 2011 Hi Adam, would you mind giving the Immunet 3.0.1 beta 2 a try? This build fixes a lot of issues with lockfiles in 3rd party software and I'd be interested in finding out if it fixes your Adobe issue as well. Don't forget to remove your Adobe path exception from Immunet before installing: http://forum.immunet.com/index.php?/topic/902-immunet-301-beta-2-available/ Link to comment Share on other sites More sharing options...
ahogan Posted April 12, 2011 Author Report Share Posted April 12, 2011 Hey Rob, 3.0.1 beta 2 does indeed fix the problem. Thanks! Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.