The "font life" entry is not required if the default value of 240 minutes (4 hours) does not impact on system performance or print job rendering. To tell Kappris to clean up based on time since a font was last used (instead of by watching the print job) one must set the following entries in kappris.ini: The effect of Kappris trying to clean up in the conventional manner is that jobs will sometimes work, sometimes hang and sometimes go missing. Copitrak, however, prevents Kappris from monitoring the print queue for this purpose and it therefore needs another means of 'cleaning up'. Conventionally, Kappris monitors the print queue to see when the job disappears from the queue in order to determine when the fonts can be destroyed and cleaned up. When Kappris sends a job to print it may have to instantiate fonts to allow that job to render correctly. Telling Kappris not to use Print Job Information Make sure therefore that the central configuration also contains the above change. This can mean that, as soon as you log in again, you lose the Kappris entry. WIN32HK_2005.ini is usually copied to the local machine from a central configuration folder every time a user logs in.
#Lasertrak process monitor how to#
IMPORTANT - Details on how to edit all three files are shown here.Īfter the files have been saved and the LaserTrak process has been restarted, Kappris should function properly. Here's a sample file: WIN32HK_2005.INIĪ new entry needs to be added to this so it becomes: An example of WIN32HK_2005 is given below. In this folder there are three files, WIN32HK_2005.ini, WIN64HK.ini and LT2005_SETTINGS.ini and it is these files that we need to edit. The actual process that will interfere with Kappris is LaserTrak and the folder we want to work with is C:\LT2005 (or LT2009 or whatever date version you may have). Kappris is also a 'pseudo printer' and we can use the same technique to exclude Kappris.
#Lasertrak process monitor pdf#
These settings have been designed so that pseudo printers such as PDF creators can be excluded from Copitrak's attentions. Getting Copitrak to leave Kappris virtual printer aloneĬopitrack has configuration settings that will make it leave Kappris alone. Kappris must be told that it cannot use print job information from the print queue in order to schedule clean-up operations.Copitrak must be told to leave the Kappris virtual printer and the Kappris printer port alone.To allow Kappris and Copitrak to work in harmony there are two important steps that must be taken: When it does this with Kappris printing behaviour from some applications can be unpredictable and printing from Microsoft Word will hang. Copitrak's job is to monitor print jobs and analyse them. Left to its own devices, if configured to monitor and cost all print jobs, Copitrak WILL prevent Kappris from working properly.
0 kommentar(er)
