This option is suitable for network file server installation, or for distribution with separate DLL files. DLLs external to the WinBatch utility that uses them must be available in order to run small utilities.

When a small WinBatch utility is run, it will look in the Windows directory and the directories in the environment PATH variable for the DLL’s. The WinBatch DLL’s and network extender DLL’s must be on the path or search drive. If you launch this utility on a PC in which a large standalone utility has been run previously, the small utility can use the same DLLs the standalone utility installed.

Hint: You can automatically install the DLL’s on the PATH in a computer.

1. Create a large executable containing only a single statement:

Display(1,"WinBatch","WinBatch installed.")

You can change this statement as you like.

2. Compile this as a large EXE with all the DLL’s your scripts are ever likely to need.

3. Copy it into a directory on the path, for example the Windows System directory, and run it from there. The DLL’s will be installed once and for all. Any subsequent batch files run on that computer can be compiled as Small Exe’s. They will use the DLL’s already installed on the computer.

Notes about the compiler:

The compiler allows you to specify version information strings to be embedded in the EXE (under "Version Info").

The compiler also creates a configuration file for each source file you compile. It will be placed in the same directory as the source file, and will have the same base name with an extension of ".CMP". For example, if you compile "C:\UTIL\TEST.WBT", it will create a configuration file named "C:\UTIL\TEST.CMP".

WinBatch+Compiler

Large EXE for Standalone PC's

Small EXE for Networked PC's

Encode for Call's from EXE files

Encrypted with Password

Windows NT native service