This error message could be a manifest problem.
The manifest must be :
- into the dll directory
- directly inside the dll (using mt.exe -manifest 
<dll_name>.dll.manifest -outputresource:<dll_name>.dll;2)


Olivier


yvanmmailbox-...@yahoo.fr a écrit :
> Sure, I have another one, my main plugin afdx.dll that works. This one 
> is necessary for bite.dll working, but I put both in the folder, like 
> I do on my installed version, and I have the error message.
>
> That's why I need some ways to search the problem. What are the main 
> differences between the portable version and the installed version 
> (except the folders) that could have a link with plugins?
> Does my installed version could create problems for the portable version?
>
> Note: I put the plugins in the "Global plugins" folder and not in the 
> "Personal plugins" folder, which does not exist.
>
> Thanks
>
> Yvan
>
> ------------------------------------------------------------------------
> *De :* Graeme Lunt <gra...@lunt.uk.com>
> *À :* Developer support list for Wireshark <wireshark-dev@wireshark.org>
> *Envoyé le :* Mardi, 23 Juin 2009, 14h58mn 10s
> *Objet :* Re: [Wireshark-dev] Plugin compatibility with Portable version
>
> Hi,
>
> There should be no particular problem using custom plugins with the 
> WiresharkPortable.
>
> As you say "one of them", can I assume that you have got other plugins 
> to work?
>
> Is it perhaps that bite.dll requires some other dlls to be present?
>  
> Graeme
>
> 2009/6/23 <yvanmmailbox-...@yahoo.fr <mailto:yvanmmailbox-...@yahoo.fr>>
>
>     Hi list,
>
>     I developed plugins that works well on standard Windows version of
>     Wireshark (1.2.0), but one of them can't be loaded on the portable
>     version (same version number). I have the following error:
>     Couldn't load module
>     F:\Softs\WiresharkPortable\App\Wireshark\plugins\1.2.0\bite.dll:
>     `F:\Softs\WiresharkPortable\App\Wireshark\plugins\1.2.0\bite.dll':
>     Le module spécifié est introuvable. (can't find specified module)
>
>     Does anyone have an idea what could be the problem?
>
>     thanks a lot
>
>     Yvan
>
>
>     
> ___________________________________________________________________________
>     Sent via:    Wireshark-dev mailing list
>     <wireshark-dev@wireshark.org <mailto:wireshark-dev@wireshark.org>>
>     Archives:    http://www.wireshark.org/lists/wireshark-dev
>     Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
>                 mailto:wireshark-dev-requ...@wireshark.org
>     <mailto:wireshark-dev-requ...@wireshark.org>?subject=unsubscribe
>
>
>
> ------------------------------------------------------------------------
>
> ___________________________________________________________________________
> Sent via:    Wireshark-dev mailing list <wireshark-dev@wireshark.org>
> Archives:    http://www.wireshark.org/lists/wireshark-dev
> Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
>              mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev@wireshark.org>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

Reply via email to