Home | Contact Us | Submit Troubleshooting Info | Search | Help


    Output | Software Solutions | Proofing | Color, Screening and Calibration | Scanning | Digital Photography | Consumables | POS


Trendsetter NEWS
MPE Controlled Release Version 1.1 (ECO CA03583, 04 Mar 2004)

Description | Fixes and Features | Install Time and Order | Workflow Compatibility

NOTE: You must install the version of Service Shell in this controlled release before downloading firmware in this controlled release.

Description

CR 1.1 upgrades TH 1.7 firmware to version 1.93, TH 2 firmware to version 1.04d, and Service Shell to version 2.5, build 770.

CD: 651-00118A (link to content of the CD on the master server)
Order this CD from CD.Requests@Creo.com.

Component

Version

Release Notes

Print Console 2.1.1 Release Notes
Service Shell 2.5.0 build 770 Service Shell 2.5, 2.5 SP1 Release Notes
Trendsetter NEWS MPE Firmware 1.16 Release Notes
TEH 1.7 firmware 1.93 Release Notes
TEH 1.7 Xilinx/LCA Firmware 1.05  
TH2 firmware 1.04d Release Notes

For general information about controlled releases, see the FAQ for Controlled Releases.

Major fixes and features

Time and Order to install and/or upgrade from previous release

Install in the order given. Total time - 1.75 hours (minimum)
For more information see the release notes for each component.

Task Time
  1. If the version of Service Shell (including build) is older than the version included in this Controlled Release CD, then install Service Shell from the Controlled Release CD.
10 minutes
  1. Go to the Patches folder on the Controlled Release CD and read the readme.txt file to find out if any patches or file upgrades (including new Service Shell scripts) are included and how to apply them. Normally, this will involve simply copying files from the Patches folder into other folders.
  1. Using Service Shell, run the "version checker" applet to create a log of the firmware and software version installed on the device. If you have applied the patches referred to in step 2, the version checker will successfully identify the correct versions of the different firmware and software.

    Note: Checking the version for the head LCA version will not work properly. The version that should be loaded onto the head should be version 1.03 or 2.00, depending on the head's hardware. Service shell version 2.4SP1 would report an error if either version is detected. Service shell version 2.5 detects these versions properly.

    Note: For CR 1.1, the "expected" version of Print Console is 2.1.4.9, and Version Checker lists earlier versions as Not Qualified. However, there is no need to upgrade Print Console if the existing version is between 2.1.1.24 and 2.1.4.9, inclusive. Therefore, if the existing version of Print Console is lower than 2.1.4.9, but higher than or equal to 2.1.1.24, select this component in the Version Checker and click Make Acceptable.
  1. Check the version of the digi driver and actual digi card (Multi-port serial adapter). Dell 2600 and Optiplex GX260 workstations should have the new digi card, identifiable by its small connector. The digi driver for these cards must be version 4.0.229.2. Do not use digi driverversion 3.10.0.189, as it will cause slow downloads. To verify the digi driver version, go to Computer Management\Device Manager\Multi-port serial adapters. To update the digi driver version, see the DigiDriver directory on the Controlled Release CD.
    The older style digi card is "Digi ClassicBoard 4 PCI," and the driver version is 1.1.0.0. Do not upgrade the driver on this type of board.
5 minutes
  1. Start Service Shell on the device server, and then select and run the FirmwareUpgrade script from the Devices script list.

    Make sure you have the controlled release CD in the CD-ROM (H drive) of the server. If you have applied the patches referred to in step 2, the script will automatically identify the correct locations of the firmware located on the CD.

    There is no need to copy the firmware files from the CD manually, as the script will perform this task. The files will be copied to the Service Shell Firmware folder by the script.

    Note: If the script fails to complete a particular download of a firmware component, you have the option of returning to the main menu and trying again (you do not have to exit the script and re-run it). Run the same script (FirmwareUpgrade), and it will automatically detect which modules were completed and attempt to load the ones that did not complete. There is no need to change your selections, as the script will automatically detect where it left off.
1 hour
  1. Check that device and all applications are functional, including load/unload of small/medium/large size media.
15 minutes
  1. Demo and provide instructions on changes to customers.
15 minutes

Workflow Compatibility

Workflow items are not part of the release, but have been tested for compatibility.


    Copyright © 2005 Creo Inc. All rights reserved. Confidential. Back to top.