Hi Alan,

As I mentioned before, there is nothing but text and graphics imported by
reference, which include PNGs, TIFFs, WMF, and JPG.  In addition, there are
almost no graphics in this particular document.

There's no specific file that the book hits at which point it crashes.
Opening individual files directly from the book work fine, its only when I
am doing a book-level change that issues arise, such as an update or
generating a TOC.

Based on what you and others have said, it certainly sounds like the LAN is
the culprit, not FrameMaker.

Sincerely,
Joe

On Wed, Feb 4, 2009 at 1:13 PM, Alan Litchfield <alan at alphabyte.co.nz>wrote:

> As suggested by others in the other thread, 650 pages is not that large and
> LANs do not limit their capacity by the number of pages in book but by the
> volume of packets that are flowing at any particular time. But as it is, it
> is very unlikely that FM would time out unless there are other problems with
> your book and in this case that is what appears to be the case.
>
> Causes for a crash when opening the files in a book are limited. I would
> suggest you check the graphics. Are there OLE linked/embedded graphics? What
> graphics formats are you using? How many graphics are there per file (as
> related to the RAM on your computer)? Are the graphics all linked or
> embedded, or both? Are there links to other kinds of objects, e.g. Visio
> files, Word files, Excel files,...?
>
> At which file does FM crash? Does it do this consistently? Does FM crash if
> you try opening this file on its own? Does FM crash if all the files are
> opened directly, as opposed to opening them with the book file?
>
> Alan
>
>
> On 5/02/2009, at 6:20 AM, Joseph wrote:
>
>  Hi all,
>>
>> As suggested by several of you, I tried opening all the files at once.
>> This
>> caused FrameMaker to have a seizure, freeze, and crashed. Then, I tried
>> copying the frame files and book to my desktop and it worked fine.  I had
>> always known that working locally with framemaker means everything
>> processes
>> faster, but I didn't realize it made that much difference.  I work on 300
>> to
>> 400 page books on this network, and FrameMaker handles those books fine. I
>> suppose its possible that 600 page books are the limit for the particular
>> network that I am on.
>>
>> Unfortunately, due to work requirements, its no possible to work on local
>> copies and then copy them up at the end of the day. I did this at another
>> place I worked at because that company's network was so slow that you
>> couldn't do anything with FrameMaker on the network, and it worked great.
>>
>>
> --
> Alan Litchfield MBus(Hons), MNZCS
> AlphaByte
> PO Box 1941, Auckland, NZ. 1140
> http://www.alphabyte.co.nz
>
>
>
>
>


-- 
Sincerely,

Joseph Lorenzini
Naperville, IL
309-319-4487

Reply via email to