novaPDF OEM is a virtual PDF printer that developers can use when needing a post-processing PDF solution. Installing novaPDF OEM should be done only via the command line parameters, as this is the only way it can be configured. Parameters used for this purpose are detailed in this article.
The mandatory post-processing operations to the resulting PDF files is a restriction for novaPDF OEM in order to stop developers from creating a PDF printer driver which would compete directly with our PDF printer driver and also to stop the end-users from simply creating PDF files with printer driver delivered via novaPDF OEM.
Author: Lorant (Softland) Updated on: 2019-02-20Read article
novaPDF SDK sends a request to create the PDF files to the printer driver that gets installed with the package, novaPDF for SDK. By default, if novaPDF SDK is unregistered, each page from the generated PDF file will contain a footer notice (that says the application is not registered). After you purchase a license and register novaPDF SDK, that footer notice won't be included in the generated PDF files.
When integrating novaPDF SDK in a 32bit application that will be distributed on Windows x64 systems too, you have to take into account some aspects regarding the default behavior of our installer. One of these is the novaPDF installer that contains both 32 bit and 64 bit versions of the novaPDF driver and of the COM interface. Because of its built-in automatic detection, when installing novaPDF on Windows x64 computers (via your application), the 64bit version of the driver and COM interface are installed (and not the 32bit version).