   WELCOME TO WINBATCH 2022a!



   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 XP/2003/Vista/7/8/8.1/10/11/2008/2012/2016/2019.  

   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 XP/2003/Vista/7/8/8.1/10/11/2008/2012/2016/2019.  
   WinBatch cannot be used on ARM based processors or versions of Windows
   earlier than Windows XP.
																											  

*****************************************************************************
*****************************************************************************
*****************************************************************************
***                                                                       ***
***                 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 2021C version.                        ***
***                                                                       ***
***    This version of WinBatch is the first to offer native support for  ***
***    64-bit integers. While the impact on an existing script will be    ***
***    very minimal there is some possibility a script could contain an   ***
***    integer manifest constant that is greater than the 2147483647 or   ***
***    less than -2147483648. In such instances previous versions of      ***
***    WinBatch allows an integer overflow or underflow to occur. This    ***
***    resulted in an inaccurate representation of the integer's true     *** 
***    value when the manifest constant is assigned to a variable, passed ***
***    to a function, or passed to a UDP. If a WIL script relies on the   ***
***    inaccurate representation to operate, it may fail because the      ***
***    integer is now represented accurately as 64-bit value.             ***
***                                                                       ***
*****************************************************************************
***                                                                       ***
***                        Note for 2019B version.                        ***
***                                                                       ***
***    As of version 2019B WinBatch no longer supports Windows version    ***
***    2000.  WinBatch 2019A and older version are available for use on   ***
***    Windows 2000 with a current WinBatch+Compiler license.             ***
***                                                                       ***
***    "Cin" and "Cout" are now WinBatch Console commands and can no      ***
***    longer be used as WIL script variable names. Any scripts using     ***
***    these reserve words as variable names will need modification.      *** 
***                                                                       ***
***                                                                       ***
*****************************************************************************
***                                                                       ***
***                        Note for 2018B version.                        ***
***                                                                       ***
***    This is the first release of 64-bit WinBatch that is large address ***
***    aware. Being large address aware enables 64-bit WinBatch to access ***
***    more than the 2 gigabytes of virtual memory that 32-bit WinBatch   ***
***    is limited too.  This means more room for text strings, WIL        ***
***    arrays, and binary buffers!  Most of the necessary changes to      ***
***    WinBatch are invisible to WIL scripts.  However, functions that    ***
***    accept or return raw memory addresses did need modification to     ***
***    support memory addresses greater than the maximum allowed 4 byte   ***
***    signed integer. This can affect any scripts that perform           ***
***    mathematical operations on raw memory address because WinBatch     ***
***    arithmetic operators only support integer values that can be       ***
***    represented in 4 bytes. Generally, this will not have any impact   ***
***    on scripts using these these function because mathematical         ***
***    operations on raw memory address are uncommon. The functions       ***
***    affected by this change are the following:                         *** 
***                                                                       ***
***      DllStructAlloc - optional second parameter is a memory address.  ***
***      IntControl 32  - p2 accepts a memory address.                    ***
***      IntControl 42  - return value is a memory address.               ***
***      IntControl 98  - p2 = 2 return value is a memory address.        ***
***                                                                       ***
***    It is unlikely that any script changes will be necessary but       ***
***    scripts executed using 64-bit WinBatch or compiled as 64-bit       ***
***    executables should be checked to ensure they are using these       ***
***    functions in a way that is compatible with this and future         ***
***    versions of 64-bit WinBath.                                        ***
***                                                                       ***
***    In addition, four WIL 64-bit extenders required modification to    ***    
***    handle large addresses.  You must use a large address aware        ***
***    versions of these extenders for this and all future versions of    ***
***    64-bit WinBatch and scripts compiled as 64-bit executables.  The   ***
***    four extenders along with their minimum required version are the   ***
***    following:                                                         ***
***                                                                       ***
***       64-Bit Extender                  Minimum Version                ***
***    ODBC (wwodb64i.dll)                      44018                     ***
***    Win32 Network (wwwnt64i.dll)**           39025                     ***
***    WinInet (wwint64i.dll)                   44088                     ***
***    WinSock (wwwsk64i.dll)                   44007                     ***
***                                                                       ***
***    ** This extender is in the main WinBatch 2018B ZIP-file/Install.   ***
***       A separate download is not usually required.                    ***
***                                                                       ***
*****************************************************************************
***                                                                       ***
***                        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.

 
   ====================
   Wi-Fi Extender 

   Connect to and disconnect from Wi-Fi networks. Setup and save connections
   to networks. Query for information about Wi-Fi networks.  Retrieve forgotten
   Wi-Fi passwords stored in saved connections.
   
   
   ====================
   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

   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 product includes a copy of WinBatch.





   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 Island Lake Consulting 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



