Joe wrote:
> I wanted to clarify one aspect of this discussion.
> Is the Open All Files in Book command causing FrameMaker
> to freeze and crash an unrelated issue with the LAN and
> indicative of some other problem (e.g. file corruption), or
> are you saying that because the LAN is causing
Hi Fred,
I wanted to clarify one aspect of this discussion. Is the Open All Files in
Book command causing FrameMaker to freeze and crash an unrelated issue with
the LAN and indicative of some other problem (e.g. file corruption), or are
you saying that because the LAN is causing Frame to crash whe
Joe wrote:
> I wanted to clarify one aspect of this discussion.
> Is the Open All Files in Book command causing FrameMaker
> to freeze and crash an unrelated issue with the LAN and
> indicative of some other problem (e.g. file corruption), or
> are you saying that because the LAN is causin
Hi Fred,
I wanted to clarify one aspect of this discussion. Is the Open All Files in
Book command causing FrameMaker to freeze and crash an unrelated issue with
the LAN and indicative of some other problem (e.g. file corruption), or are
you saying that because the LAN is causing Frame to crash whe
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 p
Joe wrote:
> Based on what you and others have said, it certainly sounds like the LAN is
> the culprit, not FrameMaker.
Yes. And the workaround that several of us have suggested (opening all
the component files before doing book-level operations) is still valid,
That approach will eliminate the
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
Joe wrote:
> Based on what you and others have said, it certainly sounds like the LAN is
> the culprit, not FrameMaker.
Yes. And the workaround that several of us have suggested (opening all
the component files before doing book-level operations) is still valid,
That approach will eliminate th
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
-boun...@lists.frameusers.com
[mailto:framers-bounces at lists.frameusers.com] On Behalf Of Joseph
Sent: Wednesday, February 04, 2009 11:21 AM
To: framers at lists.frameusers.com
Subject: Follow up on Handling Large Books in FrameMaker
Hi all,
As suggested by several of you, I tried opening all the files at
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 p
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 p
-boun...@lists.frameusers.com
[mailto:framers-boun...@lists.frameusers.com] On Behalf Of Joseph
Sent: Wednesday, February 04, 2009 11:21 AM
To: framers@lists.frameusers.com
Subject: Follow up on Handling Large Books in FrameMaker
Hi all,
As suggested by several of you, I tried opening all the files at once.
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 p
14 matches
Mail list logo
