README for Symantec Cafe 1.51 for Windows 95 and Windows NT	
=================================================================
Copyright (c) 1996 by Symantec Corporation. All Rights Reserved.


ABOUT THIS FILE
=================================================================
This readme provides important supplementary information on 
installing and using Symantec Cafe 1.51.  Please read this 
file before reporting any problems.  We recommend that everyone
begin by reading Installation Notes.  Then users new to Cafe and
especially those new to Java would benefit by reading Notes for
New Users first, then continue with the Usage Notes, which are 
specific to Cafe 1.51.


This readme contains the following sections:

*  Major Changes in Cafe 1.51
*  Installation Notes
*  Usage Notes
        - Build speed
        - Debugger
        - New IDDE options
        - Project build fixes
        - Sub-projects
        - JDK version 1.0.2
        - Cafe Companion tutorial
*  Notes for New Users
        - Java
        - Running Java applets and applications
        - Organizing your Java projects
        - Debugger
        - Remote Debugging
        - Cafe Studio
        - Environment Variables
*  Known Problems
*  Printing This File
*  Getting More Information

			*  *  *  *  *


MAJOR CHANGES IN CAFE 1.51
=================================================================
Enhancements:
o  Major(!) improvements in build speed
o  Expression evaluation
o  Dynamic expression watch view
o  Value Tips
o  More convenient debugger usage
o  "Cafe Companion" on-line tutorial

Fixes:
o  New JIT version with bug-fixes
o  Major debugger fixes
o  Improved dependency-checking
o  NT 4.0 UI compatibility issues fixed 
o  General bug-fixes

			*  *  *  *  *


INSTALLATION NOTES
=================================================================
Run setup.exe. The installation should be smooth and intuitive.  

o  Cafe 1.51 may be installed over a previous release or beta of
Cafe, version 1.0 or later.  Otherwise it must be installed to a 
clean (new) directory.  Do not install it over any releases of 
Symantec Espresso or over any releases of Symantec C++.

o  Note that we do not recommend installing into a directory name
containing spaces under NT.  This is not a problem on Windows 95.

o  If you are upgrading from Cafe 1.0 to Cafe 1.51, note this:  
Cafe 1.51 does not need the environment variables which Cafe 1.0 
has set up on your system, but the Cafe 1.51 installer will not 
make any changes on your system in this respect.  You don't need 
to change anything unless you want to.  But if you'd like to 
clean things up, then on Windows 95, edit autoexec.bat and delete
the Cafe entries for CLASSPATH, JAVA_HOME, HOMEDRIVE, HOMEPATH; 
on Windows NT, open Control Panel | System and delete the Cafe 
entries for CLASSPATH and JAVA_HOME. Using the command-line tools
will be more convenient if you leave Cafe in the PATH, but it's 
not required.  See NOTES FOR NEW USERS for details about 
environment variables. 

o  If you have NOT previously installed Cafe, and you have 
Symantec C++ installed, note this carefully:  in your Windows 
directory there are some idde config files that will conflict 
with Cafe's project view and most-recently-used (MRU) project 
list; these files all begin with the letters "scw".
    You need to MOVE (not copy) scw*.* from your Windows 
    directory to your sc\bin directory, before installing 
    or running Cafe.  SC++ will find them there.
If you run the Symantec C++ IDDE on more than one OS, you need 
to remove these files from each OS directory (win95, winNT).

o  The "Cafe Companion" tutorial document is not installed on 
your hard disk. It is left on the CD, in the directory Cafe\Doc.
The Cafe 1.5 installer will create program icons for Cafe 
Companion and for the Adobe Acrobat installer.  In order to 
read "Cafe Companion," you must have Adobe Acrobat installed on 
your system.  Run the Adobe Acrobat Installer icon to do that.
After that, running the Cafe Companion program icon will open 
the document in the Adobe Acrobat reader.  Remember that the 
Cafe 1.5 CD has to be available in the CD drive in order to 
read "Cafe Companion."  (If you want to have it available on 
your local disk, and can spare the disk space, simply create a
directory named "Doc" in your Cafe directory, copy the file 
cafecomp.pdf from the CD into your Cafe\Doc directory, and edit
the Cafe Companion program icon to point to your local copy.)

o  NT 4.0 users:  previous releases of Cafe installed the
incorrect version of ctl3d32.dll to your system32 directory.
If this applied to you, see the Known Problems section near
the end of this readme file.

			*  *  *  *  *


