Closed Bug 146386 Opened 23 years ago Closed 23 years ago

Nothing functions in rc2

Categories

(SeaMonkey :: Composer, defect)

x86
Windows 98
defect
Not set
blocker

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: bobholm, Unassigned)

References

()

Details

From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:0.9.9+) Gecko/20020416 BuildID: 20020510xx (uninstalled so can't see it) I just installed Mozilla 1.0.0 rc 2 over top of rc 1, and absolutely nothing worked -- it loaded, I could get into menus, but none of the functions did anything at all. As a result, I have removed it completely from my hard drive, restored the registry to just before I installed rc2, and restored the rc 1 files from backup. Rc1 works just fine. PLEASE -- if you're going to issue a release candidate, make sure it's a beta and not an alpha. I will wait now until you issue the final release, but I will keep my backups of rc 1 just in case the same thing (no function at all) happens with the final release. Reproducible: Didn't try Steps to Reproduce: 1. Back up all hard drives including Windows and RC 1 2. Install RC 2 over top of RC 1 3. Go on-line and load RC 2 (Messenger or Navigator, doesn't matter which) Actual Results: 4. See nothing function Expected Results: 4. See both composer and Navigator function normally the way RC 1 did 5. Find out uninstall won't work because there is no saved log listed in the registry 6. Delete RC 2 folder (brute force uninstall) 7. Restore registry to just before installation of RC 2 8. Restore RC 1 files to Mozilla folder from backup 9. Be happy that everything once again works, even if there is a security bug (I have ZoneAlarm, so I hope that will protect me some, as it is better than having to use IE 6 since RC 2 doesn't work at all on my system).
Try NOT doing an on-top-of install of RC2 and create a new profile or archive and then delete your old profile folder so that you are forced to create a new one. Keep you bookmarks.html file to drop into the new profile and similarly for the mail and news folders (if you've been using Moz for email or news). If RC2 doesn't work then, then there is a problem. However, I have been running RC2 on NT4, MacOS, and Mac OS X with no problems whatever. And the NT4 is using the same binary that you are on Win98. Try again with the clean install before surrendering. Dale
*** This bug has been marked as a duplicate of 135222 ***
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
verified.
Status: RESOLVED → VERIFIED
Hi, Dale! Thanks for the suggestions; when I installed Mozilla 1.0.0 rc1 I switched to Drive D:, not knowing whether it used the files in c:\windows\application data\etc. as Netscape 6.1 did; otherwise, I would have installed on top of 6.1 as I've been doing with all the 6.x and 4.x releases. I have just downloaded rc 3 and will try first just installing it to a different folder on C: to see if it and rc 1 can both use the same data files just as Nutscrape 6.1 and rc 1 did. (I uninstalled 6.1 after rc 1 proved stable, but I've kept Nutscrape 4.79 just in case. I will keep rc 1 as well and then decide whether to uninstall 4.79, which I haven't used in over a month since rc 1 worked with my credit union - 128-bit ssl. I will let you know here if I have further problems or find I have to go to the full extent of your suggestions [deleting the application data and setting up =all=those=folders= all over again].)
Status: VERIFIED → UNCONFIRMED
Resolution: DUPLICATE → ---
Reporter, did you try uninstalling RC2 and then installing RC3 as suggested in comment #1?
I removed rc2 but have kept rc1. I installed rc3 in a separate folder, and it works fine. The problem is that the old Netscape versions installed on top of one another, so I naturally thought the Mozilla builds would install on top of each other, too. That is clearly not the case. Users should be warned to install each new version in a new folder (btw, rc1 still works, too, so older versions don't have to be uninstalled).
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago23 years ago
Resolution: --- → FIXED
verified per comments.
Status: RESOLVED → VERIFIED
reassign in case bugs are later reopened
Assignee: syd → composer
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.