<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-CA" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">I’ve been running Win7 64bit with FM11 for some time now with my FM files on our network drive with no problems or crashes at all. I think the trick is to have
a large amount of RAM installed (at least 8 GB) and lots of spare space on your hard drive for temp files. You may find that you need to implement some sort of source control to check out/in files from your server to your local drive.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> framers-bounces@lists.frameusers.com [mailto:framers-bounces@lists.frameusers.com]
<b>On Behalf Of </b>Ken Poshedly<br>
<b>Sent:</b> August-08-13 11:54 AM<br>
<b>To:</b> FrameMaker Users List<br>
<b>Subject:</b> Windows 7 + FrameMaker 11 = BOOM!<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div id="yiv1545870390">
<div>
<div>
<div id="yiv1545870390yui_3_7_2_63_1375964420720_39">
<p class="MsoNormal" style="background:white"><span style="font-size:18.0pt;color:black">Due to the addition of 2 new contract writers and the replacement of the hard drive in an existing terminal in my department, we're now stuck with Windows 7 and FrameMaker
11 on those three platforms for the past month or so.<br>
<br>
And it's been nothing but problems ever since, with unpredictable crashes on the desktop computers used by the two contract writers, even though all three FM 11 platforms have all the Adobe patches.<o:p></o:p></span></p>
</div>
<div id="yiv1545870390yui_3_7_2_63_1375964420720_58">
<p class="MsoNormal"><span style="font-size:18.0pt;color:black"><o:p> </o:p></span></p>
</div>
<div id="yiv1545870390yui_3_7_2_63_1375964420720_64">
<p class="MsoNormal"><span style="font-size:18.0pt;color:black">One thing which does seem consistent is that FM11 does not seem to work well with files located on our network server, yet that is really the method here. Symptoms may include _extremely_ long
times to open, save and close files and MAY include the abovementioned FrameMaker crashes, though we have not yet confirmed that.<o:p></o:p></span></p>
</div>
<div id="yiv1545870390yui_3_7_2_63_1375964420720_157">
<p class="MsoNormal"><span style="font-size:18.0pt;color:black"><o:p> </o:p></span></p>
</div>
<div id="yiv1545870390yui_3_7_2_63_1375964420720_159">
<p class="MsoNormal"><span style="font-size:18.0pt;color:black">The "fix" is for the contract writers to copy files from our 4-terrabyte network drive onto external hard drives cabled to their terminals and for my coworker to copy files directly onto his computer's
internal hard drive; then copy the revised file back into place in its location on the network drive.
<br>
<br>
The two contract writer desktop computers have ridiculously internal small hard drives. (One is 29 megabytes and the other is 185 megabytes I've been told.)<o:p></o:p></span></p>
</div>
<div id="yiv1545870390yui_3_7_2_63_1375964420720_68">
<p class="MsoNormal"><span style="font-size:18.0pt;color:black"><o:p> </o:p></span></p>
</div>
<div id="yiv1545870390yui_3_7_2_63_1375964420720_72">
<p class="MsoNormal"><span style="font-size:18.0pt;color:black">Me? I'm happy as a clam with Windows XP and FrameMaker 8 working across the network with no FM crashes or other problems -- though I do have to suffer through the long times to open, save and close
files because we now must embed all our graphics instead of referencing them. (I've boohoo'd about that here in the past, so I'll not repeat the faulty reasoning for it once again.)<o:p></o:p></span></p>
</div>
<div id="yiv1545870390yui_3_7_2_63_1375964420720_141">
<p class="MsoNormal"><span style="font-size:18.0pt;color:black"><o:p> </o:p></span></p>
</div>
<div id="yiv1545870390yui_3_7_2_63_1375964420720_143">
<p class="MsoNormal"><span style="font-size:18.0pt;color:black">But doom is in my future, as all four of us are soon to get new platforms with Windows 7 and FM 11.<br>
<br>
This I really dread.<br>
<br>
Who else out there is having what seems to be incompatibility problems with platforms equipped with FM 11 and Windows 7 and how have you gotten around those problems?<br>
<br>
Off-list accounts, etc, are fine.<br>
<br>
-- Ken in Atlanta<o:p></o:p></span></p>
</div>
</div>
</div>
</div>
</div>
</div>
</body>
</html>