Sounds like some bad coding in the .dll that didn't turn off the display aspect of FM properly. You might want to look at Datazone's DZbatcher utility that would allow you to open, save as mif and then re-open and re-save as binaries via the command line in a batch file.
I wonder if Framemaker Server runs any differently, and if so, is that deliberate.
Illustrator CS5, btw, on Win7-64, has a similar problem. Actions won't even run (they stall) unless AI is the top window. Makes the PC nearly useless during batch ops.
I'm testing dzbatcher now. Interesting stuff.
With its SaveAs command, dzbatcher reports that FM is returning a -43 error, can't save the file.
Where do I look for more info on that error code (maybe others) ? I'm trying to figure out if this is a permissions problem (SaveAs must require a file create from Windows) or something else.
I'd check permissions and also make certain that you're running the command file with elevated/admin permissions.
As an alternate, you also might want to look at the demo version of mif2go. It has a built-in mifwash utility and a command line trigger via runfm.exe to do batch operations. You only need the demo version for the mifwashing and batch operations. See: http://mif2go.com/
Thanks. Will look into that.
Looks like error 43 is about a malformed parameter. Sounds like a problem between dzbatcher and FM10 (in my case).
Might very well be an issue between the apps. DZbatcher was written quite a while ago and Datazone haven't updated it. Probably aspects of the new OWL interface starting with FM9 are the suspects.
Datazone issued a patch to me within 24 hours of the report. It's working with my FM10.
Run time is approximately the same as the script from Adobe, but I now have my mouse and keyboard back under my control.
Glad to hear that Datazone are still supporting DZbatcher and it helped you out in your situation.