<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7036.0">
<TITLE>RE: [mpich-discuss] Windows and Nemesis in 1.1</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<P><FONT SIZE=2>Hi,<BR>
The default channel in MPICH2 on windows is sock (This would change in a release or two to nemesis). You can use the nemesis channel using the "-channel" option of mpiexec (mpiexec -n 2 -channel nemesis cpi.exe).<BR>
Let us know if it works for you.<BR>
<BR>
Regards,<BR>
Jayesh<BR>
<BR>
-----Original Message-----<BR>
From: mpich-discuss-bounces@mcs.anl.gov [<A HREF="mailto:mpich-discuss-bounces@mcs.anl.gov">mailto:mpich-discuss-bounces@mcs.anl.gov</A>] On Behalf Of James S Perrin<BR>
Sent: Wednesday, June 17, 2009 9:48 AM<BR>
To: mpich<BR>
Subject: [mpich-discuss] Windows and Nemesis in 1.1<BR>
<BR>
Hi,<BR>
I see that windows has nemesis support in 1.1 but is this the default channel and inter_channel method? The wmpiconfig.exe tool still lists sock and ssm as the defaults respectively and the list of available options is out of date. Can I find out what channel is actually being used. I can type "kipper" in for the channel and it still works!<BR>
<BR>
<BR>
Regards<BR>
James<BR>
--<BR>
------------------------------------------------------------------------<BR>
James S. Perrin<BR>
Visualization<BR>
<BR>
Research Computing Services<BR>
Devonshire House, University Precinct<BR>
The University of Manchester<BR>
Oxford Road, Manchester, M13 9PL<BR>
<BR>
t: +44 (0) 161 275 6945<BR>
e: james.perrin@manchester.ac.uk<BR>
w: www.manchester.ac.uk/researchcomputing<BR>
------------------------------------------------------------------------<BR>
"The test of intellect is the refusal to belabour the obvious"<BR>
- Alfred Bester<BR>
------------------------------------------------------------------------<BR>
</FONT>
</P>
</BODY>
</HTML>