After the modules have been copied, you must check thoroughly the dummy names used (such as: www.yourdomain.com, hostname.com, etc) replacing them with the actual names. This must be done for the modules *.ASP and *.INI.

Also note the executable directory name, as some modules refer to the CGI-BIN directory. If your executable directory has another name, replace all references found.

Once the modules are properly copied into the Web server and thoroughly revised, test the examples 1 and 2 using a browser:

http://www.yourdomain.com/cgi-bin/example1.asp
http://www.yourdomain.com/cgi-bin/example2.asp

The pages shown are self-explaining. In both examples you must enter the requested data and click on the "generate barcode" button.

If necessary, the user may have more font options for generating captions in addition to those shipped with CGI WEBCODE. In order to do so, just copy the desired TTF files from the folder /Windows/fonts into the same directory where CGI WEBCODE is installed. Conversely, you may delete undesired fonts, but at least the ARIAL.TTF (required) font must remain in the same directory as CGI WEBCODE. Still about fonts, remember that the OCR-B-10 BT (ocrb10n.ttf) font is the most recommended caption font, chiefly for UPC and EAN patterns.

ERROR MESSAGES:

If any kind of inconsistencies arise from the values entered, CGI WEBCODE will display a self-explaining error message instead of the barcode.

All consistency tests are applied to every variable declared in the config file, and also to every variable in the command line (at CGI WEBCODE call).