JPE Cmdline is a special, trimmed down version of the JPE Launcher tool. It is a Windows executable but has no user interface. It may be used to build portable launchers for applications or to portably launch applications. It is a leftover from previous versions of JauntePE but it's still useful since it's so quick and easy to use once you've done a small bit of initial setup work.
Usage Syntax:
JPECmdline.exe [switches] path-to-executable [executable's parameters]
The optional [switches] parameters default to -l. Separate each parameter by at least one space. Make sure to use a double-quoted path to the executable if it contains spaces. The optional executable's parameters will be passed along to the executable via its command line.
An example use of JPE Cmdline would be to create a "Run Portably" SendTo link to it with a command line of "-l -f -r". This SendTo may then be used within Explorer to instantly portably run an application's main executable by simply right-clicking on it and selecting the SendTo "Run Portably" menu item.
Before making use of JPE Cmdline, there are a few things you need to be aware of:
- It expects a copy of the jauntePE.dll file (the JauntePE runtime) to be within the same directory it is in
- To build portable launchers, it expects a copy of the JPEPortable.exe file (the generic JauntePE portable launcher) to be within the same directory it is in
- It will "root" (use as its home base) any created portable data (registry .reg file or redirected file system directories and files) in the same directory it is in
- If you want to make use of a default, common (generic) JauntePE runtime config file as a way to add-to or override any command line settings, this file must exist in the same directory that JPE Cmdline is in and must be named JauntePE_jauntePE.ini
All of the above requirements are already taken care of within the JauntePE\Toolbox\Cmdline directory. There are even a couple of example .cmd files ready for use. BuildPortable.cmd is for the building of portable launchers. RunPortably.cmd is for the portable running of applications. And yes, the .cmd files are portable as well, at least for Windows 2000 or newer.
The following table lists the switches available for portably launching an application executable. The -l switch is the main indicator for a portable launch run. The other switches are used to set up initial launch settings for the launcher and are passed on to the JauntePE runtime in-memory. Once the application has been portably launched, its initial launch settings may be overridden by use of a JauntePE runtime config ini file. JPE Cmdline does not make use of a launch config ini file, so any [Launch] section settings within an overriding JauntePE runtime config ini file are ignored.
Switch | Description |
---|---|
-l |
Launch an application executable |
-w |
Leave the current working directory alone (otherwise change it to the application executable's directory) |
-s |
Launch screensavers in display mode (otherwise bring up the screensaver's settings) |
-f |
Portablize the special folders file system changes into a common directory (rooted off of the directory that JPECmdline is in) |
-F |
Portablize the special folders file system changes into an application-specific directory (rooted off of the application executable's directory) |
-r |
Portablize the registry changes into a common .reg (JauntePE_registry.reg, located in the directory that JPECmdline is in) |
-R |
Portablize the registry changes into an application-specific .reg (located in the application executable's directory) |
-m |
Reads into memory, and makes use of an application-specific text .reg in memory - changes are written immediately to the application-specific text .reg |
-M |
Reads text or binary .reg into memory - writes full text .reg during a normal app end |
-Mt |
Reads text or binary .reg into memory - writes full text .reg during a normal app end |
-Mb |
Reads text or binary .reg into memory - writes full binary .reg during a normal app end |
-Mn |
Reads text or binary .reg into memory - updates are discarded |
The following table lists the switches available for building a portable launcher for an application executable. The -b switch is the main indicator for a build-launcher run. The initial launch settings for the launcher, stored internally within the built launcher, will all be defaulted. Which means that they will all be turned off except for the default window identification settings. These will all be turned on and using a red and black window frame border. Once the launcher has been built, its internal launch settings may be overridden by use of a JauntePE launch and/or a runtime config ini file.
Switch | Description |
---|---|
-b |
Build an application executable-specific portable launcher executable (do not rename the resulting file) |
-a |
Use the application executable's icon as the portable launcher executable's icon |
-e |
Stuff the application's executable into the portable launcher executable (will be extracted at runtime if necessary) |
-i |
Stuff the application's existing ini and/or .reg into the portable launcher executable (these files must be in the same directory as the application executable) (will be extracted at runtime if necessary) |
-c |
copy the application's executable to the build directory |
-p |
rename the application's executable so that it doesn't get accidentally executed |
-j |
copy the JauntePE runtime to the build directory |