all support questions please contact Miralis Data at email@example.com
or call them on +44 (0)1524 68818. This page is provided for the benefit
The two page Installation Summary documents (PDF format) sent with all CD's can be accessed here:
The installation process uses the familiar Installshield / Windows MSI installer used by many applications and further details on this are available here. Normally the installation process will operate correctly with normal virus scanner settings, however we have had one occasion with Mcafee Viruscan on a server when access rights required the virus protection to be switched off during installation. Also on Citrix systems with re-mapped drives you may need to install on a local workstation and then copy to the Citrix server (a known Citrix Knowledge Centre issue with Microsoft Installer).
The other point of reference in the case of problems should be the appropriate user manual - especially Section 2 and Appendix 1 in both manuals (available below).
With all our products this is automatically installed with the software and is accessible from most screens within the applications. (Full manuals for all products can also be accessed here.) Networking issues are dealt with here.
Whilst we typically refer to (say) Version 5.7 of an application, in practice versions 5.70 / 5.71 / 5.72 etc will exist. Versions such as 5.70 and 5.71 are typically used for evaluation / trial versions whilst later numbers in the sequence (5.72, 5.73 etc) are used for release versions and updates to the same.
TRIAL systems are protected and restricted to 21 day operation and/or limited numbers of uses. They MUST be installed on the local drive of the pc. (Licensed systems can, of course, be installed locally or on a network). To run TRIAL systems occasionally administrator status is required.
Other PALLETMANAGER Issues:
Other CARGOMANAGER Issues:
System fails to Run.
If either PALLETMANAGER or CARGOMANAGER fails to run after operating correctly for some time then the most likely cause is a machine problem or file corruption. The following steps are recommended:
If Step 3 cures the problem then the problem may be with one of the user data files. A full list of these is given at the end of Section 2 of the respective manuals. Copying each of these to the temporary folder should help identify any invalid files.