NOTE: The 12-step program given below has been automated via the new JPE Quickie

tool. Use of JPE Quickie is now the recommended and preferred method of initial
ly portablizing an application via JauntePE. There is also a new tutorial that w
alks you through your first use of the tool.
Here's the beginnings of what's being called the JauntePE 12-step program. It's
meant to be a guide of sorts for helping you to "properly" configure an applicat
ion for initial portable use via JauntePE. There's still some gaps to be filled,
so don't be surprised if you try the steps on an application and it doesn't wor
k.
One thing to point out now is that not every application requires this type of s
etup. But this is the most generic setup and shouldn't cause problems for those
applications that don't require it. It will just make things slightly more compl
ex if you're used to having all of an application's files in one directory. You
can setup a portablized application that way, you'll just have to learn how to d
o that on your own by reading the docs.
Another important point to make here is that it's best if the application you're
trying to portablize is not currently normally installed on the computer. Again
, this depends on the application and its installer, and how robust it/they are,
and how finicky you are. If the application is currently normally installed on
the computer, you have a decision to make. The decision is whether you want to t
ake the chance that the application and its installer are not robust at all and
will, on their own, just ignore what's currently "out there" in the non-portable
registry and file system. Or, whether you're willing to do the extra work neces
sary to help prevent a robust application or installer from causing problems wit
h your portablization efforts.
Here are the 12 steps:
1. Create a portable directory for your application. From here on "your applicat
ion" will be referred to as %appname%. So if your application is generally known
as Snafu, then replace %appname% with Snafu everywhere within this document.
Don't create the directory on the desktop or in Program Files or MyDocuments, et
c.
Use some place like "E:\Portables\%appname%". From here on this directory will b
e referred to as %launchdir%.
Create a "JPE" sub-directory in %launchdir%.
Copy JauntePE's distributed default jauntePE runtime dll file, found in the Jaun
tePE\Runtime\jauntePE\def directory, to "JPE".
2. It's best if you do a "portable install" of the application, but if you don't
have an installer for the application, do the following:
Create a "ProgramFiles" sub-directory in "JPE".
Create a %appname% sub-directory in "ProgramFiles".
Copy all of the application's files and sub-directories to this lowest-level sub
-directory, i.e., copy to %launchdir%\JPE\ProgramFiles\%appname%.
Refer to the no installer section if the application makes use of non-system dll
s, ocxs, or oles that must be portably registered.
Skip to Step 9.
3. Create a "Setup" sub-directory in %launchdir%.
4. Copy the installer for the application to %launchdir%\Setup.
5. Copy JauntePE's distributed JPEPortable launcher file, found in the JauntePE\
Toolbox directory, into %launchdir%, naming it Setup.exe.
6. Copy one of the generic JauntePE distributed JPE Quickie configuration files,
found in the JauntePE\Toolbox\Configs directory, into %launchdir%, naming it Se
tup_jauntePE.ini. The specific configuration file you copy depends upon what you
want to do. For a "normal" application, the Normal2 configuration should do. Th
e Normal3 configuration adds the ability to portablize file system paths stored
within the portable registry, via the RegTokens setting. The Greener configurati
on adds portablization of more registry keys and more special folder directories

. The Greener2 configuration adds complete registry portablization.

7. Text edit the Setup_jauntePE.ini file as follows:
Replace %APPPATH% in [Launch] Path with .\Setup
Replace %appname% in [Launch] Path with the filename of the installer, e.g., Sna
fuSetup
Replace %JRTPATH% in [Launch] JPERuntime with .\JPE
Replace %APPNAME% in [Launch] JPERuntimeIni with Setup
If this is for an application that is currently normally installed on the comput
er, see the already normally installed section below on ways to handle this situ
ation.
Save and exit.
8. Run the installer for the application via the Setup.exe launcher in %launchdi
r%:
Accept the settings per your requirements, but make sure that the application is
to be installed in the typical "%ProgramFiles%\%appname%" location, where %Prog
ramFiles% is the full path to your standard "Program Files" directory.
Don't have it run the application or do anything else after the installation has
completed.
9. Copy JauntePE's distributed JPEPortable launcher file, found in the JauntePE\
Toolbox directory, into %launchdir%, naming it %appname%.exe.
10. Copy one of the generic JauntePE distributed JPE Quickie configuration files
, found in the JauntePE\Toolbox\Configs directory, into %launchdir%, naming it %
appname%_jauntePE.ini. See Step 6 for a summary of each configuration.
11. Text edit the %appname%_jauntePE.ini file as follows:
Replace %APPPATH% in [Launch] Path with .\JPE\ProgramFiles\%appname%
Replace %JRTPATH% in [Launch] JPERuntime with .\JPE
Replace %APPNAME% in [Launch] JPERuntimeIni with %appname%
If this is for an application that is currently normally installed on the comput
er, see the already normally installed section below on ways to handle this situ
ation.
Save and exit.
12. Run the application via the %appname%.exe launcher in %launchdir%.
If all goes well, you could, if you wish, modify the %launchdir% directory's %ap
pname%_jauntePE.ini file to be more specific to your application after running t
he application in discovery mode and then using its results to optimize the conf
iguration ini.
You could also use JPE Builder to modify the %launchdir% directory's %appname%.e
xe launcher to apply the application's icon to it, embed the configuration ini i
nto it, embed the portable registry into it, etc.
I like to keep the installer handy, just in case, but if it's no longer needed,
you could also delete the %launchdir%\Setup directory and its contents, and the
%launchdir% Setup.exe and Setup_jauntePE.ini files.

Handling "already normally installed" situations

If this is for an application that is currently normally installed on the comput
er, it may be necessary for you to add in a section at the end of the configurat
ion file you're editing, that will cause the installer or application to *think*
that the application has not been installed on the computer. Doing this increas
es the chance that you'll get a clean and full install and running of the applic
ation. There are 2 ways to accomplish this, the Many Ignores method or the Pseud
o-Sandbox method. Each has its own inherent set of advantages and disadvantages.
It should be noted here that the methods given below don't cover what could be d
one to hide any normally installed application's system registry entries from th
e portably run executables. There is a way to gather this information by running

the installed application via JauntePE, making use of its Discovery feature, to
capture what registry keys the application's module(s) access. But for now this
technique is considered beyond the scope of the 12-Steps Program. A "quick and
dirty" attempt would be to run the normally installed application via JPE Quicki
e, exercise the application as much as possible, use JPE Regger to extract the r
egistry keys, and then add those keys to your configuration file(s) within a Reg
istryIgnore section.
The "Many Ignores" Method
In this method, you add the following FilesystemIgnore section, and the lines wi
thin it, to each of the configuration ini files you create:
[FilesystemIgnore]
1=%38%\*.*
2=%22%\*.*
3=%25%\*.*
4=%31%\*.*
5=%35%\*.*
6=%45%\*.*
7=%46%\*.*
8=%0%\*.*
9=%5%\*.*
10=%12%\*.*
11=%16%\*.*
12=%26%\*.*
13=%28%\*.*
14=%6%\*.*
15=%8%\*.*
16=%9%\*.*
17=%11%\*.*
18=%21%\*.*
19=%32%\*.*
20=%33%\*.*
21=%34%\*.*
The "Pseudo-Sandbox" Method
In this method, you first pre-create all of the portable file system directories
using the JauntePE Portable Dirs archive, found in the JauntePE\Toolbox\Extras
directory. Follow the instructions given in the readme.txt file within the archi
ve. You then add the following FilesystemIgnore section, and the lines within it
, to each of the configuration ini files you create:
[FilesystemIgnore]
1=38
2=%40%\..
Handling "no installer" or "can't run installer" situations
If you have a situation where you either don't have an installer for the applica
tion, or you can't run the installer due to JauntePE shortcomings, read another
tutorial here.