Usage


Installation

After you have unzipped SRPC*.ZIP into temporary directory (using the -d option) you should start setup.exe. It will run the common installation procedure. You can select between three installation options: "User only", "Developer", and "Custom". The "User only" option will install only those components that are necessary for running third-party RPC clients and servers, while the "Developer" option will install all components that are required to build your own RPC applications. With the "Custom" option you can select the installed components (as you would probably) expect.

To run RPC applications you now have to start the "portmapper". On NT you can start and stop the portmapper service from the "Services" control panel.On Windows95, where there is no service interface, you have to run the "pm_acsii.exe" from the commandline.

If you want to use symbolic names for your rpc services you should edit the "rpc"-file in the directory "%SystemRoot%\system32\drivers\etc\".

Perhaps you might want to recompile the libs, the dll, and the example-application. Compilation is currently supported by shell scripts: a "make.bat" ("makebc.bat" for Borland C++) in the main dir should do the job. During the build process the "rpcgen" utility calls the C preprocessor to do its job as it calls the cpp on Unix.

Hints for writing/porting applications with ONC RPC for Windows NT

What you need to know is, that a client program like do_cou.c has to call rpc_nt_init() and rpc_nt_exit() around the rpc action (because of the winsock initialization). Make sure that you have WIN32 defined, the "rpc" include directory in you include path, and rpc.lib in your linker line when you build an RPC-application. Be sure that exactly one version of "portmap" (see above) is running when you run your RPC-application.

Look into the "test" directory for a simple application: a "counter-server"(cou_svc.exe) and simple client (do_cou.exe) that calls the server and does some counting.

All run-time components of ONC RPC for Windows NT write their error-messages into the application log (clnt_perror() has been changed as an NT application does not always have a stderr stream). Look there first if something seems to fail.

ONC RPC for Windows NT does currently not support the authentication interface (other that AUTH_NULL).