USAGE NOTES
=================================================================
Build speed
-----------------------------------------------------------------
The amount of improvement you will see, compared to Cafe 1.2, 
depends on the size and organization of your project.  For a 
simple project in one directory, with one or two java files and 
a few classes (such as the sample projects that come with Cafe),
the speed improvement is fairly small; Cafe 1.2 was already very
fast for simple projects, and a large percentage of the few 
seconds it takes to build is just process overhead.  But for a
complex project of some size that uses packages and an output
directory, the difference can be quite dramatic on the initial
build and even moreso on incremental builds.


Debugger
-----------------------------------------------------------------
o  Latest Fixes
There were major problems in garbage collection that were causing
hangs or GPFs while loading an object to be debugged or after 
stepping.  These have been fixed.  (Test cases that previously 
would die within 50-100 steps have now been tested out to several
thousand steps with no problem.)

Problems in the debug kernel that would previously terminate the 
debugging session prematurely have also been fixed.

o  No need to Start Debugging explicitly
Now you can load a project and, for example, immediately hit F5
(or the equivalent toolbar button) to go until breakpoint, and 
the IDDE will automatically start debugging, shift to the 
Debugging workspace, and execute the Go Until Breakpoint command.

o  No need to Stop Debugging to rebuild
Now you can make changes while debugging, then do a Build or
Rebuild All (either through the menu or build toolbar), and
debugging will automatically be stopped, then the build/rebuild 
will take place.  You can then, as above, execute the newly
compiled code in the debugger by using one of the "Go" commands 
or accelerator keys.  

o  Expression Evaluation
A complete Java expression evaluator is now provided in Cafe.
While debugging, you can evaluate any Java expression, including
method calls.  NOTE that expression evaluation requires access to
the appropriate source code; if the debugger does not find the 
source code, the Evaluate Expression Result field will show this.

The expression evaluator uses the IDDE's standard search scheme
to find the source for evaluation.  This allows you to evaluate
expressions and view Value Tips while stepping in the Java 
runtime (java.lang.String, etc.).

You can evaluate an expression from:
    Source View:
        Evaluate Selection from the right-click menu
            or from the toolbar

        This feature brings up the currently-selected text in
        the Evaluate Expression dialog.  It does not work on 
        multi-line selections. If no text is selected, then 
	the dialog picks up the token that is right-clicked, 
	or that the caret is in.

    Data View:  
        Evaluate Expression from the right-click menu
            or the Evaluate! menu

    Inspector View:
        Add Expression Watch from the right-click menu
            or from the Watch menu

All of the above access methods produce the same Expression
Evaluator dialog, which allows you to enter an arbitrary 
expression in the edit text field in the top of the dialog,
presents an Evalute button which will display the value of the 
expression in the result field, and an Add Watch button which
will add the expression to the Inspector View's watch list.
You can resize and maximize the Evaluate Expression dialog.

[You can even enter expressions that are void and have side-
effects.  For example, you can enter expressions such as
        System.out.println("Prints in output window");
Experiment with it.]

o  Inspector View
The new Inspector View lets you watch a set of live expressions
as you debug your program.  You may add an expression to watch 
by using the Watch | Add Expression Watch command.  This command 
brings up an expression dialog.  You can enter an expression to
watch, and press the Add Watch button to add it to the Inspector
View.  As you step through your program, expressions present in
the Inspector View will automatically recalculate and update. 
You can delete watches by using the delete command.

The Inspector View is available with all other views on the
Window | Goto View list, as well as on the Views toolbar.

o  Value Tips
During a debugging session, when you bring the mouse over a 
variable in a source window, the value of that variable, in the
scope of the line that is currently executing (note: not in any
different scope that you may be looking at in a Source View),
will be displayed in a Value Tip window.

You can turn this feature off (default is on) in 
	Debug | Settings | General | Show Value Tips 
and set responsiveness of the Value Tip in
	Debug | Settings | General | Value Tip Delay

NOTE that Value Tips use the expression evaluation mechanism, and
likewise require access to the source code.  If you pause the
cursor over a variable from a portion of the runtime for which
source is not distributed, this cannot be evaluated and no Value 
Tip will be displayed.


New IDDE options
-----------------------------------------------------------------
The IDDE Environment Settings dialog now offers two new options:

