Hello again, it works (partially) now

Thank you @notzed for your help! Yes, my problem was that I was only running the java applet and another simultaneous demo (in this case i ran the fft2d demo) and I was NOT also running the erm's ./run.sh monitoring script (that writes to the emesh.status and ecore.status files).
To fix the problem:
1) run the erm demo run.sh script in the apps/erm directory (that gets the statuses and writes them to the emesh.status and ecore.status files).
in the /epiphany-examples/apps/erm directory:> ./run.sh2) run the compiled java applet that visualizes the emesh.status and ecore.status files. (make sure to first compile the EpiphanyMonitor2.java file using first with command
javac EpiphanyMonitor2.java (you have to install java to do this (see earlier post in this thread)))
in the /epiphany-examples/apps/erm/src/ directory:> java EpiphanyMonitor23) run the fft2d demoin the /epiphany-examples/apps/fft2d directory:> ./run.sh** smile and see the java applet update - yeah! First, you see some epiphany cores' mesh load values turn red, as they are receiving data from the ARM, then you see the epiphany core load values turning red as they are processing the fft2d application
**

however, it then appears the fft2d demo gets stuck and does not ever complete execution and the values of the cores' loads stay red indefinitely and there is no more core mesh load values depicting signs of the epiphany cores returning any results to the arm.
4) force quit the fft2d demoin the /epiphany-examples/apps/fft2d directory:> control-c5) force quit the erm demo in the /epiphany-examples/apps/erm directory:> control-c6) run the erm demo again to see the java applet update to all green (no activity)
(same as see step 1)7) run the fft2d demo again to see the java applet update to green/red (activity in first the mesh then the cpu's)
(same as step 3)Note, I had to do step
4) because the fft2d demo was not exiting on its own (even though the fft2d demo completes on its own OK when NOT running the ERM demo simultaneously)
Note, I had to do step
5) because *I think* the ERM demo was not updating the status files correctly after I force quitted the fft2d application (unless it was true that the epiphany core loads really were still active after the fft2d demo was force quitted..)
However, note, after running a couple loops of steps 3) through 7), the parallella ARM computer froze..

I'll update this thread if I ever get a stable demo

And appreciate any help if anyone sees where my problem is and/or has successfully executed the ERM demo in conjunction with any of pre-loaded demos on the parallella board.
Thank you again,
Deborah