
*****************************************************************
* Release notes for Workgroup Web       
* File: RELEASE.TXT                   
* Latest Edit: June 1, 1995 
*****************************************************************

=================================================================
		    Table of Contents
=================================================================

This file includes the following topics:

	Requirements

	Installation Notes
                Enivironmental PATH strings > 256 characters
		Configuring Workgroup Web
		WIN32S
                Configuring TCP/IP for MOSAIC
                PATHWORKS Windows95 Kit conflict
                Security Module change
                Previous Workgroup Web conflicts
                Invalid drive


	Known Problems
		WIN32S - Video Driver Problem
                       - Conflicts with MSVCRT20.DLL
		DNETHEAPSIZE Message
                Windows 95 Restrictions

-----------------------------------------------------------------
Requirements
-----------------------------------------------------------------
It is a requirement that the MOSAIC client machine be configured
with 8 MBytes of RAM or more.

It is a requirement that DOS SHARE and/or Windows VSHARE VxD MUST
be installed for Workgroup Web to function correctly.


-----------------------------------------------------------------
Installation Notes
-----------------------------------------------------------------

Enivironmental PATH strings > 256 characters
--------------------------------------------
It is possible with NT, Windows95 and the newest version of DOS to
set the PATH environmental variable to a string greater than 256
characters.  If your system falls into this situation, this version
of the install and configure will be unpredictable at the last stage
of the install and may fail at this point.  The actual installation
is complete at this point and there should be no problem continuing
in most cases.


Configuring Workgroup Web
-------------------------
To install Workgroup Web, using Microsoft Windows File Manager, move
to the DISK1 subdirectory and double click on the file SETUP.EXE.
SETUP.EXE will ask you to confirm where your Windows subdirectory
is and where you would prefer to install PWMOSAIC.

If WIN32S is installed, SETUP will prompt you to reboot your
system when the install completes.  Please ensure that all
applications are closed and data saved prior to running SETUP
for PWMOSAIC.

PWMOSAIC.INI now resides in your Windows directory.  It must be in
this location to be effective.  If PWMOSAIC fails to find it, it
will create a new copy there.

You will need at least 400K of 640K memory for this install.



Configuring TCP/IP for MOSAIC
-----------------------------
When using PWsetup to configure TCP/IP for your Workstation with
the "Customize" option, you may optionally want to have all
TCP/IP components copied to your local system as follows.

On the "Select PATHWORKS Services for Workstation" screen, select
the tasks needed by your workstation.  For PWmosaic, select
"TCP/IP" and "PATHWORKS Windows Network". This will ensure that
the TCP/IP files needed by PWMOSAIC are on your local system. You
will then be independent of the PATHWORKS system service when
running PWMOSAIC.



WIN32S
------
The version of WIN32S ( v1.20 ) included with Workgroup Web
will be installed over any previous, older version.



PATHWORKS Windows95 Kit conflict
--------------------------------
The INI file associated with Mosaic (PWMOSAIC.INI) resides in your
windows directory.  The INI file content for this kit conflicts with
the INI file associated with the PATHWORKS Windows 95 field test kits.
The help files are different.  When this kit installs, a new help
is added and the INI file is changed to point to it.  If you should
then run the PATHWORKS Windows 95 release, the help file will not
be found.


Security Module change
----------------------
The INI file associated with Mosaic (PWMOSAIC.INI) resides in your
windows directory.  The INI file content for this kit conflicts with
the INI file associated with previous releases of Mosaic v2.  In this
version, the security dll, Digest.dll, replaces Simple.dll.  The new INI
file will not support previous versions of Mosaic.  You will need to
rename the copy of the INI as the INI file to run previous versions
of Mosaic.


Previous Workgroup Web conflicts
--------------------------------
If you have installed a field test Workgroup Web kit in the past and
install this kit in the same directories, the old file WGW_TOOL.EXE
will be renamed WGW_TOOL.OLD.  WGW_DEMO.EXE will only run if the WGW_TOOL
file does not exist.


