On 2010-07-19 10:56 AM, Caden.smith Smith wrote:
I'll look into this tomorrow.
Just for your information, here is the tree:
JSS4.DLL
NSPR4.DLL
ADVAPI32.DLL
SECUR32.DLL
this is a delay-loaded dependency
NETAPI32.DLL
DNSAPI.DLL
MPRAPI.DLL
SETUPAPI.DLL
SHELL32.DLL
SHDOCVW.DLL
MSHTML.DLL
IEFRAME.DLL that finally requires IESHIMS.DLL and WER.DLL
all all three here are too (among a bunch of others in the middle).
Don't trust dependency walker output on errors when there's a little
hourglass icon next to it; it means it actually dug around to try to
figure out what is being loaded at runtime (rather than by the dynamic
linker) so there might be code around to handle the fact that they're
missing.
The stackoverflow question you referenced mentioned that they are
delay-loaded too. See also
http://www.dependencywalker.com/help/html/interpreting_errors.htm
Sorry, you're chasing the wrong thing; you actually need to figure out
what error is being reported when calling CryptoManager.initialize. Try
also to use some of the command line NSS tools; that should let you know
if it's in NSS or JSS.
--
Mook
--
dev-tech-crypto mailing list
dev-tech-crypto@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-tech-crypto
