ANNOUNCEMENT: Live Wireshark University & Allegro Packets online APAC Wireshark Training Session
April 17th, 2024 | 14:30-16:00 SGT (UTC+8) | Online

Wireshark-dev: Re: [Wireshark-dev] U3 questions/remarks

From: Ulf Lamping <ulf.lamping@xxxxxx>
Date: Sat, 03 Feb 2007 05:38:48 +0100
Graeme Lunt wrote:
Good news. I think there's only a couple of us using it to date. I find it very useful.
I'm still unsure if the ProtableApps approach is just good enough ;-)

However, the eject feature is in fact cool.
Well of the 5 programs on my U3 device, one is "for U3", one is "U3 Edition"
and the others are just their plain name. Personally I'm not for adding any
"U3" component to the name - as where you stop? Do you change to "About
Wireshark for U3" on the Help menu?
Using the term "Wireshark" would be ok, it's pretty obvious that it's running "an U3 edition" if your looking at the U3 Launchpad ;-)
As to the version in the U3 launchpad item, then that should probably go. I
find it very useful as I generally have 3 versions on my USB stick - current
public release, current development build, my personal build. This makes it
easy to see what I have fixed/broken! 8^)
Hmmm, interesting. How do you install more than one WS version on a stick? Do you use different GUID's for the different versions? Or do you simply use more than one stick ;-)

Idea: If you use different GUID's, should we add the SVN version into the GUID somehow to do this automatically?
But there are other ways handle the version number than putting it up front
on the GUI in the release build.
Given the other comments, I think I will add it to the description which
comes up as a tooltip, which is slightly easier than bringing up the
Wireshark properties.
Where does it come up as a tooltip? I'm using the U3 Launchpad (1.1.0.2) from my Toshiba stick and it doesn't show up a tooltip in the launchpad at all :-(

Maybe I'll need an upgrade for the U3 Launchpad?
Well, I've just had a quick look at this and it appears to be because the
Wireshark icon I put into the manifest has more than 256 colours. This is
not a problem for the main launchpad window but it apparently a problem for
the "More Programs" sub menu. To be fair the U3 spec says it should only be
256 colours. So I'll look at updating the makefile to automatically
downgrade the icon for the U3 package.
I think that one seems to be fixed recently :-)
Had thought about this but not come to any decision. Maybe adding something
like:

"... from the <device> U3 device on drive <drive>."

For example,
"Running on Windows XP Service Pack 2, build 2600, without WinPcap, without
AirPcap from the Sandisk Titanium U3 device on drive I:"
Sounds very good, could you add it?
WinPcap:
- if WinPcap was manually uninstalled (without a reboot in the meantime), starting WS from U3 won't ask for a new WinPcap install (the detection logic might better use the uninstall string from the registry)

In your example above, I assume you uninstalled WinPcap after having run
Wireshark once from the U3 device?
Sorry, can't remember, but that's really possible.
Currently, the U3 packaging only checks for WinPcap the first time you run
Wireshark from the U3 device.
The reason being that if you don't want to install WinPcap, you are not
continually asked each time you run Wireshark. (This is one of my use
cases.)
That behaviour sounds reasonable. However, as you won't uninstall WinPcap very often, that's not a big problem in any way.
The detection does indeed use the uninstall string - I copied the approach
from a master - it just isn't called each time you run Wireshark.

If you think this is a useful feature, it may be better to incorporate into
Wireshark itself - as if you uninstall WinPcap after installing Wireshark
from the NSIS package, you won't be prompted to install it again either.
Maybe ask if you try to "Start" a capture and WinPcap cannot be loaded?
I was thinking exactly about this myself :-) We install the winpcap installer in "Program Files" already, so it should be possible to add this without much extra work.

I'll have deeper a look into this when I'll find some time to add the version check / updater feature I'm planning to implement for the next release (as time permits) ...

Regards, ULFL