The _vti_bin directory in this directory contains the actual binary executable files that get executed when the fpstub.exe files are run from a web.

The shtml.exe program deals with all the bots that can run on a FrontPage extended web. This includes functionality such as including headers and footers, echoing out the current date or modified date of a file, managing a user forum or dealing with form processing.

The fpcount.exe program is just a web counter bot that is run when a visitor comes to your site. I suppose that this program was separated from the shtml.exe program to provide better speed upon execution.

In the _vti_aut and _vti_adm are the admin.exe and author.exe programs that the FrontPage client deals with when publishing or managing a FrontPage extended web. These programs are put in separate directories that use .htaccess files to restrict their access based on a user or group.

'nls' stands for national language support in this instance. This directory holds code page files for different languages. All you need to know about this directory is that it should exist.

This directory contains the html documentation that can also be found on the web at http://officeupdate.microsoft.com/frontpage/wpp/serk/.

The fonts used in this documentation seem to be easier to read than what is on Microsoft's website. Also, you can be sure that you'll always have the documentation that goes with your version of the extensions in case Microsoft changes information to their site.

In this directory is a source code file called fp.suid.c. This is a stub executable that will be installed in multiple places of each web's _vti_bin directory. You should be able to compile this program by running:

Upon execution, this stub file will run one of the files in the frontpage/version4.0/exes/_vti_bin directory, according to what the stub executable is named after. So, if the stub executable is named shtml.exe, it will run the shtml.exe program in the /usr/local/frontpage/version4.0/exes directory. This saves quite a lot of space in each web since the stub executable is usually only 15KB, where as the actual programs these stub files will run total over 10MB.