Wireshark · Ethereal-dev: RE : RE : RE : [Ethereal-dev] application path of ethereal in windowsregistry

["RABRET Laurent FTRD/DAC/ISS" <laurent.rabret@xxxxxxxxxxxxxxxxx>]

Hi,

Please find attached an ethereal.nsi patch that:

-          associates standard trace file extensions to ethereal *only* if such extensions are not already known in the system;

-          suppresses the linking while Ethereal is uninstalling *only* for extensions associated to Ethereal.

Regards

Laurent

 

 

-----Original Message-----
From: ethereal-dev-bounces@xxxxxxxxxxxx [mailto:ethereal-dev-bounces@xxxxxxxxxxxx] On Behalf Of Laurent Rabret
Sent: Monday, May 31, 2004 3:42 PM
To: ethereal-dev@xxxxxxxxxxxx
Subject: Re: RE : RE : [Ethereal-dev] application path of ethereal in windowsregistry

 

Ulf,

There's really no problem with the uninstaller. What it should do is just to check the file extension is associated with Ethereal before removing the link.

Regards

Laurent

>

> Guy Harris wrote:
>
>

Eric Wedel said:

Possibly I'm coming in mid-conversation here, but from my own

perspective it would be really nice if the installer could overwrite

the existing mapping for .cap (or whatever).  At our site, a bug

database often saves .cap files collected by netmon, and I personally

much prefer to open them using ethereal.  :-)

Having the extension map to ethereal would save steps there.
Time and installer features permitting, this could of course be optional.

Applications that believe that they know better than I do what application

I should use for a given file type and blithely override existing

associations somewhat irritate me (MP3 players have been a particular

source of irritation for me on Windows), so if we're to do that at all, we

should at least allow the user to specify at installation time whether the

Ethereal installer *should* override existing associations.

> We might want to have another installer page, that let's the user choose > which file types he likes to have attached from a "list of checkboxes", > so the user can select the associations required.

> As it's one of the first things I'm doing after installing Ethereal, is > adding the .cap extension to Ethereal by hand, I would like to have this > done by the installer for me :-)

> I've added an additional page to another NSIS installer for a different > project before, so it won't be too hard to get.

> One question remaining: What does the uninstaller should do with this?

> Regards, ULFL

 

>From: "Laurent Rabret" <laurent_rabret@xxxxxxxxxxx>

>To: ethereal-dev@xxxxxxxxxxxx

>Subject: Re: RE : RE : [Ethereal-dev] application path of ethereal in windows registry

>Date: Sun, 30 May 2004 18:42:08 +0200

>

>Thanks very much  guy for all the information you provided regarding

>the standard extensions. I'll propose a nsis script patch very soon

>(whenever I have access to my Windows programming computer).

>Eric, I also beleive it would be VERY disturbing to change the

>existing association between a program and a file extension that's

>why I'll do the link only for extensions the system doesn't know.

>Regards

>Laurent

>

---

The new MSN 8: smart spam protection and 2 months FREE*

Attachment: ethereal.nsi.diff
Description: ethereal.nsi.diff