Return to readme.txt CVS log

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

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

1.1       root        1: File:  hello2\readme.txt
                      2: Date:  October 1991
                      3: 
                      4: The hello2 application demonstrates a very simple
                      5: distributed application.  The client calls a remote
                      6: procedure that prints "hello, world" to the display of the
                      7: remote 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 hello 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 hello 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. To
                     33: start the client application, start another screen group and
                     34: type the name of the executable program followed by the name
                     35: of the server on which the server application is running.
                     36: For example, if the name of your server is RPCTEST, type:
                     37: 
                     38: >client RPCTEST
                     39: 
                     40: The client application calls the remote application on the
                     41: server computer and causes the server side of the
                     42: distributed application to display the following text:
                     43: 
                     44: >hello, world
                     45: 
                     46: If the client is unable to bind to the server, the client
                     47: displays a status code.  For example, if a call to the RPC
                     48: API function fails, the client application may display the
                     49: text:
                     50: 
                     51: > RpcBindToInterface: yyyyzzzz
                     52: 
                     53: where yyyyzzzz is an 8-digit hexadecimal status code. The
                     54: RPC status code is in the least significant 16 bits (the
                     55: "zzzz" portion) of the 32-bit status code.  RPC status codes
                     56: are documented in the RPC runtime documentation.
                     57: 
                     58: /* end hello2\readme.txt */

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