Kenneth R. Robinette wrote:
> Beats me. Since there must be people in the world that runs Netscape 6.2 on > Windows 98, I suspect Netscape knows about the problem and have bypassed it. > Since it knows where the nspr4.dll is, perphaps they use the extended > NSS_Initialize call and request no load of the secmod.db file. Are perhaps > they don't even use the nsrp4.dll. Or perhaps they monkey with the file > prior to reading it with nspr. No, Netscape 6 calls NSS_InitReadWrite(), just like everyone else. There is no private Netscape 6 interface. Netscape 6 *IS* and NSS application. They also use nspr4. The difference is Netscape 6 builds from source, and their own tag. It is possible that they have put their own fixes into NSPR. It looks like that is not the case. (Both the NSS and NSPR teams monitor what the client checks into the branch). > > All I know is if you use the nspr4.dll that comes with the NSS distribution, > it will fail. A call to NSS_Init will ABORT (you get the nasty windows > message stating the problem has behaved very badly), not simply fail. This > includes the tools that come with the NSS distribution such as modutil, > certutil, etc. > > Since it is a "NSPR" issue, does that mean it will never get fixed? No, we need a bug written up in mozilla, though, so we can track this issue. It looks like someone on NSS (probably me) will have to take a debug build on win98 and see what is crashing where. bob
