Hello Everyone,

Hope you are well. Well, there has been a flurry of emails on this topic and I 
(as the product manager for FrameMaker) wanted to mention a couple of things 
here to set the record straight :)

*         Network file paths: FrameMaker 11 has been tested to work with 
network file paths. There is absolutely no change in behavior between FM11 and 
the older versions. So, you should not have any problems when your files are 
stored on the network location. However, in case you are experiencing any 
crashes when working with network files, we will be happy to take a look at 
your crash logs and help your troubleshoot your specific issue.

*         FrameMaker Lock file: There is lot of discussion and some confusion 
around the purpose of the lock file. Lock file is created by FM to tell the 
user that the file is open in another instance of FM. So, if we take the 
scenario of multiple users working on the same file set (which is stored on the 
network drive) and when a file is opened in FM, it creates a lock file. If 
another user tries to open the same file, FM will give the other user a warning 
that the file is open in another instance of FM. So, this is a feature, that 
prevents users from overwriting each other's content. Furthermore, If you don't 
want lock files, you can turn them off as well. Lastly, for more information, 
about the lock file and its behavior, please read the help page 

Hope this information is useful and clarifies things. Have a great weekend!

Kapil Verma
Sr. Product Manager - Adobe Technical Communication Products

From: framers-boun...@lists.frameusers.com 
[mailto:framers-boun...@lists.frameusers.com] On Behalf Of Syed Zaeem Hosain 
Sent: Friday, February 15, 2013 5:43 AM
To: Dov Isaacs; Alan T Litchfield; framers@lists.frameusers.com
Subject: RE: "FrameMaker has detected a problem and must quit" Really?!

Hi, Dov.

What you say below is indeed what I would expect, and what is also my 
experience, with the Adobe applications I use (FrameMaker, PhotoShop and 
Acrobat Pro)- pretty much any Windows application today!

Thanks for the clarification,


From: Dov Isaacs [mailto:isa...@adobe.com]
Sent: Thursday, February 14, 2013 1:24 PM
To: Syed Zaeem Hosain (syed.hos...@aeris.net<mailto:syed.hos...@aeris.net>); 
Alan T Litchfield; 
Subject: RE: "FrameMaker has detected a problem and must quit" Really?!
Importance: High

With regards to network folders and drives, Adobe software in general is 
essentially unaware of the media and location of the file. The provided file 
path, whether provided explicitly by the user with a file open dialog or 
implicitly as a link in a document is used "as is" for operating system file 
access calls. That having been said, when one accesses files on remote and/or 
slow links or even with semi-reliable media (such as old and scratched CD-Rs 
and DVD-Rs), read errors and/or timeouts can and do occur that are much less 
likely than when accessing a file on a "local" drive. The Adobe applications 
typically don't attempt any special recovery operations when such read errors 
and/or timeouts occur. That is likely the source of problems reported.

            - Dov


Dov Isaacs
Principal Scientist
Adobe Systems Incorporated

+1 408.536.2896 (tel)
+1 408.242.5161 (cell)

345 Park Avenue
San Jose, CA  95110-2704 USA

Feel free to print this e-mail if your needs dictate hard copy.
There is no need to feel guilty about printing!
Paper is renewable and recyclable.


 [mailto:framers-boun...@lists.frameusers.com] On Behalf Of Syed Zaeem Hosain 
Sent: Wednesday, February 13, 2013 12:32 PM
To: Alan T Litchfield; 
Subject: RE: "FrameMaker has detected a problem and must quit" Really?!

I think that there may be some confusion about local vs. network 
folders/drives. Perhaps I read too much into Ken's responses from the Adobe 

In my case, all application executables are on my drive C and the data files 
are on drive E on the _same_ system. I.e., drive E is _not_ a network-mounted 
drive ... it is physically installed on my laptop.

For this "all local drives" arrangement, there should _never_ be any issue for 
any modern Windows application.

However, if the data files are on a network server, even if that folder/drive 
is "mounted" as a "local" drive letter in Windows, then I can see where 
incorrect permissions on that remote location can cause confusion and access 
issues. You _have_ to have write permission on that remote drive/folder for 

FWIW, I have used FrameMaker on a network without problems. I regularly back up 
my files onto a network server (into a folder where I have read/write access). 
Indeed, I just checked ... I don't have any difficulty opening those remote 
files, editing/saving, etc.

The point being that things on networks just have to be set up correctly, so an 
Adobe tech may want to _not_ recommend this for everybody. Regardless, I would 
not consider that as official Adobe policy.


<<inline: image001.png>>


You are currently subscribed to framers as arch...@mail-archive.com.

Send list messages to framers@lists.frameusers.com.

To unsubscribe send a blank email to
or visit 

Send administrative questions to listad...@frameusers.com. Visit
http://www.frameusers.com/ for more resources and info.

Reply via email to