["Graham Bloice" <graham.bloice@xxxxxxxxxxxxx>]

> Here's another small patch that fixes a problem when there are "empty"
> descriptions (should have dup'd empty string).

A bit better, but it is still not quite right on win32.

get_interface_list() returns a string such as "ASUSTek/Broadcom 440x 10/100
Integrated Controller (Microsoft's Packet Scheduler):
\Device\Packet_{F30D9BC7-81C8-4FF1-B98E-DDE87A2DB765}" which comprises of
two parts, the hardware description and the interface name.  It would appear
that the only reliable separator is the string ": \".

As the new code places the ethereal description in parentheses, it seems the
code to extract it from the preferences gets confused by the parentheses in
the hardware description.

As a result I'm offered the choice of three interfaces in the capture dialog
all named "(Microsoft's Packet Scheduler)" with the correct interface name
appended.

In addition after several attempts at opening the Interface Options dialog,
I end up with the same string automagically appearing as ethereal
description.

I would suggest a more robust set of delimiters for the ethereal description
string might help.

Graham Bloice