I have the 3/19 build installed in one directory, the 3/28 build in another. When I went to delete the 3/28 directory, the system refused to delete its copy of nssckbi.dll because it was in use. Since the 3/19 build is the only one running, it must somehow be using the nssckbi.dll from the 3/28 build. Whatever this dll is for, we should always use the one installed with the version we're running.
Assignee: asa → relyea
Component: Browser-General → Libraries
Product: Browser → NSS
QA Contact: doronr → sonmi
Version: other → 4.0
Hey David, we don't install this, can you work this out with the client team. Thanks. bob
Component: Libraries → Client Library
Product: NSS → PSM
Version: 4.0 → 2.0
I just finished backward compatibility testing of NSS on the PC (NT and Win2K), and I did not notice any problem switching the set of dlls that I use. Since I am neither familiar with PSM nor the whole browser installation I can only share one problem that I had - the LD_LIBRARY_PATH was set to point to the correct directory, which is ignored under Windows, and the PATH still pointed to the wrong directories - which worked perfectly fine on Unix.
Reporter - doesn't this bug seem more like an install issue, in that maybe the registry wasn't properly updated when you installed 3/28 build in another folder?
Hmm, changing the component didn't change the owner. Dave, take a look at the history. bob
Assignee: relyea → ddrinan
junruh, if you know who should own it, please reassign. When I filed this, I didn't even realize this was a PSM related dll. I have no direct knowledge of any registry key usage or other mechanism that might explain the effect I observed, so I don't feel qualified to reassign this bug myself.
Priority: -- → P4
Mass reassigning target to 2.1
Target Milestone: 2.0 → 2.1
Worksforme. I cannot reproduce with the 7/19 WinNT branch build.
Status: NEW → RESOLVED
Last Resolved: 17 years ago
Resolution: --- → WORKSFORME
Status: RESOLVED → VERIFIED
Status: VERIFIED → REOPENED
Resolution: WORKSFORME → ---
*** This bug has been marked as a duplicate of 176501 ***
Status: REOPENED → RESOLVED
Last Resolved: 17 years ago → 15 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.