User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:188.8.131.52) Gecko/20070515 Firefox/184.108.40.206 Build Identifier: Mozilla/5.0 (Windows; U; Win98; en-US; rv:220.127.116.11) Gecko/? Firefox/18.104.22.168 Mozilla 22.214.171.124 Upgrade fails to start either when upgrading from 126.96.36.199 or when doing a clean install of 188.8.131.52 (attempted from fresh download on 07/18/2007 @ 11 PM U.S. Central Time). It appears that all components are installed but when calling Firefox via shortcut or direct from the directory it just hangs. When trying to End Task Firefox is slow to end and consistently generates 2 Windows 98 Blue Screens (Operation Exception Errors). Regressing back to 184.108.40.206 is possible and this version works well on this system. However, as 220.127.116.11 fixes a critical security risk staying on 18.104.22.168 is not an option. Reproducible: Always Steps to Reproduce: 1. Attempt to run any version of 22.214.171.124 (either as upgrade from 126.96.36.199 or fresh install. 2. When Firefox hangs, Call End Program dialog- use it to End Task 3. Windows 98 blue screen results - twice. Actual Results: Upgrade to 188.8.131.52 fails on this Windows 98 machine. This happens regardless of doing a software update from within Firefox 184.108.40.206 or a clean download and install of 220.127.116.11. Calling 18.104.22.168 after a supposed install always hangs and results in Win 98 Blue screens. No Talkback dialog ever appears and program always fails to load. Expected Results: Firefox 22.214.171.124 should have opened as expected and gone to the Mozilla success page. Error is occurring on a HP Pavilion Laptop (n3310), AMD K-6 III, 256 MB RAM, 600 x 800 monitor, Trident Cyberblade i7 video adaptor, U.S. Robotics USR5411 MAXg wireless card. The OS is Windows 98 SE. Other relevant software on system: AVG Free 7.5, OpenOffice, ZoneAlarm 2.6.362, Internet Explorer 6, Lavasoft Ad-Aware SE. System also has the 3rd party mass storage device driver for Windows 98 from www.technical-assistance.co.uk/kb/usbmsd98.php. [NOTE: 126.96.36.199 is being used here as I had to regress back to it to file this report - that is why Gecko is listed as "?"] As I type this another software update has upgraded this browser to 188.8.131.52 - I am choosing the Restart Later option - which has failed twice already.
Further information: after entering this but software update downloaded the 184.108.40.206 changes - with the same result: an unusable browser. However, this time I was able to view the installing the the software updates progress bar for a few seconds before the process ground to a halt. For every occasion of this event Internet Explorer is unable to load once 220.127.116.11 halts. After using the close program/end task for both Firefox 18.104.22.168 and IE 6 it is possible to call up IE 6. However, IE 6 cannot find any sites. All other applications are unable to access the web and pings result in failures. This necessitates a reboot. At that time is when the Win 98 Blue Screens appear (Fatal Error / OE). I have captured the location and it is "0028:C0031B13". Pressing any key clears these BSODs and Win98 attempts to shut down. About 80% of the time shut down is not succesful and a power cycle/on-off-on has to be used.
do you have the latest version of AVG and zonealarm? it could be a problem with one of these... report results after updating/disabling them
This is actually a laptop for my father, however I have the latest version of AVG on the PC (it's the Free version of 7.5). As this is Windows 98 there are few options for upgrading to a newer version of ZoneAlarm I can try to see if there is one still available somewhere or can try Outpost's firewall. I did disable both to see if that made any difference - it did not. However, parts of ZoneAlarm do stay resident even if it is "disabled". I will try these as well as seeing if the installation can complete in Safe Mode.
Felix describes the symptoms perfectly. My system is win98 se with zone alarm 2.6.362. On subsequent reboot, I was able to uninstall 22.214.171.124 and re-install 126.96.36.199.
Issue does appear to be a new conflict with ZoneAlarm 2.6.362 and Firefox 188.8.131.52. This is new since 184.108.40.206 as you can uninstall 220.127.116.11 and regress down to 18.104.22.168 which will run fine with ZA 2.6.362. I have been able to get 22.214.171.124 to run with a newer trial version of ZA Internet Security Suite 6.1. I do not know what will happen when the trial version expires (assume it will just become free ZA of that build level) as this ZA version is no longer supported. ZA 2.6.362 is old but often preferred as it is simple, stable (far less issues with VSMON crashing), free of extraneous items and is often preferred by many users over newer versions for these reasons. If possible I request continuing efforts to understand what is causing a conflict with ZoneAlarm 2.6.362 and Firefox 126.96.36.199 as some of these users may have to drop firefox to stay with ZA. I have ruled out AVG 7.5 as a source of conflict as it is working with the newer version of ZA and 188.8.131.52.
I am having a similar issue but with Windows XP Media Center Edition 2006. I too have an HP Pavilion laptop, but mine is a dv6105us with an AMD Turion64 Mobile 803 Mhz and 768 MB of RAM. After I install 184.108.40.206 and run it once, my computer can no longer find the built-in Broadcom 802.11 b/g wireless card - no internet dependent programs are able to connect through the card and I am unable to see it in hardware manager in Control Panel. I can see the ethernet card, but I have not tested it. I attached a Microsoft external USB wireless card and that seems to work normally. After doing a system rollback to a setpoint prior to the FireFox upgrade, I was able to use the internal card again and use FireFox 220.127.116.11. However, reinstalling 18.104.22.168 has again made the Broadcom card 'vanish'. I then tried updating the Broadcom driver to the latest version available on the HP website but that has had no effect. I also updated the HP Wireless Assistant control panel widget as that was not working - and after the upgrade it still fails to load.
(In reply to comment #6) One additional point, I have now uninstalled 22.214.171.124 and installed 126.96.36.199 but that did restore my wifi capability as doing a rollback to a prior setpoint did. So whatever change that occurs that causes the loss of communications with the Broadcom wifi card, is not reversed by uninstalling.
Request for hardware configuration - Motherboard: Abit KG7 Processor: AMD Athlon 1133 Memory: 256MB Video: Matrox Millenium G200 agp Network: Linksys LNE100TX Sound: Creative Soundblaster PCI128 USB 1.0: VIA Integrated USB 2.0: ALI PCI USB2.0 / Firewire Controller. Significant Software - ZoneAlarm 2.6.362 Recent upgrade to IE6 for internet setup. Internet connection via ethernet <-> router <-> cable modem Other notes - Reversion to 188.8.131.52 worked without issue.
Felix, do you see this in you install FF 184.108.40.206 or higher using a straight install, using custom to put it in a specific *new* directory?
Summary: Firefox 220.127.116.11 is not able to run on some Windows 98 SE systems. → Firefox 18.104.22.168 is not able to run on some Windows 98 SE systems with ZoneAlarm
I apologize but my reply will not be helpful: I no longer am using Windows 98 on that laptop having upgraded it to Win XP SP2. I have been able to reinstall and do upgrades to newer versions of Firefox but also did an upgrade to a newer version of ZoneAlarm Free as WinXP can support the newer version. I have not tried to revert back to the older version of ZA or Firefox that originally caused the problem.
=> INVALID then for ZA flakeyness
Status: UNCONFIRMED → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → INVALID
We're now tracking such bugs. This doesn't mean it's something we can fix, merely something we hope to be able to point vendors to so they can investigate. This is an automated message.
Status: RESOLVED → UNCONFIRMED
Component: Application Update → Checkpoint Zonealarm
Product: Toolkit → Plugins
QA Contact: application.update → checkpoint-zonealarm
Resolution: INVALID → ---
Version: 1.8 Branch → unspecified
Closing old bugs in the Plugins component. We aren't going to track issues in 3rd-party plugins in the Mozilla bug tracker. In addition, support for NPAPI plugins will be removed at the end of this year; for more details see the post at https://blog.mozilla.org/futurereleases/2015/10/08/npapi-plugins-in-firefox/ If there is a serious bug in Firefox, it needs to be filed in the "Core" product, "Plug-Ins" component.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 10 years ago → 2 years ago
Resolution: --- → INCOMPLETE
Product: Plugins → Plugins Graveyard
You need to log in before you can comment on or make changes to this bug.