Thanks, Heiko, but I don't understand how the OS or network gets fingered when ALL other applications that I use work normally. Even Adobe applications.
If Frame is too impatient, that's a BUG, not a 'problem' with the ever-so-slow network. I was hoping to learn about some kind of INI file setting (make it more patient, perhaps?) or known conflicts with other applications, which can bork up the automatic application launching. If the gods are good, I won't be using FM any more in a quarter or two, so I'll just bull along with the broken beast until then. I don't have the bandwidth to rebuild my work machine to try to blindly ferret out some conflict or screwed up FM DLL or whatever.... Thanks anyway; David -------- Original Message -------- From: Heiko Haida <[email protected]> Date: Tue, February 26, 2013 2:06 pm Hello David, lately I have a similar problem: double-clicking takes verrrry long to start the application and to open the file, whereas the normal Open dialog from within the application works as usual. This is not always the case, but if, then it happens with any application, also MS Word, Excel and so on. Here it helped to uncheck the DDE option for those file-types (which is not possible for Frame-files), but today I saw that the option is checked again mysteriously. So my guess about this would be that its rather a problem with the OS or with the network, not necessarily with FrameMaker. FM seems to expect a quick answer from the OS and handles the delay as file error (my interpretation, only a guess). I am using Windows XP here, by the way. If someone has an explanation to this problem, I would also be very glad. Best regards Tino H. Haida, Berlin
