The DWebPro Trial Generator software enables you to create a dwebpro.exe binary that provides trialware capabilities. The trialware features available are:

• Day limited

  The software will run only for the specified days.

• Time limited

  The software will run only before the specified date.

• Start limited

  The software will run only for the specified times.

The DWebPro Trial Generator also includes a registration and serial number generation feature. Generated serial numbers are based on the user's name and, if desired, on a Hardware ID of the user machine.

The DWebPro Trial Generator Software

To Create the Trialware Version

1. Start the DWebPro Trial Generator tool.
2. Configure the DWebPro Trial Generator options, as desired.
3. Save the project in a safe place.
4. Use the File, Build Trial menu option to create your trialware dwebpro.exe binary.

If the Enable Registration option is selected, the generated dwebpro.exe binary supports the user registration.

If the Hide Startup Form option is selected, DWebPro will not display the trial form at startup unless the trial period is expired.

If the Check System Time option is selected, the generated dwebpro.exe binary will check the system time to verify if it has been manipulated to work around the trial limitation. If a manipulation is discovered, DWebPro will show the invalidsystemtime.html file (see below).

If the User Hardware Key option is selected, the serial number required for registering the generated dwebpro.exe binary will be based on a unique Hardware ID. This Hardware ID will be unique for each product and user PC.

Perform the following steps to clear trial version execution information from your system so that you can test your trialware in your development environment:

1. Start the DWebPro Trial Generator utility.
2. Open the project file used to generate your trialware.
3. Select File, Reset.

Perform the following steps to bundle the license with your trialware using the DWebPro Bundler tool:

• Start the DWebPro Trial Generator utility and build the trialware following the steps specified above.
• Copy the dwebpro.exe binary from the deploy folder (typically C:\DWebPro\deploy\) into the bundler folder (typically C:\DWebPro\bundler\).
• Start the DWebPro Bundler tool and bundle the license.

%WINDOW_BACKGROUND_COLOR%
%WINDOW_COLOR%
%WINDOW_FONT%
%WINDOW_FONT_SIZE%

%EXPIRATION%
%HARDWARE_ID%

%EXPIRATION%
%DAYS_REMAINED%
%HARDWARE_ID%

%EXPIRATION%
%DAYS_REMAINED%
%HARDWARE_ID%

%STARTS_REMAINED%
%HARDWARE_ID%

%HARDWARE_ID%

%USERNAME%
%SERIALNUMBER%
%HARDWARE_ID%

%USERNAME%
%SERIALNUMBER%
%HARDWARE_ID%

%EXPIRATION%
%HARDWARE_ID%

<base href="%BASE_URL%" />

DWebPro will show one of the following pages at startup depending on a specific event:

In all of the above HTML files, you can insert hyperlinks to additional information so that your users can read more information about the your software (such as licensing information). External links should use the target="_blank" attribute or a window popup JavaScript function. Local links (such as to license.html in the deploy\trial\language folder) must be relative links to the current folder. DWebPro will search for them in the correct language subfolder.

There are two main actions that a user can do during the trial process:

• Close the form.
• Enter registration information.

For closing the trial form, you have to create a hyperlink (or a button) such as the following:

<a href="?action=close">Close</a>
<input type="button" onclick="location.href='?action=close';" value="Close" />

For entering registration information, you have to create a POST form such as the following:

<form action="" method="post">
Username: <input type="text" name="username" />
<br />
Hardware ID: <input name="text" type="text" value="%HARDWARE_ID%" readonly="true" />
<br />
Serial Number: <input type="text" name="serialnumber" />
<br />
<input type="submit" value="Register" />
<input type="hidden" name="action" value="register" />
</form>

Once you have built your trialware software (and bundled the license), you can add another protection level using the DWEBPRO_HASH constant in your code to lock the Web application to the distributed dwebpro.exe binary. Here is sample PHP code that you can execute at the beginning of each script (using a require() statement):

<?php
if (preg_match('/dwebpro/i', $_SERVER['SERVER_SOFTWARE']) &&
   (!function_exists('dwebpro_getvar') || 
   (dwebpro_getvar('DWEBPRO_HASH') != '0F2CBE2FF0822E9744CD28A4BC1005A5'))) { 

     die('<h1>Invalid EXE</h1>');
}
?>

In the above example, the 0F2CBE2FF0822E9744CD28A4BC1005A5 value must be replaced with the hash of the new dwebpro.exe file. You can find the new hash value using code like the following:

<?php
print(dwebpro_getvar('DWEBPRO_HASH'));
?>