
PWMOSAIC Release Notes:                    ( July 16, 1994 )
----------------------

Installing TCP/IP for PWMOSAIC
------------------------------
When installing TCP/IP, using a Custom Install, please ensure
that you select both TCP/IP and PATHWORKS Windows Network when
working in the "Select PATHWORKS Services for Workstation" page.

This will ensure that all files needed by TCP/IP and PWMOSAIC are
available on your local system and allow you to use PWMOSAIC even
if the PATHWORKS system service is not be available.


Installing PWMOSAIC
-------------------
The version of WIN32S (v1.15a) included with PWMOSAIC must be
installed.  Any previous version of WIN32S must be replaced
with this version.

The symptom of using an earlier, incompatible version of WIN32S
is the repeated request to increase the value associated with
the DNETHEAPSIZE parameter specified in the [386enh] section
of your SYSTEM.INI file located in your windows directory.
PWMOSAIC will not start and no value of DNETHEAPSIZE will
satisfy the request.  Microsoft has fixed a problem with
WIN32S starting in releasing version 1.15a

Microsoft's SETUP.EXE program has some deceptive error message
reporting which you should note.  In particular, you can get
messages indicating share violations and others in situations
which are really reporting a situation of "disk full".
Check the amount of free space on your disk if you get an
unusual error message while installing PWMOSAIC.


WIN32S - Video Driver Problem
-----------------------------
A characteristic of this problem is that on starting PWMOSAIC,
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 situation, reboot your system and restart
Microsoft Windows.  Using File Manager, move to the PWMOSAIC
subdirectory and double click on FREECELL.EXE. This will run the
game FREECELL which Microsoft includes in their WIN32S distribution
kit to enable the user to test the proper installation of WIN32S
and its compatibility with your system.

If the system again breaks in the same way running FREECELL, then
there is an incompatibility between your system and WIN32S.

In most instances, we have found that the problem is with the
Super VGA mode video driver. You can verify this by starting the
Microsoft Windows SETUP program and changing the video driver
back to the standard VGA driver.  If the system then works, the
problem is definitely with the video driver. In this case, you
will need to contact the manufacturer or supplier of your video
card and ask for a new driver which works with WIN32S.


GROWSTUB Problem
----------------
Should you receive the following message:

        GROWSTUB
        An error has occurred in your application.
        If you choose ignore, you should save your work in a new file.
        If you choose close, your application will terminate.

Also, should you choose to "close" this window, you may also get
the following message:

        Application Error
        GROWSTUB caused a General Protection Fault in
        module POINTER.DLL at 0001:0F64

After closing that message, everything should work as if no
problem occurred.

This problem can remedied by going to the [Windows] section of
your WIN.INI file and removing the line

                c:\mouse\pointer.exe


DNETHEAPSIZE Message
--------------------
DNETHEAPSIZE is a variable used to determine the amount of 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).

A DNETHEAPSIZE message means that you should stop your Microsoft
Windows session as the next step, edit your SYSTEM.INI file in
the [386enh] section and change the DNETHEAPSIZE value set to the
value suggested. You should exit and restart Microsoft Windows
after receiving a change DNETHEAPSIZE size request, even if you
do not change this value, as the behavior of the system will
now be unpredictable.

Note that increasing the value of DNETHEAPSIZE reduces the amount
of 640K memory available to applications.

Typical values used range from 24 to 74.  You will need to
experiment to determine the value which works best for you.


INI File Options
----------------
Informing PWMOSAIC of Viewers and Players
-----------------------------------------
The PWMOSAIC.INI file will need to be modified to reflect the
way that your viewers are installed.  The basic process for
informing PWMOSAIC of an available player, for example, is,

	[Viewers]
	...
	TYPE9="audio/basic"
	...
	audio/basic="c:\<somepath>\wplany.exe %ls"
	...

	[Suffixes]
	...
	audio/basic=.au



Launching Viewers and Players
-----------------------------
PWMOSAIC has option on how files destined for a viewer are
treated.  The default action is to offer the user the
opportunity to name the file and where it is saved prior
to starting a viewer.  The file is permanent until deleted
explicitly by the user.

Alternative, changing the following [Viewers] option in 
PWMOSAIC.INI,

	Use_Temporary_Files=no

to "yes" will result in a temporary file being created
automatically and the viewer started directly.  When
PWMOSAIC is terminated, that temporary file (and all
other similarly created files) are deleted.  If
there is an abnormal termination, these files, which can be
quite large, are not deleted.

These temporary files are saved in the directory identified
by your TEMP environmental variable declared in AUTOEXEC.BAT.


