Hi folks
,
JauntePE is back thanks to "Redlar" vers 0.3.0
Heres a 12 step get ya going helpYA!
Intro:
Here's the beginnings of what I'm calling the JauntePE 12-step program. It's meant to be a guide of sorts for helping you to "properly" configure an application for initial portable use via JPE. There's still a lot of negative-path problems to be addressed, so don't be surprised if you try the steps on an app and it doesn't work. I'll try and fill in the missing parts as soon as I can.
One thing I'll point out now is that not every app requires this type of set up. But this is the most generic set up and shouldn't cause problems for those apps that don't require it. It will just make things a bit more messy for you.
1. Create a portable directory for your app. From here on "your app" will be
referred to as %appname%. So if your app is generally known as Snafu, then
replace %appname% with Snafu everywhere within this document.
- Don't create the directory on the desktop or in Program Files or
MyDocuments, etc.
- Use some place like "E:\Portables\%appname%". From here on this directory
will be referred to as %appdir%.
2. Copy JPE's distributed JauntePE_jauntePE.ini file to %appdir%.
3. Edit it to contain the additional following lines at the top (sans numbering):
1. [Registry]
2. Use=1
3. Data=.\jauntePE_registry.reg
4.
5. [Filesystem]
6. Use=1
7. Data=.\
8.
9. [Redirection]
10. Logging=1
4. Copy the %appname% installer to %appdir%. If it doesn't have one, then do
the following:
- Create a "Files" sub-directory in %appdir%.
- Create a "ProgramFiles" sub-directory in "Files".
- Create a %appname% sub-directory in "ProgramFiles".
- Copy all of the app's files and sub-directories to this lowest-level sub-
directory, i.e., copy to %appdir%\Files\ProgramFiles\%appname%.
- Skip to step 8.
5. Start JPE and drag-n-drop the %appname% installer onto the JPE launchpad.
6. Open up the launchpad icon's properties and:
- Check "Registry",
- Check "File system",
- Check "App-specific registry storage",
- Un-check "In-memory registry".
7. Run the %appname% installer via the JPE launchpad icon:
- Accept the settings per your requirements, but make sure that the app is
to be installed in the typical "%ProgramFiles%\%appname%" location, where
%ProgramFiles% is the full path to your standard "Program Files" directory.
- Don't have it run the app or do anything else after the installation has
completed.
8. Create a JauntePE_jauntePE.ini in the %appdir%\Files\ProgramFiles\%appname%
directory that contains the following lines (sans numbering):
1. [Registry]
2. Use=1
3. Ini=..\..\..\JauntePE_jauntePE.ini
4.
5. [Filesystem]
6. Use=1
7. Ini=..\..\..\JauntePE_jauntePE.ini
9. Drag-n-drop the %appdir%\Files\ProgramFiles\%appname%\%appname%.exe file
onto the JPE launchpad.
10. Open up the launchpad icon's properties and:
- Check "Registry",
- Check "File system",
- Check "App-specific registry storage",
- Un-check "In-memory registry".
11. Run the %appname% app via the JPE launchpad icon.
12. If all goes well, then you can, if you wish, modify the %appdir% directory's
JauntePE_jauntePE.ini file to be more specific to your app, i.e., optimize
the redirection entries to create the fastest possible JPEized solution,
use the build wizard to create a standalone app launcher for it, etc. I like
to keep the launchpad icons handy for editing, re-building, etc. If the new
JPE gui is ever released, it allows you to edit the app-specific JPE runtime
settings just like you can now edit the default equivalents
Command line usage =============== Syntax:
JauntePE.exe [switches] path-to-executable
-or-
JauntePE_cmdline.exe [switches] path-to-executable
The optional [switches] parameters default to -l. Separate
each parameter by at least one space.
Build switches:
-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)
Launch switches:
-l - launch an application executable
Build and launch switches:
-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 JauntePE
home directory)
-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 JauntePE home
directory)
-R - portablize the registry changes into an application-
specific .reg (located in the application executable's
diretory)
-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)
The following build and launch switches are still very much
untested and experimental:
-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 - using this switch with the -b -i switches
will also cause the stuffed .reg to be passed to the
application directly without first writing it to a
file - this is the fastest way to launch an app
N-JOY!
ispy
,
JauntePE013.zip 162.96KB
1509 downloads
,
