Upload
others
View
21
Download
0
Embed Size (px)
Citation preview
GMSSC-GTS-091-0016
Issued: July 27th, 2009
FDv4 core based PS driver
customization
Document Version 1.0
Global Technology Support Section
Overseas Technical Support Department,
Service Support Center
Global Marketing Group
FDv4 core based PS driver customization GMSSC-GTS-091-0016
2/42 Ricoh Company, Ltd.
Notice:
THIS DOCUMENT MAY NOT BE REPRODUCED OR DISTRIBUTED IN WHOLE OR IN PART, FOR ANY
PURPOSE OR IN ANY FASHION WITHOUT THE PRIOR WRITTEN CONSENT OF RICOH COMPANY
LIMITED. RICOH COMPANY LIMITED RETAINS THE SOLE DISCRETION TO GRANT OR DENY
CONSENT TO ANY PERSON OR PARTY.
Copyright © 2009 by Ricoh Company Ltd.
All product names, domain names or product illustrations, including desktop images, used in this document
are trademarks, registered trademarks or the property of their respective companies. They are used
throughout this book in an informational or editorial fashion only. Ricoh Company, Ltd. does not grant or
intend to grant hereby any right to such trademarks or property to any third parties. The use of any trade
name or web site is not intended to convey endorsement or any other affiliation with Ricoh products.
Although best efforts were made to prepare this document, Ricoh Company Limited makes no representation
or warranties of any kind with regards to the completeness or accuracy of the contents and accepts no liability
of any kind including but not limited to performance, merchantability, fitness for any particular purpose, or any
losses or damages of any kind caused or alleged to be caused directly or indirectly from this document.
Version history:
Version Issue Date Revised item
1.0 Jul. 27, 2009 1st release
FDv4 core based PS driver customization GMSSC-GTS-091-0016
3/42 Ricoh Company, Ltd.
Index
1. Introduction ................................................................................ 4
2. Target readers............................................................................ 5
3. Requirements............................................................................. 5
4. Introduction to XML.................................................................... 6
4-1. General explanation ........................................................................... 6
5. Modifying the MOX file .............................................................. 8
5-1. Structure of the MOX file .................................................................... 8
5-2. Before and after the modification ..................................................... 10
5-3. The PS driver for Universal Print’s MOX file..................................... 12
5-4. Change the default driver settings.................................................... 18
5-5. Lock/Limit driver settings.................................................................. 23
5-6. Delete one click icons....................................................................... 28
6. Modifying the PPD file ............................................................. 31
6-1. Before and after the modification ..................................................... 31
6-2. Change the default driver settings.................................................... 33
7. Customizing PS driver for Universal Print ............................... 35
7-1. Change the default UI ...................................................................... 35
8. Installation of the customized driver ........................................ 39
9. Appendix .................................................................................. 41
9-1. How to distinguish whether a driver has been customized or not..... 41
9-2. How to determine whether FDv4 core is used by a PS driver .......... 42
FDv4 core based PS driver customization GMSSC-GTS-091-0016
4/42 Ricoh Company, Ltd.
1. Introduction
This document describes procedures for the following customizations of the FDv4 core based PS driver:
General customizations:
- Change the default driver settings
- Lock/Limit driver settings
- Delete one click icons
Customizations that only apply to the PS driver for Universal Print:
- Change the default UI
These customizations can be done by manually editing a MOX file (.mox), a PPD file (.ppd) or an XML file
(.xml) in a driver package. The contents of MOX and XML files are XML (Extensible Markup Language)
formatted. However, only a limited understanding of XML is required. Section 4 “Introduction to XML” is a
basic introduction to XML. It should provide enough information for the customizations in this document.
Note1: "FDv4" is the plug-in architecture used by some of our PS drivers. Though we refer to these drivers as
being "FDv4 core based", they are in fact based on the Microsoft "pscript5" core.
Note2: Customized drivers are to be released at your own risk. Please test them thoroughly and keep track of
where you have deployed the customized drivers. If a problem happens using a customized driver, please
test the standard driver. If the problem also affects the standard driver, please report it as a standard driver
problem.
Note3: The customization will cause the driver to lose its Microsoft logo certification. Therefore, an alert
message might be displayed during installation.
FDv4 core based PS driver customization GMSSC-GTS-091-0016
5/42 Ricoh Company, Ltd.
2. Target readers
This document is intended for the support staff of Ricoh family group companies and their subsidiaries. Do
not distribute to anyone else.
3. Requirements
Printer Driver:
This document applies only to FDv4 core PS drivers. Currently available FDv4 core based PS drivers (as of
July 27th, 2009):
- PS3 driver for Model S-C4
- PS driver for Universal Print
Reference: Section 9-2 “How to determine whether FDv4 core is used by a PS driver”
Others:
- Text Editor or an XML Editor.
FDv4 core based PS driver customization GMSSC-GTS-091-0016
6/42 Ricoh Company, Ltd.
4. Introduction to XML
4-1. General explanation
Overview:
XML (Extensible Markup Language) defines a general text-based method of organizing data. A data object in
the XML specification is called an XML document. XML does not specifically define how an application should
process XML documents.
XML is standardized by the World Wide Web Consortium (W3C).
W3C web site: http://www.w3.org/XML/
Official XML specifications are available at the W3C site, but there are plenty of other easy to follow XML
tutorials on the Internet. To follow are some terms that will be used throughout this document. Please
familiarize yourself with them.
Element and tags:
An XML document is composed of a basic unit called an element. To distinguish each element, HTML-like
tags are used:
Start-tag: <element>
End-tag: </element>
Element contents are contained between these tags.
Example:
<memo>This is a pen.</memo>
Hierarchy:
One of the main features of XML is that data is organized into a hierarchical tree structure.
Example of an XML document:
<memo>
<date> 4/21/2008 </date>
<author>
<id> 0001 </id>
<name> John Doe </name>
</author>
<titile> Pen </title>
<text> This is a pen.</text>
</memo>
Note: Spaces or tabs input in front of the start-tags are not mandatory, but are sometimes inserted
FDv4 core based PS driver customization GMSSC-GTS-091-0016
7/42 Ricoh Company, Ltd.
automatically by XML editors or manually by authors to make the file easy to read in a text editor.
Tree structure of the above example:
The element at the root of the tree is called the root element. There is only 1 root element in an XML
document. In this example, “memo” is the root element. All other elements are children of “memo” and
“memo” is the parent of all elements. “author” is both a child of “memo” and a parent of “id” and “name.
Attribute:
Attributes are additional information about elements. Elements can have multiple attributes in the start-tag.
Example:
<memo security=”low”> This is a pen.</memo>
In this example, “security” is the attribute of the element “memo”. “low” is the value of the attribute.
Empty element:
In XML documents, there can be elements that do not have any content or child elements. Such an element is
called an empty element. The start-tag and end-tag are not necessary for empty elements. A special tag
called an empty-element tag such as below can be used:
Empty-element tag: <element/>
Example:
<memo/>
memo
date author title text
id name content content content
content content
root element
FDv4 core based PS driver customization GMSSC-GTS-091-0016
8/42 Ricoh Company, Ltd.
5. Modifying the MOX file
Modification of a MOX file can be used to perform the following customizations:
- Change the default driver settings (section 5-4)
- Lock/Limit driver settings to certain values (section 5-5)
- Delete one click icons (section 5-6)
5-1. Structure of the MOX file
The root element of the MOX file is ”printer”. Usually, there are 7 child elements directly under “printer”. The
following diagram shows the 7 elements and their children.
Structure of the MOX file:
Elements that will be involved in our customizations are shown in blue above. Specifically, the following
root element
printer
DriverSpecPPD
DriverSpecPScript5
DriverSpecPlugin
DefaultSettings
LayoutSettings
OneClickIconSettings
LimitationSettings
configuration
defaults
configuration
defaults
configuration
defaults
FactoryOCItem
FactoryOCItem
FDv4 core based PS driver customization GMSSC-GTS-091-0016
9/42 Ricoh Company, Ltd.
elements will be used in the following customizations:
“DefaultSettings” element: Section 5-4 “Change the default driver settings”
“LimitationSettings” and “DefaultSettings” elements: Section 5-5 “Lock/Limit driver settings”
“FactoryOCItem” element: Section 5-6 “Delete one click icons”
FDv4 core based PS driver customization GMSSC-GTS-091-0016
10/42 Ricoh Company, Ltd.
5-2. Before and after the modification
Before the modification:
Prepare a set of driver files and locate the file(s) with the extension “.mo_”. A “.mo_” file is a compressed
MOX file. There might be several of these files.
Note: The PS driver for Universal Print has a lot of “.mo_” files. Please refer to section 5-3 “The PS driver for
Universal Print’s MOX file” for more information.
Decompress the “.mo_” file(s) using the expand command from a command prompt: expand -r file path
After the decompression, remove the compressed file from the driver package.
Note: If customizing version 1.0.0 of PS driver for Model S-C4, the decompressed file’s extension will be
“.mo”. Please rename it “.mox”.
If there is more than one MOX file, you have to find and modify the MOX file for the target model(s). Each
MOX file will list the model for which it is intended. This can be seen in the “printer” element.
“printer” element:
Decompress the file.
Delete this file after decompression.
FDv4 core based PS driver customization GMSSC-GTS-091-0016
11/42 Ricoh Company, Ltd.
If you modify a MOX file, please add a comment to the file and the suffix ‘c’ to the version number. This will
serve as a reminder to you or others that the file was modified, and what the purpose of the modification was.
Comments can be added under the XML declaration using the following format:
<!-- comment -->
MOX file with comments and a modified version number:
After the modification:
Save the modified file back to its original location.
For information about the installation of the customized driver, refer to section 8 “Installation of the
customized driver”.
FDv4 core based PS driver customization GMSSC-GTS-091-0016
12/42 Ricoh Company, Ltd.
5-3. The PS driver for Universal Print’s MOX file
The PS driver for Universal Print contains a separate MOX file for each model and brand (see Table 5-3-1
and 5-3-2). Unfortunately the MOX file names are not entirely comprehensive. So in order to find the MOX file
for a particular model, you might need to open individual files and look at the “printer” element.
“printer” element:
Table 5-3-1. MOX file list - MFP (PS driver for Universal Print v.1.20.00)
Model Brand Product Name MOX file name
MP3500/DSm735e gs1331e3ud.mox Gestetner
MP4500/DSm745e gs1332e3ud.mox
IS 2435 if1331e3ud.mox infotec
IS 2445 if1332e3ud.mox
MP 3500/LD335 ln1331e3ud.mox Lanier
MP 4500/LD345 ln1332e3ud.mox
MP 3500 nr1331e3ud.mox NRG
MP 4500 nr1332e3ud.mox
Aficio MP 3500 ri1331e3ud.mox Ricoh
Aficio MP 4500 ri1332e3ud.mox
8035e sv1331e3ud.mox
A-C4.5
Savin 8045e sv1332e3ud.mox
MP 4000 gs1401e3ud.mox
MP 4000B gs1402e3ud.mox
MP 5000 gs1403e3ud.mox Gestetner/NRG/infotec
MP 5000B gs1404e3ud.mox
MP 4000/LD040 ln1401e3ud.mox
MP 4000B/LD040B ln1402e3ud.mox
MP 5000/LD050 ln1403e3ud.mox Lanier
MP 5000B/LD050B ln1404e3ud.mox
AL-C1
Ricoh Aficio MP 4000 ri1401e3ud.mox
FDv4 core based PS driver customization GMSSC-GTS-091-0016
13/42 Ricoh Company, Ltd.
Aficio MP 4000B ri1402e3ud.mox
Aficio MP 5000 ri1403e3ud.mox
Aficio MP 5000B ri1404e3ud.mox
9040 sv1401e3ud.mox
9040b sv1402e3ud.mox
9050 sv1403e3ud.mox Savin
9050b sv1404e3ud.mox
MPC3500/DSc535 gs3171e3ud.mox Gestetner
MPC4500/DSc545 gs3172e3ud.mox
ISC 3535 if3171e3ud.mox infotec
ISC 4045 if3172e3ud.mox
MP C3500/LD435c ln3171e3ud.mox Lanier
MP C4500/LD445c ln3172e3ud.mox
MP C3500 nr3171e3ud.mox NRG
MP C4500 nr3172e3ud.mox
Aficio MP C3500 raf42353ud.mox Ricoh
Aficio MP C4500 raf42453ud.mox
C3535 sv3171e3ud.mox
AP-C1
Savin C4540 sv3172e3ud.mox
MP C4000 gs3221e3ud.mox Gestetner/NRG/infotec
MP C5000 gs3222e3ud.mox
MP C4000/LD540C ln3221e3ud.mox Lanier
MP C5000/LD550C ln3222e3ud.mox
Aficio MP C4000 ri3221e3ud.mox Ricoh
Aficio MP C5000 ri3222e3ud.mox
C4040 sv3221e3ud.mox
AP-C2
Savin C5050 sv3222e3ud.mox
MPC2000/DSc520 gempc203ud.mox
MPC2500/DSc525 gempc253ud.mox Gestetner
MPC3000/DSc530 gempc303ud.mox
ISC 2020 inisc203ud.mox
ISC 2525 inisc253ud.mox infotec
ISC 3030 inisc303ud.mox
MP C2000/LD420c lampc203ud.mox
MP C2500/LD425c lampc253ud.mox Lanier
MP C3000/LD430c lampc303ud.mox
MP C2000 nrmpc203ud.mox
MP C2500 nrmpc253ud.mox NRG
MP C3000 nrmpc303ud.mox
Aficio MP C2000 raf42203ud.mox
Aficio MP C2500 raf42253ud.mox
AT-C1
Ricoh
Aficio MP C3000 raf42303ud.mox
FDv4 core based PS driver customization GMSSC-GTS-091-0016
14/42 Ricoh Company, Ltd.
C2020 sac20203ud.mox
C2525 sac25253ud.mox Savin
C3030 sac30303ud.mox
MP C2800 gs3231e3ud.mox Gestetner/NRG/infotec
MP C3300 gs3232e3ud.mox
MP C2800/LD528C ln3231e3ud.mox Lanier
MP C3300/LD533C ln3232e3ud.mox
Aficio MP C2800 ri3231e3ud.mox Ricoh
Aficio MP C3300 ri3232e3ud.mox
C2828 sv3231e3ud.mox
AT-C2
Savin C3333 sv3232e3ud.mox
MP C2050 gs3261e3ud.mox Gestetner/NRG/infotec
MP C2550 gs3262e3ud.mox
MP C2050/LD520C ln3261e3ud.mox Lanier
MP C2550/LD525C ln3262e3ud.mox
Aficio MP C2050 ri3261e3ud.mox Ricoh
Aficio MP C2550 ri3262e3ud.mox
C9020 sv3261e3ud.mox
DI-C1
Savin C9025 sv3262e3ud.mox
MP1600/DSm716 ge1311e3ud.mox Gestetner
MP2000/DSm721d ge1312e3ud.mox
IS 2316 in1311e3ud.mox infotec
IS 2320 in1312e3ud.mox
MP 1600/LD316 la1311e3ud.mox Lanier
MP 2000/LD320d la1312e3ud.mox
MP 1600 nr1311e3ud.mox NRG
MP 2000 nr1312e3ud.mox
Aficio MP 1600 rc1311e3ud.mox Ricoh
Aficio MP 2000 rc1312e3ud.mox
9016 sa1311e3ud.mox
K-C3
Savin 9021d sa1312e3ud.mox
MP 2510/DSm725e gs1341e3ud.mox Gestetner
MP 3010/DSm730e gs1342e3ud.mox
IS 2425 if1341e3ud.mox infotec
IS 2430 if1342e3ud.mox
MP 2510/LD325 ln1341e3ud.mox Lanier
MP 3010/LD330 ln1342e3ud.mox
MP 2510 nr1341e3ud.mox NRG
MP 3010 nr1342e3ud.mox
Aficio MP 2510 ri1341e3ud.mox Ricoh
Aficio MP 3010 ri1342e3ud.mox
R-C4.5
Savin 8025e sa1341e3ud.mox
FDv4 core based PS driver customization GMSSC-GTS-091-0016
15/42 Ricoh Company, Ltd.
8030e sa1342e3ud.mox
MP 2550 gs1391e3ud.mox
MP 2550B gs1392e3ud.mox
MP 3350 gs1393e3ud.mox Gestetner/NRG/infotec
MP 3350B gs1394e3ud.mox
MP 2550/LD425 ln1391e3ud.mox
MP 2550B/LD425B ln1392e3ud.mox
MP 3350/LD433 ln1393e3ud.mox Lanier
MP 3350B/LD433B ln1394e3ud.mox
Aficio MP 2550 ri1391e3ud.mox
Aficio MP 2550B ri1392e3ud.mox
Aficio MP 3350 ri1393e3ud.mox Ricoh
Aficio MP 3350B ri1394e3ud.mox
9025 sv1391e3ud.mox
9025b sv1392e3ud.mox
9033 sv1393e3ud.mox
R-C5
Savin
9033b sv1394e3ud.mox
Gestetner MP 161/DSm416 gs1321e3ud.mox
infotec IS 2416 if1321e3ud.mox
Lanier MP 161/LD016 ln1321e3ud.mox
NRG MP 161 nr1321e3ud.mox
Ricoh Aficio MP 161 ri1321e3ud.mox
S-C3
Savin 816 sv1321e3ud.mox
Gestetner/NRG/infotec MP 171 gs1461e3ud.mox
Lanier MP 171/LD 117 ln1461e3ud.mox
Ricoh Aficio MP 171 ri1461e3ud.mox S-C4
Savin 917 sv1461e3ud.mox
MP C6000 gs3201e3ud.mox Gestetner/NRG/infotec
MP C7500 gs3202e3ud.mox
MP C6000/LD260c ln3201e3ud.mox Lanier
MP C7500/LD275c ln3202e3ud.mox
Aficio MP C6000 ri3201e3ud.mox Ricoh
Aficio MP C7500 ri3202e3ud.mox
C6055 sv3201e3ud.mox
V-C2
Savin C7570 sv3202e3ud.mox
Table 5-3-2. MOX file list - LP (PS driver for Universal Print v.1.20.00)
Model Brand Product Name MOX file name
Gestetner/NRG SP 8200DN gs2221e3ud.mox
Lanier LP150dn/SP8200DN ln2221e3ud.mox
AL-P1
Ricoh Aficio SP 8200DN ri2221e3ud.mox
FDv4 core based PS driver customization GMSSC-GTS-091-0016
16/42 Ricoh Company, Ltd.
Savin MLP150DN sv2221e3ud.mox
C8140ND gs4241e3ud.mox Gestetner
C8150ND gs4242e3ud.mox
LP540C/SPC820DN ln4241e3ud.mox Lanier
LP550C/SPC821DN ln4242e3ud.mox
SP C820DN nr4241e3ud.mox NRG
SP C821DN nr4242e3ud.mox
Aficio SP C820DN ri4241e3ud.mox Ricoh
Aficio SP C821DN ri4242e3ud.mox
CLP340D sv4241e3ud.mox
AP-P2
Savin CLP350D sv4242e3ud.mox
Gestetner/NRG C7521n gec75213ud.mox
Lanier LP222cn/LP221c lalp2223ud.mox
Ricoh Aficio CL3500N riaf3503ud.mox AR-P2
Savin CLP22 saclp223ud.mox
C7526dn gs4171e3ud.mox Gestetner
C7531dn gs4172e3ud.mox
IPC 2525DN if4171e3ud.mox infotec
IPC 3030DN if4172e3ud.mox
LP226c/SP C410 ln4171e3ud.mox Lanier
LP231c/SP C411 ln4172e3ud.mox
SP C410DN ng4171e3ud.mox NRG
SP C411DN ng4172e3ud.mox
Aficio SP C410DN rc4171e3ud.mox Ricoh
Aficio SP C411DN rc4172e3ud.mox
CLP27DN sv4171e3ud.mox
G-P2
Savin CLP31DN sv4172e3ud.mox
Lanier/Savin SP C400DN ln4231e3ud.mox G-P2L
Ricoh Aficio SP C400DN rc4231e3ud.mox
Gestetner/NRG SP C420DN gs4221e3ud.mox
Lanier LP331cn/SP C420 ln4221e3ud.mox
Ricoh Aficio SP C420DN ri4221e3ud.mox G-P3
Savin CLP131DN sv4221e3ud.mox
Gestetner/NRG C7528n gec75283ud.mox
Gestetner C7535n gec75353ud.mox
IPC 2832 ini28323ud.mox infotec
IPC 3535e ini35353ud.mox
LP332c lalp3323ud.mox Lanier
LP335c lalp3353ud.mox
NRG C7535hdn nrc75353ud.mox
Aficio CL7200 ricl7203ud.mox
J-P4
Ricoh Aficio CL7300 ricl7303ud.mox
FDv4 core based PS driver customization GMSSC-GTS-091-0016
17/42 Ricoh Company, Ltd.
CLP128 saclp283ud.mox Savin
CLP135 saclp353ud.mox
Gestetner/NRG P7535n ges75353ud.mox
Lanier LP135n lanp1353ud.mox
Ricoh Aficio AP610N riap6103ud.mox K-P4
Savin MLP35n savlp353ud.mox
Gestetner/NRG/Lanier SP 4210N gs2241e3ud.mox
Lanier LP37N ln2241e3ud.mox
Ricoh Aficio SP 4210N ri2241e3ud.mox SI-P2
Savin MLP37N sv2241e3ud.mox
Note: Using the PS driver for Universal Print, the wrong (unedited) MOX file could be applied to the driver.
This could happen in the following cases:
- The driver uses bi-directional communication and decides that the connected printer is not the model that
the customizations were made for.
- A model that the driver was not customized for is manually selected from the “Select a Printer” drop-down
list in the driver’s Printer Selection tab.
“Select a Printer” drop-down list in the PS driver for Universal Print:
FDv4 core based PS driver customization GMSSC-GTS-091-0016
18/42 Ricoh Company, Ltd.
5-4. Change the default driver settings
This customization changes the default values of driver settings. The values that are restored by the Restore
Defaults buttons are also changed.
In some cases, modification of a PPD file is also required. It is mentioned later in customization examples if
necessary.
Changing the default driver settings:
root element
printer
DriverSpecPPD
DriverSpecPScript5
DriverSpecPlugin
DefaultSettings
LayoutSettings
OneClickIconSettings
LimitationSettings
configuration
defaults
configuration
defaults
configuration
defaults
FactoryOCItem
FactoryOCItem
Add child element(s).
Used as a reference.
FDv4 core based PS driver customization GMSSC-GTS-091-0016
19/42 Ricoh Company, Ltd.
5-4-1. Syntax used to define the default driver settings
:
<DefaultSettings>
<default id="feature id" opid="option opid"/>
</DefaultSettings>
:
Gray text: Original contents of the MOX file.
Black text: Added manually.
feature id: The name of a setting.
option opid: The value of a setting.
The value specified by “option opid” will become the default value of the setting specified by “feature id”.
These settings names and values are defined in the “DriverSpecPPD”, “DriverSpecPScript5”, and
“DriverSpecPlugin” elements. To follow is an example:
:
<DriverSpecPPD>
<configuration>
<feature id="…" type="…">
:
</feature>
:
<feature id="ColorModel" type="PickOne">
<option opid="CMYK"/>
<option opid="Gray"/>
</feature>
:
</configuration>
<defaults>
<default id="…" opid="…"/>
:
<default id="ColorModel" opid="CMYK"/>
:
</defaults>
:
</DriverSpecPPD>
:
“ColorModel” represents the Color Mode setting. There are 2 options for the Color Mode setting; “CMYK”
(Color) and “Gray” (Black and White). The default is “CMYK” (Color).
FDv4 core based PS driver customization GMSSC-GTS-091-0016
20/42 Ricoh Company, Ltd.
Note1: Setting or option names in the MOX file are not necessarily the same as the names shown in the
driver UI.
Note2: Do not edit “feature”, ”option” or “default” elements. Make changes only to the “DefaultSettings”
element.
5-4-2. Customization examples
Note: Contents of the MOX file are case-sensitive.
Example 5-4-1. Make “Black and White” default
:
<DefaultSettings>
<default id="ColorModel" opid="Gray"/>
</DefaultSettings>
:
Note: This customization will not take effect until the driver UI is opened. Alternatively the effects of the
customization can be forced by making changes to the PPD file. For details, refer to section 6 “Modifying the
PPD file” and Example 6-2-1.
Example 5-4-2. Make duplex default
:
<DefaultSettings>
<default id="Duplex" opid="DuplexNoTumble"/>
</DefaultSettings>
:
Note1:
DuplexNoTumble = “Long Edge” binding
DuplexTumble = “Short Edge” binding
Note2: This customization will not take effect until the driver UI is opened. Alternatively the effects of the
customization can be forced by making changes to the PPD file. For details, refer to section 6 “Modifying the
PPD file” and Example 6-2-2.
Example 5-4-3. Make “Black and White” and duplex default
:
<DefaultSettings>
<default id="ColorModel" opid="Gray"/>
<default id="Duplex" opid="DuplexNoTumble"/>
</DefaultSettings>
FDv4 core based PS driver customization GMSSC-GTS-091-0016
21/42 Ricoh Company, Ltd.
:
Note1
DuplexNoTumble = “Long Edge” binding
DuplexTumble = “Short Edge” binding
Note2: This customization will not take effect until the driver UI is opened. Alternatively the effects of the
customization can be forced by making changes to the PPD file. For details, refer to section 6 “Modifying the
PPD file”, Example 6-2-1 and 6-2-2.
Example 5-4-4. Make 2 pages per sheet default
:
<DefaultSettings>
<default id="%PagePerSheet" opid="2"/>
</DefaultSettings>
:
Note: This customization will not take effect until the driver UI is opened. There is no way to avoid this.
Example 5-4-5. Make “Locked Print” default
:
<DefaultSettings>
<default id="pdmJCJobType" opid="Secure"/>
<default id="UIJobType" opid="Secure"/>
</DefaultSettings>
:
Note: A job will be printed as a Normal Print job until the User ID and Password are manually configured by
the user.
5-4-3. Notes on the customization “Change the default driver settings”
Note1: We are only able to change the defaults of settings that have been defined in the “DriverSpecPPD”,
“DriverSpecPScript5”, or “DriverSpecPlugin” elements using the “feature” child element. Even some settings
that do meet these criteria cannot be customized. These include:
- Paper Size
- Installable Options
Default installable options can be changed by modifying the PPD file. For details, refer to section 6 “Modifying
the PPD file”. (Exception: There is no way to change the default installable options of the PS driver for
Universal Print.)
FDv4 core based PS driver customization GMSSC-GTS-091-0016
22/42 Ricoh Company, Ltd.
Note2: After changing defaults, some of the one click icons might be redundant. To delete unnecessary one
click icons, refer to section 5-6 “Delete one click icons”.
For example, after making duplex default, the “Basic Setting” and “2 sided” icons have the same settings:
Note3: Some settings require that specific accessories (Installable Options) be configured. For example, a
duplex unit is required to print in duplex. If you are customizing a driver of a model that has a duplex unit as
an option, and if you want the Duplex setting to be ”Long Edge” by default, you have to customize the driver
so that duplex unit is configured by default and the Duplex setting is default to “Long Edge”. The duplex unit
would have to be installed by editing the PPD file. Please see section 6 “Modifying the PPD file” and Example
6-2-3 for further details.
FDv4 core based PS driver customization GMSSC-GTS-091-0016
23/42 Ricoh Company, Ltd.
5-5. Lock/Limit driver settings
This customization locks driver settings to specific values or limits which settings are available.
Locking/Limiting driver settings:
root element
printer
DriverSpecPPD
DriverSpecPScript5
DriverSpecPlugin
DefaultSettings
LayoutSettings
OneClickIconSettings
LimitationSettings
configuration
defaults
configuration
defaults
configuration
defaults
FactoryOCItem
FactoryOCItem
Used as a reference.
Add child elements.
Add child element(s) in some cases.
FDv4 core based PS driver customization GMSSC-GTS-091-0016
24/42 Ricoh Company, Ltd.
5-5-1. Syntax used to lock/limit driver settings
:
<LimitationSettings>
<feature id="feature id">
<option opid="option opid"/>
:
</feature>
</LimitationSettings>
:
Gray text: Original contents of the MOX file.
Black text: Added manually.
feature id: The name of a setting.
option opid: The value of a setting.
The value specified by “option opid” will be removed from the drop-down list of the setting specified by
“feature id”. These settings names and values are defined in the “DriverSpecPPD”, “DriverSpecPScript5”, and
“DriverSpecPlugin” elements. Refer to section 5-4-1 “Syntax used to define the default driver settings” for
details.
Important Note:
If you want to remove a default option from a drop-down list, you must change the default to another option,
otherwise the setting will not be locked or limited. To change the default, refer to section 5-4 “Change the
default driver settings”. Customization examples in the next section change default settings when necessary.
5-5-2. Customization examples
Note: Contents of the MOX file are case-sensitive.
Example 5-5-1. Lock the Color Mode setting to “Black and White”
:
<DefaultSettings>
<default id="ColorModel" opid="Gray"/>
</DefaultSettings>
<LimitationSettings>
<feature id="ColorModel">
<option opid="Color"/>
</feature>
</LimitationSettings>
:
FDv4 core based PS driver customization GMSSC-GTS-091-0016
25/42 Ricoh Company, Ltd.
Note: This customization will not take effect until the driver UI is opened. Alternatively the effects of the
customization can be forced by making changes to the PPD file. For details, refer to section 6 “Modifying the
PPD file” and Example 6-2-1.
Example 5-5-2. Remove “Off” from the Duplex setting
:
<DefaultSettings>
<default id="Duplex" opid="DuplexNoTumble"/>
</DefaultSettings>
<LimitationSettings>
<feature id="Duplex">
<option opid="None"/>
</feature>
</LimitationSettings>
:
Note1:
DuplexNoTumble = “Long Edge” binding
DuplexTumble = “Short Edge” binding
Note2: This customization will not take effect until the driver UI is opened. Alternatively the effects of the
customization can be forced by making changes to the PPD file. For details, refer to section 6 “Modifying the
PPD file” and Example 6-2-2.
Example 5-5-3. Remove “1” from the Pages per Sheet setting
:
<DefaultSettings>
<default id="%PagePerSheet" opid="2"/>
</DefaultSettings>
<LimitationSettings>
<feature id="%PagePerSheet">
<option opid="1"/>
</feature>
</LimitationSettings>
:
Note: This customization will not take effect until the driver UI is opened. There is no way to avoid this.
Example 5-5-4. Lock the Job Type setting to “Locked Print”
:
FDv4 core based PS driver customization GMSSC-GTS-091-0016
26/42 Ricoh Company, Ltd.
<DefaultSettings>
<default id="pdmJCJobType" opid="Secure"/>
<default id="UIJobType" opid="Secure"/>
</DefaultSettings>
<LimitationSettings>
<feature id="pdmJCJobType">
<option opid="Normal"/>
<option opid="Sample"/>
<option opid="Hold"/>
<option opid="Stored"/>
<option opid="StoreAndPrint"/>
<option opid="DocumentBox"/>
</feature>
<feature id="UIJobType">
<option opid="Normal"/>
<option opid="Sample"/>
<option opid="Hold"/>
<option opid="Stored"/>
<option opid="StoreAndPrint"/>
<option opid="DocumentBox"/>
</feature>
</LimitationSettings>
:
Note: A job will be printed as a Normal Print job until the User ID and Password are manually configured by
the user.
Example 5-5-5. Include only “Normal Print” and “Locked Print” in the Job Type drop-down list
:
<LimitationSettings>
<feature id="pdmJCJobType">
<option opid="Sample"/>
<option opid="Hold"/>
<option opid="Stored"/>
<option opid="StoreAndPrint"/>
<option opid="DocumentBox"/>
</feature>
<feature id="UIJobType">
<option opid="Sample"/>
<option opid="Hold"/>
<option opid="Stored"/>
<option opid="StoreAndPrint"/>
FDv4 core based PS driver customization GMSSC-GTS-091-0016
27/42 Ricoh Company, Ltd.
<option opid="DocumentBox"/>
</feature>
</LimitationSettings>
:
5-5-3. Notes on the customization “Lock/Limit driver settings”
Note1: Some settings require that specific accessories (Installable Options) be configured. For example, a
duplex unit is required to print in duplex. If you are customizing a driver of a model that has a duplex unit as
an option, and if you want the Duplex setting to be locked on, you have to customize the driver so that the
duplex unit is configured by default and the Duplex setting is locked on. To perform this customization, a
combination of the “Change the default driver settings” and “Lock/Limit driver settings” customizations should
be performed. Additionally, the duplex unit would have to be installed by editing the PPD file. Please see
section 6 “Modifying the PPD file” and Example 6-2-3 for further details.
Note2: Due to incompatibilities between settings, it is necessary that some settings have priority over others.
For example, the Duplex setting cannot be used with some paper types. The Media Type (paper type) setting
has higher priority than the Duplex setting. Therefore, even if the Duplex setting is locked on, it will be
automatically set to “Off” for certain paper types (e.g. “Transparency”). These kinds of priorities are often
related to hardware accessories, such as trays, the duplex unit.
FDv4 core based PS driver customization GMSSC-GTS-091-0016
28/42 Ricoh Company, Ltd.
5-6. Delete one click icons
This customization deletes one click icons.
The customization does not apply to PS driver for Universal Print as the driver has only the “Basic Setting”
icon and the icon cannot be deleted.
Deletion of one click icons:
root element
printer
DriverSpecPPD
DriverSpecPScript5
DriverSpecPlugin
DefaultSettings
LayoutSettings
OneClickIconSettings
LimitationSettings
configuration
defaults
configuration
defaults
configuration
defaults
FactoryOCItem
FactoryOCItem
Delete “FactoryOCItem” element(s)
FDv4 core based PS driver customization GMSSC-GTS-091-0016
29/42 Ricoh Company, Ltd.
5-6-1. Structure of the ”OneClickIconSettings” element
:
<OneClickIconSettings>
<FactoryOCItem>
:
</FactoryOCItem>
<FactoryOCItem>
:
</FactoryOCItem>
:
</OneClickIconSettings>
:
Explanation:
Each “FactoryOCItem” (child element of “OneClickIconSettings”) represents a one click icon. The number of
the “FactoryOCItem” elements varies by driver. If a “FactoryOCItem” element is deleted, the corresponding
one click icon is deleted.
Note: The “Basic Setting” icon is a special icon that is not defined by “FactoryOCItem”. It is considered to be
similar in functionality to the “Restore Defaults” button. The PS driver for Universal Print has only the “Basic
Setting” icon and therefore there are no “FactoryOCItem” elements.
5-6-2. Customization examples
Example 5-6-1. Delete the “2 sided” icon
:
<OneClickIconSettings>
<FactoryOCItem>
<title lang="MUI">IDS_OC_ITEM_LANDSCAPE</title>
<description lang="MUI">IDS_OC_ITEMCOMMENT_LANDSCAPE</description>
<defaults>
<default id="%Orientation" opid="Landscape" />
</defaults>
</FactoryOCItem>
<FactoryOCItem>
<title lang="MUI">IDS_OC_ITEM_2IN1</title>
<description lang="MUI">IDS_OC_ITEMCOMMENT_2IN1</description>
<defaults>
<default id="%PagePerSheet" opid="2" />
</defaults>
</FactoryOCItem>
FDv4 core based PS driver customization GMSSC-GTS-091-0016
30/42 Ricoh Company, Ltd.
<FactoryOCItem>
<title lang="MUI">IDS_OC_ITEM_DUPLEX</title>
<description lang="MUI">IDS_OC_ITEMCOMMENT_DUPLEX</description>
<defaults>
<default id="Duplex" opid="DuplexNoTumble" />
</defaults>
</FactoryOCItem>
</OneClickIconSettings>
:
Delete these lines
FDv4 core based PS driver customization GMSSC-GTS-091-0016
31/42 Ricoh Company, Ltd.
6. Modifying the PPD file
Modification of a PPD file can be used to perform the following customization:
- Change the default driver settings
PPD file modification is sometimes used to complete a MOX modification. In other cases a PPD file
modification can be used to perform a customization that cannot be accomplished via modification of the
MOX file.
6-1. Before and after the modification
Before the modification:
Prepare a set of driver files and locate the file(s) with the extension “.ppd” or “.pp_”. There might be several of
these files. If the extension is “.pp_”, decompress it using the expand command from a command prompt:
expand -r file path
After the decompression, remove the compressed file from the driver package.
If there is more than one PPD file, you have to find and modify the PPD file for the target model(s). Each PPD
file will list the model for which it is intended. This can be seen in the line starting with “*ModelName”:
Decompress the file.
Delete this file after decompression.
FDv4 core based PS driver customization GMSSC-GTS-091-0016
32/42 Ricoh Company, Ltd.
If you modify a PPD file, please add a comment to the file and the suffix ‘c’ to the version number. This will
serve as a reminder to you or others that the file was modified, and what the purpose of the modification was.
Comments can be added using the prefix ‘*%’.
PPD file with comments and a modified version number:
After the modification:
Save the modified file back to its original location.
For information about the installation of the customized driver, refer to section 8 “Installation of the
customized driver”.
FDv4 core based PS driver customization GMSSC-GTS-091-0016
33/42 Ricoh Company, Ltd.
6-2. Change the default driver settings
6-2-1. Customization examples
Note: Contents of the PPD file are case-sensitive.
Example 6-2-1. Make “Black and White” default
Note. Modification of the MOX file is also required. Refer to section 5 “Modifying the MOX file” and Example
5-4-1.
Step 1. Search for the following text:
DefaultColorModel
Step 2. Make the following change:
Before
:
*OpenUI *ColorModel/Color Mode: PickOne
*OrderDependency: 100 AnySetup *ColorModel
*DefaultColorModel: CMYK ← Replace this line
*ColorModel CMYK/Color: "(cmyk) RCsetdevicecolor"
*ColorModel Gray/Black and White: "(gray) RCsetdevicecolor"
*CloseUI: *ColorModel
:
After
*DefaultColorModel: Gray
Example 6-2-2. Make duplex default
Note. Modification of the MOX file is also required. Refer to section 5 “Modifying the MOX file” and Example
5-4-2.
Step 1. Search for the following text:
DefaultDuplex
Step 2. Make the following change:
Before
:
*OpenUI *Duplex/Duplex: PickOne
*OrderDependency: 50 AnySetup *Duplex
*DefaultDuplex: None ← Replace this line
*Duplex None/Off: "<</Duplex false>>setpagedevice"
*Duplex DuplexNoTumble/Long Edge: "<</Duplex true /Tumble false>>setpagedevice"
FDv4 core based PS driver customization GMSSC-GTS-091-0016
34/42 Ricoh Company, Ltd.
*Duplex DuplexTumble/Short Edge: "<</Duplex true /Tumble true>>setpagedevice"
:
After (Long Edge default)
*DefaultDuplex: DuplexNoTumble
After (Short Edge default)
*DefaultDuplex: DuplexTumble
Example 6-2-3. Change the default “Installable Options”
Note1: This example does not apply to PS driver for Universal Print. There is no way to change default
installable options of the PS driver for Universal Print.
Note2: The procedure given here is for Model S-C4. The installable options differ from model to model.
Therefore, the correct values might differ from the ones described here. However, the procedure should be
similar for all models.
Step 1. Search for the block of text between “*OpenGroup: InstallableOptions/Installable Options” and
“*CloseGroup: InstallableOptions”.
Step 2. To change which optional trays are installed by default, change the line indicated below:
Before
:
*OpenGroup: InstallableOptions/Installable Options
*OpenUI *OptionTray/Option Tray: PickOne
*DefaultOptionTray: NotInstalled ←Replace this line
*OptionTray NotInstalled/Not Installed: ""
*OptionTray 1Cassette/Tray 2: ""
*OptionTray 2Cassette/Tray 2 and 3: ""
:
*CloseUI: *OptionTray
*CloseGroup: InstallableOptions
:
Available values for Model S-C4 are “NotInstalled” (default), “1Cassette” (Tray2 only) and “2Cassette” (Tray2
and 3). For example, if you want “Tray2” to be installed by default, make the following change:
After
*DefaultOptionTray: 1Cassette
FDv4 core based PS driver customization GMSSC-GTS-091-0016
35/42 Ricoh Company, Ltd.
7. Customizing PS driver for Universal Print
Some of the customizations described in section 5 “Modifying the MOX file” and section 6 “Modifying the PPD
file”, can also be performed on a PS driver for Universal Print.
This section describes customizations that are exclusively for PS driver for Universal Print:
- Change the default UI
7-1. Change the default UI
PS driver for Universal Print changes its UI based on bi-directional communication with a device. If
bi-directional communication has not been established since the driver was first installed, the driver shows
the Model V-C2 UI by default. The default UI can be changed by manually editing the file “riudm1e3.xml" in a
driver package.
Note: This customization is available for PS driver for Universal Print v.1.10.00 or later. Version 1.00.0 doesn’t
support this.
Procedure:
Step 1. Prepare a set of driver files and locate “riudm1e3.xml".
Contents of “riudm1e3.xml”:
This file needs to be modified.
FDv4 core based PS driver customization GMSSC-GTS-091-0016
36/42 Ricoh Company, Ltd.
Step 2. Open "riudm1e3.xml". Add a comment to the file and the suffix ‘c’ to the version number. This will
serve as a reminder to you or others that the file was modified, and what the purpose of the modification was.
Comments can be added under the XML declaration using the following format:
<!-- comment -->
"riudm1e3.xml" with comments and a modified version number:
Step 3. Change the name of the default model:
:
:
<modelname name="Aficio MP C7500"/>
:
:
Example -
Make the UI of “Aficio MP 5000” default:
:
FDv4 core based PS driver customization GMSSC-GTS-091-0016
37/42 Ricoh Company, Ltd.
:
<modelname name="Aficio MP 5000"/>
:
:
Note: Model names in “riudm1e3.xml" should be exactly the same as one of those in the “Select a Printer”
drop-down list in the driver’s Printer Selection tab, or in the MOX file. Please note that some model names
that start with ‘ I ‘, include a space before their names.
“Select a Printer” drop-down list in the PS driver for Universal Print:
Model name in a MOX file (“printer” element):
Step 4. Save the modified file back to its original location.
The customization is now complete.
FDv4 core based PS driver customization GMSSC-GTS-091-0016
38/42 Ricoh Company, Ltd.
For information about the installation of the customized driver, refer to section 8 “Installation of the
customized driver”.
FDv4 core based PS driver customization GMSSC-GTS-091-0016
39/42 Ricoh Company, Ltd.
8. Installation of the customized driver
There are no special requirements. The customized driver can be installed as would an ordinary driver.
However, because the customization will cause the driver to lose its Microsoft logo certification, an alert
message might be displayed during installation.
If there is a syntax error in any of the MOX, PPD or XML files, the driver UI might not be displayed correctly or
the driver might not work correctly.
Note1: On Windows Vista/2008, if a PS driver of the same model as the customized driver has already been
installed, it must be uninstalled before the customized driver is installed.
Note2: If the PS driver for Universal Print has already been installed on Windows Vista/2008, it must be
uninstalled before the customized PS driver for Universal Print is installed.
Tips - Create multiple logical printers with different default/customized settings:
Multiple logical printers of the same model and PDL but different default/customized settings, can coexist on
Windows 2000/XP/2003. This can be useful, for example, in the following situation:
A customer wants 2 logical printers of the same model to reside on the same server. One is a logical
printer that has standard settings. The other is a logical printer whose color mode is locked to “Black and
White”.
This is done for Point and Print. They want to use the Windows ACL to restrict users who can print in color.
To do this, prepare multiple drivers of the same model and PDL with different default/customized settings.
Then, create logical printers using them. There are 2 points to remember.
1. When the second logical printer is created, choose “Replace existing driver” during installation. If using
printui.dll, do not use the “/u” option.
2. The order in which multiple logical printers are created must be considered. If a logical printer is created
FDv4 core based PS driver customization GMSSC-GTS-091-0016
40/42 Ricoh Company, Ltd.
and then another is created using a driver with a MOX, PPD or XML file that has an earlier "modified" date
than that of the first driver, the second logical printer will inherit the settings of the first one. To avoid this
problem, be sure to always use a driver with MOX, PPD and XML files that have a later "modified" date than
the driver that was installed before. If necessary, update the "modified" date of the MOX, PPD or XML file.
Note1: On Windows Vista/2008, logical printers of the same model and PDL with different default/customized
settings cannot coexist. The second logical printer will inherit the settings of the first one.
Note2: The driver UI of each logical printer should be opened and then checked thoroughly before Point and
Print deployment is started.
Note3: Multiple logical printers of the PS driver for Universal Print can co-exist. However, problems can arise.
If the Current Printer (below) is changed to another model, and then changed back to the original model, the
most recently installed MOX file will be used. This will cause the local settings to be changed to those of the
new MOX file. It will also cause the settings of any existing or future Point and Print clients to be changed.
“Current Printer” in the PS driver for Universal Print:
FDv4 core based PS driver customization GMSSC-GTS-091-0016
41/42 Ricoh Company, Ltd.
9. Appendix
9-1. How to distinguish whether a driver has been customized or not
If any of the MOX, PPD or XML files were modified by following the customization procedure in this document,
it can be seen in the About window. The version of a modified file has ‘c’ at its tail.
Another way to tell is by comparing the original MOX, PPD, or XML file with the ones installed in the following
locations:
x86 Windows:
%SYSTEMROOT%\system32\spool\drivers\w32x86\3
x64 Windows:
%SYSTEMROOT%\system32\spool\drivers\x64\3
If the MOX, PPD or XML files in the above folder are different from the original MOX, PPD or XML files, the
driver might have been customized.
FDv4 core based PS driver customization GMSSC-GTS-091-0016
42/42 Ricoh Company, Ltd.
9-2. How to determine whether FDv4 core is used by a PS driver
The About window shows whether FDv4 core is used by a PS driver.
About window of an FDv4 core based PS driver (the basis of this document):
XXXXXXRE.DLL Version: 11.0.0.0 or later
XXXXXXUI.DLL Version: 11.0.0.0 or later
Additionally, an FDv4 core based PS driver will always have at least one “.mo_” file (compressed MOX file).