Closed Bug 288962 Opened 20 years ago Closed 20 years ago

Running SETUP.EXE from SAMBA share yields "Error: File not found INSTALL.INI"

Categories

(Thunderbird :: Installer, defect)

x86
Windows 2000
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 137380

People

(Reporter: stefan.kanthak, Assigned: mscott)

References

Details

User-Agent: Mozilla/4.0 (compatible; MSIE 5.01; Windows NT 5.0) Build Identifier: I placed the unpacked files of the Thunderbird 1.0.2 Windows Installer onto a SAMBA share. Running SETUP.EXE yields "Error: File not found INSTALL.INI" and installation aborts. With Thunderbird 1.0 this error did NOT show! Reproducible: Always Steps to Reproduce: 1. Unpack Thunderbird Setup 1.0.2.exe to SAMBA share 2. Doubleclick SETUP.EXE 3. See error dialog box Expected Results: Install Thunderbird See 137380 too! The same error was introduced in Firefox 1.0.2!
*** Bug 288963 has been marked as a duplicate of this bug. ***
(In reply to comment #0) > User-Agent: Mozilla/4.0 (compatible; MSIE 5.01; Windows NT 5.0) > Build Identifier: > > I placed the unpacked files of the Thunderbird 1.0.2 Windows Installer onto a > SAMBA share. Running SETUP.EXE yields "Error: File not found INSTALL.INI" and > installation aborts. > With Thunderbird 1.0 this error did NOT show! > > Reproducible: Always > > Steps to Reproduce: > 1. Unpack Thunderbird Setup 1.0.2.exe to SAMBA share > 2. Doubleclick SETUP.EXE > 3. See error dialog box > I get the same error, but in this case, I call the setup.exe from the command line. (still after uncompressing the files in the 'Firefox Setup 1.0.2.exe' or the equivalent Thunderbird exe. After selecting a a typical install, I get "Error uncompressing file \server\share\path\to\xpcom.xpi" just after it starts to copy the files. Looks like it's stripping the first backslash off the path name there. The problem can be avoided by mapping a drive first. ... ie net use x: \\server\share x:\path\to\setup.exe net use /delete x: works just fine. Unfortunately attempting to call the exe with \\\\server\share\path\to\setup.exe doesn't work :( Also, when doing a silent install (with setup.exe -ms) the setup just fails with no output.
This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
I can still reproduce this error, it shows in every version 1.0.* of FF and TB since I first reported it. Windows 2000 with Service Pack 4, the Rollup Package and all security hotfixes, Samba 2.2.11-0.1 on Debian 3.0r6, FF 1.0.6 or 1.0.7, TB 1.0.6 (localized german builds). It shows whether I access the Samba server via UNC path (actually "\\DEBIAN\PUBLIC\Windows\Mozilla\Firefox 1.0.7\") or via a mapped drive (actually "P:\Windows\Mozilla\Firefox 1.0.7\").
Depends on: 137380
Version: unspecified → 1.0
*** This bug has been marked as a duplicate of 137380 ***
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.