LiveUpdate32  07/27/1997 (Beta 1)
-------------------------------

This application is to be distributed and used with your application.
It serves as a way for your users to update application files while in the application,
provided the user has an internet connection.
Written, Tested, Designed for/by Microsoft Visual Basic 5.0,
other version's for VB4.0 32-bit and 16-bit coming soon.


Files in this distribution include(contact me if you need runtime files):

cihttp.ocx  76,288  03/18/97
regcntrl.bat
LiveUpdate32.exe  128,000  7/27/97 (Beta 1)

Requirements:
- An HTTP server
- Any development platform (VB, C++, etc.) that can "shell" an application
- Microsoft Visual Basic 5.0 runtime file: MSVBVM50.DLL
- Other runtime files: MFC42.DLL, MSVCIRT.DLL, MSVCRT.DLL

Instructions:

1. Extract the distribution files into the application project directory
you plan to distribute LiveUpdate32 with.

2. Execute the regcntrl.bat file. This .bat file will register the ActiveX control
needed by LiveUpdate32.exe

3. On the http server you plan to use as the LiveUpdate32 server you need to create
a directory,(anydirname), and file, (anyfilename), containing LiveUpdate32 info. The file on the LiveUpdate32 server
is dnloaded during the LiveUpdate32 process and is compared with a file created
by the LiveUpdate32.exe and the developer, any file updates are determined.
Here is the file that needs to be created in /LiveUpdate,(anydirname), on your LiveUpdate32 server:
LiveUpdate.dat, (anyfilename), follows this format:

-----------------------------------------
Your application title,major version,minor version,revision,application's .exe,directory where .exe is located on your http server,
(*Note: Each variable is separated by a comma, with no space after each comma, and a comma on the end)
------------------------------------------

Here's what it looks like:

-------------cut here--------------------
My Application Title,1,5,5,application.exe,/LiveUpdate,
---------everything between the dashes---

Save the file as LiveUpdate.dat, in the directory /LiveUpdate on your
LiveUpdate32 server.


Basically, here is how it works:

In your application, when the user clicks LiveUpdate32, LiveUpdate32.exe is then "shelled" from your application,
The LiveUpdate32 application will first read in variables from the LiveUpdate.ini file in the same directory as LiveUpdate32.exe.
When the user clicks "Go" in LiveUpdate32.exe, LiveUpdate32.exe contacts the
LiveUpdate32 server, downloads a text file (contains app name, version info, etc.),
compares the downloaded text file with variables now set in LiveUpdate32.exe to
determine if your main apps .exe file needs updating. If an update is necessary, it will then
download the updated file. Once the updated file is downloaded, a .bat file is
created that will rename your main Application's .exe file to OldApplicationEXE.old and copy the downloaded
file to the "normal" application file name, but the .bat file should not be
executed until after the application has been closed, because you can't overwrite
an .exe file that is open.

Help:

To get help on implementing this LiveUpdate32 program,
contact Craig, cgill@writeme.com

