Global Graphics Software Ltd Harlequin Server RIP Utility Manual

Migration Utility for Windows
Version 5.0
July 2011
Copyright and Trademarks
Harlequin RIP: Migrate
Version 5.0
July 2011
Part number: HQ-Migrate-OEM-Win
Document issue: 113
Copyright © 2011 Global Graphics Software Ltd. All rights reserved.
Certificate of Computer Registration of Computer Software. Registration No. 2006SR05517
No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form or by any
means, electronic, mechanical, photocopying, recording, or otherwise, without the prior written permission of
Global Graphics Software Ltd.
The information in this publication is provided for information only and is subject to change without notice.
Global Graphics Software Ltd and its affiliates assume no responsibility or liability for any loss or damage that
may arise from the use of any information in this publication. The software described in this book is furnished
under license and may only be used or copied in accordance with the terms of that license.
Harlequin is a registered trademark of Global Graphics Software Ltd.
The Global Graphics Software logo, the Harlequin at Heart Logo, Cortex, Harlequin RIP, Harlequin ColorPro,
EasyTrap, FireWorks, FlatOut, Harlequin Color Management System (HCMS), Harlequin Color Production Solutions (HCPS), Harlequin Color Proofing (HCP), Harlequin Error Diffusion Screening Plugin 1-bit (HEDS1), Harlequin Error Diffusion Screening Plugin 2-bit (HEDS2), Harlequin Full Color System (HFCS), Harlequin ICC
Profile Processor (HIPP), Harlequin Standard Color System (HSCS), Harlequin Chain Screening (HCS), Harlequin Display List Technology (HDLT), Harlequin Dispersed Screening (HDS), Harlequin Micro Screening (HMS),
Harlequin Precision Screening (HPS), HQcrypt, Harlequin Screening Library (HSL), ProofReady, Scalable Open
Architecture (SOAR), SetGold, SetGoldPro, TrapMaster, TrapWorks, TrapPro, TrapProLite, Harlequin RIP Eclipse
Release and Harlequin RIP Genesis Release are all trademarks of Global Graphics Software Ltd.
Protected by U.S. Patents 5,579,457; 5,808,622; 5,784,049; 5,862,253; 6,343,145; 6,330,072; 6,483,524; 6,380,951;
6,755,498; 6,624,908; 6,809,839.
Other U.S. Patents Pending
Protected by European Patents 0 803 160; 0 772 934; 0 896 771; 672 29 760.8-08.
Portions licensed under U.S. Patent No. 5,212,546; 4,941,038.
TrueType is a registered trademark of Apple Computer, Inc.
The ECI and FOGRA ICC color profiles supplied with this Harlequin RIP are distributed with the kind permission of the ECI (European Color Initiative) and FOGRA respectively, and of Heidelberger Druckmaschinen AG
(HEIDELBERG).
The IFRA ICC profiles supplied with this Global Graphics Software are distributed with the kind permission of
IFRA and of GretagMacbeth.
International Cooperation for Integration of Processes in Prepress, Press and Postpress, CIP4, Job Definition Format, JDF and the CIP4 logo are trademarks of CIP4.
Adobe, Adobe Photoshop, Adobe Type Manager, Acrobat, Display PostScript, Adobe Illustrator, PostScript, Distiller and PostScript 3 are either registered trademarks or trademarks of Adobe Systems Incorporated in the
United States and/or other countries which may be registered in certain jurisdictions.
Global Graphics Software Ltd is a licensee of Pantone, Inc. PANTONE® Colors generated by ScriptWorks are
four-color process simulations and may not match PANTONE-identified solid color standards. Consult current
®
®
PANTONE Color Publications for accurate color. PANTONE , Hexachrome , and PANTONE CALIBRATED™are
trademarks of Pantone, Inc. © Pantone, Inc., 1991.
Other brand or product names are the registered trademarks or trademarks of their respective holders.
CONTENTS
II
MIGRATE FACILITY V5.0
CONTENTS
III
US Government Use
Harlequin RIP software is a computer software program developed at private expense and is subject to the following Restricted Rights Legend:
“Use, duplication, or disclosure by the United States Government is subject to restrictions as set forth in (i) FAR 52.227-14 Alt III or (ii) FAR 52.22719, as applicable. Use by agencies of the Department of Defense (DOD) is subject to Global Graphics Software’s customary commercial license as
contained in the accompanying license agreement, in accordance with DFAR 227.7202-1(a). For purposes of the FAR, the Software shall be deemed
to be ‘unpublished’ and licensed with disclosure prohibitions, rights reserved under the copyright laws of the United States.” Global Graphics
Software Incorporated, 31 Nagog Park, Suite 315, Acton MA 01720.
CONTENTS
III
Contents
1
2
3
4
5
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Versions of the RIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Migrate procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Appendix A—Example log file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
CONTENTS
IV
Transferring settings to a new installation
Transferring settings from an installation that has been used for some time can be a difficult operation
to perform quickly and accurately. The migration utility makes this process simpler.
1 Overview
The migration utility is a self-contained, Java -based utility that transfers the majority of settings from
™
an installed and used Harlequin RIP to a freshly installed RIP of a newer version. The Java component provides an easy to use interface that is consistent across all platforms.
In general terms, the transferred settings are those related to page setups and output plugins, while
the un-transferred settings are those that may depend on the version of the RIP, such as custom page
features. See “Limitations” on page 4 for more details, including some limitations in this release.
The utility transfers page setups, including:
•
RIP memory settings.
•
Separations, screening, and color setups in version 5.0 and later.
•
Plugin parameters (as set in the Device Configuration dialog box).
•
Use of page features (but not the page features themselves).
•
Resolution and units.
•
Effects (Rotate, Negative, Trim page, and Mirrorprint).
•
Scaling.
•
JobID—f the JobID in the old RIP is higher than the JobID in the new RIP, then increase the JobID
in the new RIP to match the old RIP.
•
Cassette selection (and all cassettes whether or not used by a page setup).
•
Calibration (calibration, tone curves, and intended/actual press).
•
Trapping
From the Harlequin RIP Genesis Release v7.0 TrapProLite is not available. The trapsets can still
be migrated from earlier versions of the RIP to v.9.0. But if TrapPro was not enabled in the v.6 RIP,
or if you are migrating the trapsets from a version 5 RIP (where we did not have TrapPro, and
EasyTrap was enabled), the following warning will appear:
Trapping sets migrated. Please upgrade to TrapPro to enable them
Note: When migrating to a RIP that supports TrapPro from a RIP that does not, you should
enable TrapPro in the new RIP after the migration, otherwise your password will be lost. This is
because a new password for TrapPro is set to 0. So, if TrapPro is enabled in the new RIP and then
a migration is performed, the valid password will be overwritten by 0.
CONTENTS
1
MIGRATE FACILITY V4.1
CONTENTS
2
The migration utility also transfers:
•
Harlequin plugins, and devices based on multiple-device plugins, if not present in the new RIP,
including ProofReady plugins and the HEDS screening plugins.
Note: If migrating a ProofReady plugin for Epson VSD or ENCAD printers, please ensure that
the ProofReady plugin is installed into the destination RIP before migration. Then to complete
the migration process create a page setup for the plugin in the destination RIP.
•
Some OEM plugins, such as the DI-file plugin.
Note: If migrating a third-party plugin, please ensure that the plugin is installed into the destination RIP before migration. Then to complete the migration process create a page setup for the
plugin in the destination RIP. Some third-party plugins install DLLs which will not be migrated.
Note: Migrate copies over to the new RIP any folder under /Devices of the source RIP if it contains a plugin that is not already in the target RIP. It will not override any plugin that is already in
the target folder (that is, it will skip the copy), but upgrades the settings to the newer version if
necessary, and merges them into the plugin in the new RIP. Migrate will not delete any plugin
from the new RIP.
•
Passwords that have enabled plugins and other RIP extras.
•
Simple imposition settings
Some of the schemes present in the Genesis Release v7.0 have been changed for v7.1 and later. If
you migrate the imposition setups from v7.0 to v7.1 (or later) they will work correctly. The following table shows the relationship between the deprecated Genesis Release v7.0 schemes and
the new schemes present in the v7.1 (or later):
Bindin
Spine HorGutt VertgFold er
Gutter
Edge
Old
Scheme
New
Scheme
Pages Pages-Up
Across
SaddleStitch_
Left_1
SaddleStitch_2 Left
Auto
GutterB
GutterA
0
0
SaddleStitch_
Right_1
SaddleStitch_2 Right
Auto
GutterB
GutterA
0
0
SaddleStitch_
TopA_1
SaddleStitch_2 TopA
Auto
GutterB
GutterA
0
0
SaddleStitch_
TopB_1
SaddleStitch_2 TopB
Auto
GutterB
GutterA
0
0
SaddleStitch_
TopC_1
SaddleStitch_2 TopC
Auto
GutterB
GutterA
0
0
SaddleStitch_2x SaddleStitch_
_Left_1
S&R_1
Left
Auto
GutterA
GutterB
1
2
SaddleStitch_2x SaddleStitch_
_Right_1
S&R_1
Right
Auto
GutterA
GutterB
1
2
SaddleStitch_2x SaddleStitch_
_TopA_1
S&R_1
TopA
Auto
GutterA
GutterB
1
2
SaddleStitch_2x SaddleStitch_
_TopB_1
S&R_1
TopB
Auto
GutterA
GutterB
1
2
SaddleStitch_2x SaddleStitch_
_TopC_1
S&R_1
TopC
Auto
GutterA
GutterB
1
2
Table 1 Migration of deprecated Simple Imposition schemes
CONTENTS
2
MIGRATE FACILITY V4.1
CONTENTS
3
1.1 InstallAnywhere
In the InstallAnywhere releases of the Harlequin RIP, the Migrate utility is supplied on the Documentation & Tools CD, which forms part of the CD set for evaluation distributions.
For further details on the exact location of the Migrate utility for your chosen platform, refer to the
Readme at the top level of the CD.
1.2 Folder structure
The utility is supplied with an appropriate runtime version of Java for Windows and UNIX platforms.
For these platforms the runtime version is the Java Runtime Environment (JRE). The JRE has its own
documentation, including a license concerning its use: this documentation is in the jre folder of the
utility.
1.3 Document structure
The remainder of this document covers:
•
Supported versions of the RIP—see “Versions of the RIP” on page 3.
•
Requirements—see “Requirements” on page 3.
•
Limitations—see “Limitations” on page 4.
•
Migrate procedure—see “Migrate procedure” on page 6.
•
Example log file—see “Appendix A—Example log file” on page 11.
2 Versions of the RIP
The migration utility can transfer settings between various versions of the RIP. The oldest version RIP
supported by Migrate is version 4.1r4.
There is no support for migration to, or from, beta versions of the RIP, though it may be possible for
some versions. There is also no support for migration to version 5.0r0 (and earlier beta versions), and
this particular migration is known not to work.
3 Requirements
The old and new installations of the RIP and the migration utility must be accessible on the same
computer.
The computer must be capable of running Java. In general, this imposes a lower requirement than
running the RIP, but may require a later operating system than that required by version 4.5 or earlier
of the RIP. The Java distributions do not give a full specification, but these are guidelines:
•
All Windows platforms must have 32 MB of free RAM, 21 MB of free disk space, and otherwise
be able to run the newer version of the RIP.
The utility creates a small number of temporary files, in the SW folder of the new RIP installation.
These files are all in the temporary newSW folder and should not occupy more than 5 MB in total,
unless large profiles have been imported into the original RIP. The utility copies some information
from these temporary files into the configuration files of the new installation and removes the temporary files at the end of a migration, leaving only a log file of what was done.
You can run the utility from the CD or you can copy it to a system drive and run it. If you make a local
copy of the utility, you can remove it once you have completed the migrate.
CONTENTS
3
MIGRATE FACILITY V4.1
CONTENTS
4
4 Limitations
The aim of the utility is to transfer those settings for which a new setting can be deduced safely in the
new RIP. We are working to reduce the number of limitations, but some are based on Java implementations and are outside our direct control.
4.1 Limitations in the utility
The migration utility does not transfer:
•
Fonts. (There is a separate utility for fonts.)
•
The Workspace and Page buffer folder locations, as configured in the RIP Extras dialog, are not
transferred.
•
Media Manager settings.
•
Custom screens installed in the RIP.
•
Settings between RIPs with different localizations.
•
Emulation profiles
If you have imported emulation profiles into a pre Eclipse Release RIP and wish to migrate to a
Eclipse Release or later RIP, you must re-import the profiles into the destination RIP. The Migrate
utility issues a warning to this effect. Note however, that imported page setups continue to reference emulation profiles and will not need to be updated once the relevant emulation profiles
have been imported.
The migration utility transfers some features partially:
•
Configure RIP
Only the Print buffer and Network buffer settings from Configure RIP dialog of the old RIP are
migrated to the new RIP.
•
Input channels
A spool folder is only migrated if it is located within the old SW folder. If this is the case, it is
migrated to the same location in the new SW folder.
If a channel name in the old version of the RIP matches a channel name that already exists in the
new version of the RIP, the migrated channel name is postfixed by _M00.
•
Page Features
If any page setups use special page features (ones not supplied with the new RIP by your supplier) you will need to copy these page features into the new RIP. Some page features may need
rewriting to suit a newer version of the RIP but, for example, you may wish to do this anyway in
order to use LanguageLevel 3 or other features of a newer version RIP.
•
File-based output plugins
Page setups using the TIFF output plugin or other file-based output plugins that use folders
named in their configuration dialog boxes, will still use the location defined in the old RIP. You
may wish to change the locations if the old RIP defined a location in its own folder. You can probably leave the location unchanged if the old location was outside the old RIP’s folder hierarchy.
•
Page setups using the Fuji Pictography plugin
The utility cannot migrate page setups using the Fuji Pictography plugin from version 4.x to
version 5.x where there is a corresponding plugin in the newer RIP installation. There is a warning if this situation occurs.
CONTENTS
4
MIGRATE FACILITY V4.1
CONTENTS
5
4.2 Version-based limitations
The migration utility transfers some features differently between various versions of the RIP.
Any version to version 5.0 revision 0:
•
It is not possible to transfer settings to version 5.0 revision 0 from any other version of the RIP.
(Transfer of settings from version 5.0 is possible, as is transfer from a version earlier than 5.0 to a
version later than 5.0.)
Version 4.1 to version 4.5 (or later):
•
Page setups named the same as the folder containing the plugin
Any page setup named exactly the same as the folder containing that plugin in the later version
of the RIP, does not appear. There is no reported error and all items used by the page setup transfer correctly, but the page setup does not appear in the Page Setup Manager. This is limited to
page setups originating in version 4.1 because of changes in the way that the RIP maps file names
when there are duplicated or illegal file names.
Version 4.5 to version 5.1 (or later):
•
Color management setups
If you migrate a color management setup from a separating configuration in version 4.5 to
version 5.1 or later, the transferred color setups are listed in the appropriate color space (probably
CMYK) for the Printing Press device, rather than the original device.
Version 4.1 or 4.5 to version 5.1 (or later):
•
Calibration curve display differences
Calibration curves are transferred in full from old installations and, once transferred, the curves
are used for output to the same accuracy, but there may be some difficulty in viewing the data
points. For example, when using the default CMYK calibration target, 24 patch values per channel are migrated from version 4.1 or 4.5. The Calibration Manager of 5.1, shows fewer patch
values because a default CMYK target uses 18 patches. Only a calibration curve with a sudden
jump at one of the nominal values 25, 35, 45, 55, 65, or 75 will look different, and even a curve like
that will be used with full accuracy. (Substituting a custom target with 24 patches will enable all
the migrated data to be viewed in version 5.1 or later of the RIP.)
Any version before 5.1r1 to version 5.1r1 (or later):
•
Change of name for Linear in Intended Press or Actual Press
The Page Setup dialog box in version 5.1r1 and later does not offer the Linear option in the
Intended Press or Actual Press menus. The None option is equivalent, so a page setup migrated from
an earlier version uses None. There is no effect on output.
Any version to a version before 5.1r2:
•
Devices named using a slash ( / ) character
If page setups in an existing installation of the RIP use a device given a name (in the Device Manager) that contains a slash character, it is not possible to migrate those page setups successfully to
a version earlier than 5.1r2. It is possible to migrate other page setups from the same installation,
provided that they do not use the slash character. (The migration log file will contain a warning
for the page setups that failed to migrate.)
It is possible to migrate page setups using these names if migrating to version 5.1r2 or later.
CONTENTS
5
MIGRATE FACILITY V4.1
CONTENTS
6
Any version to version 8.0r0 (or later):
•
In v8.0r0 Black point compensation has been added to ColorPro
Migration to v8.0r0 will work. However, Black point compensation will only work with color
transforms composed entirely of ICC profiles, that is, the method will have no effect on device
independent color spaces such as CalGray, CalRGB, CIEBasedxxx, but will work for ICCBased
and embedded ICC profiles. Also, the ICC profiles supplied in setreproduction must be
installed in an v8.0r0 RIP, that is, the method will have no effect on output profiles migrated from
earlier versions of the RIP. Therefore, if you have decided to Migrate your setups and you want to
use the new Black Point Compensation option, you must manually re-install your ICC profiles.
The HEDS feature released with v8.0r0 can be enabled before or after the migration. Also, HEDS
might need to be re-selected if used by any non-standard plugin’s Color Separation Setup that is
not using a PhotoInk device colorant family.
Any version to version 8.1r0 (or later):
•
Emulation BVD-FOGRA profiles which have been replaced in v8.1 will not be copied from older
versions, unless a color setup is using them.
Version 8.2rx to version 8.3:
Migration from v8.2rx to v8.3 is not allowed when using Migrate v4.2r0.
Any version to version 9.0r0 (or later):
•
The BVD_FOGRA press profiles have been replaced by new FOGRA and IFRA press profiles. If
you use these files in a Press Calibration setup in the Calibration Edit dialog, you must edit the
setup after migration, and select one of the replacement profiles available in the RIP.
4.3 Platform-based limitations
Most platform-based limitations are due to variations in the implementation of Java for the various
platforms. We anticipate that these implementations will improve.
5 Migrate procedure
Note: From the Harlequin RIP v5.5 or later non-Harlequin plugins are treated in much the same way
as Harlequin plugins. The only difference is that Migrate knows which version of Harlequin plugin it
expects for a particular version of RIP, and patches the difference between the old and new.
Note: From v5.5 Migrate copies over to the new RIP any folder under /Devices of the source RIP if it
contains a plugin that is not already in the target RIP. It will not override any plugin that is already in
the target folder (that is, it will skip the copy), but upgrades the settings to the newer version if necessary, and merges them into the plugin in the new RIP. Migrate will not delete any plugin from the new
RIP.
Make sure you have installed the new version of the RIP so that it is usable on the same computer as
the old installation of the RIP.
If migrating a ProofReady plugin for Epson VSD or ENCAD printers, please ensure that the ProofReady plugin is installed into the destination RIP before migration. Then to complete the migration
process create a page setup for the plugin in the destination RIP.
If migrating an OEM plugin, please ensure that the plugin is installed into the destination RIP before
migration. Then to complete the migration process create a page setup for the plugin in the destination RIP.
Note: Some third-party plugins install DLLs which will not be migrated.
CONTENTS
6
MIGRATE FACILITY V4.1
CONTENTS
7
Do not use the new RIP before performing the migration except, perhaps, to check that it operates and
that the user interface appears in the correct language. If you do more, the migrated page setups may
conflict with, and override, settings that you think you have made in the new RIP. If you have made
tests and created page setups and other settings, we suggest that you delete that installation of the RIP
and migrate into a fresh installation.
If your computer has a suitable CD-ROM drive, you can execute the utility from that drive. If you do
not have a convenient CD-ROM drive, you must copy the folder containing the utility to a hard disk
available to the computer.
A quick overview of the procedure is:
•
Use the utility—see “Using the migration tool” on page 7.
•
Copy or re-create any items and settings not transferred by the utility—see “Copy or re-create
any items not transferred by the utility” on page 9.
•
Check the RIP—see “Check the new RIP” on page 9 and read “Notes on transferred page
setups” on page 10.
5.1 Using the migration tool
1.
Before starting the migration procedure, quit all loaded versions of the Harlequin RIP.
Note: Before using the migration tool, you must have loaded each of the two RIP versions at least
once. The migration tool will not find RIPs that have not previously been loaded. However, it is
not necessary to have run any jobs through the RIP prior to using the migration utility.
2.
Start the Migrate utility by running Migrate.exe. The Harlequin RIP Migration Utility dialog box
opens, as shown in Figure 1. The controls in the dialog allow you to select the old and new RIP
versions that you want to transfer settings and password files between.
3.
Choose the old RIP (the one you are transferring from). Click the button labelled Select “From” RIP
and, using the dialog box that opens, navigate to the installation folder containing the RIP, then
click Open. The program will scan the folder and its subfolders, searching for all instances of the
Harlequin RIP. Any RIPs found are displayed in the Version menu.
4.
Depending on the folder selected, or how you have installed the RIPs, there may be more than
one RIP to choose from in the Version menu. From the menu, choose the appropriate RIP.
CONTENTS
7
MIGRATE FACILITY V4.1
CONTENTS
Figure 1
5.
8
Harlequin RIP Migration Utility dialog box
Choose the new RIP (the one you are transferring to). Click the button labelled Select “To” RIP and,
in the dialog box that opens, choose the folder containing the new RIP. Again, depending on the
folder selected there may be more than one RIP in the Version menu.
Note: The “To” RIP cannot be the same as the “From” RIP, otherwise, Migrate will issue an error
message and abort.
6.
Click the Migrate button to start the migration process. The utility scans the old RIP and displays
its progress in the Messages text panel. (While doing this, the utility is building a list of changes in
files held in a temporary folder in the new RIP.)
A typical period is up to five seconds per simple page setup when scanning and under a second
per file when merging the temporary files. During these processes there should be no long pauses
(over 60 seconds) without text appearing in the Messages text panel.
If the utility fails to find information about a plugin, it is unable to transfer any page setups using
that plugin. The utility reports each problem of this kind with a dialog box displaying the message:
There is no information in the Tones Table for the plugin (plugname)
Click OK to dismiss the dialog box. If any page setups use this plugin you will see this message:
The page setup “setup_name” could not be migrated.
Do you wish to continue?
Click OK if you wish to continue with the migration, without the named page setup. Click Cancel
if you wish to cancel the whole migration session.
If the utility reports this error for a plugin supported by your supplier, or you see any other problems, contact your supplier and give details.
Note: If the “From” RIP is any release of version 4.1, you will see a dialog box saying that
filemap.dat does not exist. This is harmless; click OK to continue.
CONTENTS
8
MIGRATE FACILITY V4.1
CONTENTS
7.
9
If there are no problems, the utility displays a dialog box asking:
The migrate session was successful. Do you wish to merge migrated SW folder with your
original SW folder?
Click OK to merge the temporary files and commit the changes. Again, the Messages text panel
shows the progress of copying the files. Alternatively, click Cancel if you wish to leave your new
RIP unchanged.
Note: Delete the newSW folder inside the SW folder if you click Cancel.
8.
The utility displays a dialog asking:
The migrate session was successful. Do you wish to quit the migration utility?
If you answer Yes, the utility exits.
If you answer No, you can transfer settings to or from other RIPs in the same session. Change the
“From” or “To” RIP using the appropriate button before clicking Migrate again.
5.2 Copy or re-create any items not transferred by the utility
Start the new RIP and if required, do the following.
•
Make any other settings required in the Configure RIP dialog box, for example, memory settings
and so on.
•
Copy or install any custom screens.
•
Install any custom fonts.
•
If your old installation used any custom page features, copy them from the old RIP to the
SW/Page Features folder of the new RIP.
•
Create any color management setups needed.
•
Enable the use of ColorPro in Eclipse Release or later RIPs.
•
If migrating to Eclipse Release or later RIPs, you need to import any emulation profiles that were
associated with color setups in the original RIP.
•
Check the locations used by file-based output plugins.
5.3 Check the new RIP
First, check the listing of page setups in the Page Setup Manager dialog box. If the listing appears correct, edit each page setup that may use custom page features, color management, trapping, or a filecreating output device. If a page setup uses one of these options, check that you have supplied a suitable item of the correct name. “Copy or re-create any items not transferred by the utility” on page 9
summarizes what you may need to do.
Next, print a simple job to each transferred page setup. Start by selecting Disable output in the Output
Controller / Monitor before you print and Roam the page buffers. If the page buffers appear correct,
enable output and send some page buffers to the output device. Look for errors in the Output
Controller / Monitor and for messages in the RIP Monitor window.
If these tests show no errors the new RIP is ready for use.
CONTENTS
9
MIGRATE FACILITY V4.1
CONTENTS
10
5.4 Notes on transferred page setups
Successive versions of the RIP handle page setups and other collections of settings in different ways,
especially in the way that they are named. The following notes may help you find settings that you
think may not have been transferred.
•
When you migrate from a Level 2 page setup to version 5.1 or later, the migrated page setup
uses LanguageLevel 3 by default. If the Level 1 compatibility setting is chosen in a migrated
page setup, this is transferred, but later use or editing of the page setup may detect an option
setting, such as separating, where Level 2 is required. A dialog box announces where this
happens.
CONTENTS
10
MIGRATE FACILITY V4.1
CONTENTS
11
Appendix A—Example log file
The migration utility produces a log of the migration procedure, stored as migrate.log in the folder
containing the SW folder of the installation to which you are transferring settings. This text file is a
record of all the messages in the Messages panel, together with any questions and responses asked in
dialog boxes.
This is an example of transferring settings from Harlequin PLUS Server RIP v8.3r0 to Harlequin PLUS
Server RIP v9.0r0:
Harlequin RIP Migration Utility
Version 5.0r0
Migrating from Harlequin RIP version "8.3 Revision 0 HARLQN Licence Server MT RIP"
to version "9.0 Revision 0 HARLQN Licence Server MT RIP"
Starting migration at: Fri Jun 10 10:11:01 BST 2011
Building file mapping table ... completed.
Migrating plugins and devices ...
* Plugin "epson3800" already exists.
- Migrating color profiles for plugin "epson3800" ...
- Migrating color rendering intents for plugin "epson3800" ...
** "Enhanced Matte 360" already exists.
** "Premium Photo Glossy 2880" already exists.
** "Enhanced Matte 720" already exists.
** "Premium Luster Photo 1440" already exists.
** "Premium Luster Photo 720" already exists.
** "Premium Photo Glossy 1440" already exists.
** "Premium Photo Glossy 720" already exists.
** "Premium SemiGloss Photo 1440" already exists.
** "Proof Commercial SemiMatte 1440" already exists.
** "Proof Commercial SemiMatte 720" already exists.
- Migrating Screen Names for plugin "epson3800" ... completed.
* Plugin "epson7900plate" already exists.
* Plugin "okipcl" already exists.
- Migrating color profiles for plugin "okipcl" ...
** "Bvd-fogr" already exists.
* Plugin "pdfraster" already exists.
CONTENTS
11
MIGRATE FACILITY V4.1
CONTENTS
12
* Plugin "testnone" already exists.
* Plugin "tiff" already exists.
- Migrating color profiles for device "Preview" ...
** "Bvd-fogr" already exists.
- Migrating Device Manager ...
-- All devices of plugin "okipcl.i32" migrated.
-- All devices of plugin "tiff.i32" migrated.
Plugins and devices migration completed.
Migrating separations ...
- Migrating separations for device "None" ...
- Migrating separations for device "OKI PCL Halftone" ...
- Migrating separations for device "Preview" ...
- Migrating separations for device "TIFF.X00" ...
Separations migration completed.
Migrating inksets ...
Inksets migration completed
Migrating Imposition Manager ...
Imposition Manager migration completed.
Migrating color rendering intents ...
Color rendering intents migration completed.
Migrating color space resources ...
Color space resources migration completed.
Migrating color setups ...
- Migrating color setups for device "OKI PCL Halftone" in space "DeviceCMYK" ...
-- "(No Color Management)" migrated.
- Migrating color setups for device "Press" in space "DeviceCMYK" ...
- Migrating color setups for device "Preview" in space "DeviceCMYK" ...
-- "(No Color Management)" migrated.
-- "colsetk1" migrated.
-- "colsetk2" migrated.
- Migrating color setups for device "Preview" in space "DeviceGray" ...
-- "(No Color Management)" migrated.
CONTENTS
12
MIGRATE FACILITY V4.1
CONTENTS
13
- Migrating color setups for device "Preview" in space "DeviceRGB" ...
-- "(No Color Management)" migrated.
- Migrating color setups for device "OKI PCL Halftone" in space "DeviceCMYK" ...
- Migrating color setups for device "Preview" in space "DeviceCMYK" ...
- Migrating color setups for device "Preview" in space "DeviceGray" ...
- Migrating color setups for device "Preview" in space "DeviceRGB" ...
Color setups migration completed.
Migrating page setups ...
- "Default Page Setup" migrated.
- "etup1" migrated.
- "setup2" migrated.
- "setup3" migrated.
Page setups migration completed.
Migrating RIP configurations (memory settings and passwords) ... completed.
Migrating JobID ... no migration needed.
Migrating calibration sets ... completed.
Migrating cassette manager ...
Cassette manager migration completed.
Migrating units database ... completed.
Migrating UI Preference ... completed.
Migrating screen list ... completed.
Migrating Press color profiles ...
* "BVD-FOGRA positive gloss" already exists.
* "BVD-FOGRA positive LWC" already exists.
* "BVD-FOGRA positive matt" already exists.
* "BVD-FOGRA positive uncoated" already exists.
* "Commercial A" already exists.
* "Linear" already exists.
* "SWOP (CGATS TR001)" already exists.
* "Linear" already exists.
Press color profiles migration completed
Migrating Emulation color profiles ...
CONTENTS
13
MIGRATE FACILITY V4.1
CONTENTS
14
CONTENTS
14
* "3M Matchprint" already exists.
* "3M Matchprint (Standard)" already exists.
* "Bvd-fogr" already exists.
* "Commercial A" already exists.
* "DuPont Cromalin" already exists.
* "DuPont Waterproof Commercial" already exists.
* "DuPont Waterproof Publication" already exists.
* "FOGRA11_OFCOM_PO_P1,2_F60_03" already exists.
* "FOGRA12_OFCOM_PO_P3_F60_03" already exists.
* "FOGRA13_OFCOM_PO_P4_F60_03" already exists.
* "FOGRA14_OFCOM_PO_P5_F60_03" already exists.
* "FOGRA19_OFCOM_PO_P1,2_F70_03" already exists.
* "FOGRA20_OFCOM_PO_P3_F70_03" already exists.
* "FOGRA21_OFCOM_PO_P4_F70_03" already exists.
* "FOGRA22_OFCOM_PO_P5_F70_03" already exists.
* "Fuji ColorArt Comm CR-T3 Gloss" already exists.
* "Fuji ColorArt Pub CR-T3 MMatte" already exists.
* "IFRA26" already exists.
* "IFRA30" already exists.
* "SWOP (CGATS TR001)" already exists.
Emulation color profiles migration completed
Migrating ICC profiles ...
* "Bvd-fogr" already exists.
* "ECI_USWebCoatedSWOP.icc" already exists.
* "scRGB.icc" already exists.
* "sRGB_IEC61966-2-1_withBPC.icc" already exists.
ICC profiles migration completed.
Migrating ICC color rendering dictionaries ...
ICC color rendering dictionaries migration completed.
Migrating input channels ...
Input channels migration completed.
Merging files ... completed.
MIGRATE FACILITY V4.1
CONTENTS
15
Migration completed at: Fri Jun 10 10:11:07 BST 2011
Notes about the log file
1.
The log starts at the point that you click Migrate, so it does not show the exact messages that may
appear as you select RIPs and the utility identifies the RIP version. This text is typical of the message shown when migrating from v8.3r0 to v9.0r0:
Migrating from Harlequin RIP version "8.3 Revision 0 HARLQN Licence Server MT RIP" to
version "9.0 Revision 0 HARLQN Licence Server MT RIP"
2.
If the utility is unable to determine the exact revision of a RIP installation, the utility will report
the difficulty and then continue without error.
3.
If you perform more than one migration to the same destination RIP, the log for the second and
subsequent migration session is added to the end of the log for the earlier migration.
4.
The messages consistently use the term migrating for stages that build the temporary newSW
folder, and merging for the stage where the utility modifies the RIP to which you are migrating.
CONTENTS
15
">