Hi, GV! I rebuilt the wireshark with the VS2005 SP1 redistribution package, now the problem is solved. Thanks!
regards, Guo Gianluca Varenni wrote: > You need to install the VC runtime build 762 on the target machine. That is > the easiest way to have a version of Wireshark built with Visual Studio 2005 > Express Edition SP1 running on a machine. > > http://www.microsoft.com/downloads/details.aspx?FamilyID=200B2FD9-AE1A-4A14-984D-389C36F85647&displaylang=en > > Alternatively you need to add the VC runtime (msvcr80.dll, the exact version > matching the manifest embedded in the wireshark binaries) and a specific > manifest file to the wireshark folder that allows the local resolution of > the C runtime to the local copy of it and not the copy that is usually > installed in the side-by-side execution folder of windows > (c:\windows\WinSxS, if you are familiar with .NET it's more or less the GAC > for unmanaged DLLs). > > In case of the runtime build 762, the manifest file should be called > "Microsoft.VC80.CRT.manifest" and its content should be the following one > > <?xml version="1.0" encoding="UTF-8" standalone="yes"?> > <assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0"> > <noInheritable></noInheritable> > <assemblyIdentity type="win32" name="Microsoft.VC80.CRT" > version="8.0.50727.762" processorArchitecture="x86" > publicKeyToken="1fc8b3b9a1e18e3b"></assemblyIdentity> > <file name="msvcr80.dll" hash="10f4cb2831f1e9288a73387a8734a8b604e5beaa" > hashalg="SHA1"><asmv2:hash xmlns:asmv2="urn:schemas-microsoft-com:asm.v2" > xmlns:dsig="http://www.w3.org/2000/09/xmldsig#"><dsig:Transforms><dsig:Transform > > Algorithm="urn:schemas-microsoft-com:HashTransforms.Identity"></dsig:Transform></dsig:Transforms><dsig:DigestMethod > > Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"></dsig:DigestMethod><dsig:DigestValue>n9On8FItNsK/DmT8UQxu6jYDtWQ=</dsig:DigestValue></asmv2:hash></file> > <file name="msvcp80.dll" hash="b2082dfd3009365c5b287448dcb3b4e2158a6d26" > hashalg="SHA1"><asmv2:hash xmlns:asmv2="urn:schemas-microsoft-com:asm.v2" > xmlns:dsig="http://www.w3.org/2000/09/xmldsig#"><dsig:Transforms><dsig:Transform > > Algorithm="urn:schemas-microsoft-com:HashTransforms.Identity"></dsig:Transform></dsig:Transforms><dsig:DigestMethod > > Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"></dsig:DigestMethod><dsig:DigestValue>0KJ/VTwP4OUHx98HlIW2AdW1kuY=</dsig:DigestValue></asmv2:hash></file> > <file name="msvcm80.dll" hash="542490d0fcf8615c46d0ca487033ccaeb3941f0b" > hashalg="SHA1"><asmv2:hash xmlns:asmv2="urn:schemas-microsoft-com:asm.v2" > xmlns:dsig="http://www.w3.org/2000/09/xmldsig#"><dsig:Transforms><dsig:Transform > > Algorithm="urn:schemas-microsoft-com:HashTransforms.Identity"></dsig:Transform></dsig:Transforms><dsig:DigestMethod > > Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"></dsig:DigestMethod><dsig:DigestValue>YJuB+9Os2oxW4mY+2oC/r8lICZE=</dsig:DigestValue></asmv2:hash></file> > </assembly> > > Hope it helps > GV > > PS. This stuff is documented in the MSDN documentation, I don't remember the > exact term for this on top of my head. It's something like "local > deployment" or similar. > > > > > ----- Original Message ----- > From: "Hongxiang GUO" <[EMAIL PROTECTED]> > To: <[email protected]> > Sent: Wednesday, August 01, 2007 11:20 PM > Subject: [Wireshark-dev] To create a wireshark installer > > > >>Hi, I am trying to install the wireshark built with [EMAIL PROTECTED] on >>another PC. But when I launch the installed wireshark.exe, it warns the >>missing of msvcr80.dll. According to Matthias's advice >>(http://www.wireshark.org/lists/wireshark-dev/200703/msg00628.html), >>actually the issue comes from the version mismatch of x86_micrisift.VC80. >>------------------------- >>The building machine is installed with version 8.0.50727.762 and >>8.0.50727.42, but wireshark was built with version 762. So the wireshark >>can not run on the PC where only version 42 is installed. >> >>Matthias said we can manualy modify manifest file, but manifest file is >>automatically generated during built. So can anyone give some solution? >> >>Thanks, >>Guo >> >>_______________________________________________ >>Wireshark-dev mailing list >>[email protected] >>http://www.wireshark.org/mailman/listinfo/wireshark-dev > > > _______________________________________________ > Wireshark-dev mailing list > [email protected] > http://www.wireshark.org/mailman/listinfo/wireshark-dev _______________________________________________ Wireshark-dev mailing list [email protected] http://www.wireshark.org/mailman/listinfo/wireshark-dev
