        Skeletal instructions for using the contents of this tar file
		(for defgb 4.2 et seq.  WJS.  Jul 04)

	This release contains several bug fixes.  The majority of the
work, however, reflects a library reorganization and a new method
for building the JGOFS system.  These changes were enough to "earn"
a new .N release.

	The makefiles add the cc options -lm and -g to the
CC string set up in build-env.pl.  You may need/want to change these.

Files:
        By default, the defgb build procedure looks for outer in the
src/methods directory.  If the outer you wish to use is elsewhere,
please edit makefile.defgb appropriately. Similarly, the defgb build
looks for files that outer needs in src/methods and src/include.  If
they are not there, or not  needed, please edit makefile.defgb
appropriately.
	This release no longer includes a version of outer.
	The name of this file has been changed from readme to
readme.defgb.
	This release reflects the perl replacements for build & build-env
(get buildXX.tar and read its doc files for more info).  Accordingly,
1) master_makefile.defgb has become makefile.defgb (and the former
shell makefile.defgb removed)  &  2) the various make*defgb*.csh files
have been removed.


Incompatibilities with older versions of defgbXX.tar:
	There are no known incompatibilities with older versions of
the defgb image.
	The make files for defgb 4.2 have been modified to assume the
existence of a src/include directory (containing "appropriate" files), and 
to assume that src/methods/outer.c has .brev functionality (which also
implies the existence of the required support files for that version of
outer)
	Several files formerly included in defgbXX.tar have been
moved to libupdXX.tar (included with outerXX.tar, which is included
with defgbXX.tar)

Notes:

	1)  All files are text.

	2)  The "switch" documentation discusses compilation options.
The "param1" documentation discusses run-time options.  Some are duplicated,
so they can be set either way.
	    In particular, if your node does not have the JGOFS "jdb"
routines (or the http routines they call), you may need to set the
READ_OBJECTS compilation switch to FALSE.  The jdb routines are normally
found in the library file /jgofs_root/src/lib/jgofs.a. 

	3)  Documentation:
	There are presently no "user", "new feature", or "bug/incompatibilty"
documents-sorry.  Also, "JGOFS system" documentation is not present, and
familiarity with the JGOFS system is assumed.  JGOFS system documentation
may be available via a WWW browser at http://puddle.mit.edu/datasys/jgsys.html
and/or http://lake.mit.edu/~glenn/datasys/jgsys.html.  Documentation more
related to data preparation for the system can be found at
http://usjgofs.whoi.edu/howtoputdata.html and 
http://globec.whoi.edu/globec-dir/data_org_ret.html
        User, new feature and some incompatibility information can be
found in the param1.doc file.  It is organized as a reference document,
but has some description that may be useful as a user document.  Incompat-
ibility information can be found at the end of the file.
        Incompatibility information can also be found at the end of the
defgb_switches.doc file.  The ultimate source of information about how things
have changed is the revision section of the code of each module.  Old revision
sections are in the defgb_revision.doc file.
	The defgb_bugs.txt file describes some known problems as well
as a "wish list", which by implication can explain some less-than-optimal
behavior of the program
	varlist.doc is a discussion of how JGOFS object variable lists get
made from strictly def-formatted input files and from more flexibly formatted
input files.
	comment_considerations.doc is a discussion about how defgb and other
pieces of the JGOFS system deal with commments.

	4)  Debugging suggestions:
a) The defgb_errs.txt file contains the text of various error messages.  Some
   messages have more information with them about what might cause the problem
   and/or which code module the message comes from. [Note: the contents of
   this file are not being kept up to date as of ~defgb v 4.  Sorry]
b) Try running the method interactively.  The parameters on the command
   line are the parameters from the .objects file (but not comma separated).
   To see the text of what the html code will be, set the last 5
   characters of the environment variable PATH_INFO to .html0 (the 0 is the 
   level to display).  You may need to quote some parameters on the command
   line that you do not need to quote in the .objects file.
c) If the method works interactively but dies when run by the httpd server
   (and jgofs program serv), check for file access problems due to the switch
   between "you" running the interactive program and whatever username is
   running the httpd server.  Scripts need the appropriate x access.  If
   you have no luck, try setting up an error sink (see diagnostics optional
   file info in the .doc file-an appropriate command in an indirect file might
   be		diagnostics = \ error_sink = defgb.err		)
d) It may be possible to help diagnose performance problems by doing a
   function call trace, since this output is time stamped (see diagnostics
   optional file info in the .doc file-an appropriate command in an indirect
   file might be
	diagnostics = \ debug_sink = defgb.debug; trace_level = 40	)
