|
|
1.1 root 1: File: mandel\readme.txt
2: Date: November 1991
3:
4: The mandel application demonstrates a sample Windows client
5: distributed application. The client calls a remote
6: procedure that performs the intensive calculations needed
7: for the image.
8:
9: BUILDING THE SAMPLE PROGRAM
10:
11: You can build the application from its source files using
12: the nmake utility. The makefile allows you to build a
13: standalone version (without RPC) or a version that uses
14: remote procedure call over local named pipes on the NT
15: server (with RPC). The makefile also supports both i386 and
16: MIPS computers.
17:
18: To build the application for the i386 environment, set the
19: CPU environment variable to "i386":
20:
21: >set CPU=i386
22:
23: To build the application for the MIPS environment, set the
24: CPU environment variable to "MIPS":
25:
26: >set CPU=MIPS
27:
28: To build and run a standalone version of the application
29: called mandel.exe, use the following commands so that the
30: RPC environment variable is undefined:
31:
32: >set RPC=
33: >nmake cleanall
34: >nmake
35:
36: To build the RPC version of the application, client.exe and
37: server.exe, use the following commands:
38:
39: >set RPC=1
40: >nmake cleanall
41: >nmake
42:
43: If you have difficulty building the application, it may be
44: that some files are in different directories than expected.
45: You may need to set the LIB, PATH and INCLUDE environment
46: variables.
47:
48: RUNNING THE DISTRIBUTED APPLICATION
49:
50: To run the standalone version of the mandel application,
51: type
52:
53: >mandel
54:
55: To run the RPC version of the mandel application, start the
56: server side of the distributed application:
57:
58: >net start server
59: >server
60:
61: The server program starts and waits for client requests. To
62: start the client application, start another screen group and
63: type the name of the executable program.
64:
65: >client
66:
67: The client application calls the server application in the
68: server screen group to calculate the data for the picture.
69:
70: If the client is unable to bind to the server, the client
71: displays a status code. For example, if a call to the RPC
72: API function fails, the client application may display the
73: text:
74:
75: > RpcBindToInterface: yyyyzzzz
76:
77: where yyyyzzzz is an 8-digit hexadecimal status code. The
78: RPC status code is in the least significant 16 bits (the
79: "zzzz" portion) of the 32-bit status code. RPC status codes
80: are documented in the RPC runtime documentation.
81:
82: The "continuous" option indicates whether the program will
83: continuously draw images.
84:
85: The "zoom in" option is effective only after you have
86: selected a region using the left mouse button.
87:
88: /* end mandel\readme.txt */
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.