|
|
1.1 root 1: This directory contains the files for the sample distributed application
2: "yield":
3:
4: File Description
5:
6: README.TXT Readme file for the YIELD sample
7: YIELD.IDL Interface definition language file
8: YIELD.ACF Attribute configuration file
9: YIELDC.C Client main program
10: YIELDC.RC Client resource file
11: YIELDC.DLG Client dialog box definitions
12: YIELDC.DEF Client module definition file
13: YIELDS.C Server main program
14: YIELDP.C Remote procedures
15: MAKEFILE Nmake file for Windows NT
16: MAKEFILE.win Nmake file for Win 3.x
17:
18: ------------------------------------------------------
19: BUILDING SERVER APPLICATION FOR MICROSOFT WINDOWS NT:
20: ------------------------------------------------------
21:
22: The following environment variables should be set for you already.
23: set CPU=i386
24: set INCLUDE=c:\mstools\h
25: set LIB=c:\mstools\lib
26: set PATH=c:\winnt\system32;c:\mstools\bin;
27:
28: For mips, set CPU=mips
29:
30: Build the sample server application:
31:
32: nmake cleanall
33: nmake
34:
35: These commands build the server executable program YIELDS.EXE.
36:
37: --------------------------------------------
38: BUILDING THE CLIENT APPLICATION FOR WIN 3.X
39: --------------------------------------------
40:
41: Build the sample client application:
42:
43: nmake -f makefile.win cleanall
44: nmake -f makefile.win
45:
46: These commands build the client executable program YIELDC.EXE.
47:
48: ------------------------------------------
49: RUNNING THE CLIENT AND SERVER APPLICATIONS
50: ------------------------------------------
51:
52: On the server, enter
53:
54: yields
55:
56: On the client, choose the Run command from the File menu in the
57: Microsoft Windows 3.x Program Manager and enter YIELDC.EXE.
58:
59: Several command line switches are available to change settings for
60: the server application. For a listing of available switches, enter
61:
62: yields -?
63:
64: Bug: If you cancel in the middle of a custom yield, you must wait
65: for the number of seconds you originally set before making another
66: remote procedure call.
67:
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.