Closed Bug 190586 Opened 22 years ago Closed 21 years ago

Release Notes (1.0 ~ 1.4) document profile location for win98/95 w/ log-in

Categories

(www.mozilla.org :: General, defect)

x86
Windows 98
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: lowella, Assigned: danielwang)

References

()

Details

User-Agent:       Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.0.2) Gecko/20021120 Netscape/7.01
Build Identifier: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.0.2) Gecko/20021120 Netscape/7.01

It would appear that in page:
	
"http://www.mozilla.org/releases/mozilla1.3a/"

under section:

"Profile Locations"

the line:

"Windows 95 & Windows 98 C:\Windows\Application Data\Mozilla\Profiles\[Profile
Name]\[random string].slt\"

should read:

"Windows 95 & Windows 98 C:\WINDOWS\Profiles\[User]\Application
Data\Mozilla\Profiles\[Profile Name]\[random string].slt\"

Regards,

Lowell Anderson

Reproducible: Always

Steps to Reproduce:
1. Read the page and compare to actual location :-)
2.
3.

Actual Results:  
See above

Expected Results:  
See above
-->asa.
Assignee: rudman → asa
That's the profile location for windows w/o log-in

(see bug 121578 attachment 111317 [details])
Blocks: 133795
Component: User → webmaster@mozilla.org
Product: Documentation → mozilla.org
Summary: Windows 98 Profile Location Wrongly Dodumented → Release Notes (1.0 ~ 1.3a) document profile location for win98/95 w/ log-in
Version: unspecified → other
Owen is taking QA for "repeating relnote" bugs. Sorry for the spam; search for
the previous string to find and delete these messages.
QA Contact: rudman → malachi
-> me
Assignee: asa → stolenclover
Summary: Release Notes (1.0 ~ 1.3a) document profile location for win98/95 w/ log-in → Release Notes (1.0 ~ 1.4) document profile location for win98/95 w/ log-in
Status: NEW → ASSIGNED
fixed
Status: ASSIGNED → RESOLVED
Closed: 21 years ago
Resolution: --- → FIXED
Product: mozilla.org → Websites
Component: www.mozilla.org → General
Product: Websites → www.mozilla.org
You need to log in before you can comment on or make changes to this bug.