Frame crashes when creating PDF --- SOLVED (I think/hope)

[Yves Barbion]

Hi Framers,

I think/hope I resolved the problem of Frame crashing when creating a 
PDF. This is what I did:

   1. Clean up my Windows/Fonts folder: it had 980 fonts before (220
      MB), now reduced to 413 fonts (75 MB). It had the most exotic
      fonts like "Baby Kruffy", no idea where they come from. I guess
      they came along with some installed programs, which is a nuisance.
   2. Delete c:\windows\system32\fntcache.dat (which was 2.2 MB)
   3. Reboot: fntcache is now 650 KB.
   4. Frame 7.2: Print to Adobe PDF -> everything OK.
   5. Shut down Windows and restart.
   6. Frame 7.2: Print to Adobe PDF or Save as PDF -> everything OK. And
      Save as PDF goes incredibly fast now.

Moral of the story: keep the Windows/Fonts folder clean!


Yves Barbion 
Documentation Architect
Adobe-Certified FrameMaker Instructor
____________________________________

Scripto bvba
Asselsstraat 65
9031 Gent
Belgium
T: +32 494 12 01 89
F: +32 9 366 50 32
BTW (VAT) BE 0886.192.394
skype: yves.barbion
____________________________________



Dov Isaacs wrote:
> Are you using "save as PDF" or are you printing to the
> "Adobe PDF" PostScript printer driver instance?
>
> 	- Dov
>  
>
>   
>> -----Original Message-----
>> From: Yves Barbion
>> Sent: Thursday, June 14, 2007 1:06 PM
>>
>> Configuration:
>>
>>    - FrameMaker 7.2 with DITA App Pack
>>    - Windows XP
>>    - Acrobat Distiller 6 with Dov's recommended Job Options
>>    - Adobe PDF printer driver instance, settings configured as
>>    recommended by Dov (Graphic > Print Quality: 600 dpi etc.)
>>
>> This configuration has always worked for me, but lately, 
>> every time I create
>> a PDF file for the first time, Frame crashes, regardless 
>> whether I print a
>> single file (any file) or a book, using Save as PDF or print 
>> to the Adobe
>> PDF printer driver instance.
>>
>> I delete the C:\WINDOWS\system32\FNTCACHE.DAT file and 
>> reboot, and then
>> everything works fine again.
>>
>> So okay, this is my workaround, but I'm wondering: isn't 
>> there a permanent
>> fix for this problem?
>>
>> Thanks in advance.
>> _______________________________________________
>>     
>
>