Return to readme.txt CVS log

Up to [WindowsNT SDKs] / mstools / samples / rpc / hello3

Microsoft Windows NT Pre-Release 11-19-1991

File:  hello3\readme.txt
Date:  October 1991

The hello3 application demonstrates a very simple
distributed application.  The client prompts the user for a
string, then calls a remote procedure that displays the
specified string to the display of the remote server.

BUILDING THE SAMPLE PROGRAM

You can build the distributed application executables from
their source files using the nmake utility. A makefile for
the application is provided with the hello program. Type

>nmake cleanall
>nmake

If you have difficulty building the application, it may be
that some files are in different directories than expected.
You may need to set the PATH and INCLUDE environment
variables.

RUNNING THE DISTRIBUTED APPLICATION

To run the hello application, start the Microsoft NT
Operating System server service and start the server side of
the distributed application:

>net start server
>server

The server program starts and waits for client requests. You
need to know the name of the server in order to start the
client application. If you do not know the name, type the
following command on the server:

>net config rdr

The net config rdr command lists the computername.

To start the client application, start another screen group
and type the name of the executable program followed by the
name of the server on which the server application is
running. For example, if the name of your server is RPCTEST,
type:

>client RPCTEST

If the client successfully binds to the server, the client
application prompts you for the string to display on the
remote server:

>Enter a string to send to the server:

Enter the message that you want to see displayed on the
server. The client calls the remote application on the
server computer and causes the server side of the
distributed application to display your text.

If the client is unable to bind to the server, the client
displays a status code.  For example, if a call to the RPC
API function fails, the client application may display the
text:

> RpcBindToInterface: yyyyzzzz

where yyyyzzzz is an 8-digit hexadecimal status code. The
RPC status code is in the least significant 16 bits (the
"zzzz" portion) of the 32-bit status code.  RPC status codes
are documented in the RPC runtime documentation.

/* end hello3\readme.txt */

This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.