Hi, I just assigned X: to one of my network folders, created a new file there and imported a graphics file. No problem. Everything as it should be (FrameMaker 11 on Windows 7).
When your graphics file is on the same network drive, the path should be relative. That means, X: is not mentioned in the path name. Did you check the MIF file whether your path contains any X? Did you create a local file and import a graphics file from X:? Vice versa? What happens? What happens, if you assign another drive letter to one of your folders on X: and create a FrameMaker file there? Import a graphics file from this folder? All sorts of things may happen. However, I would also tend to believe that this is not related to the drive letter X:. Best regards Winfried From: framers-bounces at lists.frameusers.com [mailto:framers-boun...@lists.frameusers.com] On Behalf Of Stephen O'Brien Sent: Friday, November 15, 2013 8:50 PM To: Frame Users (framers at lists.frameusers.com) Subject: FM9 files on network - logical network drive X: Hi, (Windows7, FM9) The server (ex. \\Server<file:///\\Server>) that houses our FM files is assigned a logical drive X:. I believe this has something to do with protecting against viruses. FM does not like this. For example, when an image is imported into a FM document using the X: path, the image blinks in the FM document, as if FM continually updates the definition of X: and the image path becomes momentarily unknown and then becomes known (and so the blinking where the image is displayed and then appears in gray and so on). Now I realize that some cross-references to other FM documents contain X: in the target document path. FM does not like that either. May crash because of this. Our IT guy says that the X: cannot be removed (same profile for all). My team of tech writers usually uses a shortcut (defined correctly from \\Server<file:///\\Server>) to open books/documents but someone always forgets. I now have scripts that check the path for x-refs and images imported by reference. Does anyone know if this problem exists in later versions of FM (10 or 11)? That would solve this problem once and for all. Many thanks, Stephen O'BRIEN Coordonnateur ? la documentation et r?dacteur technique senior | Documentation Coordinator and Senior Technical Writer InnovMetric Logiciels | Software sobrien at innovmetric.com<mailto:sobrien at innovmetric.com> T (1) 418.688.2061 F (1) 418.688.3001 [cid:image001.jpg at 01CEE43A.DCAE4E50]<http://www.innovmetric.com/> [cid:image002.jpg at 01CEE43A.DCAE4E50] <http://www.youtube.com/polyworks/> [cid:image003.jpg at 01CEE43A.DCAE4E50] <http://www.facebook.com/InnovMetric> [cid:image004.jpg at 01CEE43A.DCAE4E50] <http://www.twitter.com/PolyWorks> [cid:image005.jpg at 01CEE43A.DCAE4E50] <https://plus.google.com/u/0/100086255572014990082/posts> AVIS DE CONFIDENTIALIT?/CONFIDENTIALITY NOTICE: Ce message peut contenir des renseignements confidentiels appartenant exclusivement ? InnovMetric Logiciels inc. ou ? ses filiales. Si vous n'?tes pas le destinataire indiqu? dans ce message (ou responsable de livrer ce message ? la personne indiqu?e ou pr?vue) ou si vous pensez que ce message vous a ?t? adress? par erreur, vous ne pouvez pas utiliser ou reproduire ce message, ni le livrer ? quelqu'un d'autre. Dans ce cas, veuillez le retourner ? l'exp?diteur et le d?truire. Proprietary confidential information belonging to InnovMetric Software Inc. and its affiliates may be contained in this message. If you are not a recipient indicated or intended in this message (or responsible for delivering this message to such a person), or you think for any reason that this message may have been addressed to you by mistake, you may not use or copy this message, or deliver it to anyone else. In which case, notify the sender and destroy the e-mail. ________________________________ This e-mail contains privileged and confidential information intended for the use of the addressees named above. If you are not the intended recipient of this e-mail, you are hereby notified that you must not disseminate, copy or take any action in respect of any information contained in it. If you have received this e-mail in error, please notify the sender immediately by e-mail and immediately destroy this e-mail and its attachments. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.frameusers.com/pipermail/framers/attachments/20131118/c03f5372/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 2370 bytes Desc: image001.jpg URL: <http://lists.frameusers.com/pipermail/framers/attachments/20131118/c03f5372/attachment.jpg> -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 2304 bytes Desc: image002.jpg URL: <http://lists.frameusers.com/pipermail/framers/attachments/20131118/c03f5372/attachment-0001.jpg> -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.jpg Type: image/jpeg Size: 1892 bytes Desc: image003.jpg URL: <http://lists.frameusers.com/pipermail/framers/attachments/20131118/c03f5372/attachment-0002.jpg> -------------- next part -------------- A non-text attachment was scrubbed... Name: image004.jpg Type: image/jpeg Size: 2159 bytes Desc: image004.jpg URL: <http://lists.frameusers.com/pipermail/framers/attachments/20131118/c03f5372/attachment-0003.jpg> -------------- next part -------------- A non-text attachment was scrubbed... Name: image005.jpg Type: image/jpeg Size: 2322 bytes Desc: image005.jpg URL: <http://lists.frameusers.com/pipermail/framers/attachments/20131118/c03f5372/attachment-0004.jpg>
