And seconding the idea of opening all the files locally, the two
biggest bottlenecks are local RAM and disk free space and a
combination of network speed and server speed for opening and closing
the remote files. If you're running slowly or Frame is having trouble,
those are your first two items to check.

FWIW, I think 2G RAM is about the minimum you want to be running...
and the drive needs to have a significant chunk of free space.

One other possible bottleneck is if your local virus checker is
processing each component file each time FM hits it. If it is, and
it's possible to configure it, try to minimize screening network


Art Campbell
               art.campbell at
  "... In my opinion, there's nothing in this world beats a '52
Vincent and a redheaded girl." -- Richard Thompson
                                                      No disclaimers apply.
                                                               DoD 358

On Wed, Feb 4, 2009 at 11:25 AM, Pappy <mrbassman at> wrote:
>>I am working on a 650-page document in unstructured FrameMaker 8. Due to the
>>size of the document, its incredibly difficult for FrameMaker to execute
>>book-wide commands, such as performing an update or generating the TOC.
>>I have thought about splitting the document into two different books, but I
>>need one integrated TOC.
>>Does anyone have any suggestions that would make executing book-wide
>>commands with a book this size easier?
> Are you opening all the files in the book before you do the book-wide 
> commands?
> 650 pages isn't all that big. We have Frame book files that are nearly 3000 
> pages.
> =============================
> Rick Henkel
> _______________________________________________
> You are currently subscribed to Framers as art.campbell at
> Send list messages to framers at
> To unsubscribe send a blank email to
> framers-unsubscribe at
> or visit 
> Send administrative questions to listadmin at Visit
> for more resources and info.

Reply via email to