o  Run Applet in Internet Browser
If this is checked on (default is off), then when you select 
Project | Execute for an applet, instead of using appletviewer
to run your applet, the IDDE will run whatever application is 
registered for the .html filetype.  In most cases this will be
Netscape or Internet Explorer.

o  Minimize IDDE on execution
If this is checked on (default is off), then when you select 
Project | Execute, the IDDE will minimize to an icon until the 
application or applet is closed, at which point the IDDE will 
re-maximize.  Otherwise the IDDE will simply launch the project 
executable as a separate process and remain maximized.


Project build fixes
-----------------------------------------------------------------
o  Forward references to non-public classes

//FOO.java
class FOO
{
    BAR  a;
}

//X.java
class BAR
{
    int  b;
    FOO  c;
}

If the above two files were in a Cafe 1.2 project, the project
did not build.  This is resolved in Cafe 1.51.

o  Source files not in package directories
For building only, you may now have your source files in 
directories other than their respective package directories.

//C:\Cafe\Projects\test1\FOO.java
import pack1.*;
class FOO
{
    BAR  a;
}

//C:\Cafe\Projects\test1\BAR.java
package pack1;
class BAR
{
    int  b;
    FOO  c;
}

If the above two files were in a Cafe 1.2 project, the only
way to get the project to build reliably would be to make a 
directory named pack1 in one of the directories in classpath,
and place BAR.java in that directory.

This should no longer be necessary for building.  However, we
still recommend that you do this for debugging purposes.


Sub-projects
-----------------------------------------------------------------
o  Getting the full benefit of the major performance improvements
in Cafe 1.51 requires that the project files be regenerated in 
order to incorporate the new build rules (which enable high-speed
dependency-checking,etc).  This is handled automatically for all
single-level projects: the Cafe IDDE will regenerate the project
files for any existing project when it is opened for the first
time in Cafe 1.51.  However, the IDDE does not automatically open
and update any sub-projects.  If you have any hierarchical
projects, here's how to get the sub-projects updated:

In the left pane of the Project View, double-click on the master-
project folder to display the sub-project folders below it. Then
just single-click on each sub-project folder in turn: this opens
the project and updates it.  (You'll notice the activity messages
in the status line above.)  This needs to be done only once per 
project, of course.  After opening each of the sub-projects, 
click on the master-project folder again, and now Build or 
Rebuild All will use the new rules throughout your project.


JDK Version
-----------------------------------------------------------------
o  Cafe 1.51 incorporates the Java Development Kit version 1.0.2 
from Sun Microsystems.  For full details, refer to:
	http://java.sun.com/products/JDK/1.0.2

Here is one item that we want to call to your attention:
No support for 4-bit color!  This limitation is in the AWT from 
Sun.  Trying to run a graphical application when the display is 
set for less than 256 colors (8-bit) gets an AWT exception and a 
message telling you that it can't run with less than 256 colors.


o  The custom Cafe classes are in a separate zipfile from the Sun 
JDK classes. The CLASSPATH in sc.ini has symclass.zip in addition
to Sun's classes.zip. This is mostly a behind-the-scenes thing 
that has no obvious impact on users, but it will help us to 
accommodate future updates to the JDK more easily.


Cafe Companion tutorial
-----------------------------------------------------------------
Cafe Companion is a hands-on tutorial, designed as an interactive,
exercise-oriented introduction to Java and to Symantec Cafe.  It
has sections appropriate for those new to programming and/or to
the use of development environments, and sections to help 
experienced programmers get up to speed as fast as possible in
creating Java applets and applications in Symantec Cafe.  The 
detailed Table of Contents makes it easy to select the starting 
point that works best for you.  Note that Cafe Companion does not
address the specific features that are new with Cafe 1.51, such 
as Expression Evaluation, Value Tips, Inspector View, etc.

[See Installation Notes for details on installation and access.]

			*  *  *  *  *


NOTES FOR NEW USERS
=================================================================
Java
-----------------------------------------------------------------
o  Note that the Java architecture has two characteristics 
that are unfamiliar to most Windows users, but critical:  long 
file-names and case-sensitivity.  The source file extension is 
.java; if you copy a Java project with a utility that does not 
support long file-names (e.g., DOS, 16-bit zip utility, etc.), 
the extension will be truncated to .jav and will not work.  If 
you invoke the compiler with the name of the file in lower case 
and the actual name is in mixed case, the compiler will not 
recognize the file.  The name of the .java file must exactly 
match the name of the public class in the file, including case.

