This file is my own version of eLiTeWrap 1.03.
Dissabled, edited and reassebled so no longer detected by AntiVirus software.
Gobo
www.teamvirus.net/gobo







.`..`..`..`..`..`..`..`..`.
eLiTeWrap 1.03
.`..`..`..`..`..`..`..`..`.

(C) Tom "eLiTe" McIntyre, 1999
tom@dundeecake.demon.co.uk
http://www.dundeecake.demon.co.uk/elitewrap

BUG REPORTS ONLY (NO SUPPORT PROVIDED): elitewrap@dundeecake.demon.co.uk

If you downloaded this file from somewhere other than the official site, above,
visit it now to make sure you have the latest version!

.`..`..`..`..`..`..`..`..`.
Standard disclaimer
-------------------
BY USING THIS SOFTWARE YOU AGREE THAT NO-ONE INVOLVED IN ITS PRODUCTION MAY BE
HELD PARTIALLY OR TOTALLY RESPONSIBLE FOR ANY PROBLEMS ARISING FROM ITS USE OR
MISUSE.
.`..`..`..`..`..`..`..`..`.

Hi, this is another eLiTe production :) Enjoy...

eLiTeWrap is an EXE wrapper, used to pack files into an archive executable that
can extract and execute them in specified ways when the packfile is run. For
example, you could create a setup program that would extract files to a
directory and execute programs or batch files to display help, copy files, etc.

The advantages eLiTeWrap has over other common self-extractor programs and EXE
wrappers are:
+ Programs in the packfile can be extracted without starting
  + Unlike many EXE wrappers, files can be automatically extracted into a
    temporary directory, from where other programs in the packfile or on the
    user's system can manipulate them
+ Programs inside the packfile and on the user's system can be automatically
  started
  + Unlike many self-extractor utilities, eLiTeWrap has the ability to
    start any number of programs, contained in the packfile, or existing on
    the user's system
+ Programs (packed and external) can be started visibly, or hidden from the
  user
  + Programs that do not require user input can be started completely hidden
    from the user
+ Programs can be started synchronously or asynchronously
  + The packfile can be made to wait for a program to finish before the rest of
    the files are processed
+ Script files can be written to automate the creation of packfiles
+ Full CRC-32 checking is built in
  + 32-bit cyclic redundancy checks are preformed to ensure that files are
    complete, undamaged, and that they have not been tampered with
+ Packfiles are produced with an icon

Usage
=====
The eLiTeWrap archiver ("elitewrap.exe") is a command-line utility, used as
follows:

elitewrap.exe [scriptfile]

Running elitewrap.exe with no parameters will start the program ready to
receive input from the user. The on-screen prompts are descriptive enough that
little explanation should be necessary. However, I will run through them:

Prompt                              Response
------                              --------
Enter name of output file:          ] This is the packfile you want to create.
                                    ] Remember to specify a .exe extension, for
                                    ] example: "install.exe".

[If the file already exists you will be asked whether or not to overwrite it]

[Now each of the operations will be displayed, just for your reference, as
 follows:]
Operations: 1 - Pack only
            2 - Pack and execute, visible, asynchronously
            3 - Pack and execute,  hidden, asynchronously
            4 - Pack and execute, visible,  synchronously
            5 - Pack and execute,  hidden,  synchronously
            6 - Execute only,     visible, asynchronously
            7 - Execute only,      hidden, asynchronously
            8 - Execute only,     visible,  synchronously
            9 - Execute only,      hidden,  synchronously

Enter package file #1:              ] This is the name of the first file you
                                    ] want to pack, or execute. For example, to
                                    ] specify "go.exe" in the current directory
                                    ] you would just type "go.exe". To specify
                                    ] a file elsewhere on your system, specify
                                    ] a full path, for example:
                                    ] "c:\windows\calc.exe".

Enter operation:                    ] This is where you specify an operation,
                                    ] one of the single-digit numbers from the
                                    ] operation list above.
