PRB: RPC Installation Problem

Last reviewed: November 2, 1995
Article ID: 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 reference words: 3.10
KBCategory: kbnetwork kbprb
KBSubcategory: NtwkRpc

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: November 2, 1995
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.