Generally speaking, PowerPro is portable in the sense that it doesn't write its
settings into the Windows
registry but instead saves them to file pproconf.pcf file (default) in its
installation folder. This allows to
move PowerPro to another PC by simply copying its installation folder. However,
there are some
exceptions to consider.
The PowerPro setup program does write to the registry the installation folder
path, and explorer file
type extensions associated with PowerPro files, .powerpro, .ppronote,
.powerproclip. I believe
Windows also records flags for whether a program start group and a desktop
shortcut icon were
created. If you copy powerpro to another PC, you can recreate registry settings
for explorer file types
using a registry editor or other suitable means; note that PowerPro doesn't
need this information in
order to run, it's only for added convenience when double clicking in explorer.
The Powerpro setup program can install PowerPro for multiple users, in which
case .pcf files - and
possibly other files such as notes, are stored in each user's own application
data directory. I have no
experience with this type of setup, but I'm pretty sure it can be easily
portabilized.
By default PowerPro doesn't install an explorer context menu, but it can add
one when clicking button
Install Context Menu in the Setup tab of pproconf.exe. This will write some
keys into the Windows
registry. Likewise buttons Install Taskbar bar and Install Tray Support in the
same tab write into the
registry. I have no experience with Taskbar bar. I know that Tray Support
appends "\path\to
\pprotray.exe" to the value of HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT
\CurrentVersion\Winlogon.
As noted elsewhere, portability of scripts and configuration is improved if you
use relative paths instead
of absolute ones. Most fields in command list item setup dialogs understand
relative paths - with
respect to PowerPro's start folder - or environment variables - if
"pproconf.exe > Setup > advanced
setup > Other > replace %environment var% throughout command" is enabled. So
for instance, in a
command list button setup dialog, you could refer to an icon in file
\path\to\PowerPro\icons\img.ico
simply as icons\img.ico. Or you could set an environment variable
ICONS=\path\to\icons\folder before
running PowerPro, then refer to an icon as %ICONS%\img.ico.
Inside scripts you could use expressions involving
Env("ICONS")++"\icons\img.ico", pprofolder++?"\icons
\img.ico", etc.
Finally, in some cases you may want to start PowerPro from ppBangTwice.exe -
available in the yahoo
group files section - because ppBangTwice.ini allows you to specify the
PowerPro start path.
