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:

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.


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.