green

content:

Install:
Static:
BlackBox/WhiteBox
support(+) / not support(-)
W+ W- B+ B-

archive format:.zip .cab(2 kinds in fact?) .msi .exe

Dynamic
DS: SB ....
DD: *Mon

RunTime

--------

[Install]

[[static aspect]]

(1) the property of your downloaded files
White: get by unpacked (general .zpi file)
Black: get by simulation running (general .exe or .msi, including .pak.exe)

+: support
-: no support

W+: no installation & officially support (notepad++)
sample: .zip
W-: no installation (in fact similar as W+)
sample: .zip
B+: installation but officailly support (like U3/PA)
if U3/PA site officially says they support, relunctant count as B+
sample: .pak.exe
B-: installation & no portable/green edition
sample: .exe

official site may offer B-, W(+/-), B+
PA site may offer B+ (i have a U3 before and its quality...)
or google to findout B+

if you are clear about what is, for convience & update(upgrade), you can

use B+

(2) the file format of your downloaded files: jsut as in content
your research in them: use
TC: enter/Ctrl-PageDown (also its plugin like MSI)
7-zip or winrar
Universal Extractor
(PEiD as a utility)
sample:
.zip: tc built in support (ENTER)
.cab: seems built in support by TC (example: TC its self's installation

package)
.msi: tc+MSI, or 7-zip, or UE
.exe: Ctrl+pageDown, or 7-zip. or UE

[[dynamic aspect]]
for files of kinds B(lackBox), esp. B-, you may want to simulatig the

installation progress. 2 way:
compare result with initial status: I call it:
DS (Dynamic Static).
use: Sanboxie, regsnap, ...
monitor the whole progress:
DD (Dynamic Dynamic)
use: FileMon & RegMon

[RunTime]
without relation to the above, a program may:
generate/modify file (whether under pragram dir or not)
sample: the .ini file ; data file ; position file ; help.gid ;
%appdata% ; my document ; %temp% ; sendTo ; system32\ ;
....
modify registry
sampel: rightButton Menu ; fileAssocaition
load service (!)
load device driver (!)