Step-by-Step to wrap a vbs into an .exe

Question

Here is a way to use Iexpress 2.0 to wrap your VBS scripts into an .exe. Iexpress 2.0 is native to Win XP and Win 7 and is quite useful when you have a VBS that is dependent on other files, like and install program or even an HTA. Once you have created the .EXE package a .SED file is also create in the same directory, which is the instructions for the Iexpress.exe. You can edit the .SED file in notepad and then run the iexpress wizard and select Open Existing Self Extraction Directive file and create your new package. This is helpful when you want to add new files, change the command line, or the output directory, you do not need to go through the whole package process again. Below are the instructions on how to create a new .EXE using Iexpress 2.0.
1.     On a computer running Windows XP or Windows 7, click Start, click Run, enter iexpress, and click OK. This starts the IExpress Wizard.
2.     On the Welcome to IExpress 2.0 page, select Create new Self Extraction Directive file and click Next.
3.     On the Package purpose page, select Extract files and run an installation command and click Next.
4.     On the Package title page, type a title for your package and click Next.
5.     On the Confirmation prompt page, select No prompt and click Next.
6.     On the License agreement page, select Do not display a license and click Next.
7.     On the Packaged files page, click Add and select the vbs script from the directory in which it resides:
8.     When you finish adding files, click Next.
9.     On the Install Program to Launch page, in the Install Program box, type c:\windows\system32\cscript.exe “yourVBS.VBS”  OR  c:\windows\system32\wscript.exe “yourVBS.VBS” Leave the Post Install Command box BLANK.
10.  On the Show window page, select Hidden and click Next.
11.  On the Finished message page, select No message and click Next.
12.  On the Package Name and Options page, enter the path and filename that you want for this distribution package. Check both boxes and click Yes to the warning under Options and click Next.
13.  On the Configure restart page, select No restart and click Next.
14.  On the Save Self Extraction Directive page, select Save Self Extraction Directive (SED) file:, edit the path and name of the file, and click Next.
15.  On the Create package page, click Next. When the package has been created, click Finish to exit.
16.  The package will now be created with the name you specified and have an extension of .EXE ex. “yourVBS.EXE”
Thanks, LikeToCode...Please click "Mark as Answer" when you get the correct reply to your question.

Answer 1

Self Extraction Directive (SED) file Explained
Here is a copy of a Self Extraction Directive (SED) file. Keep in mind you can IExpress 2.0 to create an .EXE for many items like batch files, Inf files, VBS files and other .exe files. For
this purpose we are talking about VBScripts. You can edit this file and "recompile" your .exe. Why would you want recompile your .exe? To name a few you might find unwanted behavior in your VBS or you may need to add additional files and you don't want to
have to go through the entire IExpress setup again, so you would change data in this file and in two clicks your app is recompiled.
First, let’s talk about some important sections in this SED file. There are five sections Version, Options, Strings, SourceFiles, and SourceFiles0. When editing your SED files you will
be mostly working in the Strings, SourceFiles, and SourceFiles0 sections, most of the Options section was done when you created the package for the first time.
Here is the strings section with comments:
[Strings]
InstallPrompt=  
‘Use if you want the user to confirm your install, I never use this option.
DisplayLicense= 
‘Use if you have an EULA or the like, I never use this option.
FinishMessage= 
‘If you want to inform the user that your install is done.
TargetName=    
‘The directory path and name of your .EXE 
FriendlyName= 
‘This is the package title and what is help in memory.
AppLaunched=  
‘This is the command line REMEMBER to use quotes around directory paths with spaces
PostInstallCmd=
‘If you have an app that need to run last put the command line here.
AdminQuietInstCmd= 
‘You use this to tell IExpress when given the /q:a switch what command to use for the internal exe, vbs, hta, etc.
UserQuietInstCmd=    ‘You use this to tell IExpress when given
the /q switch what command to use for the internal exe, vbs, hta, etc.
FILE0= 
‘The name of the source file. Every file you include will have a FILE1= or FILE2= and so on.
Here are the SourceFiles and SourceFiles0 sections:
[SourceFiles]
SourceFiles0= 
‘The directory path containing all of the source files listed in this SED file.
[SourceFiles0] 
‘For every FILEx= listed in the strings section you MUST have the variable listed here.
%FILE0%=
%FILE1%=
%FILE2%=
Complete Self Extraction Directive(SED) for an app called HelloWorld.EXE
[Version]
Class=IEXPRESS
SEDVersion=3
[Options]
PackagePurpose=InstallApp
ShowInstallProgramWindow=1
HideExtractAnimation=1
UseLongFileName=1
InsideCompressed=0
CAB_FixedSize=0
CAB_ResvCodeSigning=0
RebootMode=N
InstallPrompt=%InstallPrompt%
DisplayLicense=%DisplayLicense%
FinishMessage=%FinishMessage%
TargetName=%TargetName%
FriendlyName=%FriendlyName%
AppLaunched=%AppLaunched%
PostInstallCmd=%PostInstallCmd%
AdminQuietInstCmd=%AdminQuietInstCmd%
UserQuietInstCmd=%UserQuietInstCmd%
SourceFiles=SourceFiles
VersionInfo=VersionSection
[VersionSection]
FileDescription=Installer for Hello World
LegalCopyright=
CompanyName=Your Company Name
FileVersion=1.1
InternalName=Hello World
OriginalFilename=Hello_World
ProductName=Hello World
ProductVersion=1.1
[Strings]
InstallPrompt=
DisplayLicense=
FinishMessage=
TargetName=C:\Scripts\Iexpress_Installs\HelloWorld.EXE
FriendlyName=Hello World
AppLaunched=C:\Windows\system32\wscript.exe Hello.vbs
PostInstallCmd=<None>
AdminQuietInstCmd=
UserQuietInstCmd=
FILE0="Hello.vbs"
FILE1="example.txt"
[SourceFiles]
SourceFiles0=C:\Scripts\Iexpress_Installs\
[SourceFiles0]
%FILE0%=
%FILE1%=