LDSS is supported on all previously supported printers. In addition, support for the following new printers has been added in this release.

Transcription

1 LEXMARK DOCUMENT SOLUTIONS SUITE ReadMe for version OVERVIEW This ReadMe file pertains to the current release of the LEXMARK DOCUMENT SOLUTIONS SUITE for multifunction printers (MFPs) and single-function printers (SFPs). Lexmark Document Solutions Suite (LDSS) is a collection of software designed to increase the value of hard copy output while decreasing the cost of handling these documents. The suite is comprised of three core components: * Lexmark Document Distributor * Lexmark Document Producer * Lexmark Document Portal Lexmark Document Distributor (LDD) is a flexible document routing application that automates manual processes by giving users the power to scan, fax, copy, print, , or archive with the push of a button. Lexmark Document Producer is a server-based electronic forms solution that uses intelligent merge capabilities to merge electronic forms with host variable data. Merged forms can be sent out via , fax, ftp, or to an electronic archive. Lexmark Document Portal is a server-based electronic forms repository that stores forms in a print-on-demand system organized by document name. The forms can be accessed from a Lexmark touch-screen MFP or web-client interface. 2. SUPPORTED PRINTERS LDSS is supported on all previously supported printers. In addition, support for the following new printers has been added in this release. Document Distributor and Document Producer Multifunction Printers (MFPs) * X543, X544 * X651de, X652de, X654de, X656de, X658de * Note: These devices require firmware level LR.MN.P128 or later. Single-Function Printers (SFPs) * C540, C543, C544 * E260, E360, E460 * T650, T652, T654 Document Portal Multifunction Printers (MFPs) * X651de, X652de, X654de, X656de, X658de * Note: These devices require firmware level LR.MN.P128 or later. 3. REQUIREMENTS SYSTEM REQUIREMENTS Page: 1

2 The following are the recommended minimum RAM and disk requirements for LDSS server and client installations. a. A dedicated server with a minimum of 512MB RAM and 512MB free disk space for the server and 1GB free disk space for the database. b. Print'N'Send, Select'N'Send, and Workflow Composer have no additional system requirements beyond the operating system requirements. c. Document Solutions Desktop client should have at least 128MB RAM. d. Forms Composer and Forms Manager installations require a minimum of 1GB RAM and 1GB free disk space. Note: When installing on a Microsoft Server 2003 machine, ensure that the quota setting does not inhibit the LDSS installation. PLATFORM SUPPORT a. Document Distributor Server, Document Producer Server, Document Portal Server, OCR, Bar Code, Data Transformer, and Data Config * Windows 2000 Server SP4 * Windows Server 2003 SE SP1 * Windows Server 2003 SE SP2 b. Document Distributor Server Manager and Document Producer Server Manager * Windows 2000 Server SP4 * Windows Server 2003 SE SP1 * Windows Server 2003 SE SP2 * Windows XP Pro SP1 * Windows XP Pro SP2 c. Print'N'Send and Select'N'Send * Windows 98 SE * Windows ME * Windows XP Pro SP1 * Windows XP Pro SP2 d. Workflow Composer, Forms Composer, Forms Manager, and Data Composer * Windows XP Pro SP1 * Windows XP Pro SP2 4. PACKAGE CONTENTS The following file is included in the LDSS package. a. LDSS_3x_SP5.exe The LDSS service pack 5. INSTALLATION DETAILS To upgrade to LDSS 3.3.9, install the service pack directly on top of LDSS 3.3 and above. Upgrading directly from LDSS 3.2 or lower to LDSS is not supported. To upgrade Forms Composer and Forms Manager to version 3.3.9, install these components directly from the version of CD 8. The service pack is not Page: 2

3 required. 6. KEY FEATURES AND BENEFITS OF THE RELEASE Installation a. CD 8 installation (Forms Composer and Forms Manager) has been updated. Forms Manager a. Support for USB drives has been added. Forms Composer/Producer/Distributor a. A "Show Mapped Entry Name" feature has been added in Forms Composer. b. Copy and paste of variables on the data side has been enhanced in Forms Composer. c. Embedded fonts can be deleted more easily in Forms Composer's Properties. d. A time-out feature has been added to confirmation page printing. e. The ability to add multiple subforms at once has been added. f. In Server Manager, if a user loads a formset that already exists on the server, the user will be prompted to make sure they want to overwrite the existing formset. g. A pipe priority setting has been added. h. The name of the pipe has been added in the original object properties. i. Keywords are automatically populated in Document Portal. 7. LIMITATIONS AND COMPATIBILITY OF THE RELEASE LDSS Uninstall and Reinstall Considerations If you uninstall LDSS after applying a service pack and wish to reinstall any LDSS component, you must complete the following steps. 1. Install the desired LDSS component from the LDSS 3.3 CDs. 2. Install the desired LDSS component from the LDSS 3.3 CDs again. 3. Install the current service pack (LDSS 3.3.9). "Flushing Buffer" Message on Forms Card Printers When merging forms on a printer or MFP with a Forms Card, you may occasionally notice a "Flushing Buffer" message on the operator panel. This is not an error indicator. The message appears as a normal part of memory management performed by the Forms Card. Form Activation Conditions For activation conditions, spaces do not equal the number zero. Formset File Names Do not use any of the following characters as part of a variable name: #, $, &, [, ],, :,, <, >. These are special characters in the Forms Composer text editor and can cause problems if used in a variable name. Chinese form names are currently not supported on MFPs. Page: 3

