diff --git a/README b/README
index e714530e1ca4f44d13596c59243f2159dfe92439..ea71fc4af66f4d9d89b0581116c8d82a250d49db 100644
--- a/README
+++ b/README
@@ -49,13 +49,16 @@ LD_LIBRARY_PATH:
 
 for the music utility to find its library.)
 
-A MUSIC multisimulation is specified in a configuration file given as
+A MUSIC co-simulation is specified in a configuration file given as
 the first argument to the music utility.  The test subdirectory
 contains a collection of examples, for example:
 
 cd test
 mpirun -np 4 /usr/local/bin/music demo.music
 
+On some systems, this way of invoking a MUSIC co-simulation isn't
+supported. Se blow for an alternative method.
+
 
 * Compilation and linking flags
 
@@ -76,7 +79,7 @@ MPI_LDFLAGS   Linking flags
 
 * Porting
 
-When launching a set of applications in a multisimulation, MUSIC needs
+When launching a set of applications in a co-simulation, MUSIC needs
 to go outside the MPI standard in two respects:
 
 1. It needs to know the MPI process rank of the running process before
@@ -94,6 +97,24 @@ mpidep/mpidep.c.  For more details, see the file PORTING in this
 directory.
 
 
+* Alternative way to invoke MUSIC co-simulations
+
+In case the method of launching MUSIC described under "Getting
+started" above fails, there is an alternative method:
+
+Let's assume that we want to launch application A with binary a and Na
+processes, and application B with binary b and Nb processes. These are
+listed in a standard MUSIC config file ab.music with block labels A
+and B. The standard way to launch these would be:
+
+  mpirun -np <Na+Nb> music ab.music
+
+(where <Na+Nb> is a number). These can alternatively be launched in
+MPMD style as:
+
+  mpirun -np Na ./a --music-config ab.music --app-label A : -np Nb ./b --music-config ab.music --app-label B
+
+
 * Where to find more information
 
 The MUSIC manual and other information can be found on the MUSIC wiki: