Closed Bug 210382 Opened 23 years ago Closed 22 years ago

Cannot start 1.4 RC2 on Windows 2000 Server SP3

Categories

(SeaMonkey :: General, defect)

Product:
SeaMonkey
Component:
General
Platform:
x86
Windows 2000
Type:
defect
Priority:
Not set
Severity:
critical

Tracking

(Not tracked)

Status:
RESOLVED DUPLICATE of bug 195600

People

(Reporter: aidan_s_marcuss, Unassigned)

Details

User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; .NET CLR 1.0.3705) Build Identifier: http://ftp.mozilla.org/pub/mozilla/releases/mozilla1.4rc2/mozilla-win32-1.4rc2-installer.exe Got an "Application Error" dialog with the following message: The instruction at "0x610f0769" referenced memory at "0x6c614349". The memory could not be "read". Click on OK to terminate the program Click on CANCEL to debug the program Reproducible: Always Steps to Reproduce: 1. Double-click on Mozilla desktop icon installed by the installer. Actual Results: Get an application error and Mozilla will not start. Appliction error dialog says: The instruction at "0x610f0769" referenced memory at "0x6c614349". The memory could not be "read". Click on OK to terminate the program Click on CANCEL to debug the program Expected Results: Started up.
Reporter, have you installed this Mozilla on top of an older version ? Please don't do that. Always install in an empty directory, or uninstall the older version first. It's in the installation notes.
I did initially install it over RC1 - and then tried removing RC1 and installing it again - same result. As a note, I've never had a problem install over before, but I do understand that the release notes say you should.
Severity: blocker → critical
It's not necessarily that mozilla needs to be uninstalled first, but rather that it needs to be installed into an *empty* directory. Although it's a good idea, the former does not necessarily guarantee the latter.
This is probably a dupe of bug 195600. Aidan, can you confirm if installing to a completely empty directory (not just Uninstalling from control panel) solved this? Thank you.
I can confirm that installing into an empty directory did solve the problem.
Per Aidan's comments, I am duping this against bug 195600. *** This bug has been marked as a duplicate of 195600 ***
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.