Closed
Bug 224846
Opened 21 years ago
Closed 17 years ago
[INSTALLER] Firefox does not run on freshly installed Windows 98 machines
Categories
(Firefox :: Installer, defect, P3)
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: bugs, Unassigned)
References
Details
Starting the Firebird.exe file on a clean install of Windows 98 produces an error - linked to file 'oleaut32' which is not found. Sounds like we're either linking against something we don't need in the static build, or we're not distributing a required dll file.
Reporter | ||
Updated•21 years ago
|
Status: NEW → ASSIGNED
Priority: -- → P1
Target Milestone: --- → Firebird1.0
Comment 1•21 years ago
|
||
*** Bug 225013 has been marked as a duplicate of this bug. ***
Comment 2•21 years ago
|
||
Adjusting summary in anticipation of a possible fix for bug 224989 and to make finding installer bugs easier. Also taking QA Contact.
QA Contact: bugzilla
Summary: Firebird does not run on freshly installed Windows 98 machines → [INSTALLER] Firebird does not run on freshly installed Windows 98 machines
Comment 4•21 years ago
|
||
If we ever start distributing builds built with VS.NET, we're going to have the same problem, possibly, because the C/C++ runtimes are no longer shared system files, but need to be distributed with the application itself (msvcr70.dll/msvcp70.dll for VS.NET 2002 and msvcr71.dll/msvcp71.dll for VS.NET 2003). I think that Microsoft is pushing people towards using their MSI installer package on Windows.
Reporter | ||
Updated•20 years ago
|
Target Milestone: Firefox1.0 → Firefox1.0beta
Comment 5•20 years ago
|
||
*** Bug 240014 has been marked as a duplicate of this bug. ***
Comment 6•20 years ago
|
||
I got the oleaut32 error on a Win98 installation several years old, using the ZIP version of 0.8. What is [INSTALLER] doing in the summary? Why is the component installer?
Reporter | ||
Updated•20 years ago
|
Priority: P1 → P3
Target Milestone: Firefox1.0beta → After Firefox 1.0
Firefox works fine for me in a fresh install of Windows XP. I can't say the same about Mozilla. It installs properly with no errors, but running the exe does nothing. Double click, see the hour glass, see it vanish, notice nothing happens (not even an added process).
Comment 8•20 years ago
|
||
(In reply to comment #7) If indeed that's verifiable, it's another bug, not this one.
Comment 9•20 years ago
|
||
*** Bug 238160 has been marked as a duplicate of this bug. ***
Comment 10•20 years ago
|
||
(In reply to comment #0) > Starting the Firebird.exe file on a clean install of Windows 98 produces an > error - linked to file 'oleaut32' which is not found. Sounds like we're either > linking against something we don't need in the static build, or we're not > distributing a required dll file. I got this error with a new install of Windows 98. I downloaded a newer version of oleaut32.dll (I think it was from www.dll-flies.com) and firefox now seems to be working fine. I noticed that previously my computer had another version of oleaut32.dll which was about half the size, so the file oleaut32.dll isn't missing, its just a really old version.
Updated•20 years ago
|
Summary: [INSTALLER] Firebird does not run on freshly installed Windows 98 machines → [INSTALLER] Firefox does not run on freshly installed Windows 98 machines
Comment 11•20 years ago
|
||
In my installation of windows 98 (not fresh) I, instead of getting an error in oleaut32, get the 'FIREFOX caused an invalid page fault in module SECUR32.DLL' message on startup.
Comment 12•20 years ago
|
||
I tried to install "Firefox Setup 1.0PR.exe" on a fresh installation of Windows 98. The installation runs fine but when I start firefox I got an dialog that complained about a missing oleaut32.dll.
Updated•19 years ago
|
Assignee: bugs → nobody
Status: ASSIGNED → NEW
QA Contact: bugzilla → installer
Target Milestone: Future → ---
Updated•17 years ago
|
Version: unspecified → 1.0 Branch
Comment 13•17 years ago
|
||
WONTFIX - Firefox 3 won't support Windows 98.
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•