   WELCOME TO WINBATCH 2016b!



   WinBatch is the Windows Batch Language that you can use to write
   real honest-to-goodness Windows batch files to control every
   aspect of your machine's operation.  There are more than hundreds
   and hundreds of different functions that allow you to do *anything* 
   with WinBatch!

   This package contains all the pieces you need to create batch files
   for Windows 2000/XP/2003/Vista/7/8/8.1/10/2008/2012.  

   The pieces are:

   WinBatch Interpreter      32-bit & 64-bit versions
   FileMenu                  32-bit or 64-bit version  
   PopMenu                   32-bit version
   WinBatch Studio           32-bit (32-bit & 64-bit debuggers)
   WIL Dialog Editor         32-bit

   This software package -- if you have the WinBatch+Compiler -- 
   also contains:

   WinBatch Compiler         32-bit & 64-bit versions


 

   ======================================================================
   SYSTEM REQUIREMENTS

   WinBatch requires an Intel X86, AMD X64 or compatible processor running 
   Microsoft Windows 2000/XP/2003/Vista/7/8/8.1/10/2008/2012.  
   WinBatch cannot be used on ARM based processors or versions of Windows
   earlier than Windows 2000.
																											  

*****************************************************************************
*****************************************************************************
*****************************************************************************
***                                                                       ***
***                 Converting scripts to the latest version              ***
***                                                                       ***
***    In general, our policy is to make new versions of WinBatch         ***
***    as compatible as possible with older versions of WinBatch,         ***
***    and to limit the occasions when we feel compelled to               ***
***    introduce what we term "breaking changes", where we change         ***
***    WinBatch in a way that may cause perfectly functioning scripts     ***
***    to no longer work correctly with the new version of WinBatch.      ***
***                                                                       ***
***    We've attempted to make a list of these changes that might         ***
***    break currently running scripts and to give you some               ***
***    background on the issues involved so that you can successfully     ***
***    modify your scripts to run under the latest version of WinBatch.   ***
***                                                                       ***
***                                                                       ***
***                                                                       ***
*****************************************************************************
***                                                                       ***
***                        Note for 2015B version.                        ***
***                                                                       ***
***    WinMacro, the WinBatch macro recorder, is now available as a menu  ***
***    option on PopMenu's main menu on Windows Vista/2008 and newer      ***
***    versions of the Windows operating system.                          ***
***                                                                       ***
***    WinMacro required extensive modifications to make it compatible    ***
***    with newer versions of Windows.  These changes mean WinMacro no    ***
***    longer supports Windows 2000 and also mean that while legacy       ***
***    macro archive files recorded with previous versions of WinMacro    ***
***    can still be play back on Window XP/2003, new macros cannot be     ***
***    added to the old archives.  In order to create new macros on       ***
***    Windows XP/2003 using the new WinMacro, a new macro archive file   ***
***    must be used.                                                      *** 
***                                                                       ***
***    Legacy archive file macros cannot be played back on Windows        ***
***    Vista/2008 and newer versions of the Windows operating system.     ***
***    However, the legacy macros can be converted to WIL scripts on XP   ***
***    and the resulting scipts can be used on Vista/2008 and newer.      ***    
***                                                                       ***
***                                                                       ***
*****************************************************************************
***                                                                       ***
***                        Note for 2013A version.                        ***
***                                                                       ***
***    Fixed several problems with the MousePlay function                 ***
***    incorrectly locating the mouse cursor on multi-monitor systems     ***
***    when using a window origin instead of a screen origin. Also        ***
***    fix problems that caused the function to use an invalid            ***
***    origin instead of the origin of the restored parent window         *** 
***    when the parent windows was minimized and a child window           ***
***    was specified. These are breaking change that may require          *** 
***    changing existing scripts that use the function.                   *** 
***                                                                       ***
***    Modified the legacy WinMacro application to reflect the            ***
***    multi-monitor fix in the MousePlay function.  This may require     ***
***    rerecording macros that were record using mouse coordinates        *** 
***    relative to a specific window instead of to the screen.            ***
***                                                                       ***
***                                                                       ***
*****************************************************************************
***                                                                       ***
***                        Note for 2010B version.                        ***
***                                                                       ***
***    IntControl 31 has been changed to enumerate only 64-bit Explorer   ***
***    windows on 64-bit versions of Microsoft Windows. Previously, the   ***
***    IntControl only enumerated 32-bit Explorer Windows on 64-bit       ***
***    versions of the operating system. This does not affect Windows 7   ***
***    or Windows 2008 R2 because the 64-bit versions of these operating  ***
***    systems do not display stand-alone 32-bit Explorer windows.        ***
***    However, 64-bit XP, Vista, Windows 2003, and Windows 2008 do so    ***
***    you may need to modify any scripts that rely on the IntControl to  ***
***    enumerate 32-bit Explorer windows on those systems.                ***
***                                                                       ***
***                                                                       ***
*****************************************************************************
***                                                                       ***
***                        Note for 2007C version.                        ***
***                                                                       ***
***    The StrInsert function was added in 2007B.  The original           ***
***    implementation was incorrect, and has been changed in 2007C        ***
***    If you used the StrInsert function in 2007B, you will need to      ***
***    revisit the code to adapt it to the now correct version.           ***
***                                                                       ***
*****************************************************************************
***                                                                       ***
***                                                                       ***
***                Converting scripts from 2004A and older.               ***
***                                                                       ***
***    In general, our policy is to make new versions of WinBatch         ***
***    as compatible as possible with older versions of WinBatch,         ***
***    and to limit the occasions when we feel compelled to               ***
***    introduce what we term "breaking changes" where we change          ***
***    WinBatch in a way that may cause perfectly functioning scripts     ***
***    to no longer work correctly with the new version of WinBatch.      ***
***                                                                       ***
***    Beginning with the 2004B version we introduced a number of         ***
***    enhancements to WinBatch revolving around OLE/COM automation       ***
***    and the ability to handle a richer set of variables, rather        ***
***    than the older WinBatch standard of integers, strings and          ***
***    floating point numbers.  In order to this to function, we had      ***
***    to make some obscure changes to some rarely used functions.        ***
***    Most WinBatch programmers are not even aware of these functions,   ***
***    much less even having used them.  Thus most scripts in existence   ***
***    will not need to be modified due to the changes introduced         ***
***    between the 2004A and 2004B versions.                              ***
***                                                                       ***
***    However, for those who may be affected...                          ***
***                                                                       ***
***    **** Breaking changes introduced in the 2004B version ****         ***
***                                                                       ***
***    1) The VarType() function modified.  With the addition of          ***
***    new variable types called "Variants", a new return code was        ***
***    added to the VarType() function and most returns from any          ***
***    OLE/COM function is now a Variant.                                 ***
***                                                                       ***
***    If you were using the VarType() function to determine a            ***
***    variable type returned my a COM/OLE function, you may need         ***
***    to revise your code.                                               ***
***                                                                       ***
***    2) The ObjectTypeGet() function has been modified to return        ***
***    a richer set of object types, including arrays.  WinBatch          ***
***    code that uses the ObjectTypeGet function may need to be           ***
***    examined.                                                          ***
***                                                                       ***
***    3) The handling of array data returned by COM/OLE functions        ***
***    has been modified to include native WinBatch support for           ***
***    COM/OLE arrays.  WinBatch code dealing with array data             ***
***    returned from COM/OLE functions may need to be examined to         ***
***    ensure compatibility.                                              ***
***                                                                       ***
***    4) Due to incompatibility reasons certain older extenders          ***
***    have been deemed "incompatible" with WinBatch.  Two of these       ***
***    extenders are old and not expected to be in widespread use.        ***
***    However one extender is current and may cause issues.  The         ***
***    "AddExtender" function will recognise these incompatible           ***
***    and flag an error.  The extenders are:                             ***
***                                                                       ***
***       wwwnt32i.dll   old  - all versions incompatible                 ***
***       wwctl32i.dll   old  - all versions incompatible                 ***
***       wwctl34i.dll   current -  20032 and older incompatible          ***
***                      Recommend using wwctl44i.dll instead             ***
***                                                                       ***
***    5) IntControl(83,...) is now obsolete. This intcontrol was used    ***
***    to specify the desired return type of various byte arrays from     ***
***    a COM/OLE function call.  Conversion is now either automatic or    ***
***    is accomplished by the BinaryAllocArray() function.                ***
***                                                                       ***
***                                                                       ***
***    6) The WMI_SCRIPTER program that was being discributed via         ***
***    the Tech Support Database was affected by the "breaking            ***
***    change" mentioned in item #1 above.  A new revised version of      ***
***    WMI_Scripter is now available.                                     ***
***                                                                       ***
***                                                                       ***
***                                                                       ***
*****************************************************************************
***                                                                       ***
***                                                                       ***
***                                                                       ***
***                                                                       ***
***                                                                       ***
***                                                                       ***
***                 Converting scripts older then 2002J                   ***
***                                                                       ***
***                                                                       ***
***                                                                       ***
***                                                                       ***
***      **** Breaking changes introduced in the 2002J version ****       ***
***                                                                       ***
***  1) In OLE/COM methods and properties that return an array of bytes   ***
***     The older versions of WinBatch would store this information into  ***
***     a Binary Buffer.  Starting in the 2002J version the data is       ***
***     stored into an array as a default.  IntControl(83... may be used  ***
***     to restore the previous behavior.  We expect maybe three people   ***
***     may be inconvenienced  by this change.                            ***
***                                                                       ***
***  2) The following functions now return an error if "delimiter" is     ***
***     more than a single character.                                     ***
***                                                                       ***
***       Arrayize                                                        ***
***       AskItemList                                                     ***
***       ItemCount                                                       ***
***       ItemExtract                                                     ***
***       ItemInsert                                                      ***
***       ItemLocate                                                      ***
***       ItemRemove                                                      ***
***       ItemReplace                                                     ***
***       ItemSort                                                        ***
***                                                                       ***
***                                                                       ***
***     Problems generally occur in scripts that used the two character   ***
***     sequence @CRLF as a delimiter.  What was really happening was     ***
***     that an @CR was used as a delimiter and the @LF was ignored.      ***
***     This caused hard to find script bugs.  Now the single character   ***
***     delimiter rule is enforced.  Many scripts can be fixed by merely  ***
***     changing the @CRLF to an @CR.                                     ***
***                                                                       ***
***                                                                       ***
***                                                                       ***
*****************************************************************************
***                                                                       ***
***                                                                       ***
***                                                                       ***
***      **** Breaking changes introduced in the 2001a version ****       ***
***                                                                       ***
***  1) In DiskFree and DiskSize, the items in "drive-list" can no        ***
***     longer be separated with spaces (in order to now support UNC's    ***
***     containing spaces). Vertical bars " | " or tabs will work.        ***
***                                                                       ***
***  2) In ItemCount, trailing delimiters are now significant.            ***
***     This means that the comma-delimited list "a,b,c," has 4 items     ***
***     in it.  Older versions of WinBatch reported 3 items in the list.  ***
***                                                                       ***
***  3) In ItemInsert, trailing delimiters are now significant.  This     ***
***     means that if you specify a blank item ("") and an offset of -1,  ***
***     a blank item will be added to the end of the list, even if the    ***
***     list already has a trailing delimiter.                            ***
***                                                                       ***
***  4) The following functions no longer add a trailing delimiter to     ***
***     the returned list (some of these are "legacy" functions that      ***
***     are no longer documented):                                        ***
***                                                                       ***
***         AskFileText                                                   ***
***         AskItemList                                                   ***
***         ItemSelect                                                    ***
***         RegQueryItem                                                  ***
***         TextBox                                                       ***
***         TextBoxSort                                                   ***
***         TextSelect                                                    ***
***                                                                       ***
***                                                                       ***
***  5) FileExist now returns @FALSE if the file name contains            ***
***     any '/' characters (this change was actually made in WB 99M).     ***
***                                                                       ***
***                                                                       ***
***  6) In WinBatch version 2001P the IconReplace function and            ***
***     IntControl 37 were modified in support of Windows XP.  Please     ***
***     see documentation for exact changes.  The most important          ***
***     problem is that if you use custom icons (as opposed to icons      ***
***     supplied with the compiler) you may have to re-draw them          ***
***     to work properly on XP and newer machines.                        ***
***                                                                       ***
***                                                                       ***
***                                                                       ***
*****************************************************************************
***                                                                       ***
***                                                                       ***
***                                                                       ***
***                                                                       ***
***      **** Breaking changes introduced in the 98a version ****         ***
***                                                                       ***
***                                                                       ***
***  1) Time functions return a 4 year date instead of a 2 year date      ***
***                                                                       ***
***  2)  Several functions that return a delimited list no longer         ***
***      return a trailing delimiter, standardizing the structure         ***
***      of a delimited list variable.  Unless you are manipulating       ***
***      lists outside of the standard functions (Item...) this           ***
***      should not cause a problem.                                      ***
***                                                                       ***
***  3)  Changed the way the following string sorting and comparison      ***
***      functions operate:                                               ***
***                                                                       ***
***         BinarySort                                                    ***
***         ItemSort                                                      ***
***         ItemSortNc                                                    ***
***         StrCmp                                                        ***
***         StriCmp                                                       ***
***         >, >=, <, and <= (operators)                                  ***
***                                                                       ***
***      Previously, they were sorting (or comparing) strings on a        ***
***      character-by-character basis.  They now perform a "word sort",   ***
***      which compares strings  based on their collation sequence.       ***
***      Hyphens and apostrophes are considered of minor importance,      ***
***      and all other non-alphanumeric characters are sorted before      ***
***      any alphanumeric character.  This type of sort is also           ***
***      called a "dictionary" sort, as the fields are sorted into        ***
***      the same order that they would appear in a dictionary.           ***
***                                                                       ***
***                                                                       ***
*****************************************************************************
*****************************************************************************
*****************************************************************************

 

   This package also contains assorted Microsoft compatible
   NETWORK EXTENDERS.  They are generally installed by default.  
   If you want the network extenders installed, the "Install 
   Network Extenders" checkbox must be checked during the setup 
   process.  If you missed installing the extenders, just re-run
   setup and try again.


   Extenders for Novell Netware and many additional Extenders may 
   also be found in the "Extenders" subdirectory on the CD-ROM and 
   also at our website.  Significant enhanced functionality is 
   available with the various extenders.

   You can install the optional WIL Extenders by running their 
   SETUP.WBTs (located in their respective directories on the CD), 
   after you have installed WinBatch.
 
   Each extender has its own detailed CHM file and a TXT file describing
   additions and changes.

   Additional information on these extenders (and the latest arrivals)
   is available from our technical database at:

           http://techsupt.winbatch.com 

   under the heading:  "WIL Extenders".


   WIL Extenders are special purpose DLLs to extend the usability and 
   friendliness of WinBatch.  Here's a PARTIAL list of some extenders: 



   ====================
   Control Manager Extender

   Perfect control over all Windows dialog boxes. See inside list boxes,
   interrogate check boxes, set radio buttons, handle the new tabbed
   dialogs. 


   ====================
   CpuInfo Extender

   CPU speed, benchmark and other CPU information extender. 



   ====================
   Huge Math Extender

   Performs arithmetic on huge (up to 2000 digit) numbers.


   ====================
   IP Address Grabber Extender

   Get the machine's IP Addresses


   ====================
   MAPI Extender

   Perform MAPI Operations

   Mostly for use with Microsoft Exchange

   ====================
   ODBC Extender

   Our ODBC extender. 
   Familiarity with ODBC required. 

   ====================
   Postie Extender

   The Ultimate Internet Email extender. Sends and receives POP3,
   IMAP4, and NNTP (newsgroup) email. Able to send an receive mime
   or uuencoded attachments.


   ====================
   Printer Control Extender

   Assists in working with printer drivers. Sets default printer. Changes
   printer properties, Installs and removes printers, etc.

 
   ====================
   Process Information Extender

   Retrieve information about processes and modules.

 
   ====================
   RAS Connectoid Extender

   Create, manage, modify, rename and copy the Dialup RAS
   "connectoids" used in dial-up networking.


   ==================== 
   Registry Search Extender

   Registry Searcher. This extender, in combination with build-in WIL
   Registry function and perform a search and replace of most registry
   items.


   ====================
   File Search Extender

   Find files. Find data in files. Traverse directories. High speed file and
   text search engine.  

   To copy, move, or delete file and directory structures, see the Shell
   Operations extender

 
   ====================
   Serial Port Extender

   Talk to serial ports. Communicate with modems, X-10 household
   controllers, lab equipment, pretty much any serial device. Script BBS
   sessions. Does X/Y/Z-modem transfers. Write a phone dialer. Get your
   stock quotes. No need to try scripting HyperTerminal, do it directly
   with this extender. 


   ====================
   Shell Operations Extender

   Performs Explorer-style file operations with animated graphics. Can
   also copy, delete, and move entire directory structures. Also has a
   simple Progress bar and a MessageBox that will timeout!


   ====================
   WILX Utility Extender 

   Various Utility functions

   Note: WILX is already in the main WinBatch ZIP file. A separate
   download is not usually required.


   ====================
   WinInet Extender

   Use Windows built-in services to grab web pages (SSL too!) FTP and
   Dial-up networking. Requires Windows 98/ME/2000/XP or at least MSIE
   4.0 installed. 

 
   ====================
   WinSock Extender

   Our older Internet extender. Send Internet text-only email, grab web
   pages, automate FTP sessions, and more. Supports direct access to
   tcp/ip sockets. Includes proxy/firewall support  

   For full email support see the Postie Extender. For better http://, https://
   and ftp support see the WinInet extender.

 
   ====================
   Zipper Extender 

   ZIP and UNZIP files.





   Improvements from previous versions

   The file "The list of Fixes and Improvements.txt" details the 
   many bug fixes and enhancements that have been made to the 
   program since many previous releases.





   About the WinBatch Compiler

   Also available is our "WinBatch+Compiler," (if you have not  
   purchased it yet).  With the WinBatch+Compiler, you can turn 
   your WBT files into standalone EXE files that you can distribute 
   on a royalty-free basis.

   Have a BIG network?  Want all your users to run your WBT files?
   Compile the WBT files with the WinBatch Compiler and put the
   EXEs up on the server.

   Making specialized WinBatch files for clients?  Don't want them
   modifying your files?  Just compile the WBT files, and give the
   EXEs to your client.

   Are you the "corporate guru"?  Get a compiler.  Compile those WBT
   files and hand them out like candy.

   The WinBatch Compiler, a separate product from the WinBatch
   Interpreter contained in these files, is available for $495.00,
   plus shipping, if applicable.  The WinBatch Compiler includes a
   copy of WinBatch.  In addition, if you buy a copy of WinBatch, you
   have 90 days to upgrade to the Compiler and just pay the difference
   in price (plus shipping).





   HOW TO INSTALL WINBATCH


   Use our SETUP.EXE program, which will copy the files for you
   and install a WINBATCH Start Menu or Program Manager group.

   To use our SETUP.EXE program...  


     1) Close down all extraneous Windows applications.

     2) Double-Click on the SETUP.EXE program

     3) When the setup program asks for a directory, specify initial
        directory, or accept the given default.


   NOTE:  If you are updating from a previous version, and made any of the
          WinBatch files READ-ONLY, remove the read-only attribute from
          the files before running setup.
          (Or else the setup process may hang)



   WinBatch can run in English, French, German, and "Val Speak".
   The strings are controlled by the WWWDLANG.* files. If you
   just launch WinBatch by itself, it will then automatically
   run the "default.wbt" file.  The default.wbt file has a number
   of buttons allowing you to perform various operations. Select
   the "Advanced Options" button,  A new small dialog should appear.
   Select the "Foreign Language Support" button to select a
   language.  If a particular string has not yet been translated
   to the selected language (and there always are some) it will
   appear in English.



   An order form may be found in the WinBatch help file.  
   Once you are viewing the order form, you can then select
   the Print button to obtain a hard copy.  





 The following information may be found below:

    a) Information on our fully functional demos and our
       "Registration Reminder" screens.

    b) A basic, concise explanation of our disclaimers.

    c) Installation instructions for our automated installation
       program. 

    d) Generic uninstall instructions.

    e) Our update policy.

    f) On-line support.

    g) The long, drawn out legalese section, software license
       information, limited warranty, trademarks, etc.

    h) Information on other products that we offer.

    i) Ordering information.

    j) How to find the Order Form.

















                   REGISTRATION REMINDERS

 Unlicensed copies of Wilson WindowWare products are 100% fully
 functional.  We make them this way so that you can have a real
 look at them, and then decide whether they fit your needs or
 not.  Our entire business depends on your honesty.  If you use
 it, we expect you to pay for it.  We feel that if we treat you
 well, you will treat us well.  Unlicensed copies of our 
 products do have a registration reminder screen that appears
 whenever you start the program.  This shouldn't really affect
 your evaluation of our software.

 We're sure that once you see the incredible quality of our 
 software, you will dig out your credit card, pick up the phone,
 call the nice people at our 800 number and register the
 software. 

 If you work for a large corporation, you can purchase most of
 our products the same way you buy your retail software.  Just
 send the purchase request up the line.  Most all the corporate
 software suppliers purchase considerable volumes from us on a 
 regular basis.

 When you pay for the software you like, you are voting with
 your pocketbook, and will encourage us to bring you more of the
 same kinds of products.  Pay for what you like, and then, more
 of what you like will almost magically become available.


                        LEGAL MATTERS

 Of course the usual disclaimers still apply.  We are not 
 responsible for anything at all.  Nothing.  Even if we are held
 responsible, the limit of our liability is the licensing fees
 you paid.  The full text of our license agreement is found near
 the bottom of this file. 
















                 HOW TO INSTALL THIS SOFTWARE

  Use our snazzy setup program...

        1) Close down all extraneous Windows applications.  
           (You do have to be in Windows to run SETUP.EXE)

        2) Double-Click on the SETUP.EXE or use the Software
           install facility (if available) in Control Panel.

        3) When the setup program asks for a directory, specify
           an initial directory, or accept the given default.      

        4) When the screen comes up that asks you what you want
           to install, do your selections, then hit the NEXT 
           button to continue. If you want to install Network 
           extenders or non-English language support, this is 
           your opportunity.


 





                    UN-INSTALL INFORMATION

 This software may be uninstalled via the uninstall option
 in the Control Panel Add/Remove software dialog, or by running
 the uninstal.exe program in the WinBatch/System subdirectory.  If 
 you simply delete all the files first, you will not be able to
 run the uninstall program and there may still be traces of the
 program in various places on the system.


















                        UPDATE POLICY



