On clients running Microsoft® Windows® 95, invokable TPs are configured through the Windows 95 registry.
Note With Windows 95, the recommended method for setting registry variables for autostarted invokable TPs is to use the sample TP configuration program, TPSETUP. Compile INSTALL.C, the source code for TPSETUP, for the Windows 95 environment. When you write an installation program for autostarted invokable TPs, it is recommended that you add code similar to TPSETUP to the installation program. For information about TPSETUP, see Sample CPI-C TPs in the SDK.
The following table lists the registry entries used for the types of invokable TPs that can be run on Windows 95-based clients:
| Type of TP | Location in registry | Possible registry entries |
|---|---|---|
| Autostarted invokable TP running as an application1 on a Windows 95-based client | HKEY_LOCAL_MACHINE SOFTWARE Microsoft SnaBase Parameters TPs TPName Parameters |
SNAServiceType:REG_DWORD:{ 0x5 | 0x6 } PathName:REG_EXPAND_SZ:path LocalLU:REG_SZ:LUalias Parameters:REG_SZ:ParameterList TimeOut:REG_DWORD:number AcceptNames:REG_SZ:TPNameList ConversationSecurity:REG_SZ:{ YES | NO } AlreadyVerified:REG_SZ:{ YES | NO }2 Username1:REG_SZ:Password12 ... UsernameX:REG_SZ:PasswordX2
|
| Operator-started invokable TP running as an application on a Windows 95-based client | HKEY_LOCAL_MACHINE SOFTWARE Microsoft SnaBase Parameters TPs TPName Parameters |
SNAServiceType:REG_DWORD:0x1A LocalLU:REG_SZ:LUalias TimeOut:REG_DWORD:number ConversationSecurity:REG_SZ:{ YES | NO } AlreadyVerified:REG_SZ:{ YES | NO }2 Username1:REG_SZ:Password12 ... UsernameX:REG_SZ:PasswordX2 |
Notes:
1 Before an autostarted TP can be started as an application on a Windows 95-based client, the TPSTART program must be started. For more information, see Sample CPI-C TPs in the SDK.
2 AlreadyVerified and Username/Password entries are used only if ConversationSecurity is set to YES.