<html><head><style type="text/css"><!-- DIV {margin:0px;} --></style></head><body><div style="font-family:times new roman,new york,times,serif;font-size:14pt"><div>FWIW,<br><br>I just learned from Adobe tech support (via phone call) that the permissions in FrameMaker 11.0 have been modified so that the data files should also be on the same hard drive where FM 11.0 is installed. Working across drives (FM here, data files there) is no longer an accepted practice -- at least not with FM11.<br><br>I guess this explains the flaky, intermittent nature of my coworker's FM crashes because that (the "wrong" way is just how we've been doing things here.<br><br>Incidentally, I'm still using FM 8.0 the "wrong" way and with no crashes.<br><br>-- Ken in Atlanta<br><br></div><div style="font-family:times new roman, new york, times, serif;font-size:14pt"><div style="font-family:arial, helvetica, sans-serif;font-size:10pt"><font face="Tahoma" size="2"><hr
size="1"><b><span style="font-weight: bold;">From:</span></b> Ken Poshedly <poshedly@bellsouth.net><br><b><span style="font-weight: bold;">To:</span></b> techwr-l@techwr-l.com<br><b><span style="font-weight: bold;">Sent:</span></b> Wed, February 13, 2013 10:47:05 AM<br><b><span style="font-weight: bold;">Subject:</span></b> "FrameMaker has detected a problem and must quit" Really?!<br></font><br>
To all,<br><br>Please excuse this x-posting (Framemaker list), but no replies at all from there <br>so far.<br><br>My coworker is running FrameMaker 11.0 and is frustrated because twice this <br>morning, FrameMaker crashed on his terminal (luckily creating recovery files, <br>though).<br><br>The warning pop-up window that displayed announcing this glorious impending <br>shutdown stated "Internal Error 11014, 8122692, 8122986, 10866845. . . "<br><br>We have looked at the extremely cryptic error log file that was generated and of <br>course, it's as clear as mud to me.<br><br>Note that my coworker prefers to keep his book and all member chapter files <br>open. He also prefers to embed all his graphics so the various chapter file <br>sizes are MUCH larger than if the graphics were referenced. Thus, the <br>following:<br><br>Title page with copyright page -- 835 Kb (no graphics)<br>TOC -- 870 Kb (again, no
graphics)<br>Section 1 -- 4,740 Kb<br>Section 2 -- 8,720 Kb<br>Section 3 -- 14,983 Kb<br>Section 4 -- 45,815 Kb<br>Section 5 -- 22,066 Kb<br>Section 6 -- 53,033 Kb<br><br>For instance, Section 6 is 89 pages in length with all graphics (strictly line <br>art) embedded and the file size is 53,033 Kb (that's a little over 53 <br>megabytes). In a previous version of this manual (when the graphics were <br>referenced), the file size was just a mere fraction of this (perhaps 20 Kb or <br>30 Kb).<br><br>His computer is a "TRISTAR" pc, with an Intel Core2 Duo CPU, E8500 @ 3.16 Ghz, <br>3.17 Ghz, 3.24 Gigabytes of RAM; running Windows XP Professional, Version 2002, <br>Service Pack 3.<br><br>So the questions:<br><br> * What do those internal error numbers specifically mean?<br> * Is/are the error/errors caused by a hardware problem or a software problem?<br>-- Ken in
Atlanta<br>^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^<br>STC Vice President Nicky Bleiel is giving a free webinar on best practices<br>for creating mobile help.<br><br>Learn more: <a href="http://bit.ly/WNaCzd" target="_blank">http://bit.ly/WNaCzd</a><br><br>^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^<br><br>You are currently subscribed to TECHWR-L as <a ymailto="mailto:poshedly@bellsouth.net" href="mailto:poshedly@bellsouth.net">poshedly@bellsouth.net</a>.<br><br>To unsubscribe send a blank email to<br><a ymailto="mailto:techwr-l-leave@lists.techwr-l.com" href="mailto:techwr-l-leave@lists.techwr-l.com">techwr-l-leave@lists.techwr-l.com</a><br><br><br>Send administrative questions to <a ymailto="mailto:admin@techwr-l.com" href="mailto:admin@techwr-l.com">admin@techwr-l.com</a>. Visit<br><a href="http://www.techwhirl.com/email-discussion-groups/" target="_blank">http://www.techwhirl.com/email-discussion-groups/</a> for more
resources and info.<br><br>Looking for articles on Technical Communications? Head over to our online magazine at <a href="http://techwhirl.com" target="_blank">http://techwhirl.com</a><br><br>Looking for the archived Techwr-l email discussions? Search our public email archives @ <a href="http://techwr-l.com/archives" target="_blank">http://techwr-l.com/archives</a><br></div></div>
</div></body></html>