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 [cid:image001.png at 01CE0AB6.8EBB5390] Dov Isaacs Principal Scientist Adobe Systems Incorporated +1 408.536.2896 (tel) +1 408.242.5161 (cell) isaacs at adobe.com<mailto:isaacs at adobe.com> 345 Park Avenue San Jose, CA 95110-2704 USA http://www.adobe.com<http://www.adobe.com/> 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. ISAACS-OFFICE.corp.adobe.com From: framers-bounces at lists.frameusers.com [mailto:framers-bounces at lists.frameusers.com] On Behalf Of Syed Zaeem Hosain (syed.hos...@aeris.net) Sent: Wednesday, February 13, 2013 12:32 PM To: Alan T Litchfield; framers at lists.frameusers.com 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 tech! 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 example. 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. Z -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.frameusers.com/pipermail/framers/attachments/20130214/02951c54/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 871 bytes Desc: image001.png URL: <http://lists.frameusers.com/pipermail/framers/attachments/20130214/02951c54/attachment.png>