10.4.2233 is the latest version for non SSE2 systems.
But, what do I do in order to be able to open the settings for Avast Online Security within Firefox v47.0.1? Do I find a way to revert/downgrade Firefox to v26.0?
Edit:Oh, and and idea what would be the latest version of MalwareBytes Anti-Malware for non SSE2 systems?
- I wouldn’t advice to use an outdated version of FF…!! You can try FF ESR, though.
- Probably V1.75, but I’m not sure about that.
- Could you explain FF ESR to me.
- Any idea where I can find out the latest version of MBAM for non-SSE2 systems?
- Here you go: https://www.mozilla.org/en-US/firefox/organizations/faq/
- Nope, sorry. (You could ask at MBAM forum…)
Ok, now for some questions…how is FF ESR different from the regular FF and, in conjunction, what would switching to FF ESR from FF do to resolve the situation?
If you’re not keen on FF’s latest and ‘greatest’, there’s Firefox ESR (Extended Support Release) meant for organisations. It’s up-to-date on ‘security’ but cuts a lot of the recent frippery and is more modifiable.
There’s also Pale Moon, but that’s a bigger step!
https://www.mozilla.org/en-US/firefox/organizations/
http://www.palemoon.org/
How would Firefox ESR work as far as trying to access the settings for Avast Online Security?
- Did you read the link (Reply #24) I provided…!? ???
- The “about:config” trick you mentioned in Reply #2 might still work.
- Yes, I did read the information presented at the link. However, I guess I just don’t seem to understand the information being put forth concerning the contrast between FF & FF ESR.
- From the looks of it, as best as I can tell, it would seem the reason AOS in v47.0.1 was disabled (therefore necessitating the use of the “about:config” trick to re-enable AOS) is because apparently, v47.0.1 views AOS as being unsigned (as in AOS could not be verified for use in v.47.0.1). Now, I don’t know if that’s the reason why I’m unable to access the settings page for AOS within v.47.0.1. Therefore, I can’t be entirely sure, but from my interpretation, it would kinda almost then seem like that, even if I was to switch from using v.47.0.1 to using the latest version of FF ESR, if FF ESR views AOS as being unsigned (a.k.a. that AOS could not be verified for use in the latest version of FF ESR), then it’s not going to matter if I use the “about:config” trick to keep AOS enabled, I won’t be able to access the settings page for AOS within FF ESR.
Did you not see what I said in my latest post?
- Well, that’s already as easy as it gets. (You could ask a friend to help you understand.)
- It’s up to you if you want to test/try it.
So, why exactly is it that I’m being given the suggestion of switching from FF v47.0.1 to FF ESR 45.4.0esr as far as resolving the problem with AOS? Is it thought/believed that AOS would work properly (as in being able to access AOS’s settings page within the browser) with FF ESR as compared to how it’s acting with FF?
Everything already answered in my prior replies.
What is Mozilla Firefox ESR? Mozilla will offer an Extended Support Release (ESR) based on an official release of Firefox for desktop for use by organizations including schools, universities, businesses and others who need extended support for mass deployments.What part of it is it that you do not understand ?
So, I take it to mean “mass deployments” refers to Firefox being utilized by very large groups of people…
So then, what would extended support for that type of situation entail?
https://www.mozilla.org/en-US/firefox/organizations/faq/ > click on You can read more about the plan here
All information is right there.
Read it and if you don’t understand it ask someone to explain it.
OK, so here’s what I’ve gathered from what I’ve read & seen about FF ESR:
-
ESR is essentially almost the same as FF, except ESR is more modifiable/customizable, at least according to Giraffe & the FAQ portion of the ESR section of Firefox’s website (as to what extent, I have no clue) (FYI:found out from here that the configuration for ESR apparently can be modified in a way so as to completely disable the add-on signing requirement; for FF, starting with v41.0, doing that “about:config” trick only overrode the requirement, thereby allowing the add-on to remain active in the browser’s toolbar & its basic settings to be accessed by clicking the add-on in the toolbar, but its settings page couldn’t be accessed, as the add-on isn’t seen as being verifiable to be used in FF)
-
each “stable” (as in post-testing & -certification) series release for ESR starts with v??.2 & ends at v??.6 (the last two in the series release, v??.7 & v??.8, end up in the overlapping period for testing & certification of the next series) & the first version in the “stable” portion of the series release starts with same starting number as its mainline counterpart (e.g. the first version in the “stable” portion of the ESR counterpart to v52.0 would be v52.2.0)
At this point, if I’m wrong, I would gladly appreciate someone correcting me.
- now, on this page, it does state, “Who is it not for? Individual users who always want the latest features, performance enhancements and technologies in their browser without waiting for them to become available in ESR several development cycles later.” Well, to be honest, in a situation like this (as far as how old the technology in the problem computer is, as it would apparently seem the computer is pretty much on the older side, as the processor is non-/pre-SSE2 & it’s operating system is a 32-bit copy of Windows XP Pro), as long as the add-ons & plug-ins that have been installed in the browser work properly, I don’t mind doing the same thing for FF ESR as it relates to FF that most of my fellow Firefox users would do for FF as it relates to builds/versions currently in the Beta, Developer Edition (formerly Aurora), & Nightly distribution channels.
Now, the question I have is that, when it comes to switching from Firefox v47.0.1 to Firefox ESR v45.4.0, if I elect to keep Firefox’s current customizations (saved passwords & bookmarks, installed add-ons & plug-ins, etc.) when I’m asked whether or not to save them at the start of v47.0.1’s uninstall process, would I still have access to those customizations in Firefox ESR after I install v45.4.0?
BTW: After careful thought & consideration, I’m leaning towards uninstalling Malwarebytes Anti-malware from the problem computer, seeing as how it would seem Avast Free Anti-virus seems to be good enough at doing the job it was created to do, not to mention XP’s built-in firewall hasn’t had any problems doing what it’s supposed to do.
Although MBam and avasst do have some overlap, both can and will detect things the other doesn’t.
I suggest to keep both.
The XP firewall is not doing what a good/decent firewall needs to do.
It doesn’t check outbound traffic, only inbound.
Best is to use a good hardware firewall.