Please enable JavaScript to view this site.

Navigation: Installing Win2PDF

Deploying Win2PDF

Scroll Prev Top Next More

If you are deploying Win2PDF to a large number of computers (50+), Dane Prairie Systems can create a customized version of the Win2PDF install program that will automatically enter license codes and company information for each installed copy of Win2PDF. There are also silent install flags available for the deployment, which are documented below.


The following command line options are supported by the Win2PDF setup program:



Instructs Setup to be silent or very silent. When Setup is silent the wizard and the background window are not displayed but the installation progress window is. When a setup is very silent this installation progress window is not displayed. Everything else is normal so for example error messages during installation are displayed and the start up prompt is (if you haven't disabled it with the '/SP-' command line option explained above)

If a restart is necessary and the '/NORESTART' command isn't used (see below) and Setup is silent, it will display a "Reboot now?" message box. If it's very silent it will reboot without asking.



Instructs Setup not to reboot even if it's necessary.


If you invoke the install with the following command line, it will bypass all user intervention, hide the progress bar, and it will not reboot even if necessary.




The Win2PDF install only has to reboot if you are upgrading a previous installation of Win2PDF.



Instructs Setup to suppress Win2PDF specific warnings that can occur when installing on terminal servers, such as the following message:

"Server operating system detected. If you decide to purchase Win2PDF and intend on using the product in a multi user server based application, you must purchase a server license of Win2PDF."



Instructs Setup to suppress message boxes. Only has an effect when combined with '/SILENT' and '/VERYSILENT'.

 The default response in situations where there's a choice is:

-Yes in a 'Keep newer file?' situation.

-No in a 'File exists, confirm overwrite.' situation.

-Abort in Abort/Retry situations.

-Cancel in Retry/Cancel situations.

-Yes (=continue) in a DiskSpaceWarning/DirExists/DirDoesntExist/NoUninstallWarning/ExitSetupMessage/ConfirmUninstall situation.

-Yes (=restart) in a FinishedRestartMessage/UninstalledAndNeedsRestart situation.


5 message boxes are not suppressible:

-The About Setup message box.

-The Exit Setup? message box.

-The FileNotInDir2 message box displayed when Setup requires a new disk to be inserted and the disk was not found.

-Any (error) message box displayed before Setup (or Uninstall) could read the command line parameters.

-Any message box displayed by [Code] support function MsgBox.



Causes Setup to create a log file in the user's TEMP directory detailing file installation and [Run] actions taken during the installation process. This can be a helpful debugging aid. For example, if you suspect a file isn't being replaced when you believe it should be (or vice versa), the log file will tell you if the file was really skipped, and why.


The log file is created with a unique name based on the current date. (It will not overwrite or append to existing files.)

 The information contained in the log file is technical in nature and therefore not intended to be understandable by end users. Nor is it designed to be machine-parse-able; the format of the file is subject to change without notice.



Same as /LOG, except it allows you to specify a fixed path/filename to use for the log file. If a file with the specified name already exists it will be overwritten. If the file cannot be created, Setup will abort with an error message.



Prevents the user from canceling during the installation process, by disabling the Cancel button and ignoring clicks on the close button. Useful along with '/SILENT' or '/VERYSILENT'.