The section is primarily intended for use by those who wish to manually maintain their JauntePEized applications. Those unfamiliar with how the JauntePE launcher and runtime work should make use of the JPE Quickie tool instead, as much of what is discussed in this section is automated by that tool.
The 0.3.0 version JauntePE standalone launcher is identical in use to its predecessors except for the use of a new set of launcher settings which allows you to modify how a given launcher behaves without having to build a new launcher exe - you just build a new launcher ini instead.
The 0.3.0 version JauntePE runtime is identical in use to its predecessors except for the use of several new sets of runtime settings, several new performance enhancements, and some bug fixes. One thing that should be noted up front however, is that the portable registry .reg file's contents are slightly different with 0.3.0, which makes any 0.3.0 modified .reg file incompatible with any previous version's runtime dll. So make a backup copy of any existing portable registry .reg files first before trying it out with 0.3.0, just in case you need to revert back to an older version.
To make use of the 0.3.0 launcher exe and runtime dll, you must at least do the following:
-
Copy the JPEPortable.exe file to the launch directory of your choice.
This is the generic 0.3.0 launcher. You can find it in the JauntePE\Toolbox directory. This step is mandatory for existing 0.2.0 or older standalone JauntePEized applications since the communication mechanisms between the 0.3.0 launcher and the 0.3.0 runtime have changed, primarily to allow the use of JauntePE on 9x Windows, but also to allow for new 0.3.0 functionality. If you try to run an 0.2.0 or older launcher with the 0.3.0 runtime dll, you will get and error message and the launched application will be terminated.
When the launcher is run, its directory is assigned to the %appdir% substitution token which is available for use in any JauntePE configuration ini path. The launcher does not have to reside in the same directory as the executable it launches unless you don't want to use a launch config ini to specify where the to-be-launched executable resides. -
Rename the copied JPEPortable.exe to something meaningful. Rename it with a .scr extension if you wish to launch a screensaver.
The filename does not have to contain the _portable suffix as in prior versions. The filename minus any _portable suffix is assigned to the %appname% substitution token. The %appname% substitution token plus the file extension is then used as the default application executable to be launched. If this file is not found in the %appdir% directory, the %appname% substitution token plus a .jpe extension is used as the default application to be launched. If this file is not found the launcher quits with an error message, unless a launcher config ini is found and it contains a [Launch]Path setting that "points" to the executable to be launched. -
Copy the Runtime\jauntePE\def\jauntePE.dll file somewhere convenient for use by this, and possibly other future, portablization efforts.
This is the only runtime JauntePE dll that you need for 0.3.0. 0.3.0 does not require nor make use of madchook.dll. The name of the file must remain jauntePE.dll.
There are other, specialized, builds of this dll that you might want to make use of later, in a separate download. Especially if you plan on creating your own distributable "wrapper", as there are much smaller plugin-specific builds, such as the registry-only and file system-only builds. Refer to the DLL Builds section for a complete list of all of the available runtime dll builds. -
Create, or modify an existing, %appname%_jauntePE.ini launch settings file, to specify any launch settings you may wish to use, as the launch settings are all off by default.
In other words, if your launcher's name is Firefox.exe, the launch settings file must be named Firefox_jauntePE.ini.
This file must reside in the same directory as the portable launcher. An example_jauntePE.ini in the Toolbox directory has been provided for you as a starting point if you so wish. It contains a commented-out entry for every possible setting's valid value. So all you have to do is uncomment out the lines as needed and modify the few that require a path or some other non-fixed value. See the included examples if you are unfamiliar with these new settings. The launch reference also provides more detailed explanations of these settings. There are also a number of generic and application-specific launch/runtime combo config ini files available in the Toolbox\Configs directory.
Make sure you have the Path and JPERuntime settings correct for the to-be-launched executable and JauntePE jauntePE.dll files. Also, although not mandatory, it would be a good idea to go ahead and set the JPERuntimeIni setting to either "point" to the same %appname%_jauntePE.ini file or to the one you choose to create or modify in the next step. -
Create, or modify an existing, %appname%_jauntePE.ini, JauntePE_jauntePE.ini, or explicitly specified runtime settings file, to specify any runtime settings you may wish to use.
This file may be the same as the launch ini but does not have to be. Please see the runtime reference if you have any questions regarding its contents.