o  "Introduction To Java Programming" is provided in the help 
file INTRO.HLP, accessible through the Help manu in the IDDE.  
Corresponding samples, if you elect to install the Cafe Tutorial, 
are in Cafe\Samples\Java\Intro.  Electing to install Cafe Sample 
Files installs lots of interesting samples in Cafe\Samples\Java.


Running Java Applets and Applications
-----------------------------------------------------------------
o  Java applets are called from Hypertext links, such as links in 
internet Web pages.  The links are written in editable text using
the Hypertext Markup Language (HTML).  If you open one of the 
sample .html files in the editor, you can see the format for 
invoking an applet from an HTML file.  Java applets are executed 
by running appletviewer.exe on an HTML file.  (Appletviewer then 
invokes the Java runtime DLL with the class file specified in the 
.html file.)  

o  Java stand-alone applications, such as the AppExpress example
or Cafe\Samples\Java\PaintEditor, are executed by running 
java.exe (the loader for the Java runtime DLL) on a .class file.

o  When you choose Execute Program in Symantec Cafe:
- If the project is of type Applet, the Symantec Environment runs 
appletviewer on the HTML file specified in the HTML File field
in the Project Settings dialog, or if the HTML file is not 
specified, on the basename of the current project plus the 
extension .html. 
- If the project is of type Application, the Symantec Environment 
runs the Java Virtual Machine (VM) with the class file specified 
in the Main Class field in the Project Settings dialog, or if the 
class is not specified, on the basename of the current project.


Organizing Your Java Projects
-----------------------------------------------------------------
o  In Java the 'package' statement is used to organize source 
(.java) and class (.class) files. The compiler, the interpreter 
and the appletviewer then use this organization to find files.

o  The 'package' statement in a java source file indicates that 
the classes in that file make up part of the package.

o  The 'import' statement is used to gain access to classes that
are defined in other packages.

o  For a discussion of the package and import statements and 
their association with CLASSPATH, please consult the Java 
Language Reference, available on the Cafe Help menu.


Debugger
-----------------------------------------------------------------
o  In stepping through projects in the debugger, you may 
occasionally get "ClassName.java not found," even though the 
ClassName.class file is in the Java\Lib\classes.zip file.  
The reason is that there are several groups of class and source 
files that Sun provides to developers, depending on the license 
agreement. The general license agreement (the one included with
Cafe) allows use of the sources of the run-time library. However,
there are certain system files that can be shipped only in 
.class bytecode, not with their sources.


Remote Debugging
-----------------------------------------------------------------
o  Overview
A component named caferemote.exe provides remote debugging 
support. The installer places it in your Cafe/Bin directory.  
You run caferemote on the (remote) machine on which your Java 
app or applet will be run and debugged.

o  Requirements
Cafe needs to be installed on the remote machine. The class files
and HTML files need to be located on the remote machine.  Both 
the local and the remote machine need to have TCP/IP installed 
and working properly.

o  How to debug a remote Applet/Application
To start a remote debugging session, open a console session on 
the remote machine. Move to the directory containing the class 
and HTML files of the app you intend to debug and execute 
caferemote.  Caferemote will display some version information, 
and then an agent password and the machine's IP address. Click 
OK.  Remote debugging is now enabled.

On the machine which is running the debugger, load the project 
corresponding to the class and HTML files you are debugging on 
the remote host machine.  Select Debug | Settings | General tab.
Check "Enable Remote Debugging" and enter the Agent Password 
and Host Address as reported by caferemote. When you select 
Start/Restart debugging, the IDDE will initiate a remote 
debugging session to the remote machine.

To exit caferemote on the remote machine, select the Caferemote 
console window and type "Ctrl-C".  This will terminate the debug 
session currently in process. To continue you will need to 
re-execute caferemote in order to get a new agent password.


Cafe Studio
-----------------------------------------------------------------
o  When resources are added to a project with Cafe Studio, the 
controls and menus are placed between a set of special tags in 
the .java file.  These tags are used for the declaration and 
initialization of both menus and controls.  If these tags are 
removed, compilation errors will result: therefore it is 
imperative that you do NOT delete these tags.  Below is an 
example of these tags:

//{{INIT_CONTROLS
button1=new Button("My Button");
add(button1);
//}}

//{{DECLARE_CONTROLS
Button button1;
//}}

