Closed Bug 197495 Opened 23 years ago Closed 22 years ago

Installer freezes when default path does not exist

Categories

(SeaMonkey :: Installer, defect)

x86
Windows 2000
defect
Not set
blocker

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: dj28, Assigned: ssu0262)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2b) Gecko/20021016 K-Meleon 0.7 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2b) Gecko/20021016 K-Meleon 0.7 The Mozilla installer completely freezes when the default drive it attempts to install on does not exist. When one tries to press "Next" or "Browse" to try to change the drive on which Mozilla defaulted to install on (but doesn't exist), the installer will proceed to use 100% CPU and freeze. Drive D: on my system is the drive in which Mozilla defaulted to install on. However, this drive does not exist. Attempts to press the "Browse" button to change it have failed, resulting in the SETUP.EXE taking up 100% CPU and freezing. Reproducible: Always Steps to Reproduce: 1. Start installer 2. When drive defaults to one that doesn't exist (drive D: for example), press "Browse" Actual Results: CPU usage rockets to 100% and the installer freezes. Expected Results: Mozilla should allow you to change the drive to one that does exist (C: for example). SETUP.EXE is the problem. I have no idea why Mozilla defaults to drive D: on my system to install on. That drive does not exist, and I cannot attempt to change it without Mozilla freezing.
Is that still happening in 1.5 or later? pi
No response, closing. pi
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → WORKSFORME
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.