Closed Bug 465821 Opened 16 years ago Closed 14 years ago

Failed installation on Vista

Categories

(SeaMonkey :: Installer, defect)

SeaMonkey 1.1 Branch
x86
Windows Vista
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: avakoff, Unassigned)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.18) Gecko/20081031 SeaMonkey/1.1.13
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.18) Gecko/20081031 SeaMonkey/1.1.13

I installed Seamonkey 1.1.13 on my XP computer, and all was fine.

I tried to install Seamonken on my wife's Vista computer and got an Error 201 message early indicating a problem installing Netscape.

So I tried reinstalling an earlier version of Seamonkey with similar results.

Not only that, but after several tries, I discovered I could no longer find my wife's saved Seamonkey Email files.

So I installed Firefox and Thunderbird with no problem. But her saved Emails are no where to be found.



Reproducible: Always

Steps to Reproduce:
1. Download to the computer the Seamonkey program.
2. Double click on the program to launch the installer.
3. Installation failed!
Actual Results:  
No installation.

Missing Seamonkey Email files.

Expected Results:  
I expected Seamonkey to be installed. It wasn't.

Installed Seamonkey.
Use http://forums.mozillazine.org/viewforum.php?f=40&st=0&sk=t&sd=d&start=0 for seamonkey support. However, there are a few things you can do. Try uninstalling any previous Seamonkey/Netscape, etc. programs on your computer. Then, download a fresh install, from http://www.seamonkey-project.org/. Then try to install. The best bet for you is to try the Seamonkey support forums though. I am able to install just fine on Vista.
Severity: major → normal
Version: unspecified → SeaMonkey 1.1 Branch
old XPFE installer is dead, and SeaMonkey 1.x has been discontinued.

SeaMonkey 2 should work fine with Vista, however.
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.