
                        WGT 5.1 for Watcom C/C++ 10.x
                                 DEMO VERSION
                             by Egerter Software

Update: You can now contact us at egerter@egerter.com.  Our new web site
is http://www.egerter.com.


This release of WGT 5.1 is for DEMO purposes only and may not be used for
profit in any way.  It contains a limited set of instructions and a lack of
documentation.  Example files which cannot be compiled with this reduced
version have been provided in an executable form.

Additional features found in commercial version:
------------------------------------------------
- 9 other library files including sprite animation, 3d math, drop-down
  menus, scrolling engine, joystick commands, FLI/FLC animation routines,
  file selector, serial communications, VESA SVGA system
- full source code for 3d rendering engine, drop-down menu library,
  scrolling engine, sprite library, communications library and GIF routines
- 3.6 megabyte graphics and sound demo (called FLIGHT) written with
  WGT 5.0 for an international competition (the demo won 3rd place)
- shareware version of a 32-bit protected mode digital sound system for
  playing music and mixing sound effects real-time (DSIK 2.0)
- license agreement
- printed 405 page manual including:
        a) Programmer's Guide
        b) Sprite Editor
        c) Map Maker
        d) Reference manuals for all 10 libraries
        e) Printed source code for scrolling library, menu library,
           sprite library and 3d rendering engine

To order, please fill out the enclosed ORDER.TXT file and send proper payment
(instructions are on the form). Orders will be shipped via courier for
customers outside of Canada and via Canada Post otherwise.

******************************************************************************
Installing the Software
-----------------------

At the DOS prompt, type INSTALL and the installation program will begin.
This program will copy all or part of the toolkit to your hard drive.
It will create a directory called WGT5 in the root directory. Each part of
the toolkit will have a subdirectory in the WGT5 directory.

Follow the on-screen prompts to complete the installation.

This DEMO version contains the following areas:

******************************************************************************
Making Example Files
--------------------

        If an executable version of a source code file is not present, then
you must build one using the included batch files. Most batch files can simply
be run to produce the EXE, but the MAKE.BAT in the WGT5\EXAMPLES must be used
as:     MAKE wgt04       or     MAKE wgt12  for example.

Files in the main example directory are numbered from 01 to 70. There is one
exception to this rule, because WGT68 has its own directory and contains 5
versions of the program.

******************************************************************************
**** ATTENTION WGT 4.0 Users ****
    Major Changes from WGT 4.0
=================================

New structures:

extern struct {
  short xres;                   /* Horizontal screen resolution          */
  short yres;                   /* Vertical screen resolution            */
  short videomode;              /* Current videomode                     */
  int   videobanksize;          /* Size of memory bank (VESA)            */
  short (*bankswitch)(short);   /* Pointer to bank switch routine (VESA) */
} WGT_SYS;

        This structure contains a few important statistics which can be
read by the user. DO NOT change these variables yourself. VIDEOMODE does
not change when using wsetmode, only with vga256 and wvesa_init.



typedef struct {
  short but;                    /* Mouse button being pressed  */
  short mx;                     /* Horizontal mouse coordinate */
  short my;                     /* Vertical mouse coordinate */
} callback_data;
extern callback_data mouse;

        All mouse variables are now found within this structure. 



        The scrolling library has been dramatically altered. Many routines
now use different parameters.  The basic command order has been maintained
but should be verified against the new examples.

******************************************************************************
CONVERTING TURBO/BORLAND C PROGRAMS TO WATCOM

To convert previous WGT programs to Watcom, simply do a search and replace on:

Search for              Replace with            *** Order is important!
==========              ============
int                     short
long                    int
but                     mouse.but
mx                      mouse.mx
my                      mouse.my

far                     NOTHING (remove all FAR references in code)



Functions Which Have Been Eliminated:
=====================================

All EMS functions
All SB routines
wdetectcpu

******************************************************************************

Library File Changes:
=====================

All library files have been renamed to include WC indicating Watcom.

WFLIC_WC.LIB   -now uses memory instead of EMS, so check the include file
                for variable names and defines

Old name                        New Name
********                        ********
WGT4.LIB                        WGT5_WC.LIB
WSPR.LIB                        WSPR_WC.LIB
WGTJOY.LIB                      WJOY_WC.LIB
WGTSCROL.LIB                    WSCR_WC.LIB
WGT3D.LIB                       WGT3D_WC.LIB
WFILE.LIB                       WFILE_WC.LIB
WGTMENU.LIB                     WMENU_WC.LIB
WGTFLIC.LIB                     WFLIC_WC.LIB
WGTVESA.LIB                     WVESA_WC.LIB


******************************************************************************

Other Notes
===========

- wsetscreen now works with ANY block. Clipping variables are set to match
  the image dimensions.

- many DOS and BIOS functions use different structures and parameters than
  the Turbo/Borland versions. Be sure to check the manuals when trying to
  find compatibility errors (compiler warnings).

- All image loading functions are capable of handling ANY size picture as
  long as the machine has enough memory to hold it. Our machines have
  8 megs of RAM and therefore a 2900x2900 pixel image is out of reach, but
  a 2800x2800 pixel image is possible (as long as program size is small :)