The end of  maintenance subscriptions
-------------------------------------

Beginning in July 2017 versions of our products, Island Lake Consulting
is no longer offering maintenance subscriptions.  Instead we offer
one year of free downloads with you license purchase.


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

When you purchase a new copy of one of our products, your purchase price
will include one-year of free updates.  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 purhcase a new version with free updates for  an additional 
year.  If you choose not to purchase a new version, you will be able to 
continue to use the versions which were released prior to the date your
license expiry, 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,
2018, you will be licensed to use any versions of that product which are
released in 2018.  If you choose not to renew your license, you won't be 
licensed to use new versions which are released after that.  But you will be 
licensed to use the 2018 versions forever.


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

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

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

If you purchased an older version of one of our products and your
maintenace or update period has expired, you will need to purchase 
the current version of the product to download it.


What day does my free update period expire?
-------------------------------------------------

The free update period always expire on the last day of the specified
month.  If you purchase a new product in Jan. 2018, your update period
for that product will expire at the end of Feb. 2019.  


What happens when I purchase a new version?
------------------------------------------------------

When you purchase a new version, you will receive a new license code 
which will allow you to download and use an additional year's worth of
releases.  


Do I have to wait until the expiration date to purchase a new license?
---------------------------------------------------------------

We recommend that you wait until your license period enters the one
month grace period to purchase a new license.


What if I want to purchas a new license after it has expired?
-------------------------------------------------------------