[Explanation:
 "1" (pack only) will cause the file to be packed into the archive, and
 extracted into a temporary directory when the packfile is run. A program that
 is executed from the packfile after this can then manipulate it. This method
 should be used for storing data files that cannot be executed.

 "2"-"5" (pack and execute) will cause the file to be packed into the archive
 and executed when the packfile is run. You can choose to start the program
 visible or invisible, asynchronously (the packfile self-extractor will
 continue when this program is running) or synchronously (execution of the
 packfile will be stopped until this program has finished).

 "6"-"9" (execute only) will NOT store the file in the packfile, but rely on
 the file existing on the user's system - it could be an integral system
 utility, like "notepad.exe", or it could have been extracted earlier. The
 program will search the following places, in the following order, for these
 files:
    Current directory
    Directory from where the packfile was started
    System directories (NT uses 32-bit then 16-bit system directories)
    Windows directory
    All directories specified in the PATH environment variable
 
 IMPORTANT: If you wish to pack and execute the same file twice or more in the
 archive you must use an option from 2-5 the first time, and 6-9 subsequent
 times. The file will already have been extracted, and so will be reused. Not
 only does this save disk space, but specifying the same filename twice will
 not work if the file is open (i.e. the program is running) the second time
 the file is extracted. ]

Enter command line:                 ] If you specified an option "2"-"9" then
                                    ] you will be prompted for a command line.
                                    ] This is an appended to the filename to
                                    ] form a complete command that will be
                                    ] executed. This could be used for starting
                                    ] WINHELP.EXE with your help file, for
                                    ] example. This is optional. Press Enter to
                                    ] skip this option.

Enter package file #2:              ] You will now be asked for another file,
                                    ] then another, and so on. You can just
                                    ] press Enter at one of these prompts to
                                    ] stop adding files.

Example
-------
This is an example of what you could type to produce an installer package that
displays a readme file in notepad, waits until they've read it, then invisibly
installs the software, and runs a demo in the foreground:

::: Screendump starts :::
eLiTeWrap 1.03 - (C) Tom "eLiTe" McIntyre
tom@dundeecake.demon.co.uk
http://www.dundeecake.demon.co.uk/elitewrap

Stub size: 7712 bytes

Enter name of output file: install.exe
Operations: 1 - Pack only
            2 - Pack and execute, visible, asynchronously
            3 - Pack and execute,  hidden, asynchronously
            4 - Pack and execute, visible,  synchronously
            5 - Pack and execute,  hidden,  synchronously
            6 - Execute only,     visible, asynchronously
            7 - Execute only,      hidden, asynchronously
            8 - Execute only,     visible,  synchronously
            9 - Execute only,      hidden,  synchronously

Enter package file #1: readme.txt
Enter operation: 1
Enter package file #2: c:\windows\notepad.exe
Enter operation: 8
Enter command line: readme.txt
Enter package file #3: setup.exe
Enter operation: 3
Enter command line:
Enter package file #4: demo.exe
Enter operation: 2
Enter command line: -fullscreen -cols:red,green,blue -text:"Installing applicat
ion... Press Q to quit this demo when ready..."
Enter package file #5:
All done :)
::: Screendump ends :::

Scriptfile Usage
================
As mentioned above, eLiTeWrap supports the use of scripts. The scripts are very
simple, in that a script contains the exact text that would normally be typed
into the archiver, in the same order, and nothing else. There is one exception:
where a blank line is desired, a single ~ should appear alone at the start of
the line. The above example could be scripted as follows:

::: Begin sample script :::
install.exe
readme.txt
1
c:\windows\notepad.exe
8
readme.txt
setup.exe
3
~
demo.exe
2
-fullscreen -cols:red,green,blue -text:"Installing applicat ion... Press Q to q
uit this demo when ready..."
::: End sample script :::   NOTE: The long line should appear on only one line

If this script was saved in a file called "install.ews" (the ews stands for
eLiTeWrap Script, but extension is irrelavent), you could then run
"elitewrap.exe install.ews" and the install.exe file would be generated
automatically. The information is displayed on screen as if it had been typed.

NOTE: When using a script, the overwrite confirmation prompt is not displayed,
neither is the operation list. Also, no additional error checking is performed,
so you should examine the output to ensure that no errors were produced.
TIP: If more than a screenful of output is produced, you can use the command:
"elitewrap.exe install.ews|more" read the output one page at a time.

All files created will be deleted when they have been closed and the
self-extractor has finished.

Future Versions
===============
In future versions I hope to add the following features:
+ Compression
+ Encryption
+ Ability to specify an icon file when creating the packfile
+ Improve the scripting capability
+ Possibly design a GUI (graphical user interface)

.`..`..`..`..`..`..`..`..`.
EOF