Introducing maintenance subscriptions
-------------------------------------

Beginning with the 2003 versions of our products, Wilson WindowWare is
introducing a new licensing procedure for our software updates.  In the
past, we have released major new versions every few years which
required an upgrade fee, and periodic minor versions which were free for
those who had already purchased the latest major version.  This system had a
couple of drawbacks: it penalized users who purchased a product late in the
cycle, and it discouraged us from adding new features on an ongoing basis.
Therefore, we have decided to switch to a maintenance subscription system.


How does it work?
-----------------

When you purchase a new copy of one of our products, your purchase price
will include a one-year maintenance subscription.  During that year, you
will be entitled to download and use any new versions of that product which
are released, free of charge.  At the end of the year, you will have the
option to renew your subscription for an additional year.  If you choose not
to renew your subscription, you will be able to continue to use the versions
which were released prior to your maintenance subscription expiration, but
you will not be licensed to use future versions of the product.


Will the software I buy stop working after the year is up?
----------------------------------------------------------

NO!!!  The licensing period is based on the date that the software was
released, not on the current calendar date.  If you buy a product on Jan. 1,
2003, you will be licensed to use any versions of that product which are
released in 2003.  If you choose not to renew your maintenance subscription,
then you won't be licensed to use new versions which are released after
that.  But you will be licensed to use the 2003 versions forever.