o  All new classes created through the "New Class" option in 
FormExpress and MenuExpress will be automatically added to the 
current project.

o  When renaming or deleting controls or menus, Cafe Studio will 
update the init and declaration areas within the corresponding 
.java file accordingly.  We are able to do this because of the 
tags used by Cafe Studio.  However, it is the responsibility of 
the developer to update all other methods that may be affected 
by this change -- for example, the handleEvent method.

o  Creating new classes in Cafe Studio when it is running as a 
stand-alone application requires that the RC be saved before a 
new resource (Form/Menu) can be added.  Once the RC has been 
saved, Cafe Studio will generate the appropriate .java files in 
the same directory as the .rc file.

o  Java reserved/key words should not be used as member, method 
or class names in Cafe Studio.  If they are used, your code will 
not compile.

o  Resource scripts (*.rc) must be saved in the same directory as 
the corresponding source files (*.java).


Environment Variables
-----------------------------------------------------------------
o  Cafe does not use environment variables.  This eliminates
conflicts with other installations of the JDK on the same system.
For your own convenience in running from the command-line, you 
may choose to have Cafe\Bin and Cafe\Java\Bin in your PATH, but 
the tools themselves do not need this. (E.g., you can, if you
wish, run a Java app by typing d:\cafe\java\bin\java ClassName.)

o  The Cafe installer will create a new sc.ini file in your 
Cafe\Bin directory.  The sc.ini file contains the settings for 
CLASSPATH, JAVA_HOME, etc. that are used by Cafe.  You can 
customize CLASSPATH by editing this file; if Cafe is already 
running when you edit sc.ini, you need to restart Cafe before
changes to sc.ini will take effect. The IDDE and all of the 
command-line tools read sc.ini.

			*  *  *  *  *


KNOWN PROBLEMS
=================================================================
Workspace
-----------------------------------------------------------------
o  The workspace configuration file has been changed in the final
release of Cafe 1.51. This means that if you have customized your
workspaces in a previous release of Cafe, you will need to redo 
your customizations for Cafe 1.51.


Compiler
-----------------------------------------------------------------
o  An output directory of "." doesn't work if you are compiling 
on the root directory of a drive.  The sj compiler gives an error
that "." is not a directory.


Debugger
-----------------------------------------------------------------
o  The debugger does not search duplicate class names in the 
expected order, going to Java source before application source. 
The problem is in Sun's design of class searching.  This problem 
will not occur if the class in question is in a package.


Debugging with native DLLS
-----------------------------------------------------------------
o  If you are building a native DLL that links with the Java 
runtime, you must build a specific debug version of your native 
DLL.  This debug version of your native DLL must be linked with 
the javai_g import lib, not the javai import lib with which you
linked the release version.  If you attempt to debug Java code 
that uses an incorrectly linked DLL, your code will crash while 
debugging.

[If you are experiencing problems stepping around calls into 
native DLL's supplied by third-party companies, you may wish to
contact them directly.]


Linking with javai.lib
-----------------------------------------------------------------
o  "When I link with the javai.lib and javai_g.lib files that 
come with the Cafe release, I get a "corrupt file" message from 
the MS linker; when I link with the same libs from the Sun JDK 
release, the linker is OK."  Explanation:  the original files 
from Sun are in COFF format, which is what VC uses. SC++ uses
OMF format.  In Cafe, we ship the libs in both COFF and OMF 
formats: javai.lib and javai_g.lib are OMF format, while 
javai.lib_coff and javai_g.lib_coff are COFF format.


What happened to the stack trace?
-----------------------------------------------------------------
o  "When I try to print Exception.StackTrace from my code, it 
doesn't work."  The reason this occurs is that the JIT compiles 
bytecode to native code at the method level, and once that is 
done, the Java context of the method is lost completely.  Once 
a method gets compiled, it is no longer running in the Java VM -
it is really native code. Calls are made directly, native method
to native method, via native code.  The stack is no longer the 
Java stack, the Java execution environment is no longer there, 
so there is no stack trace to speak of, as there is no context 
information saved for compiled methods.

