Huge thanks to our Platinum Members Endace and LiveAction,
and our Silver Member Veeam, for supporting the Wireshark Foundation and project.

Wireshark-bugs: [Wireshark-bugs] [Bug 5512] msvcr80.dll error trying to start tshark on windows

Date: Thu, 23 Dec 2010 07:48:42 -0800 (PST)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=5512

Bill Meier <wmeier@xxxxxxxxxxx> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |INVALID

--- Comment #7 from Bill Meier <wmeier@xxxxxxxxxxx> 2010-12-23 10:48:41 EST ---
(In reply to comment #6)
> I wrote a script that did 
> set path=
> before calling tshark, now it works. So, my fault, I guess.
> Many thanks for helping.

You're welcome.

For the record: 

Re:

>   There are a number of "Delay Load Modules" which I could imagine 
>   somehow want msvcr80.dll (if I understand the way Windows handles DLL's).

In actuality, the dependencies for the Delay Load Modules are shown in the
"depends" output so I was wrong about that.

Looking at the "depends" Help I see that there are other dependencies which can
be detected only by doing "Application Profiling".

Extract from the Help: (See the Help for more details).

Case 4 and 5 require runtime profiling, a new feature in Dependency Walker 2.0.
For more information on profiling, see the Using Application Profiling to
Detect Dynamic Dependencies section.

-- 
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.