Re: [Wireshark-dev] Microsoft Visual C Version 6 support is a bit outdated ...

2006-12-18 Thread Gerald Combs
Ulf Lamping wrote: > Gerald Combs wrote: >> No complaints here. Are there any issues with the supporting libraries >> that need to be addressed, e.g. msvcrt.dll vs msvcr7.dll? >> > Do you mean legal issues, or something else? I mean having Wireshark linked against a newer CRT DLL and glib link

Re: [Wireshark-dev] Microsoft Visual C Version 6 support is a bit outdated ...

2006-12-18 Thread Ulf Lamping
Gerald Combs wrote: > No complaints here. Are there any issues with the supporting libraries > that need to be addressed, e.g. msvcrt.dll vs msvcr7.dll? > Do you mean legal issues, or something else? Regards, ULFL ___ Wireshark-dev mailing list Wires

Re: [Wireshark-dev] Microsoft Visual C Version 6 support is a bit outdated ...

2006-12-18 Thread Gerald Combs
Ulf Lamping wrote: > Hi List! > > We currently only "support" MSVC Version 6 for the Windows builds. > > As Version 6 is pretty much outdated and it's possible that I won't have > access to such an installation in the near future, it seems to become > time to make WS buildable on a newer MSVC v

[Wireshark-dev] Microsoft Visual C Version 6 support is a bit outdated ...

2006-12-18 Thread Ulf Lamping
Hi List! We currently only "support" MSVC Version 6 for the Windows builds. As Version 6 is pretty much outdated and it's possible that I won't have access to such an installation in the near future, it seems to become time to make WS buildable on a newer MSVC version. If available time permit

Re: [Wireshark-dev] Changed capture options default settings to use real time display

2006-12-18 Thread Stephen Fisher
On Tue, Dec 19, 2006 at 02:07:39AM +0100, Ulf Lamping wrote: > Accordingly, I've changed the defaults "Update list of packets in > realtime" and "Auto scroll" to TRUE and the "show summary window" to > FALSE. Good catch, thanks! Steve ___ Wireshark

[Wireshark-dev] Changed capture options default settings to use real time display

2006-12-18 Thread Ulf Lamping
Hi List! To my surprise, after installing WS on a new machine, I've realized that the default capturing options are still to show the capture summary window while a capture is in progress. Unfortunately, this hides a very helpful feature to new users - unless he/she figures out that this featu

Re: [Wireshark-dev] [PATCH] ISIS dissector

2006-12-18 Thread Stephen Fisher
On Sun, Dec 10, 2006 at 04:06:15AM +0100, Sebastien Tandel wrote: >a little patch against revision 20088 in packet-isis-lsp.c for the > following : > - hf_isis_lsp_remaining_life declared but unused > - replacing a proto_tree_add_uint useless with proto_tree_add_item Your patch has been check

Re: [Wireshark-dev] How to dissect bit information

2006-12-18 Thread Anders Broman \(AL/EAB\)
Hi, In addittion look at the funktion dissect_gsm_map_ISDN_AddressString() ip packet-gsm_map.c and item = get_ber_last_created_item(); subtree = proto_item_add_subtree(item, ett_gsm_map_isdn_address_string); proto_tree_add_item(subtree, hf_gsm_map_extension, parameter_tvb, 0,1,FALSE); proto_

Re: [Wireshark-dev] How to dissect bit information

2006-12-18 Thread Anders Broman \(AL/EAB\)
Hi, The value used to mach the value string value is the "masked out" value. So if the value is 0xc0f0 and the mask is 0xc00 the value used to match the string would be 3. BR Anders Från: [EMAIL PROTECTED] genom [EMAIL PROTECTED] Skickat: må 2006-12-18 08:09 Ti

[Wireshark-dev] How to dissect bit information

2006-12-18 Thread taraniteja.vishwanatha
Hi Anders/ Steve , This is with regards to the mail posted by vikash "How to dissect bit information". As you have suggested we can get the desired bit/bits by masking the remaining bits.But the problem we are facing is there is a set of values assosiated with each bit / bits.In Wireshark, t

Re: [Wireshark-dev] Adding "copy packet data" functionality to the packet list and packet details panes

2006-12-18 Thread Douglas Pratley
Thanks for the feedback. > Having two Copy menu items in the details context menu might > be too much, however, "remixing" the copy menu items will be > easy once the functionality is settled, so the menu structure > shouldn't be a problem. Yep; I'll just get something working and see how it