Re: Slow Distill Times

[Dov Isaacs <isaacs@xxxxxxxxx>]

Is it the "distill time" really or are you including the time it takes
to produce the PostScript. How are you using the "save as PDF" feature
or are you printing to file using the "Acrobat Distiller" printer instance
or what?

The "save as PDF" under FrameMaker 7 should not have that problem. Otherwise,
look at the driver settings for the "Acrobat Distiller" printer instance.
For spooling, change the settings to allow spooling and to begin printing
AFTER the full document is spooled.

        - Dov


At 4/25/2003 07:51 AM, Nilles, Tom wrote:
>Dov,
>
>I've completed the upgrade to W2000 and Frame 7, Acrobat 5 etc. and for the
>most part, I am extremely pleased with the new features etc.
>
>I have noticed an eerily slow distill time for my books using the Distiller
>instance in Acrobat 5. It's true that I do have some rather large images in
>these books, but it's taking about 20+ minutes to distill a book that can't
>be more than 2MB in total.
>Any suggestions? Previous to the upgrade, distill times were less than 5
>minutes using Frame 5.56 and NT4.x.
>
>Thanks in advance.
>
>Tom Nilles
>Manager, Tech Publications
>Optical Solutions, Inc.
>763-268-3352 (PH)
>763-268-3301 (FAX)
>
>
>
>-----Original Message-----
>From: Dov Isaacs [mailto:isaacs@adobe.com]
>Sent: Friday, April 25, 2003 9:45 AM
>To: framers@FrameUsers.com
>Cc: Dov Isaacs; framers@frameusers.com; framers@omsys.com
>Subject: Re: Anchored Frames Causing Frame Crashes
>
>
>I cannot guarantee that additional RAM will solve your problem. I do know
>that
>Windows and applications run somewhat squirrelly if you don't have enough
>memory
>to really satisfy the threshold requirements of the OS plus memory
>allocation
>requests of applications and their underlying support libraries. With the
>extra
>memory, your performance will certainly improve and if the symptoms stop,
>mazel tov,
>problem is at least masked and you can get on with your work!
>
>In terms of "crash log files", look in your FrameMaker directory for files
>of
>the form "FrameLog_##.##.##_##.##.##.txt". Those contain the crash
>information.
>
>        - Dov
>
>
>At 4/25/2003 07:24 AM, richard.melanson.rm@us.agfa.com wrote:
>
>
>>Thank you for responding Dov,
>>
>>I am not sure about the crash log, I did a search on *.log on my computer
>and I
>>think I may have found some files that are what you mention here but I am
>unsure
>>how to ID them. Dr. Watson does not start, I do not get a BSOD, Win2000
>seems
>>unaffected. I am going to request additional RAM, 512 to be specific. Do
>you
>>feel that this will eliminate the problem?? Thanks again.
>>
>>Richard A. Melanson
>>Technical Writer, AGFA Corp.
>>(978) 658-0200 x5364
>>richard.melanson.rm@us.agfa.com
>>
>>
>>
>>|--------+----------------------->
>>|        |          Dov Isaacs   |
>>|        |          <isaacs@adobe|
>>|        |          .com>        |
>>|        |                       |
>>|        |          04/24/2003   |
>>|        |          08:22 PM     |
>>|        |                       |
>>|--------+----------------------->
>>
>>---------------------------------------------------------------------------
>-|
>>  |
>|
>>  |       To:     Richard Melanson/EXJOM/WIL/AGFA/US/BAYER@AGFA
>|
>>  |       cc:     framers@omsys.com, framers@frameusers.com
>|
>>  |       Subject:     Re: Anchored Frames Causing Frame Crashes
>|
>>
>>---------------------------------------------------------------------------
>-|
>>
>>
>>
>>
>>Richard,
>>
>>No, this isn't expected behaviour. Do you get any crash log or Dr. Watson
>>file on the crash? I assume that you are NOT getting a BSOD ("Blue Screen
>>of Death") from Windows.
>>
>>Truth may it be said, 256MB of memory is really at the extremely low end
>>of usability for Windows 2000. The problem is that with only 256MB of real
>>memory, most of that memory is being used by the operating system and
>>various system services that many users run (virus checkers, port monitors,
>>instant messengers, etc.). Very little is left for real applications
>programs.
>>Even 750MB of swap file is very low. I typically advise a minimum of 512MB
>>of real memory for Windows 2000/XP and a swap file at least three times
>>that size ... and that recommendation is for notebook systems that cannot
>>support even more memory. In reality 1GB is a much more realistic memory
>>configuration for Windows 2000/XP and publishing applications. With other
>>applications such as Illustrator and Photoshop concurrently running with
>>FrameMaker and your normal bunch of desktop applications such as email
>>and a few browser windows, 1.5GB or 2GB is not unreasonable.
>>
>>        - Dov
>>
>>
>>At 4/24/2003 08:15 AM, richard.melanson.rm@us.agfa.com wrote:
>>>Hello Everyone,
>>>
>>>I am working in Framemaker 6.0 p405 on a Dell OptiPlex gx240. I have a
>40gig
>>>drive and 256meg ram, Win2000 with every patch that is available, 750meg
>swap
>>>file. What is happening is this, I have some documents containing numerous
>>steps
>>>with anchored frames at the end of each step containing imported by
>reference
>>>jpeg files of what the steps discuss. I am relocating the anchored frames
>by
>>>either grabbing the anchor at the end of the step or just grabbing the
>entire
>>>frame, doing a cut and then a paste to the new location. After a few times
>of
>>>doing this, Frame will crash HARD, what I mean by hard is that there are
>NO lck
>>>files created by Frame, all of the changes I have added to the document
>are
>>lost
>>>up to the last time I did a save, Frame restarts with no problem and I am
>able
>>>to reopen the file I was working on when Frame crashed without Frame
>saying
>>that
>>>anything had happened.
>>>
>>>Has anyone ever heard of this, it is causing me much heartburn. Thank you
>>>Everyone for your help.
>>>
>>>Richard A. Melanson
>>>Technical Writer, AGFA Corp.
>>>(978) 658-0200 x5364
>>>richard.melanson.rm@us.agfa.com
>
>
>--------------------------------------------------------------------------
>Archives: http://lists.frameusers.com/cgi-bin/lyris.pl?visit=framers
>Website: http://www.FrameUsers.com
>Administration: listadmin@FrameUsers.com
>
>You are subscribed to framers as: tnilles@opticalsolutions.com
>Send a blank email to leave-framers-26002T@lists.FrameUsers.com to
>unsubscribe.


** To unsubscribe, send a message to majordomo@omsys.com **
** with "unsubscribe framers" (no quotes) in the body.   **