|Thunking and the KiXtart RPC Service|
Choosing Where to Install the KiXtart RPC Service - Starting the KiXtart RPC Service
Unlike Windows NT, Windows 9x does not provide all the Win32 APIs that KiXtart 95 needs to gather information, such as the user's full name and group memberships. KiXtart uses two programming methods to solve this problem: thunking and Remote Procedure Calls (RPCs)
Thunking is the term used when connecting to a 16-bit API from a 32-bit application. The 16-bit APIs required by KiXtart are provided by Netapi.dll. Kx16.dll and Kx32.dll provide the so-called thunking layer required to connect to Netapi.dll.
Unfortunately, Netapi.dll does not provide all the information that is of interest to KiXtart. Most notably, Netapi.dll does not provide access to the logon domain, the security identifier (SID), the primary group, the home drive and local groups. The KiXtart RPC service provides these missing pieces of information to KiXtart using RPCs. The client side of the RPC interface is provided in Kx95.dll
The server side of the RPC interface is provided in Kxrpc.exe, and this should be installed and run on one or more Windows NT systems. The KiXtart RPC service can run on any Windows NT system: a workstation, a standalone server, or a logon server. The system must be either a member of the logon domain or a member of a resource domain that has a trust relationship with the logon domain.
Using the KiXtart RPC service is optional. However, without it, extended information, such as local groups, is not available to Windows 9x systems.