> And you were using the same version of WinPcap in both cases?
Yes, 3.1.
I wound up using 0.10.14 for captures, and 0.99.0 when I needed
newer dissector support. .10.14 would work .99.0 would crash.
Using the same capture filters, .99.1p1 works. Whew!
-----Original Message-----
From: Guy Harris [mailto:guy@xxxxxxxxxxxx]
Sent: Thursday, June 08, 2006 7:33 PM
To: Eric Wedel
Cc: wireshark-dev@xxxxxxxxxxxxx
Subject: Re: [Wireshark-dev] ethereal -> wireshark settings?
On Jun 8, 2006, at 7:18 PM, Eric Wedel wrote:
> Not sure if this is politic or not, but it would be convenient if the
> ethereal settings were automagically imported into wireshark when
> there are no ws settings.
> [Tested 0.99.1p1 under windows.]
>
> I manually copied
> C:\Documents and Settings\ewedel\Application Data\ethereal\cfilters
> to
> C:\Documents and Settings\ewedel\Application Data\wireshark\cfilters
> and wireshark read them fine.
Yes, it should either try opening "...\ethereal \..."/"~/.ethereal/..."
if "...\wireshark\..."/"~/.wireshark/..."
fails, or try copying those to the Wireshark location and then try
opening them.
> On a side note, I'm happy to report that multi-term capture filters
> don't crash wireshark, at least in my limited testing. That's a vast
> improvement from 0.99.0.
And you were using the same version of WinPcap in both cases?
