Closed Bug 179892 Opened 22 years ago Closed 16 years ago

Installer exits with no error after unpacking files - problem with TMP environment var

Categories

(SeaMonkey :: Installer, defect)

x86
Windows 2000
defect
Not set
major

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: erik, Unassigned)

References

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.9) Gecko/20020311 Build Identifier: mozilla-win32-1.2b-installer.exe If you have an envionment variable with a space in a directory component and there is also a file called the same name as the first word in the directory component, then the installer just drops dead with no information about why. This is a longstanding bug. Reproducible: Always Steps to Reproduce: 1. mkdir "c:\temporary directory" 2. set TMP=c:\temporary directory 3. create file called c:\temporary (it is important that this is a file, not a dir) 4. Run installer Actual Results: Files are unpacked, then program exits Expected Results: Install Mozilla
yeps thats true. We should at least warn that there's an error unpacking files!
Status: UNCONFIRMED → NEW
Ever confirmed: true
the installer actually gets unpacking into "C:\temporary dir\ns_temp\" but it seem s to be the launching of the setup.exe file from within that dir that is the problem.
just create a file called "ns_temp" in your %TEMP directory and you're unable to launch the installer. It just quits Sean: Do we need to quote something to get this working? Is it correct that setup.exe is launched from: http://lxr.mozilla.org/mozilla/source/xpinstall/wizard/windows/nsinstall/nsinstall.cpp#892 ?
having a file called "ns_temp" is actually another bug since nothings gets unpacked or anything.
Henrik, that's correct. That is where it gets launched from.
Assignee: dveditz → ssu
Status: NEW → ASSIGNED
*** Bug 183228 has been marked as a duplicate of this bug. ***
Product: Browser → Seamonkey
QA Contact: bugzilla → general
Assignee: ssu0262 → nobody
Status: ASSIGNED → NEW
Seamonkey and Firefox are using a new NSIS based installer. resolving this old bug, please reopen if you still get this with the new installer
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.