LEXMARK DOCUMENT SOLUTIONS SUITE 3.3.8
Release Notes and Helpful Hints
System Requirements
The following are the recommended minimum RAM and disk requirements for Lexmark Document Solutions Suite v3.3.8 server and client installations:
A dedicated server with a minimum of 512MB RAM, 512MB free disk space for the server and 1GB free disk space for the database is recommended.
Print ‘N’ Send, Select ‘N’ Send and Workflow Composer have no additional system requirements beyond the operating system requirements.
Document Solutions Desktop client should have at least 128MB of RAM.
Forms Composer and Forms Manager installations require a minimum of 512MB RAM and 512 MB free disk space.
When installing on a Microsoft Server 2003 machine, ensure that the quota setting does not inhibit the LDSS installation.
Readme
These Release Notes will be used in place of the traditional readme file and Lexmark Technical Support Center concerns list.
Language Support
All Lexmark Document Solutions Suite software is available in English, French, Italian, German, Spanish, Brazilian Portuguese, Danish and Norwegian.
Platform Support
The table below shows the platform support details for each of the LDSS components:
Windows 98 SE Windows ME Windows 2000 Pro SP4 Windows 2000 Server SP4 Windows Server 2003 SE Windows Server 2003 SE SP1 Windows Server 2003 SE SP2 Windows XP Pro SP1 Windows XP Pro SP2 Document Distributor Server X X X X X Document Producer Server X X X X X Document Portal Server X X X X X
OCR X X X X X Bar Code X X X X X Document Distributor Server Manager X X X X X X X Print 'n' Send X X X X X Select 'n' Send X X X X X Workflow Composer X X X Forms Composer X X X Forms Manager X X X Data Transformer X X X X X Data Config X X X X X Data Composer X X X
Language Support
All Lexmark Document Solutions Suite software is available in English, French, Italian, German, Spanish, Brazilian Portuguese, Danish and Norwegian.
LDSS 3.3.8 New Features
New Device Support
New support for the following products: Lexmark C530, C532 and C534 Lexmark E450dn Lexmark C770 and C772 Lexmark X772e Lexmark C780 and C782 Lexmark X782e Lexmark C935
Lexmark X940e and X945e Lexmark X644e EC2 Lexmark X646e EC2 Lexmark X850e EC2 Lexmark X852e EC2 Lexmark X854e EC2 Lexmark X642e EC1
Optra Forms Intercept
Ability to Save Variable for Re-Use Floating Subforms
Greek & Cyrillic Monospace Font support Vertical Text Centering
Additional Finishing Support (Copies, Collate, Staple, Punch) – Job Profile
Forms Manager
Forms Manager Defrag Flash Updated Delete Printer Functions
Forms Composer/Producer/Distributor
Bubble Font (OMR)
Enhanced Page Delimiters
Support for PDF 1.6 Merged Output (3.3.7 supports 1.3) Updated Bar Code Engine to closely match Forms Card Control-P (Print) in Forms Composer Viewer
Forms Composer: Added Go to Page Options
Forms Composer: Select Line Spacing Type Via Radio Buttons Forms Composer: Speedup Startup/Font Dialogs
RFID Support
New Action Module to Secure PDFs
Updates to DataSet object (Remove page of data, Add page of data, Get list of all keys in a page, …)
Document Producer Sends DataSet to Printer Server performance improved for Uploading formset
Old: If 2500 formsets, 8 minutes to upload single New: If 2599 formsets,
4.62 minutes to upload existing 2.8 minutes to upload new Small file performance improvement Performance when adding device-improved Scan Settings Override
Updated OCR and Bar Code Engine Barcode Any command
IE7 for Windows, Firefox for Mac Server Monitor
Comment and Uncomment for Workflow Composer Workflow Composer prompts for local settings
LDSS 3.3.8 ISSUES
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 Service Pack 4 (LDSS 3.3.8).
Flushing Buffer message on Forms Card printers
When merging forms in 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 the 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 not currently supported on MFPs.
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 will cause the subform to float back to the top.
EAN_8_PLUS_2 Barcode Read is failing with 180 Degree Rotation
A rotation of 180 degrees from the initial vertical and horizontal positions of the barcode results in a read failure, even if the direction is set to LDD_BCDIR_ANY.
Server Monitor Settings
By default, the server monitor is disabled. If required, the user can enable it by configuring <LDD_Install_Dir>\Server\settings\sbmonitor.xml. Before performing any changes, please go through the instructions in the readme for the server monitor. The path of the readme could be: <LDD_Install_Dir>\Server\settings\sbmonitor.txt.
Forms Card DLE Issues
Data Stream Processing
The Forms Cards and Document Producer will process a data stream that contains pages that do not match any page activation conditions differently: Document Producer will ignore the page of data, but will continue to process the remaining pages of data as normal, while the Forms Card will begin to print just 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. Additionally, the time for the first merge page to print will extend since the printer must compare an increasing number of project activation conditions.
Cyrillic or Greek Characters with Forms Card
Most Microsoft Windows fonts include Cyrillic and Greek characters. This will allow 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 Unpredictable When Printer in Error State
While 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, it is required that the printer be deleted from the 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.” Therefore, it will be required to delete the printer and add it again.
Flash Code Updates
When installing updated code to a Forms Card the printer or MFP must have a minimum of 128MB of 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, crashing the printer, and other undesirable behaviors.
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 will exhibit the matching-data-stream-behavior.
When a filter of a certain type is activated and receives a data stream not of that type, it will exhibit the non-matching-data-stream-behavior.
Issue 2: Behavior for Multiple Streams
When a filter of a certain type is activated, it will process multiple, sequential data streams of that type, each according to the matching-data-stream-behavior. For example, if a filter of type A is activated and four streams are sent to it, then:
the filter will process stream one of type A data according to the matching-data-stream-behavior, then
the filter will process stream two of type A data according to the matching-data-stream-behavior, then
the filter will process stream three of type A data according to the matching-data-stream-behavior, then
the filter will process stream four of type A data according to the matching-data-stream-behavior, and so forth.
However, when a filter of a certain type is activated, if 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-stream-matching-data-stream-behavior. So, for example, if a filter of type A is activated and four streams are sent to it, then:
the filter will process stream one of type A data according to the matching-data-stream-behavior, then
the filter will process stream two of type B data according to the non-matching-data-stream-behavior, then
the filter will process stream three of type A data according to the matching-data-stream-behavior or the non-matching-data-stream-behavior, then
the filter will process stream four of type A data according to the matching-data-stream-behavior or the non-matching-data-stream-behavior, and so forth.
Lexmark and Lexmark with diamond design are trademarks of Lexmark International, Inc., registered in the United States and/or other countries.
Other trademarks are the property of their respective owners.
