Folders
Branding folder
When starting the application, you will be asked for the branding folder. This is the folder where the new msi files will be generated. You can create a new folder or use an existing one. If you choose an existing folder, the files from the folder will be deleted and the original msi installers will be copied there and injected with the new properties.
Settings file
If you already have run the tool and you only wish to change some options, select the settings file from the previous run.
Files
There are several files that can be injected in the.msi:
Customization (.ctm) and License (.lic) files.
License file contains information about your license and Customization file is used for re-branding options. Contact novaPDF OEM support team for more information about re-branding.
When buying a the novaPDF OEM license will receive these two files. You should use them both to create a licensed printer.
If you do not have the novaPDF OEM license yet, select the "Use default Customizations (*.ctm) and License (*.lic) files" option to use some files that the novaPDF OEM provide for trial testing.
Controls (.ctl) file
Special customization file for the Profile Manager tool. Contact novaPDF OEM support team for more information about customizing Profile Manager tool.
Forms (.nps) file
This file contains the printer forms available for the printer. This is a text file and you can modify it to distribute the forms you wish. User defined forms should have a format like this:
0;0;281;36x48 inches;36x48 inches;914400;1219200;0;0;0;0;
(increase the form number on third position and specify form width and height in thousands of millimeters)
Resolutions (.npr) file
This file contains the resolutions available for the printer. This is a text file and you can modify it to distribute the resolutions you wish. Resolutions should be values between 50 and 2400 and you can specify maximum 100 resolutions.
EULA (*.rtf)
Default EULA file is empty. You can select the EULA document for your application.
Help (.chm) file
If you wish to install a diffrent help file in.chm format.
Use only default profiles and presets
It will be installed an empty profiles database, containing only default options. The default profiles database will overwrite existing profiles database from previous installation.
Use profiles and presets you defined
If you wish to distribute some public profiles with your application, you can define the public profiles by running the Profile Manager tool. The profiles database will be included in your customized msi.
Overwrite existing profiles and presets
If this option is set, the new profiles database will be copied over existing profiles database from previous installation so the new defined profiles will be available on upgrades installations too. If this option is not set, when upgrading over a previous installation the profiles database is not copied so are kept previous profiles.
Default Files
All files from Default files folder will be included in the msi. Add there all files (image watermarks, certificates, overlay files) you wish to distribute.
OEM specific save parameters.
Location
Where should the pdf files be saved: Local or Server. In case the printer is shared in the network, Local means the computer from where the document is printed and Server means the computer where the printer is installed.
Folder
The path to the folder where to save the pdf files. If this is on a different computer, use UNC paths. You can use novaPDF OEM specific macros (see Save File macros) and environment variables in the folder path.
Username and Password
If the user that prints the documents does not have rights to access the folder, enter an user name and password that has the necessary rights.
File
PDF file name. You can use next macros in the file name:
[N] - document name (as is registered in the printer queue when printed)
[YMD], [Y], [M], [D] - date macros: year, month, day
[HIS], [H], [I], [S] - time macros: hour, minute, second
[C] - Counter: if a file the same name exists in the folder, the counter is increased. By default the counter has two digits (like 01) but you may specified a different number of digits for instance "0001" corresponds tp macro [C4]
[W] - computer name
[U] - user name
[O] - domain
[L] - process name of the application that prints the document
[R] - printer name
[P] - profile name
When file exists
What action to do when a file with the same name already exists in the save folder:
- Overwrite
- Do not save
- Auto number new files
- Append date and time
- Auto number existing files
OEM specific run parameters.
Application
Full path to the application executable to be launched after a PDF is created. You can use environment variables in the application path and next novaPDF OEM specific macros:
[W] - computer name
[U] - user name
[O] - domain
[R] - printer name
[P] - profile name
Parameters
The arguments that should be passed to the application. "%1" will be replaced with the full name and path of the PDF file. "%2" will be replaced with the process name of the printing application. You can also use next novaPDF OEM specific macros (see Run application).
Username and Password
If the user that prints the documents does not have rights to access the application, enter an user name and password that has the necessary rights.
Run as
How to run the application:
- Normal
- Minimized
- Hidden
Run type
How to start the application:
- Run from shell
- Run as child process
Results
When pressing the inject button the new customized msi files will be created.
The settings you filled in these pages can be saved in an ini file in the branding folder.
After running the tool, next msi files will be available in the branding folder:
- novaPDF11PrinterDriver(x64).msi or novaPDF11PrinterDriver(x86).msi - each of them installs both 32 and 64 bit versions of the printer driver
- novaPDF11OEM(x64).msi or novaPDF11OEM(x86).msi - install the custom, licensed printer
Note
After the msi files are injected with your custom parameters, their digital signature becomes invalid so they need to be signed again. See more details in the topic Build an installation package bundle