TRANSFERRING SETTINGS TO A NEW INSTALLATION
CONTENTS
3
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.
This document describes the migration to the Harlequin MultiRIP v10.0 (HMR) using Migrate v7.0r0.
1 Overview
The migration utility is a self‐contained, Java
an installed and used Harlequin RIP
™
‐based utility that transfers the majority of settings from
or Harlequin MultiRIP
™ to a freshly installed MultiRIP 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 5 for more details, including some limitations in this release.
The utility generally transfers page setups, including:
• RIP memory settings.
• Separations, screening, and color setups.
• 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—if the JobID in the old RIP is higher than the JobID in the new RIP, 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
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 migra‐ tion is performed, the valid password will be overwritten by
0
.
The migration utility also transfers:
• Harlequin plugins, and devices based on multiple‐device plugins, if not present in the new RIP.
Note: Plugins are not migrated when migrating from a 32‐bit to a 64‐bit RIP.
TRANSFERRING SETTINGS TO A NEW INSTALLATION
CONTENTS
4
• Some OEM plugins.
Note: If migrating a third‐party plugin, ensure that the plugin is installed into the destination RIP before migration. To complete the migration process create a page setup for the plugin in the des‐ tination 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 con‐ tains 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.
1.1 Folder structure
The utility is supplied with an appropriate runtime version of Java for Windows. The runtime version is the Java Runtime Environment (JRE). The JRE has its own documentation, including a license con‐ cerning its use: this documentation is in the jre
folder of the utility.
1.2 Document structure
The remainder of this document covers:
• Supported versions of the RIP—see
“Versions of the RIP” on page 4
.
•
Requirements—see “Requirements” on page 4 .
•
Limitations—see “Limitations” on page 5 .
•
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.
This document describes migration to HMR v10.0 from v8.1, v9.0rx, v2.0rx, v3.0rx.
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,
TRANSFERRING SETTINGS TO A NEW INSTALLATION
CONTENTS
5
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 tempo‐ rary files at the end of a migration, leaving only a log file of what was done.
You can run the utility by double‐clicking Migrate.exe which is located (by default):
C:\Users\<name>\HMR_10_0_Generic\migrate\SW_Migrate
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 implemen‐ tations and are outside our direct control.
4.1 Limitations in the utility
The migration utility does not transfer:
• 32‐bit plugins to 64‐bit RIPs (a warning dialog is displayed during the migration).
• Additional installed fonts. (The basic 32 fonts do transfer.)
• PDFR password.
• Memory settings return to default
• Page buffering returns to Multiple Parallel
• 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 TIFF/IT‐P1 RIP and wish to migrate to a
TIFF/IT‐P1 or later RIP, you must re‐import the profiles into the destination RIP. The Migrate util‐ ity 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
.
