Note that if the master node is shutdown, screen saver based nodes will periodically retry to contact the master until it restarts (or the screen saver is stopped).
Screen saver nodes (and browser-based nodes) should rarely be used for development due to the JVM class unloading problem.
In addition to not having a DOGMA master installation present, screen saver based nodes should either not have the node installation, or not have them reachable via CLASSPATH.
You must also have JDK 1.1.5 or greater installed on the nodes you wish to use.
Step 1 - Verify your master installation and local JDK installation
by starting up DOGMA on
the master node and then starting a browser based node on the local
node. (e.g. type "startDOGMA" from the c:\dmaster\run directory on
the master node and then typing "c:\jdk1.1.6\bin\appletviewer.exe http://mymaster.byu.edu:8180/DOGMA/NodeCon.html).
Step 2 - Unzip DOGMAWin32Saver.zip
Step 3 - Move the subdirectory ".hotjava" to your JDK directory (e.g. c:\jdk1.1.6). (If this directory already exists you must either delete it, or copy all files from the DOGMA distribution to that directory overwriting when necessary.)
Step 4 - Move the file DOGMA.scr to your windows system directory (e.g. c:\winnt\system32).
Step 5 - You should now be able to see the DOGMA Screen Saver on your
list of screen savers. Now adjust the settings in the screen saver
to reflect you local installation. Note that the DOGMA Deactivation
Setting controls how DOGMA reacts when a user stops the screen saver.
Deactivating immediately causes all user programs running on the node at
the time to terminate. Deactivating when idle causes the node to
wait for all running applications to terminate before exiting (NOT YET
IMPLEMENTED AS OF DOGMA 0.7), deactivating never causes DOGMA to go into
the background and not actually exit.