From: Javier Fernandez Baldomero <javier@casip.ugr.es>
Newsgroups: comp.parallel.pvm
Subject: PVM beta for Win95
Date: Tue, 06 Oct 1998 10:50:11 +0100
Organization: Centro Informatico Cientifico de Andalucia
Message-Id: <3619E7D3.446B9B3D@casip.ugr.es>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit


Hi!:

	I installed pvm3.4beta6 for Win95 and was not able
to configure it for BorlandC. Makefiles are always those
for VisualC++. Also, looking at the files in \windows\temp\pvm 3.4
does not help. .CAB files are not recognized as valid cabinet
files for "extract" (expand? ouch, my memory... :-)

	Has anybody run into the same problem? Are Makefiles
for BorlanC somewhere around? Since I recompiled everything for
VisualC++, I have no problem right now, but the libraries
obtained are significantly different from those in the
distribution. "lib" from VisualC++ (or was it dumplib? ouch...)
does not recognize them as VisualC++ libraries, while tdump...
well, the one from BorlandC, does.

	I suspect the VisualC++ libraries are overwritten by
the BorlandC ones during the installation process, when instalshield
says: "Installing VisualC++ libraries" and then says "Installing
BorlandC libraries" although I chose VisualC++.

	Any suggestions? How may I pick the BorlandC Makefiles,
or the VisualC++ libraries, from the .cab files?

	The README file says that xpvm still hangs sometimes,
but the source is not there. May I install tcl/tk for Win95,
and then the source from the unix PVM version, and then recompile?
Are there makefiles for that?

	Thank you in advance

-javier