Closed Bug 142367 Opened 23 years ago Closed 14 years ago

NSREG.DAT still created on install in %WINDIR%

Categories

(Core Graveyard :: Profile: BackEnd, defect)

x86
Windows 2000
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: pete, Assigned: ccarlen)

References

Details

From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0rc2) Gecko/20020503 BuildID: NSREG.DAT is still created on install in %WINDIR%. this is the registry file that held profile information in Netscape 4 and appears to be a leftover that shouldn't be created by Mozilla. it only appears to be referenced in Mozilla code in relation to dealing with legacy profiles, and NSS: http://lxr.mozilla.org/seamonkey/search?string=nsreg.dat can we get rid of NSREG.DAT or am I missing something?
hmmm this seems correct. Dan: why do we do this?
Status: UNCONFIRMED → NEW
Ever confirmed: true
it seems to be used in the GetOldRegLocation function weird. I dont Mozilla or Netscape use the file anymore. I'm not sure where in the source it's being created.
I bet this is profile migration. Communicator 4.x profiles were stored in this file, but if they don't stat for the file before attempting to use it they'll end up creating an empty one.
if this doesn't get prevented from being created for 1.0.0 then I think it should get mentioned in the Release Notes section describing files that're created
Must be the profile code that creates the nsreg.dat even when there are no legacy profiles. NSREG.DAT is also create on a clean install.
Assignee: dveditz → ccarlen
Component: Installer → Profile Manager BackEnd
QA Contact: bugzilla → ktrina
Keywords: mozilla1.1
If the file doesn't already exist during installation, we shouldn't create it.
QA Contact: ktrina → gbush
Blocks: 52016
adt: nsbeta1-
Keywords: nsbeta1nsbeta1-
QA Contact: agracebush → profile-manager-backend
nsreg.dat is gone according to mxr
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → WORKSFORME
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.