o  "Why do I get a stack trace only when I run in the debugger?"
The reason is that the debugger uses the interpreter, not the
JIT, to run the target code, so the full context information is
available.  (It is also possible to disable the JIT for test 
purposes; see workaround #2 below.)


Method already being compiled
-----------------------------------------------------------------
o  The symptom is that execution of a Java application is stopped 
by an error that says "method is already being compiled."  This
error message comes from the JIT, and the cause is compile
recursion.

Explanation:
As the JIT compiles a method, it must resolve references made to
other classes.  For this reason, the 'jitting' process may cause
other classes to be loaded.  When a class is loaded, its static
initializer method is run.  Static initializers execute only that
one time, so they, themselves, are interpreted, not 'jitted'.  
A static initializer method can, however, invoke other methods 
which will be 'jitted' before they are run.  When a static 
initializer method is run by way of resolving a class reference
while 'jitting' a method, and that static initializer method 
invokes (or invokes a method which invokes) the method being 
'jitted' (the one with the class reference), a 'Method already
being compiled!' error is generated and execution cannot continue.

Workaround:
1. In order to work around this problem, one must first determine 
which class reference is causing the failure.  (The next version
of the JIT will issue an informative error message giving the 
failure class and method name and signature in the message box.)
Then it is a matter of forcing the problem class reference to be
resolved before the problem method is 'jitted'.  Probably the 
easiest way to do this is to make a reference to that class in 
the static initializer of the 'jitted' method's class.  

2. In order to execute this application in the Cafe environment
without changing the code, it is necessary to disable the JIT,
thus causing the runtime engine to use the interpreter, instead.
To disable the Cafe JIT, do the following in the environment 
where the application is to be run:
	set JAVA_COMPCMD=disable
You can do this in a console window and run the application from
the command-line, or run Cafe\Bin\cafe.exe from that environment
and execute the application in the Cafe IDDE, or add the "set" 
command to sc.ini, but in that last case no app[let]s will have
the benefit of the JIT until the command is removed from sc.ini.
To re-enable the JIT in a console environment, simply clear it:
	set JAVA_COMPCMD=


Cafe Companion
-----------------------------------------------------------------
o  On page 2-7, there is a statement that when the compiler finds
an error in the code, the IDDE opens the source file at the line
containing the error and opens another window with reference 
information pertaining to the situation.  This statement is not
correct.  The actual behavior:  compiling a file may produce
several error messages in the Output window; double-clicking on
an error message opens the source file at the indicated line 
number.  Placing the mouse cursor on a word in the source file
and hitting F1 will do a keyword search in the online Help 
documents and bring up, for example, the Java API page for that 
method name, or a selector dialog if the keyword appears in 
more than one Help topic.


NT 4.0 and ctl3d32.dll
-----------------------------------------------------------------
o  In previous releases of Cafe, the installer was not able to
distinguish between beta releases of NT 4.0 and Windows 95, and
mistakenly installed the Windows 95 version of ctl3d32.dll onto
NT 4.0 systems.  In applications that care about this (Source
Safe 3.0 is one), the symptom on startup is an error message,
"unable to initialize the 3D system," then on OK the program 
runs, but without its normal 3D dialog style.  To fix this, 
copy the correct version of ctl3d32.dll from the Cafe 1.51 CD,
cafe\redist32\nt\ctl3d32.dll, to your NT system32 directory.

Cafe 1.51 itself, specifically Cafe Studio, seems to run fine 
on NT 4.0 with either version of ctl3d32.dll.

			*  *  *  *  *


PRINTING THIS FILE
=================================================================
NT 3.51 Notepad has a default fixed font that does not fit a 
standard text page correctly.  To print this file from Notepad 
on NT 3.51, please change the default font (Edit | Set Font) to 
any regular 12-pt. font, such as MS Serif or Arial. This problem
is only in NT 3.51 Notepad.

			*  *  *  *  *


GETTING MORE INFORMATION
=================================================================
o  For more information on the Java language and related issues:
		http://java.sun.com

o  For wide-ranging public discussions and technical tips about
using Java, see the usenet newsgroup hierarchy: 
		comp.lang.java.*
A good place to start is:
		comp.lang.java.misc

o  For direct help from Symantec Technical Support Engineers:
		CompuServe:  "GO SYMDEVTOOLS"
		Email:        support_javawin@symantec.com
		Telephone:    (541) 465-8470 

o  For the latest Symantec Cafe developments and information on
Java topics, please visit our Web site:
		http://cafe.symantec.com

			*  *  *  *  *


Enjoy yourself and be productive in the Symantec Cafe!


Sincerely,

The Symantec Internet Tools Team 