You are not penalized for allowing your license to expire.  However,
we do recommend that you keep your license current so that you have
immediate access to fixes and improvements as soon as they become
available. 



                      ON-LINE SUPPORT

 Island Lake Consulting LLC has on-line support!

 Island Lake Consulting 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-2018 by Island Lake Consulting LLC
 WINBATCH+COMPILER Copyright © 1991-2018 by Island Lake Consulting LLC
 WEBBATCH          Copyright © 1996-2018 by Island Lake Consulting LLC



                  END-USER LICENSE AGREEMENT
                    AND LIMITED WARRANTY
                         WinBatch®
                      WinBatch®+Compiler
                         WebBatch®

                       – IMPORTANT –
           READ CAREFULLY BEFORE INSTALLING THE SOFTWARE.
   
   By installing or using any portion of the WinBatch®, 
   WinBatch®+Compiler, or WebBatch® Software (the “Software”), you 
   accept all of the following terms and conditions of this 
   End-User License Agreement and Limited Warranty 
   (the “License Agreement”).
                  
                     LEGAL EFFECTIVENESS
   
   THIS IS A LEGAL AGREEMENT BETWEEN ISLAND LAKE CONSULTING LLC, 
   DOING BUSINESS AS WINBATCH, THE COPYRIGHT OWNER OF WINBATCH®,
   WINBATCH®+COMPILER, AND WEBBATCH® (“We”) AND THE PURCHASER OF A
   LICENSE TO THE SOFTWARE AND/OR END USER OF THE SOFTWARE (“You”).
   CAREFULLY READ THIS LICENSE AGREEMENT BEFORE INSTALLING, USING, 
   OR OPENING A PACKAGED COPY OF THE SOFTWARE. WE WILL NOT ACCEPT ANY
   PURCHASE ORDER OR SELL YOU A LICENSE TO INSTALL AND USE THE 
   SOFTWARE UNLESS YOU AGREE TO ALL OF THE TERMS OF THIS LICENSE
   AGREEMENT. IF YOU DO NOT AGREE TO THESE TERMS, DO NOT OPEN, 
   INSTALL, OR USE THE SOFTWARE ON YOUR COMPUTER OR OPEN A PACKAGED 
   COPY. REMOVE ANY AND ALL COPIES OF THE SOFTWARE FROM YOUR COMPUTER 
   AND RETURN THE SOFTWARE AND ANY ACCOMPANYING MATERIALS WITHIN 
   THIRTY (30) DAYS OF PURCHASE, WITH PROOF OF PURCHASE, FOR A FULL 
   REFUND OF THE AMOUNT YOU ORIGINALLY PAID FOR THE SOFTWARE.

                       SOFTWARE LICENSE
   This License Agreement grants you a license to the Software. You 
   are a licensee and not an owner of copies of the Software. This 
   License Agreement, as well as copyright and other intellectual 
   property laws and international treaties protect this Software, and 
   set forth your specific rights to use the Software. The provisions 
   of this License Agreement are conditions of your license. If you
   materially violate a condition, then your use of the Software is 
   without authority and may therefore make you liable for infringing 
   our copyright in the Software.
   Upon payment of the single copy license fee, we grant you the right
   to install the Software on a single computer.

   You may make a single additional copy of the Software for backup or 
   archival purposes. If you receive a copy of the Software 
   electronically and on disk, you may use the disk copy for archival
   purposes only. Copyright law prohibits you from making any other 
   copy of the Software and user manual without our permission.

   Your license to the Software is perpetual as long as you observe 
   the conditions of this License Agreement.

   If you have licensed the WinBatch+Compiler product you may compile 
   scripts that you author 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. You may not use the Software, however, to provide 
   script-compiling services for others, whether inside or outside 
   your organization. A license to use the Software is necessary to 
   utilize the Software’s script-compiling functionality.  
   
   You may not alter, modify, or adapt the Software or user manual, 
   or create any derivative works based on them. We distribute the 
   Software in computer executable form only, and do not allow user 
   access to the underlying source code and data. You may not reverse 
   engineer, decompile, or disassemble the Software to gain access to 
   such code and data, except to the extent applicable law expressly 
   permits such activity. Decompiling or disassembling the Software 
   may also violate the Software’s copyright.

   You may not sublicense, sell, rent, lend, lease, sublicense, or 
   give away the Software to others. You may, however, transfer the 
   Software, written materials, and this License Agreement as a 
   package if the other party registers with us and agrees to accept 
   this License Agreement. You may not retain any copies of the 
   Software yourself once you have transferred it. Any unauthorized 
   copying, distribution, or modification of the Software will 
   automatically cancel your license to use the Software and violate 
   the Software’s copyright.

                   LIMITED WARRANTY AND REMEDIES
   We warrant that the Software will perform in substantial 
   compliance with the specifications set forth in the user manual 
   provided with the Software, provided that it is not modified and 
   it is used on computer hardware and with an operating system for 
   which it was designed. We also warrant that any disk media and 
   printed user manuals we supply are free from defects in materials 
   and workmanship under normal use.

   These warranties are limited to the 90-day period from your 
   original purchase of a license to the Software. If you report in 
   writing within 90 days of purchase a substantial defect in the 
   Software’s performance, we will attempt to correct it or, at our 
   option, authorize a refund of the amount you originally paid for 
   your license to the Software. If you return faulty media or a 
   printed user manual during this period, we will replace it free 
   of charge. You must pay the cost of delivery to us and insure 
   items being returned, since we do not accept the risk of loss or 
   damage in transit.
   
   THE WARRANTIES AND REMEDIES SET FORTH ABOVE ARE EXCLUSIVE AND IN
   PLACE OF ALL OTHERS, ORAL OR WRITTEN, EXPRESS OR IMPLIED, 
   CONCERNING THE SOFTWARE OR USER MANUAL. WE DO NOT AND CANNOT 
   WARRANT THE PERFORMANCE OR RESULTS YOU MAY OBTAIN USING THE 
   SOFTWARE. EXCEPT FOR THE FOREGOING LIMITED WARRANTY AND REMEDIES, 
   AND FOR ANY WARRANTY, CONDITION, REPRESENTATION, OR TERM TO THE 
   EXTENT TO WHICH IT CANNOT OR MAY NOT BE EXCLUDED OR LIMITED BY LAW
   APPLICABLE TO YOU IN YOUR JURISDICTION. WE MAKE NO OTHER 
   WARRANTIES, REPRESENTATIONS, OR CONDITIONS, EXPRESS OR IMPLIED, 
   WITH RESPECT TO THE SOFTWARE, MEDIA,OR USER MANUAL, INCLUDING 
   THEIR MERCHANTABILITY, SATISFACTORY QUALITY, NON-INFRINGEMENT OF 
   THIRD PARTY RIGHTS, INTEGRATION, OR FITNESS FOR A PARTICULAR 
   PURPOSE. WE WILL IN NO EVENT BE LIABLE FOR ANY DIRECT, INDIRECT, 
   SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES ARISING FROM THE USE
   OF OR INABILITY TO USE THE SOFTWARE OR USER MANUAL, EVEN IF WE 
   HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

   Because software in general is inherently complex and may not be 
   completely free of errors, We are not responsible for any costs 
   including, but not limited to, lost profits or revenue, loss of 
   time or use of the Software, loss of data, the cost of recovering
   software or data, the cost of substitute software, claims by third
   parties, or similar costs. In no event will our liability exceed 
   the amount paid for the license to the Software.

                  NOTICES TO GOVERNMENT LICENSEES

   The Software and manual are “Commercial Items,” as that term is 
   defined at 48 CFR 2.101, consisting of “Commercial Computer 
   Software” and “Commercial Computer Software Documentation,” as 
   such terms are used in 48 CFR 12.212 or 48 CFR 27.7202, as 
   applicable.  Consistent with 48 CFR 12.212 or 48 CFR 227.7202-1 
   through 227.7202-4, as applicable, the Commercial Computer 
   Software and Commercial Computer Software Documentation are being
   licensed to U.S. Government end users only as Commercial Items and
   with only those rights as are granted to all other end users 
   pursuant to the terms and conditions of this License Agreement.
   Unpublished-rights reserved under the copyright laws of the United
   States. Island Lake Consulting LLC, 1425 NW Island Lake Rd., 
   Silverdale, Washington 98383-9484 USA.

   Any State, instrumentality of a State, and officer or employee of a
   State or its instrumentality acting in their official capacity will
   not be immune under any doctrine of sovereign immunity from suit 
   for violating this License Agreement or the Software’s copyright.

                             GENERAL

   The laws of the State of Washington, USA govern this License 
   Agreement. Any lawsuit to enforce this License Agreement or the
   Software’s copyright may be brought and tried in the state court 
   for or federal district court comprising Kitsap County, 
   Washington, USA. The substantially prevailing party in any lawsuit
   will be entitled to recover its reasonable attorney’s and expert’s
   fees and expenses.

   This License Agreement is the complete and exclusive statement of 
   the agreement between you and us concerning use of the Software. It
   supersedes any prior agreement or understanding, oral or written, 
   between you and us, or our respective agents and employees, with 
   respect to this subject.  None of our distributors, resellers, 
   dealers, or agents is authorized to make any modification, 
   extension, or addition to this License Agreement and the limited 
   warranty and limitation of liability included in this License
   Agreement.


                    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 Island Lake Consulting LLC 
  WebBatch          is a registered trademark of Island Lake Consulting LLC
  WinBatch+Compiler is a trademark of Island Lake Consulting LLC  









              *** ISLAND LAKE CONSULTING 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.                       Eval only 

 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.     $69.00

 WebBatch        - Quick and easy scripting language for Web
                   Servers running Windows NT.  Included free
                   with WinBatch+Compiler.
                   
                   http://www.winbatch.com           $69.00/free





                    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.
    - And, of course, our 30-day money back guarantee.


  Our products can be obtained at http://www.winbatch.com. 




          
          
          
          
          
          
          
          
          
          


