Paul Bunyan consists of several components. The functionality of these components is described in the main help file installed by the setup program, PB.hlp. The purpose here is to enumerate the files installed and registry entries created by setup for each component in order to aid in removal/repair of a damaged setup. Each optional component consists of multiple files and possibly registry entries. The setup component is always installed.
Files may be installed in three distinct places:
The application directory is just the main install directory, which is specified on the Setup Type screen during the installation process. It defaults to the same value as the message server directory. Files may also be installed in sub-directories under this directory.
The message server component of Paul Bunyan is implemented as an NT service. (On 9x it runs before login.) The service must be installed on a local drive to function properly. This is typically the Program Files directory, which is identified by the following registry entry:
If that entry does not exist or it does not point to a local, fixed drive, the setup program will attempt to obtain the drive letter for the first fixed disk on the system and append the path ‘Program Files\Paul Bunyan’ to it. If the setup program can obtain no fixed, local drive, the message server component cannot be installed. The message server directory is established by the setup program and cannot be changed by the user.
The system directory is the sub-directory of the windows directory containing 32-bit dynamic link libraries and drivers. It is typically named System32 and is obtained from the Win32 API function GetSystemDirectory.
Files: PBViewer.exe (PBView95.exe on 9x), PB.hlp, PB.cnt, Sample.pbw
Location: The application directory.
Registry entries: Values will be entered under the following keys:
Notes: Viewing the help file will cause the temporary files PBViewer.gid and PBViewer.fts to be created.
Files: PB.h, PBD.lib, PBR.lib, PBDM.lib, PBRM.lib, PBDMD.lib, PBRMD.lib, PBToMH.h, PBToMH.idl, PBToMH_i.c, PBCOM.dll, PBLog.exe
Location: Files with extensions *.h, *.idl, and *.c will be put in the \Include subdirectory under the application directory. Files with the *.lib extension will be put in the \Lib subdirectory under the application directory. PBCOM.dll and PBLog.exe will be put in the system directory and a copy will also be put in the \Redist subdirectory under the application directory.
Registry entries: PBCOM and PBLog.exe both have registry entries associated with them. Since they are installed as part of the both the API and the Message Server they are discussed in common below.
Files: PBServer.exe, PBLog.exe, PBToMH.DLL, PBCOM.dll, PBSvrCtl.exe.
Location: PBCOM.dll and PBLog.exe in the system directory
PBServer.exe, PBSvrCtl.exe, and PBToMH.DLL in the service directory.
Registry entries: PBCOM and PBLog.exe both have registry entries associated with them. Since they are installed as part of the both the API and the Message Server they are discussed in common below. Message server specific values will be entered in the following locations:
HKEY_LOCAL_MACHINE\SOFTWARE\Diamond Sierra\Paul Bunyan
PBToMH.DLL is the proxy/stub DLL for the message handler interface. It registers itself by creating entries under the following key:
Files: _Setup.cn_, _Setup.ex_, _Setup.hl_, Setup.exe, Setup.inf
Location: The application directory.
Registry entries: The installation creates uninstall entries under the following key:
Registry entries for PBCOM.dll and PBLog.exe
Note that PBCOM.dll and PBLog.exe will installed if either the API or message server are installed.
PBCOM.dll will register itself as a COM server creating appropriate entries under the following keys:
Both PBCOM.dll and PBLog.exe will be registered as shared DLLs under the following value names: