NOTE: Before running this example, you must first put a copy of the JPEPortable.exe file in the Normal2 directory and rename it to notepad.exe.

This example presents a new typical way of using the jauntePE runtime when first starting to portablize an application. This is the new recommendation. The "old" recommendation is given in the Normal example.

The ini itself...

The Launch section

This section's settings are all launch settings and are read by the JauntePE-built application launcher. Each overrides its equivalent stored within the launcher executable file.

Please note that with the new Path, JPERuntime, and JPERuntimeIni settings, you now have complete control over the placement of the various files necessary to launch an application via JauntePE.

The ExeDir setting is turned off in this example since we don't want the current working directory changed to that of the launched executable's directory, but rather, want it to remain the same, which in most cases should be the launcher's directory. This allows relative paths to text files to be used on the command line, such as in bat or cmd files.

[Launch]
Path=%System%\%appname%.exe
JPERuntime=..\Runtime\Def\jauntePE.dll
JPERuntimeIni=.\%appname%_jauntePE.ini
ExeDir=0

The rest of this file's sections are all for runtime settings and are read by the JauntePE runtime dll. Each overrides its equivalent stored within the launcher executable file.

The Redirection section

This section's settings are from the Portablizer plugin's Redirection section and the Identification plugin's Redirection section.

If you're familiar with the "old" JauntePE runtime ini settings, these should look familiar to you. Please note the explicit setting of the settings. This is done since the launcher used has all settings turned off by default.

Also note that in this example the use of the in-memory portable registry is turned on (MemRegistry=1). This is the new recommended setting when initially setting up an application that you are not familiar with. Using the in-memory portable registry allows the new FillRegistry, RegMerge, and RegIgnDel registry-oriented settings to be turned on, which ultimately means that the "virtual" registry, that JauntePE presents to the application, behaves much more like the real system registry than in previous versions.

Also note the explicit indication to apply this ini's settings to any launched child applications (RedirMisc=1), and the explicit indication to prevent MS Installer installs from running (RedirMSI=1). Again, turning these 2 settings on is recommended if you are not familiar with the launched application.

The use of ExcludeAppDir has the application's executable's directory automagically added to the file system exclusion list. This will allow the application to be run from a desktop folder, for instance, with none of the problems of the past when one did this. Keep in mind, however, that applications that like to store their locations in the registry or elsewhere, will most likely do so using a non-portable path, even if you use the 12-Steps recommended directory structure and setup the application to run from a portable "Program Files" directory.

The use of WFSMerge allows the application, or you via the application's use of the shell file system browsing windows, to browse the portable file system and the real file system as if they were one.

[Redirection]
UseIcon=1
ModFrame=1
FlashDisco=1
IconDisco=1
InnerColor=0
OuterColor=0

MemRegistry=1
FillRegistry=1
RegMerge=1
RegIgnDel=1

RedirMisc=1
RedirMSI=1

ExcludeAppDir=1
WFSMerge=1

Logging=1
LogPath=.\%appname%_jauntePE.log
LogFuncs=1
Discovery=2

The Registry sections

With registry redirection, by default ALL registry changes are redirected, so the only keys we need to concern ourselves with are the ones that we DON'T want to have redirected into the portable registry. The list presented here is one that I've created during testing. You may need to add to it or take away from it for your particular applications.

[Registry]
Use=1
Data=..\Data\%appname%.reg

[RegistryExclude]
1=HKEY_LOCAL_MACHINE\Hardware
2=HKEY_LOCAL_MACHINE\Security
3=HKEY_LOCAL_MACHINE\System

[RegistryTemp]
1=HKEY_CLASSES_ROOT
2=HKEY_LOCAL_MACHINE
3=HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer
4=HKEY_CURRENT_USER\Software\Microsoft\Windows
5=HKEY_CURRENT_USER\Software\Microsoft\Windows NT

The Filesystem sections

As with registry redirection, by default ALL file system changes are redirected. This is the recommended starting usage for file system redirection since you don't really have any idea yet how the application makes use of the file system. Once you determine this then you can begin excluding as needed. Ideally you should be able to get to the point where you can exclude all and then add back in just those directories of interest.

The SpecialFolders entries are included here only to keep this example's portable file system directory names consistent with the other examples. You don't have to enter them if you don't want, as the jauntePE runtime will default them to something sensible as needed.

[Filesystem]
Use=1
Data=..\Data\Filesystem

[SpecialFolders]
5=Documents
20=Fonts