Noted	Fixed	Problem

v9	-	Netscape Navigator will not run the benchmarks when loaded
		from a local file as opposed to a URL, but fails with a
		security violation. This is not actually a bug in either
		the harness or Navigator; it's just a consequence of the
		conservative security choices Netscape made. It should be
		of no consequence to us since it's most likely that the
		run rules will require running from a URL anyway.

v8	v11	The mechanism for automatically determining platform
		property files is unreliable because the property
		values are set by the JVM vendor and may not match the
		name preferred by the system vendor. E.g., Netscape
		uses 'sunos' for os.name where Sun uses 'Solaris';
		Sun uses 'macos' for os.name where Apple uses 'Mac OS'.
		We need to rethink whether the platform file is needed,
		and if so, provide a table of synonyms.

v8	v11	_209_db troubles running from remote URL
		Only a problem for different workload sizes. Randy and
		Salina are working on resizing it appropriately.

v8	v10	Need legal clearance to redistribute javac byte codes
		so it is omitted from this release

v8	v9	System.gc() is not being called in between successive
		benchmark iterations of an autorun sequence

v8	v9	_222_mpegaudio won't run from remote URL

v8	v9	_222_mpegaudio runs from the command line only when
		your current directory is _222_mpegaudio

v6	v7	_213_javac won't run from the specjava harness

v6	v8	_213_javac requires the (possibly non-portable)
		symbolic link 'work' from the top-level directory.
		This should be changed to instead find the top
		level directory from a property setting and
		navigate to the proper directory from there

v5	v8	newmst won't run from the command line. See
		spec/benchmarks/_204_newmst

-----
@(#)Errata.txt	1.4 10/24/97