What about existing customers?
------------------------------

If you purchased one of our products in 2001, you have a maintenance
subscription for that product which expires at the end of Feb. 2003.

If you purchased one of our products in 2002, you have a maintenance
subscription for that product which expires at the end of Jan. 2004.

If you purchased an older version of one of our products, you do not have an
active maintenance subscription.  You may upgrade to the current version of
the product for a discounted price, depending on the version that you have.


What day does my maintenance subscription expire?
-------------------------------------------------

Maintenance subscriptions always expire on the last day of the specified
month.  If you purchase a new product in Jan. 2010, your maintenance
subscription for that product will expire at the end of Feb. 2011 (we give
an additional month to allow for shipping time).  If you renew your
maintenance subscription, it will be extended to the end of Feb. 2012.


What happens when I renew my maintenance subscription?
------------------------------------------------------

When you renew your maintenance subscription, you will receive a new license
code which will allow you to download and use an additional year's worth of
releases.  In addition, you will receive a package with the current version
of the software and the latest printed manuals - assuming you do not select
the "License Only" shipping option available.


Do I have to wait until the expiration date before I can renew?
---------------------------------------------------------------

No.  You may renew your maintenance subscription at any time during the year
before the expiration date.  No matter how far before the expiration date 
you renew, your existing maintenance subscription will be extended for a full
additional year.


