The VTS installation directory contains a series of files used by VTS. These files and their extensions are described below.
.BMP files The .BMP files within the VTS installation directory are bitmap image files used by various components of VTS. These bitmaps are featured on dialogs that appear throughout VTS during standard operations.
.CUT files The .CUT files contained within your VTS installation directory are image files in a special format used by the VTS software.
.CHM files The .CHM files contained in the VTS installation directory are the help files for VTS. These are created in the Windows HTML Help format.
.RUN files The .RUN files contained within the VTS installation directory are run-time files that VTS uses when it executes. These cannot be edited.
.VAL files The .VAL files contained within the VTS installation directory store the last-known values for different properties. For example, when you configure properties for a shape tool, such as a rectangle, the Rectangle Style dialog will display these properties on the next occasion you open the dialog. These property values are stored in a .VAL file.
Exec.log The Exec.log file within the VTS installation directory is used in conjunction with the Pulse.log file when logging data to VTS data log files. Exec.log is a file that has a new 8-byte record added to it each time VTS starts, and should not be accessed otherwise.
Install.log The Install.log file is a text file that contains logged information about the installation of your copy of VTS such as the version, the source of the installation, the files that have been copied to your hard drive, and the time and date of the installation.
Messages.txt The Messages.txt file contains a series of messages used by VTS when the scripting code has errors during a compile.
Palette.pal The Palette.pal file is a binary file containing palette information for VTS. There are 256 distinct colors in the VTS palette.
ProtoTyp.src The ProtoTyp.src file contains scripting code integral to the VTS software.
Setup.ini The Setup.ini file is an initialization or configuration file that is created the first time you run VTS. The Setup.ini configuration file is the main configuration file for VTS that enables the setting of variables that affect system-wide performance of VTS. In summary, it contains the list of applications that are to be displayed in the VAM, a number of customizable or private label settings, link tolerances, RPC-related variables, and a series of replaceable text labels. Setup.ini is described in Setup.ini.
Toolpost.txt The Toolpost.txt file contains a series of tool tip labels that apply to the Module Tree and State Diagram programming utilities used by VTS programmers.
Uninstall.bat The Uninstall.bat file is a batch file used to locate any run-time files created by VTS so that they can be removed during the uninstall process.
Uninstall.exe The Uninstall.exe file is the main executable file for uninstalling the VTS software. Double-clicking the Uninstall.EXE file cleanly removes VTS and all its files and resources from your hard drive.
VTS.exe The VTS.exe file is the main executable file for VTS.
Note: VTS.EXE accepts a command-line switch that dictates how many copies of VTS can be run simultaneously on your machine. If "/c=m" is found in the command line, as many copies can be run at once as can be tolerated by your machine. Otherwise, only one copy may be run at any one time.
Webfunc.txt The Webfunc.txt file contains data related to VTS functions within the VTS scripting language.
In addition to the files summarized above, the VTS installation directory contains application directories. Application directories are created each time you begin a new VTS application. It is important to note that each time a new application is created, all the directories and files relevant to the new application are stored in an individual application directory on the root of the VTS installation directory. Whether the new application is based upon the VTS layer or on a customized application layer, the new application's folder is still stored on the root of the VTS installation directory; in other words, application subdirectories within application directories do not exist.
Now that you have had an introduction to some of the directories and files that are located within the VTS installation directory, we will take a closer look at two internal directories integral to the creation of new applications:
The VTS layer directory
The Template directory