Closed Bug 239231 Opened 21 years ago Closed 21 years ago

Can't start Mozilla 1.6 after image restore

Categories

(SeaMonkey :: General, defect)

x86
Windows 2000
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: ekiczek, Unassigned)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax) Build Identifier: http://ftp.mozilla.org/pub/mozilla.org/mozilla/releases/mozilla1.6/mozilla-win32-1.6-installer.exe I install Moz 1.6 and it works fine. I reboot the machine and use imaging software (ZenWorks, which I've used many times before) to create an image of the HD. I then wipe the HD and re-install the image. After imaging, everything works fine EXCEPT Moz. The first time I try to run Moz, it takes an abnormally long time for the splash screen to appear. Then I get an Alert box with no message and two thin bars where OK and Cancel buttons might be. These can be clicked, but nothing happens when I do so. Moz then dies. An uninstall and re-install cures this problem. I have tried imaging and restoring the image on multiple machines. The problem does not occur in Moz 1.5. Reproducible: Always Steps to Reproduce: 1. Install Moz 1.6 2. Image the PC, then restore the image 3. Launch Moz 1.6 Actual Results: Moz, takes an abnormally long time for the splash screen to appear. Then I get an Alert box with no message and two thin bars where OK and Cancel buttons might be. These can be clicked, but nothing happens when I do so. Then Moz dies. Expected Results: Launched and initiated a browser screen.
The point of imaging software is that it creates an *exact* copy of the system at a certain point. That said, there is no reason why Mozilla would not work after restoring an image, *if* the image is created properly. FWIW, Mozilla works fine after restoring TrueImage and Ghost images.
-> WFM
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → WORKSFORME
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.