2
PVM version 3.4: Parallel Virtual Machine System
3
University of Tennessee, Knoxville TN.
4
Oak Ridge National Laboratory, Oak Ridge TN.
5
Emory University, Atlanta GA.
6
Authors: J. J. Dongarra, G. E. Fagg, M. Fischer,
7
G. A. Geist, J. A. Kohl, R. J. Manchek, P. Mucci,
8
P. M. Papadopoulos, S. L. Scott, and V. S. Sunderam
9
(C) 1997 All Rights Reserved
13
Permission to use, copy, modify, and distribute this software and
14
its documentation for any purpose and without fee is hereby granted
15
provided that the above copyright notice appear in all copies and
16
that both the copyright notice and this permission notice appear in
17
supporting documentation.
19
Neither the Institutions (Emory University, Oak Ridge National
20
Laboratory, and University of Tennessee) nor the Authors make any
21
representations about the suitability of this software for any
22
purpose. This software is provided ``as is'' without express or
25
PVM version 3 was funded in part by the U.S. Department of Energy,
26
the National Science Foundation and the State of Tennessee.
28
________________________________________________________________________
30
This is a supplement to the main Readme file. The reader should consult
31
that file for more information.
37
1. Possible User Specifications - Different Compiler Dependencies
38
2. Installation, Environment Settings
39
3. Startup Differences compared to the Unix version
40
4. Additional Software for WIN32
41
5. Further, detailed information
48
What we are working on (in WIN32):
50
- rshd for convenient startup:
51
Currently users have to install a rshd or rexecd on their
52
machines which is often Shareware. However some of them do
53
not follow the BSD specification.
54
Also it is required to specify the location of the daemon
55
executable which may be installation dependent and different
58
We have a rshd in progress which is BSD compliant, but also
59
converting the $VARIABLES to their corresponding values set
60
in the registry. This way the daemon location is no longer
61
needed. However this daemon is allowing only one connection
62
at a time, but we are working on that.
65
XPVM comes with beta6 but is crashing from time to time in its
67
This is hard to debug since the SEGV is in the TK library. But
68
probably someone can give us some hints.
71
We would like to integrate all the applications we provide in one
77
From Beta 6: (09/30/98)
79
fortran make files updated to actually work
80
win32 beta merged with unix beta into single source PVM version
82
From Beta 5: (01/22/98)
84
Bug fixes (tracer, console, daemon),
89
From Beta 4: (09/23/97)
91
First InstallShield Version,
99
1. Unlike standardized compilers in the Unix world, different flags
100
and libs are used for WIN32. Currently we distinguish between
101
Borland 5.0 or VC++ 4.0 or higher. Thus, a dependency file in
102
%PVM_ROOT/conf named WIN32.def can be modified to point to the
103
INCLUDE and LIB directories of the installed Compiler.
104
It also provides a compiler detection mechanism,
105
which works with a normal compiler installation (checking for
106
INCLUDE environment variables).
108
2. The installation is now wizard guided. Required information is
109
stored in the registry. For manual installation, please see
110
the documentation in PVM3.4\WIN32\Installation.doc.
112
3. PVM is started by invoking the console command "pvm" with an additional
113
hostfile argument which identifies potential resources. The machine
114
on which "pvm" is run for the first time (in a given session) is
115
referred to as the "master daemon." If this machine crashes, your
116
PVM virtual machine goes down (a single point of failure).
117
The hostfile should be referenced by full path, e.g. pvm d:\hostfile.
119
Manual adding of hosts is performed by the "add" command in the
120
"pvm" console. Add commands must specify the location of the daemon
123
pvm> add "hostname dx=d:\pvm3\lib\win32\pvmd3.exe"
125
4. Rshd or rexecd are required for WINNT, Rshd for WIN95. This is
126
additional (shareware) software that you will find on the WWW,
127
as long as MS does not offer its own solution.
128
Please note that the rshd is required to run remote processes
129
under your account. If you find pvm{d,l}.System in your PVM_TMP
130
directory, then the rshd is NOT working properly.
132
5. If you are new to PVM, please read the book on PVM or check out the
133
user's guide. You will find it on the PVM homepage at:
135
http://www.csm.ornl.gov/pvm
137
6. Before using PVM, you should test the functionality of the additional
140
"rsh remotehost -l login dir | more"
142
This should show the directory listing of the remote host. Piping
143
to "more" additionally checks for buffered std{io,err}.
145
7. We are aware of Fortran problems when calling one of the
146
pvm_pk* functions. This is currently an open question.
added
removed
Readme.Win32
