Good morning. Once again thank you both for the feedback that turned me on the right track.
I'll try to resume what was the problem and yes, it was related to some "wild goose chase". Using dumpbin instead of dependency walker I did verify that IEFRAME.DLL depends on both missing libs that don't exist in WinXP. However, there were also some other dependencies missing that are more familiar to you. these were: PLC4.DLL, PLDS4.DLL and MOZCRT19.DLL These are all under Firefox and I found them easy. I just didn't add them to the lib path because I was focusing on the libs I couldn't find and this was where the problem came To wrap things up, although WER.DLL and IESHIMS.DLL are dependencies they are only called in Vista/7. The problem came in fact for not adding the mozila libs to the libpath and I was going for a "Wild Goose Chase" instead. Hope my feedback helps you solve similar problems in the future Cheers Cad On Mon, Jul 19, 2010 at 7:24 PM, Nelson B Bolyard <nel...@bolyard.me> wrote: > On 2010-07-19 10:56 PDT, Caden.smith Smith wrote: > >> Just for your information, here is the tree: >> >> JSS4.DLL >> NSPR4.DLL >> ADVAPI32.DLL > > The factors under the control of the way in which JSS and NSPR are built > end here. Anything below this point has NOTHING to do with them. > > Everything below this point is interdependecies of system libraries. > If you have a system library, 9 levels down, whose presence is TOTALLY > UNKNOWN to JSS and NSPR, and it depends on a missing DLL, that is no > fault of JSS or NSPR, or of the way they were built. > >> 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 > > My guess is that you've installed some package on your XP system that was > intended for a Vista system, and it installed some Vista DLLs on your XP > system (e.g. it installed a vista IEFRAME.DLL). That DLL now wants another > vista DLL that is not on your system. But this has nothing to do with JSS > or NSPR. > > I'll add that we've seen this "dependency walker" tool lead developers on > some wild goose chases before, telling them about dependencies that didn't > exist (were not, in fact, real dependencies). The one windows tool that I > believe for dependency information is the program dumpbin. Run it as > > dumpbin /dependents some.dll > > and it will tell you the other DLLs upon which that named DLL depends. > It will give you the entire list. Anything not on that list is not a > direct dependency of that named DLL. > -- > 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
