aboutsummaryrefslogtreecommitdiffstats
path: root/packaging/portableapps/win32/readme.txt
blob: 3cb6411c0c8c1b5bbc838ec4d4d68be937c4da6e (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
$Id$

Portable Wireshark
==================

This directory contains experimental packaging for running Wireshark under the Portable Apps 
(http://www.portableapps.com/). 

The packaging relies on the same "manifest" as used by the U3 packaging. Therefore there is no need to maintain a list of relevant files for the Portable Wireshark. Only the U3 list needs to be updated.

Currently only an additional menu item for Wireshark is added - the other tools could be added to Portable Apps menu if required.

WinPcap
=======

If you want to capture packets, then WinPcap needs to be installed. Wireshark Portable will try and install WinPcap if it doesn't find it installed on the local machine. If it does install it, it will uninstall it when Wireshark Portable quits.
A quieter install/de-install for WinPcap would help matters - but ultimately a minimal installation mechanism needs to be identified for WinPcap. But that is not for the Wireshark forum.

NSIS
====

The Portable Apps packaging uses the NullSoft Scriptable Installer System (NSIS) to create a installation package to install onto the USB drive, and a launcher to launch Wireshak from the USB drive.

NSIS is used by the standard Win32 installation mechansim (packaging/nsis) but an additional plug-in is required for the Wireshark Portable launcher. This is now automatically downloaded and installed from the wireshark-win32-libs repository.

INI Settings
============

To be documented.