I run FM11 on Win7 Enterprise 32bit, 4gb RAM and also on Win7 Ultimate 64bit, 8gb RAM and suffer few crashes. The majority of crashes I have suffered is when I have a book with .xml children whether I was using a network share or locally. When the .xml files were converted to .fm files, most crashes went away.
.fm files are more of a challenge for me because FM is fairly new product experience and I am used to writing in XML editor view; besides FM11 XML View with auto-validating turned on is very slow. So it is workable. The other major issue I have had with files on network shares, especially the rules file, I had to make certain the server where the share resides is WEBDAV enabled and the problem went away. David Coe Sr. Technical Editor Documentation and Training 407.514.2332 office 407.508.9959 mobile david.coe at gdit.com<mailto:david.coe at gdit.com> www.gdit.com<http://www.gdit.com/> General Dynamics Information Technology National and Homeland Security Division Integrated Security and Instrumentation Solutions 12249 Science Drive, Suite 220 Orlando, Florida 32826 [cid:image003.png at 01CE9765.4ACA3520] From: framers-bounces at lists.frameusers.com [mailto:[email protected]] On Behalf Of Ken Poshedly Sent: Thursday, August 08, 2013 11:54 AM To: FrameMaker Users List Subject: Windows 7 + FrameMaker 11 = BOOM! 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. 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. 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. 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. 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.) 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.) But doom is in my future, as all four of us are soon to get new platforms with Windows 7 and FM 11. This I really dread. 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? Off-list accounts, etc, are fine. -- Ken in Atlanta -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.frameusers.com/pipermail/framers/attachments/20130812/8f5b64e1/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 11483 bytes Desc: image003.png URL: <http://lists.frameusers.com/pipermail/framers/attachments/20130812/8f5b64e1/attachment.png>
