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

Note: This archive is from the project's previous web site, ethereal.com. This list is no longer active.

Date Index Thread Index Other Months All Mailing Lists
Date Prev Date Next Thread Prev Thread Next
From: "Eric Wedel" <ewedel@xxxxxxxxxxx>
Date: Fri, 28 May 2004 18:15:12 -0700
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.

regards,
Eric, BlueArc Engineering

-----Original Message-----
From: ethereal-dev-bounces@xxxxxxxxxxxx
[mailto:ethereal-dev-bounces@xxxxxxxxxxxx]On Behalf Of RABRET Laurent
FTRD/DAC/ISS
Sent: Friday, May 28, 2004 2:38 AM
To: Ethereal development
Cc: Biot Olivier
Subject: RE : RE : [Ethereal-dev] application path of ethereal in
windowsregistry


Ok, because there are many applications on the network analysers market
we could add some flexibility... What about linking ethereal with
standard file extensions (.cap, .pcap, .acp, etc...) *not already used
in the system* (at the time Ethereal is installing of course). If you
think it's reasonable, I can change the nsis script for this.

I'll have to pick up standard extensions associated with all the formats
Ethereal is able to deal with. If some of you guys have already some
knowledge regarding this, thanks in advance for their help