To Funcky II owners:


Since ProVision:Windows (PVW) uses Funcky II's Notepad, both
PWFUNCS.LIB and PWKERNEL.LIB contain code from the Funcky II
library.  If you using other functions from Funcky II (and
therefore need to link in the Funcky II library) you should
link in both PWFUNCS.LIB and PWKERNEL.LIB before the Funcky
II libraries.  This will insure that the Notepad code
contained within the PVW libraries will be linked in instead
of the Notepad code in the Funcky II libraries.

In some cases the Notepad code contained in the
ProVision:Windows libraries may be more up-to-date than your
copy of Funcky II.  It is for this reason that we recommend
you make sure the PVW Notepad code is linked in.  If you
have a reason for removing the Notepad code from the PVW
libraries, you can do so with the PWFUNCS.SUB and
PWKERNEL.SUB autoresponse files.  You can use Funcky II's
FLIB.EXE utility with these autoresponse files in the
following manner:

FLIB PWFUNCS.LIB  @PWFUNCS.SUB

FLIB PWKERNEL.LIB @PWKERNEL.SUB


Please note that PWKERNEL.LIB contains a module named
PWGTDRIV.OBJ which is a replacement for Funcky II's
GTDRIVER.OBJ.  There is no need for you to link in Funcky
II's GTDRIVER.OBJ and, in fact, linking it in could slightly
reduce performance.


Some of the Funcky II functions cause the external symbol
___funstackused to be declared.  This symbol causes the
stack size of the Clipper application to increase which is
necessary for some of the Funcky II functions, but this is
not necessary for the Notepad code contained within PVW.  It
is for this reason that PWKERNEL.LIB contains a module named
PWFUNSTA.OBJ which resolves the ___funstackused symbol
without increasing the stack size.  It could be possible
that using other functions from the Funcky II library could
cause stack faults since the stack size is not increased.
If this happens you can remove this module with the FLIB.EXE
command:

FLIB PWKERNEL.LIB -PWFUNSTA


