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

This example presents a few typical ways of using the new "fake drives" plugin via the CryptoDrive sections' settings. Three fake drives are created, J:, K:, and L:, each with a slightly different set of intended use.

If the J:, K:, and L: drive letters are already in use on your system, you will need to change these drive letters in the ini if you would like to run this example and see the plugin in action.

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.

[Redirection]
MemRegistry=2
UseIcon=1
ModFrame=1

The Registry sections

These section's settings are from the Portablizer plugin's Registry, RegistryExclude, and RegistryInclude sections.

When registry redirection is used, by default ALL registry changes are redirected. In this example we're only concerned with portablizing the application's settings, which we previously discovered was all stored in one registry key. So we first exclude everything (the 1=* line) from redirection and then include back in only that key needing redirection.

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

[RegistryExclude]
1=*

[RegistryInclude]
1=HKEY_CURRENT_USER\Software\Microsoft\%appname%

The Filesystem sections

These section's settings are from the Portablizer plugin's Filesystem, FilesystemExclude, FilesystemInclude, and SpecialFolders sections.

When file system redirection is used, by default ALL file system changes are redirected. In this example we're only interested in portablizing the current user's "My Documents" shell folder and the fonts folder. Having a portablized "My Documents" is a good example of how to carry around your documents and still be able to get to them quickly. Having a portablized fonts folder shows you how to make use of fonts that you carry around with you.

We're not interested in portablizing any other folders. So we first exclude everything (the 1=* line) from redirection and then include back in only those special folders needing redirection.

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

[FilesystemExclude]
1=*

[FilesystemInclude]
1=5
2=20

[SpecialFolders]
5=Documents
20=Fonts

The ShellUsage section

This section's settings are from the Shell Usage plugin's Shell Usage section.

These settings turn on the features that attempt to prevent the application from telling the shell to add any used files to the shell's "most recently used" documents list, and to attempt to prevent the application from deleting files to the shell's recycle bin.

[ShellUsage]
Use=1
PreventMRU=1
PreventBinUse=1

The CryptoDrive sections

These section's settings are from the Fake Drives plugin's CryptoDrive and CryptoDrive? sections.

These settings set up the FakeDrives directory as the base for all of this example's fake drives.

The J: fake drive sets up the ini's parent directory as its root since it's ini-relative path is .\FakeDrives\..\..\ which is equal to ..\. Since the J: drive is not an encrypted drive, it is an example of how to use a fake drive to access your portable documents in a portable manner via non-portable apps that like to store full paths to the documents they open.

The K: fake drive sets up the FakeDrives\K directory as its root using the defaulted path of the drive letter appended to [CryptoDrive]Path. K: is also an example of how to set up an encrypted drive that you don't want to remember the password of.

The L: fake drive also sets up the same FakeDrives\K directory as its root using an explicitly specified path relative to the [CryptoDrive]Path. Since the L: drive is also an encrypted drive, but the password for it is not given via the ini, you will be prompted for the drive's password (which is the same as the K: drives.)

[CryptoDrive]
Use=1
Path=.\FakeDrives

[CryptoDriveJ]
DriveType=2
CryptType=0
Serial#=123456789
Volume=jpeDriveJ
Path=..\..\

[CryptoDriveK]
DriveType=2
CryptType=3
Serial#=987654321
Password=This is a passphrase
Volume=jpeDriveK

[CryptoDriveL]
DriveType=2
CryptType=3
Serial#=123498765
Password=
Volume=jpeDriveL
Path=K