I'll look into this tomorrow.
Just for your information, here is the tree:
JSS4.DLL
NSPR4.DLL
ADVAPI32.DLL
SECUR32.DLL
NETAPI32.DLL
DNSAPI.DLL
MPRAPI.DLL
SETUPAPI.DLL
SHELL32.DLL
SHDOCVW.DLL
MSHTML.DLL
IEFRAME.DLL that finally requires IESHIMS.DLL and WER.DLL
Cheers
Cad
On Mon, Jul 19, 2010 at 6:25 PM, Wan-Teh Chang <w...@google.com> wrote:
> I can suggest two things to help track this down.
>
> 1. Find out which DLLs require IESHIMS.DLL and WER.DLL.
> This should be a chain of DLL dependencies that ultimately
> leads to an NSS or NSPR DLLs (the "culprit"). Right now I
> don't know what the culprit is.
>
> The NSPR DLLs are:
> nspr4.dll, plc4.dll, plds4.dll, or
> libnspr4.dll, libplc4.dll, libplds4.dll
>
> The NSS DLLs are:
> nss3.dll, nssutil3.dll, softokn3.dll, freebl3.dll, nssdbm3.dll,
> smime3.dll, ssl3.dll, nssckbi.dll
>
> 2. Find out the environment variable that we need to set
> to change the target Windows version for Windows SDK.
>
> Wan-Teh
> --
> dev-tech-crypto mailing list
> dev-tech-crypto@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-tech-crypto
>
--
dev-tech-crypto mailing list
dev-tech-crypto@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-tech-crypto
