PRB: RPC Installation Problem |
Q104315
The information in this article applies to:
- Microsoft Win32 Software Development Kit (SDK) for Windows NT, version 3.1
SYMPTOMS
There is a problem with the Remote Procedure Call (RPC) service installation. Setup searches the Windows directory for WINSOCK.DLL. If the file is found, Setup installs RPC16C3.DLL.
This is a problem if you are dual booting a machine between Windows 3.1 and Windows NT because Windows 3.1 uses an older TCP/IP interface, which is called RPC16C3X.DLL on the distribution disks. When you run Windows NT, you will want to use the newer TCP/IP interface, called RPC16C3.DLL.
WORKAROUND
If you are dual booting and using RPC, a workaround to this problem is to rename your WINSOCK.DLL file to something else, such as WINSOCK.XXX. This will cause Setup to copy the correct version of the TCP/IP dynamic-link library (DLL).
Additional query words:
Keywords : kbnetwork kbAPI kbOSWinNT310 kbRPC kbSDKPlatform kbGrpDSNet
Issue type : kbprb
Technology : kbWin32SDKSearch kbAudDeveloper kbSDKSearch kbWin32sSearch kbWin32SDKNT310
Last Reviewed: January 15, 2000 |