Return to readme.txt CVS log

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

Annotation of mstools/samples/rpc/adder1/readme.txt, revision 1.1.1.1

1.1       root        1: File:  adder1\readme.txt
                      2: Date:  October 1991
                      3: 
                      4: The adder1 application demonstrates a very simple
                      5: distributed application.  The client calls a remote
                      6: procedure to add two short integers.  The remote
                      7: procedure adds the numbers and returns them to the server.
                      8: 
                      9: BUILDING THE SAMPLE PROGRAM
                     10: 
                     11: You can build the distributed application executables from
                     12: their source files using the nmake utility. A makefile for
                     13: the application is provided with the adder program. Type
                     14: 
                     15: >nmake cleanall
                     16: >nmake
                     17: 
                     18: If you have difficulty building the application, it may be
                     19: that some files are in different directories than expected.
                     20: You may need to set the PATH and INCLUDE environment
                     21: variables.
                     22: 
                     23: RUNNING THE DISTRIBUTED APPLICATION
                     24: 
                     25: To run the adder application, start the Microsoft NT
                     26: Operating System server service and start the server side of
                     27: the distributed application:
                     28: 
                     29: >net start server
                     30: >server
                     31: 
                     32: The server program starts and waits for client requests. You
                     33: need to know the name of the server in order to start the
                     34: client application. If you do not know the name, type the
                     35: following command on the server:
                     36: 
                     37: >net config rdr
                     38: 
                     39: The net config rdr command lists the computername.
                     40: 
                     41: To start the client application, start another screen group
                     42: and type the name of the executable program followed by the
                     43: name of the server on which the server application is
                     44: running. For example, if the name of your server is RPCTEST,
                     45: type:
                     46: 
                     47: >client RPCTEST
                     48: 
                     49: The client calls the remote application on the
                     50: server computer and causes the server side of the
                     51: distributed application to add the short integers 
                     52: 1 and 2.  The server displays the simple calculation:
                     53: 
                     54: >1 + 2 = 3
                     55: 
                     56: The client displays the result returned 
                     57: from the remote procedure:
                     58: 
                     59: >result from remote procedure = 3
                     60: 
                     61: If the client is unable to bind to the server, the client
                     62: displays a status code.  For example, if a call to the RPC
                     63: API function fails, the client application may display the
                     64: text:
                     65: 
                     66: > RpcBindToInterface: yyyyzzzz
                     67: 
                     68: where yyyyzzzz is an 8-digit hexadecimal status code. The
                     69: RPC status code is in the least significant 16 bits (the
                     70: "zzzz" portion) of the 32-bit status code.  RPC status codes
                     71: are documented in the RPC runtime documentation.
                     72: 
                     73: /* end adder1\readme.txt */

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