Hi Barry and Matt, Yes, I do not have proper MPI authentication to run on this single processor machine, which has MPICH2 installed. However, I do not expect the users on this type of machine needs to install MPICH2 to run my Petsc app. So, I went to another single processor PC, which has no MPICH2 installed, ran my Petsc app. It complains that mpich2mpi.dll and mpich2.dll are missing. So, I just copied these DLL's to a directory on the PATH then my Petsc app would run fine.
Thank you both again for your help, Thuc -----Original Message----- From: owner-petsc-users at mcs.anl.gov [mailto:[email protected]] On Behalf Of Barry Smith Sent: Saturday, October 11, 2008 5:52 PM To: petsc-users at mcs.anl.gov Subject: Re: Does Petsc built with MPICH2 work in a single processor box? Looks like you may not have the proper MPICH demons running on this "uniprocessor" machine? Barry On Oct 11, 2008, at 6:03 PM, Thuc Bui wrote: > > Hi all, > > I am able to build Petsc-2.3.3-p15 with MPICH2 under Windows and > make it a > DLL. It works great with my app in a dual core laptop. However, when > the > same executable runs on a uniprocessor windows box, it gives me the > following errors: > > ... > [0] Error creating mpiexec process...2 > [0] launchMpiexecProcess failed > Fatal error in MPI_Init: Other MPI error, error stack: > MPIR_Init_thread(294): Initialization failed > MPID_Init(82)........: channel initialization failed > MPID_Init(383).......: PMI_Get_id returned 1 > ... > > Are these errors due to PatscInitialize() failing to initialize MPI > on a > single processor box? > > If this is the case, is there a way in PetscInitialize or else where > to turn > off MPI without having to recompile Petsc with the option --with- > mpi=0? > > Many thanks in advance for your help, > Thuc Bui >
