[Wireshark-dev] cannot load the module error

2010-04-27 Thread ankur madan
Hi, i created my own dissector "dissbill".i created the dll and manifest of this plugin and copied it to c:\program files\wireshark\plugin.after that i run tshark.exe though cmd.it gave me the error,could not load the module and msvcr80.dll not found. after this i copied msvcr80.dll to system32

Re: [Wireshark-dev] cannot load the module error

2010-04-27 Thread Graham Bloice
On 27/04/2010 11:05, ankur madan wrote: > Hi, > i created my own dissector "dissbill".i created the dll and > manifest of this plugin and copied it to c:\program > files\wireshark\plugin.after that i run tshark.exe though cmd.it > gave me the error,could not load the module and

Re: [Wireshark-dev] cannot load the module error

2010-04-27 Thread ankur madan
I have downloaded version 1.2.7 and installed it separatelly and i have copied the dllat *c:\program files\wireshark*. i have build version of wiresshark at *c:\wireshark*,through which i created my own dissector. so i copied the dll from *c:\wireshark\plugins to c:\program files\wireshark\plugins\

Re: [Wireshark-dev] cannot load the module error

2010-04-27 Thread Graham Bloice
On 27/04/2010 11:19, ankur madan wrote: > I have downloaded version 1.2.7 and installed it separatelly and i > have copied the dllat *c:\program files\wireshark*. > i have build version of wiresshark at *c:\wireshark*,through which i > created my own dissector. > so i copied the dll from *c:\wiresh

Re: [Wireshark-dev] cannot load the module error

2010-04-27 Thread wsgd
Using VS2008 is the best solution. If it is not possible. For runtime error R6034, you can also look at : - http://msdn.microsoft.com/en-us/library/ms235560%28VS.80%29.aspx For the msvcr80.dll problem, see : - http://www.microsoft.com/downloads/details.aspx?familyid=32bc1bee-a3f9-4c13-9c99-220b

Re: [Wireshark-dev] cannot load the module error

2010-04-28 Thread ankur madan
thanks for the suggestions,but it is not working out for me.still having the same rumtine error. On Tue, Apr 27, 2010 at 11:55 PM, wsgd wrote: > Using VS2008 is the best solution. > > > If it is not possible. > For runtime error R6034, you can also look at : > - http://msdn.microsoft.com/en-us/l