Skip to main content
Inspiring
June 6, 2013
Question

FM10 Progress-bar indicator shows no progress

  • June 6, 2013
  • 2 replies
  • 1208 views

I'm using FM10 (v10.0.2.419) on Windows 7 OS.

When I print to postscript, the pink ribbon that used to show the progess does not display any longer,

and the percentages indicator remains at 0%.

Any ideas? My colleague right next to me is using the same SW and HW and does not have this problem.

Thanks in advance for any ideas....

    This topic has been closed for replies.

    2 replies

    Arnis Gubins
    Inspiring
    June 6, 2013

    Do you see the page numbers increasing below the progress bar (thermometer in FM's parlance)? Does the job "print" to completion? What device are you printing to?

    You could check your maker.ini file to see if the colour definition has been changed to be a background grey. The default setting should be:

    [Thermometers]

    ;-------------------- Thermometer Color Definitions -----------------------

    ThermoDoneColor=255, 0, 255

    ThermoRemainingColor=192, 192, 192

    There are two versions of the maker.ini file. The global one in the %FMhome% folder and the user-specific one in the \Users\<username>\AppData\Roaming\Adobe\FrameMaker\11 folder.

    iatimaAuthor
    Inspiring
    June 9, 2013

    Hello Arnis,

    I do see the page number increase below the thermometer and the job does print to completion.

    I am printing to .ps (and later distill to PDF).

    I checked both maker.ini files.

    The global maker.ini has the default values

    The soecific maker.ini has no [Thermometer] section.

    Any further thoughts?

    Arnis Gubins
    Inspiring
    June 9, 2013

    Hmmm, seems like you have a broken thermometer... 

    I presume you've rebooted your machine at some point and that this still persists. Are you on a 32- or 64-bit Win7 system? Was anything installed or updated just before the thermometer stopped working?

    Bob_Niland
    Community Expert
    Community Expert
    June 6, 2013

    What's in the .log file?