What if I want to renew my subscription after it has expired?
-------------------------------------------------------------

You may renew your maintenance subscription retroactively after it has
expired.  However, you will first have to pay for the period of time between
the expiration date and the current date.  For example, if your maintenance
subscription expires at the end of Feb. 2004 and you choose not to renew it,
but then in Oct. 2004 you decide to resume your maintenance subscription,
you would have to pay a pro-rated amount for the months between Feb. 2004
and Oct. 2004 to bring your subscription up to date, and then pay for an
additional year of maintenance from Oct. 2004 to Oct. 2005.  Your new
maintenance subscription expiration date would then be Oct. 2005, and you
would receive a new license code which would be valid until then.



                      ON-LINE SUPPORT

 Wilson WindowWare has on-line support!

 Wilson WindowWare lives on the INTERNET. We maintain a
 World Wide Web Server and an anonymous ftp site

    WWW URL    http://www.winbatch.com

 Tech support database is available at
  
               http://techsupt.winbatch.com

 and our tech support forum -- where you can post questions and code --
 is available via a link from our Tech Support database.













                     THE LEGALESE SECTION

 WINBATCH          Copyright © 1991-2016 by Wilson WindowWare, Inc
 WINBATCH+COMPILER Copyright © 1991-2016 by Wilson WindowWare, Inc
 WEBBATCH          Copyright © 1996-2016 by Wilson WindowWare, Inc



                     SOFTWARE LICENSES
                SHAREWARE LICENSE - END USER

 Wilson WindowWare software is not and has never been public
 domain software, nor is it free software. 

 Non-licensed users are granted a limited license to use our
 software on a 21-day trial basis for the purpose of determining
 whether the software is suitable for their needs.  Any use
 of our software, except for the initial 21-day trial, requires
 registration.  The use of unlicensed copies of our software,
 outside of the initial 21-day trial, by any person, business,
 corporation, government agency or any other entity is
 strictly prohibited. 


 SHAREWARE LICENSE - FOR DISTRIBUTION OF SHAREWARE FILES,
 USER GROUPS, BBS's, ONLINE SERVICES, SHAREWARE VENDORS, and
 OTHERS

 A limited license is granted to copy and distribute our
 shareware software only for the trial use of others, subject to
 the following limitations:

  1)    The software must be copied in unmodified form, complete
        with the file containing this license information.

  2)    The full machine-readable documentation must be included
        with each copy.

  3)    Our software may not be distributed in conjunction with
        any other product without a specific license to do so
        from Wilson WindowWare.

  4)    Vending of our software products in retail stores (by
        "shareware rack vendors") is specifically prohibited
        without prior written authorization.

  5)    No fee, charge, or other compensation may be requested
        or accepted, except as authorized below:

     A) Non-profit user groups may distribute copies of the our
        products to their members, subject to the above
        conditions, without specific permission.  Non-profit
        groups may collect a disk duplication fee not to exceed
        five dollars.

     B) Operators of electronic bulletin board systems (sysops)
        and web site operators (webmasters) may make our products 
        available for downloading only as long as the above 
        conditions are met.  An overall or time-dependent charge 
        for the use of the bulletin board system or web site is 
        permitted as long as there is not a specific charge for 
        the download of our software.

     C) Mail-order vendors of shareware software approved by
        the ASP may distribute our products, subject to the
        above conditions, without specific permission.  Non-
        approved vendors may distribute our products only after
        obtaining written permission from Wilson WindowWare.
        Such permission is usually granted.  Please write for
        details (enclose your catalog).  Vendors may charge a
        disk duplication and handling fee, which, when pro-rated
        to each individual product, may not exceed eight
        dollars.








 LICENSED COPIES OF OUR SOFTWARE ARE GOVERNED BY THE FOLLOWING:

    THIS SOFTWARE IS NOT FOR SALE: The software is subject
    to the following license terms and conditions.
    
    SOFTWARE LICENSE granted, when required fees paid, by 
    Wilson WindowWare, Inc., a Washington corporation, with 
    its mailing address at 5421 California Ave. SW. Seattle,
    WA 98136. The software contained in this package is 
    licensed to you as the end user. It is not sold.
    
    1.0 The software contained in this package 
    (hereafter referred to as "the Software") is copyrighted 
    material owned by Wilson WindowWare, Inc. Payment of the
    single copy license fee authorizes one named person to 
    use the Software on one computer provided this copyright
    is not violated and provided the rules outlined herein 
    are observed.
     
    1.1 One person may use the Software on any single 
    computer. This license can be transferred only once in 
    any twenty-four hour period. You must pay for additional
    copies of the Software if more than one person uses it 
    during any 24 hour period of time, or if the Software 
    is used on two or more computers. Neither concurrent use
    on two or more computers, nor use by more than a single 
    individual on a network is permitted without 
    authorization and payment of other license fees.
     
    1.2 You may make copies of the software for backup 
    purposes, as long as all such copies, along with the 
    original, are kept in your possession or control.
    
    1.3 You may not make any changes or modifications to 
    the Software, including, but not limited to, decompiling,
    disassembling, or otherwise reverse engineering it. You 
    may not rent or lease it to others. You may not use it 
    on a computer network if more than one user can use it 
    during any one 24 hour period of time.

    1.4 If you have licensed the WinBatch+Compiler product
    you may compile scripts and, with the exception of
    scripts that interpret or attempt to interpret the
    script language, provide these compiled scripts 
    (and any required DLLs) to any number of end users 
    without additional licenses or payment of additional fees.



                    LIMITED WARRANTY

     
    EXCEPT AS PROVIDED ABOVE, WILSON WINDOWWARE DISCLAIMS
    ALL WARRANTIES,  EXPRESS OR IMPLIED, INCLUDING,BUT NOT
    LIMITED TO IMPLIED WARRANTIES OF MERCHANTABILITY AND 
    FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THE 
    PRODUCT. SHOULD THE PROGRAM PROVE DEFECTIVE, THE 
    PURCHASER ASSUMES THE RISK OF PAYING THE ENTIRE COST 
    OF ALL NECESSARY SERVICING, REPAIR, OR CORRECTION AND 
    ANY INCIDENTAL OR CONSEQUENTIAL DAMAGES. 
    
    IN NO EVENT WILL WILSON WINDOWWARE BE LIABLE FOR ANY 
    DAMAGES WHATSOEVER (INCLUDING WITHOUT LIMITATION DAMAGES
    FOR LOSS OF BUSINESS PROFITS, BUSINESS INTERRUPTION, LOSS
    OF BUSINESS INFORMATION AND THE LIKE) ARISING OUT OF THE
    USE OR THE INABILITY TO USE THIS PRODUCT EVEN IF WILSON 
    WINDOWWARE HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH 
    DAMAGES.
     
    THIS SOFTWARE IS NOT DESIGNED OR INTENDED FOR USE OR 
    RESALE AS ON-LINE CONTROL EQUIPMENT IN HAZARDOUS 
    ENVIRONMENTS REQUIRING FAIL-SAFE PERFORMANCE, SUCH AS 
    IN THE OPERATION OF NUCLEAR FACILITIES, AIRCRAFT 
    NAVIGATION OR COMMUNICATION SYSTEMS, AIR TRAFFIC 
    CONTROL, DIRECT LIFE SUPPORT MACHINES, OR WEAPONS 
    SYSTEMS, IN WHICH THE FAILURE OF THE SOFTWARE COULD 
    LEAD DIRECTLY TO DEATH, PERSONAL INJURY, OR SEVERE 
    PHYSICAL OR ENVIRONMENTAL DAMAGE ("HIGH RISK ACTIVITIES"). 
    
    WILSON WINDOWWARE SPECIFICALLY DISCLAIMS ANY EXPRESS OR
    IMPLIED WARRANTY OF FITNESS FOR HIGH RISK ACTIVITIES.
     
    Use of this product constitutes your acceptance of this 
    agreement and subjects you to its contents.
     
    U.S. GOVERNMENT RESTRICTED RIGHTS
    Use, duplication, or disclosure by the Government is 
    subject to standard shrink-wrapped software restrictions.
    Contractor/manufacturer is Wilson WindowWare, Inc. 
    5421 California Ave SW / Seattle, WA 98136




                    TRADEMARKS

  Microsoft and MS-DOS are registered trademarks of the
  Microsoft Corporation.
  Windows is a trademark of Microsoft Corporation.

  WinBatch          is a registered trademark of Wilson WindowWare, Inc.  
  WebBatch          is a registered trademark of Wilson WindowWare, Inc.
  WinBatch+Compiler is a trademark of Wilson WindowWare, Inc.  









              *** WILSON WINDOWWARE PRODUCTS ***


 WinBatch        - Write your own Windows Batch Files!  Dialogs,
                   automatic program control, and powerful data
                   manipulation lets you control your Windows.
                   A must for the power user.  Includes FileMenu
                   and PopMenu.                           $99.95

 WinBatch        - NOT A SHAREWARE PRODUCT.  The WinBatch
    +              compiler can compile WinBatch batch files into
 Compiler          standalone EXE files that may be distributed
                   on a royalty free basis.  Great for networks
                   and corporate gurus.  Compile your WBT files
                   and then hand them out like candy.    $495.00

 WebBatch        - Quick and easy scripting language for Web
                   Servers running Windows NT.  60-day FREE eval
                   copies available.  Purchase includes a FREE
                   copy of WinBatch.  Get an eval copy from:
                   
                   http://www.webbatch.com        $295





                    ORDERING INFORMATION

 Licensing our products brings you wonderful benefits.  Some of
 these are:
    - Gets rid of that pesky reminder window that comes up when
      you start up the software.
    - Insures that you have the latest version of the product.
    - Encourages the authors of these programs to continue 
      bringing you updated/better versions and new products.
    - Gets you on our mailing list so you are occasionally
      notified of spectacular updates and our other Windows
      products.
    - And, of course, our 90-day money back guarantee.


  An order form may be found in the application help file.  
  Once you are viewing the order form, you can then select
  the File - Print Topic menu item to obtain a hard copy.




          
          
          
          
          
          
          
          
          
          


