Microsoft KB Archive/104550

From BetaArchive Wiki
< Microsoft KB Archive
Revision as of 16:03, 18 July 2020 by 3155ffGd (talk | contribs) (importing KB archive)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.
Knowledge Base


RPLLINK.EXE Allows Dynamic Loading and Unloading of Protocols

Article ID: 104550

Article Last Modified on 10/31/2006

This article was previously published under Q104550

SUMMARY

RPLLINK.EXE, which is run by default after the NET START RDR on an RPL workstation, enables the post-boot use of Demand Protocol Architecture (DPA) to load and unload protocols dynamically. DPA loading and unloading requires that network device drivers be available in the MS-DOS device driver chain, and RPLLINK.EXE links device driver chains together so that they are available by name to drivers and programs.

You need RPLLINK.EXE only if you are dynamically loading and unloading protocols such as TCP/IP, XNS, DLC, or IPX. If you are not, you do not need RPLLINK.EXE, in which case you can remove it. Then NetBEUI is loaded statically, as it is anyway under RPL, but other protocols are not available for demand loading or unloading by means of DPA. If you remove RPLLINK.EXE, you do not need to modify CONFIG.SYS, AUTOEXEC.BAT, PROTOCOL.INI, or LANMAN.INI; NetBEUI will be available by default. NETBIND.EXE is not the proper binding program to run on an RPL client; binding is taken care of in DOSBB.CNF, which you should not modify.


Additional query words: 2.00 2.10 2.10a 2.20 2.0 2.1 2.1a 2.2

Keywords: KB104550