4 Form Design Recommendation Do not place objects on top of subform objects. Design your form so that subforms are the top-level objects. You can temporarily send a subform to the back to work on other objects on the pages, but saving the formset causes the subform to float back to the top. Server Monitor Settings By default, the server monitor is disabled. If required, you can enable it by configuring <LDD_Install_Dir>\Server\settings\sbmonitor.xml. Before making any changes, please read the instructions in the ReadMe for the server monitor. The path of the ReadMe is: <LDD_Install_Dir>\Server\settings\sbmonitor.txt. Incorrect Compression Type for Scanned TIFF Image If a profile is created either with or without scan override options (color, paper type, etc.) and with TIFF file format and Packbits/LZW compression, the scan output from the device does not have the selected compression type. This issue occurs on the following devices with the following firmware levels. Device C772 with 4600 MFP X642e X644e, X646e X782e X850e, X852e, X854e X940e, X945e Firmware Level P283 P307b P261 P305a P450 P051 BAR CODE ISSUES EAN_8_PLUS_2 Bar Code Read Fails if Bar Code is Scanned Vertically When the EAN_8_PLUS_2 bar code is scanned vertically, the bar code engine fails to read the bar code. EAN_8_PLUS_2 Bar Code Read Fails if Bar Code is Rotated A rotation of 180 degrees from the initial vertical and horizontal positions of a bar code results in a read failure even if the direction is set to LDD_BCDIR_ANY. FORMS CARD DLE ISSUES Data Stream Processing The Forms Card and Document Producer each have different methods of processing data streams that contain pages that do not match any page activation conditions. Document Producer ignores the page of data, but continues to process the remaining pages of data normally. The Forms Card begins to print only the data for all remaining pages of data in that job. Slow Forms Card Response As more forms are added to a printer, the Forms Manager form display will begin to slow. In addition, the time for the first merge page to print will increase because the printer must compare an increasing number of project activation conditions. Page: 4

5 Cyrillic or Greek Characters with Forms Card Most Microsoft Windows fonts include Cyrillic and Greek characters. This enables merged forms to display correctly in Forms Composer with many different fonts. However, the only printer fonts that contain Cyrillic or Greek characters are CG-Times International, Courier International, ArialMT, TimesNewRomanPSMT, and Univers International. Printer Functions Are Unpredictable When Printer is in Error State When the printer is in an error state, the "Add Formsets," "Delete Formsets," and "Query Printer" functions respond unpredictably. Must Delete Printer from Forms Manager While Formatting Disk While formatting the disk or flash memory, you must delete the printer from Forms Manager. If this is not done, an error message may appear in Forms Manager indicating, No files were found on the device. Delete and add the printer to download required files. To avoid this error, delete the printer before formatting the disk, then add it again. Flash Code Updates For installations of updated code to a Forms Card, the printer must have a minimum of 128MB RAM. Filter Behavior For the Forms Card, there is no defined behavior when a filter receives data of a type that does not match the active filter. The device may crash, eject paper, or pass the data on unchanged. This could include the following issues. Definitions: * Matching-data-stream-behavior Transform the incoming data stream according to the definition of the active filter. * Non-matching-data-stream-behavior Pass the data stream on unchanged, corrupt the data and pass it on, flush the buffer, perform incorrect merges, print the raw or corrupt data stream, crash the printer, and other undesirable behavior. Issue 1: Behavior for a Single Stream When a filter of a certain type is activated and receives a data stream of that type, it exhibits the matching-data-stream-behavior. When a filter of a certain type is activated and receives a data stream not of that type, it exhibits the non-matching-data-stream-behavior. Issue 2: Behavior for Multiple Streams When a filter of a certain type is activated, it processes multiple, sequential data streams of that type, each according to the matching-datastream-behavior. For example, if a filter of type A is activated and four streams are sent to it, then: * The filter processes stream one of type A data according to the * The filter processes stream two of type A data according to the * The filter processes stream three of type A data according to the * The filter processes stream four of type A data according to the Page: 5

6 matching-data-stream-behavior, and so forth. However, when a filter of a certain type is activated and it receives a data stream not of that type, subsequent data streams of that type may be handled according to the matching-data-stream-behavior or non-matching-data-streambehavior. For example, if a filter of type A is activated and four streams are sent to it, then: * The filter processes stream one of type A data according to the * The filter processes stream two of type B data according to the non- * The filter processes stream three of type A data according to the matching-data-stream-behavior or the non-matching-data-stream-behavior, then * The filter processes stream four of type A data according to the matching-data-stream-behavior or the non-matching-data-stream-behavior, and so forth. For additional LDSS documentation, please see the Lexmark Document Solutions Suite v3.3 Publications web page: Page: 6