These settings will help you portablize an application's file system special folder usage and optimize an already portablized application's file system special folder usage.

By default, all of the file system special folder accesses made by an application are not redirected into a portable file system. The following sections allow you to modify that behavior.

There are several substitution tokens that may be used within any of the settings requiring a file system path.

Launched application related tokens are %appdrive%, e.g. H:, %appdir%, e.g. H:\Portables\Firefox, and %appname%, e.g. Firefox.

And environment variable names enclosed within percent signs may be used as well, such as %ComputerName%, %UserName%, or %Temp%. You are responsible for ensuring that the environment variable is available on all versions of Windows on which the configuration ini will be used.


The [Filesystem] section


The [Redirection] section


The [FilesystemExclude] section

In this section you specify the file system special folders that you don't want to be portablized. There are two ways to do this. The first is to enter an ascending, consecutively numbered list of special folder numbers for the associated file system special folders that you don't want to be portablized. The second is to enter 1=* as the only entry, which tells JauntePE to exclude all file system special folders from being portablized. You then optionally enter a list of special folder numbers for the associated file system special folders that you do want to be portablized via the FilesystemInclude section.

Here is an example that excludes all "Windows install directory" special folders from redirection:

[FilesystemExclude]
1=20
2=36
3=37
4=41
5=56

In addition to using special folder numbers by themselves, you may also use special folder number tokens, optionally followed by a subdirectory path. The tokens are entered as a %#% string, with # being one of the special folder numbers. You can use the %appdir% and %appname% replacement tokens anywhere within any subdirectory path for this type of entry.

Here is an example that excludes the DirectX subdirectory of the "Windows system" special folder from redirection. The second entry also excludes the application's subdirectory of the "user profile" special folder from redirection:

[FilesystemExclude]
1=%37%\DirectX
2=%40%\%appname%

It's also possible to enter regular paths, either relative or absolute, and either local (paths using drive letters) or remote (paths using server domains and network shares.) Any relative path in this section is relative to the configuration ini containing it.

Here are some examples for each possible non-special folder related path type. Keep in mind that these are just examples, so they don't make much sense for real world use as is:

[FilesystemExclude]
1=C:\
2=D:\myDownloads
3=\\%userdomain%
4=\\myServer\\myData
5=..\myPortables
6=%temp%

Here's a real world use example of how to "safely" (possibly - see below) portablize an application that has its portable file system rooted on the desktop, or within any other special folder:

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

[FilesystemExclude]
1=.\JPE

The above example is not necessarily a 100% fool-proof way to ensure that no problems will arise when you have a portable file system rooted within a redirectable file system directory. Because no testing has been done to "prove" that the example settings resolve any and all problems that may occur. The only way to accomplish this for certain is to not have the portable file system rooted within a redirectable file system directory.


The [FilesystemInclude] section

In this section you specify the file system special folders that you want to be portablized. You do this by entering an ascending, consecutively numbered list of special folder numbers for the associated file system special folders. Since all of the file system special folders are portablized by default, you only make use of this section when you have 1=* as the only entry in the FilesystemExclude section.

Here is an example that includes all "Windows install directory" special folders for redirection:

[FilesystemExclude]
1=*

[FilesystemInclude]
1=20
2=36
3=37
4=41
5=56

In addition to using special folder numbers by themselves, you may also use special folder number tokens, optionally followed by a subdirectory path. The tokens are entered as a %#% string, with # being one of the special folder numbers. You can use the %appdir% and %appname% replacement tokens anywhere within any subdirectory path for this type of entry.

Here is an example that includes the DirectX subdirectory of the "Windows system" special folder for redirection. The second entry also includes the application's subdirectory of the "user profile" special folder for redirection:

[FilesystemExclude]
1=*

[FilesystemInclude]
1=%37%\DirectX
2=%40%\%appname%

It's also possible to enter regular paths, either relative or absolute, and either local (paths using drive letters) or remote (paths using server domains and network shares.) Since the paths are not special folder number related, you must also enter the associated redirection path in the SpecialFolders section. Any relative path in this section is relative to the configuration ini containing it, unlike a relative path in the SpecialFolders section.

Here are some examples for each possible non-special folder related path type:

[FilesystemInclude]
1=C:\
2=D:\myDownloads
3=\\%userdomain%
4=\\myServer\\myData
5=..\myPortables
6=%temp%

[SpecialFolders]
C:\=Drives\C
D:\myDownloads=Portable\Downloads
\\%userdomain%=Portable\ServerData\%userdomain%
\\myServer\\myData=Portable\ServerData\myServer
..\myPortables=D:\Portables
%temp%=Portable\Temp


The [FilesystemIgnore] section

In this section you specify the file system special folders that you want to hide from the application as existing in the file system. You do this by entering an ascending, consecutively numbered list of special folder numbers for the associated file system special folders.

This list of file system special folders is used by JauntePE only after it has been determined that a given file system special folder is to be portablized and that the file system special folder does not exist in the portable file system. Then, if the given path is a "FilesystemIgnore" path, the application is told that the path does not exist. In practice, putting file system special folder paths into this section prevents an application from using the contents of any like file system special folders.

In addition to using special folder numbers by themselves, you may also use special folder number tokens, optionally followed by a subdirectory path. The tokens are entered as a %#% string, with # being one of the special folder numbers. You can use the %appdir% and %appname% replacement tokens anywhere within any subdirectory path for this type of entry.

You may also use a special \*.* path-ending qualifier on any entry using a special folder number token, as an indicator to JauntePE to "ignore" the contents of the path's directory but to treat the directory itself as if it exists.

Here is an example of what JPE Quickie uses when the "This is for an application already normally installed or run" checkbox is selected.

It's also possible to enter regular paths, either relative or absolute, and either local (paths using drive letters) or remote (paths using server domains and network shares.) Any relative path in this section is relative to the configuration ini containing it. Here are some examples for each possible non-special folder related path type:

[FilesystemIgnore]
1=C:\
2=D:\myDownloads
3=\\%userdomain%
4=\\myServer\\myData
5=..\myPortables
6=%temp%

You may also be able to enter a regular path with the special \*.* path-ending qualifier appended to it, although this has not been tested. For example, entering 1=D:\*.* would be a way to tell JauntePE to treat the contents of the D: drive as if it doesn't exist, but to treat the drive itself as if it does exist.


The [SpecialFolders] section

In this section you specify the subdirectory paths you want to use as overrides for any of the portable file system special folder default relative paths. You do this by equating the special folder number with the overriding subdirectory path. The overriding subdirectory path may be relative or absolute. If entered as a relative path, it is taken to be relative to the Data path given in the Filesystem section.

Following is an example that overrides the default relative path for all of the "desktop" special folders:

[SpecialFolders]
0=Desktop1
16=Desktop2
25=Desktop3

In this section you also specify associated entries for each unique regular path, i.e., non-special folder path, entered in the FilesystemExclude, FilesystemInclude, and FilesystemIgnore sections. Please see those section's descriptions for examples of what needs to go into this section for those types of paths.

The following table lists all of the currently used folder numbers (as of Vista) and their associated JauntePE default relative paths and summary descriptions. The JauntePE default relative path is what would be used if you don't override the special folder with your own relative path within the [SpecialFolders] section.

The "Summary Description"s given below have all been summarized from this MSDN Library web page. Please be aware that, as noted in the linked-to page, not all special folders are available on all versions of Windows.