Invalid drive
-------------
In some very rare cases, install and configure will offer an initial
installation path which is ill-formed.  The drive letter is not
followed by a ":" as it should.  Please edit this path by inserting
the ":" should you wish to accept this path.



-----------------------------------------------------------------
Known Problems
-----------------------------------------------------------------

WIN32S - Video Driver Problem
-----------------------------
A characteristic of this problem is that on starting MOSAIC,
the screen is not properly drawn and the PC hangs.  While drawing
the initial screen, messages such as,

           Error!
           ERROR! (0x00000057 - 0xff11)
           Cannot bitblt memory bitmap to screen.

may occur. Once these errors have occurred, the system must be
rebooted.

To confirm this problem is related to WIN32S, follow these steps:

   1. Reboot your system and restart Microsoft Windows.

   2. Access the File Manager and move to the

                <windows>\system\win32s
                
      subdirectory.

   3. Double click on FREECELL.EXE.

      This runs the game FREECELL that Microsoft includes in the
      WIN32S distribution kit. FREECELL enables you to test the
      proper installation of WIN32S and its compatibility with
      your system.

If you run FREECELL and experience the same display problems you
saw when running MOSAIC, then there is an incompatibility
between your system and WIN32S. In most cases, the Super VGA mode
video driver is the source of the problem. You can verify this by
starting the Microsoft Windows SETUP program and changing the
video driver option to the standard VGA driver. If the system
works correctly, the problem is the video driver. In this case,
you should contact the manufacturer or supplier of your video
card and ask for a new driver that works with WIN32S.

You may also notice peculiar behavior with font clipping and other
visual oddities from time to time.  We have found that this too
is related to WIN32S and simply stopping and restarting
Windows can fix this.


WIN32S - Conflicts with MSVCRT20.DLL
------------------------------------
There have been reports where variants of MSVCRT20.DLL have the
same version number as the variant on this kit but for some reason,
are not compatible with WIN32S.  Should you find this a problem,
rename the MSVCRT20.DLL to some other name and re-install this kit
to install the version of MSVCRT20.DLL supplied with this kit.




DNETHEAPSIZE Message
--------------------
DNETHEAPSIZE is a variable used to determine the amount of
conventional ( 640K ) memory to be reserved for TCP/IP memory
buffers.  The number is incremented in steps of 4 and represents
the memory reserved in Kbytes (thousands of bytes).

If Windows displays a DNETHEAPSIZE message, follow these steps:

   1. Stop your Windows session.

   2. Edit your SYSTEM.INI file. Go to the section [386enh] and change
      the DNETHEAPSIZE value to the value suggested in the error message.
      Typical values range from 24 to 74. You should experiment to
      determine the value that works best for your system.

   3. Exit the editor and restart Windows.

You should exit and restart Windows after receiving a change
DNETHEAPSIZE size request even if you do not change the value
because the behavior of your system will be unpredictable until
you do so.

Note that increasing the value of DNETHEAPSIZE reduces the amount
of conventional ( 640K ) memory available for applications.
Also, the parameters NETHEAPSIZE ( Microsoft ) and DNETHEAPSIZE (
PATHWORKS ) control the size of the same memory area.  The
parameter with the largest value is used.  If making a change,
change DNETHEAPSIZE.

When running PWMOSAIC with PATHWORKS and Microsoft Windows 3.1,
typical values for DNETHEAPSIZE range from 24 to 74.  When
running PWMOSAIC with PATHWORKS and Microsoft Windows for
Workgroups, the value needed will typically fall in the range
48 - 78.  A higher value is needed when using Windows for Workgroups
as the Windows for Workgroups network uses this space as well.

In either case, you will need to experiment to determine the
value which works best for you.  It may be necessary to reduce
the number of applications running concurrently.


Windows 95 Restrictions
-----------------------
Filenames must conform to the DOS 8.3 specification when working with
Windows 95.  This limitation will be removed in the final release.


