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

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: "RABRET Laurent FTRD/DAC/ISS" <laurent.rabret@xxxxxxxxxxxxxxxxx>
Date: Fri, 28 May 2004 11:38:08 +0200
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

PCAP				.cap, .acp, .pcap
LANALYZER			?
NG SNIFFER			?
SNOOP				.snoop
SHOMITI			?
IPTRACE			?
NETMON			?
NETXRAY			?
RADCOM			?
ASCEND			?
NETTL				?
TOSHIBA			?
I4BTRACE			?
CSIDS				?
PPPDUMP			?
ETHERPEEK			?
VMS				?
ETHERWATCH			?
VISUAL_NETWORKS		?
COSINE			?
5VIEWS			?
ERF				?
HCIDUMP			?
NETWORK_INSTRUMENTS	?
AIROPEEK			?
EYESDN			?


-----Original Message-----
From: ethereal-dev-bounces@xxxxxxxxxxxx
[mailto:ethereal-dev-bounces@xxxxxxxxxxxx] On Behalf Of Guy Harris
Sent: Friday, May 28, 2004 4:52 AM
To: Ethereal development
Subject: Re: RE : [Ethereal-dev] application path of ethereal in windows
registry

RABRET Laurent FTRD/DAC/ISS said:
> There's also a straight and forward way that does not require any
access
> to the registry: the ShellExecute(...) system call. Just one
constraint:
> you must call a valid file that extension is associated to Ethereal.
> Hummm, it seems there's no such an association created in the nsis
> script so I propose a patch to automatically do this with '.cap'
> extensions. Thanks to check in.

See my earlier mail on this thread for reasons why ".cap" isn't the
right
choice for libpcap-format capture files (too many network analyzers
already use it, so it's *already* overloaded).

WildPackets' ProConvert uses ".dmp"; Analyzer:

    http://analyzer.polito.it/

appears to use ".acp" - I'd be inclined to make ".acp" the default, as
Analyzer is another free packet analyzer with libpcap format as its
native
format, unless the Ethereal-derived Packetyzer:

    http://www.packetyzer.com/

has a default suffix other than ".acp" *and* that suffix isn't the
".cap"
that:

    the Windows version of Sniffer;

    Network Monitor;

    Shomiti Surveyor;

    Acterna Domino, Fireberd[sic] 500, and LinkView PRO;

    Fluke Protocol Inspector;

already use (for file formats different from each other, although
*maybe*
all the Acterna products use the same format).

_______________________________________________
Ethereal-dev mailing list
Ethereal-dev@xxxxxxxxxxxx
http://www.ethereal.com/mailman/listinfo/ethereal-dev