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

> Let me know if the latest patch takes care of this. As long as device
> names do not contain parens or commas, the ethereal description string
> syntax should be OK. However, I'd like the syntax to be as safe as
> possible. What's the possibility of future device names having parens or
> commas?
>

I have no idea what may be in future device names.  Certainly those on XP
have parens.

With your latest changes (patch III) the windows descriptions have been
removed in the Interface Options dialog, but IMHO this makes things much
more difficult as you only have the actual interface names to look at which,
as I mentioned previously, are not very helpful being strings such as
"\Device\Packet_{F30D9BC7-81C8-4FF1-B98E-DDE87A2DB765}" which are somewhat
hard to relate to actual NICS.

At least with the Windows description visible, as long as your NICs are
different hardware, you can see what's what.

I've attached a dump of the dialog showing the problems.  I've resized the
dialog so (mostly) all the text is displayed.

Option1 is the state of play before your latest changes, although this did
get confused sometimes.  Option2 is after your latest changes.

Thanks for your efforts, we will get there in the end :-)

Graham Bloice

Attachment: option1.png
Description: PNG image

Attachment: option2.png
Description: PNG image