beautypg.com

Before installing 1-18smzm.ps – Xerox DocuColor 242-252-260 con built-in Fiery controller-16185 User Manual

Page 3

background image

Page 3 of 4

Copyright 2010© Electronics for Imaging, INC.

Customer Support

Release note template v1.0

 1-14USY8: Tiff files are rotated 90 degrees when scanned to FTP/SMB
 1-14VEHT: Every page is offset when sending a single set of a Multi-page

job.

1-13LADE: Splash locks up when printing duplex imposed jobs with
settings for image shift on the back side

1-15B0TL Unable to access Configure from CWS5.

1-14M186: Cover is not pulled from Tray 3 when using VDP settings.

1-15GESI: Jobs with slip sheets printed in grayscale mode outputs different
results when printed more than once

1-15T653: Printing Word files using PS and/or PCL driver, outputs
horizontal white lines or streaks in the images.

1-15DWOL: Authenticated printing not working via LPR.

1-16OS6J: PDF outputs with banding on top of the page.

1-

16TZLT: Users can’t disable Port 9100 services in Fiery server set-up or

Configure.

1-178Q41: User can not clear close toner door error message.

1-170XJ5: The following symbols (3, &, +) are not printed correctly with
Composite Overprint Enabled.

1-187PSX: Configure doesn't launch when Java version 6 update 20 is
installed.

Before installing 1-18SMZM.ps

1. Known issues listed below, read before installing 1-18SMZM.ps patch:

This patch obsoletes all the above individual and composite patches.

The patch 1-RBQRL: to enable MSI popup must be installed over the composite
patch.

1-ZG4BK- Custom paper will not print to stacker tray with the D finisher. This
only works with the C-finisher. The behavior is working per the Finisher
specification.

2. 1-11FIR6: The fix for 1-11FIR6 was causing the LPR printing to fail when user

authentication was enabled, hence the second fix to revert it was provided in 1-
15DWOL.The assumption for first bug is incorrect, where the customer wants
username from DL to be overriding the username from PS file (%% EFFor).For
all our codebases we are trusting %EFFor more than what comes from
DL_openSession as %%EFFor is being generated by our driver. If the %%EFFor
is present in the PS file and is blank that will cause the username to be

This manual is related to the following products: