Rechercher dans l’assistance

Évitez les escroqueries à l’assistance. Nous ne vous demanderons jamais d’appeler ou d’envoyer un SMS à un numéro de téléphone ou de partager des informations personnelles. Veuillez signaler toute activité suspecte en utilisant l’option « Signaler un abus ».

Learn More

How to turn off upgrade nagging?

  • 2 réponses
  • 6 ont ce problème
  • 11 vues
  • Dernière réponse par the-edmeister

more options

I am among MANY people who want CHOICE in whether or not to upgrade software on THEIR machines. After following many threads about this, all the statements say upgrade, no matter what the questions actually asked. Realize the FINAL WORD about our machines is ours. WE OWN THEM, NOT THE SOFTWARE MANUFACTURERS. This makes the bottom line OUR choice. If we don't want to upgrade, it's OUR FINAL word, not the software manufacturers. This is in response to the question of getting rid of upgrade nagging. The thread has always been closed without any answer to the question as asked. Invariably, when an upgrade occurs, there are incompatibilities which are left for the user to sort out, many times taking hours to days, some not ever being fixed and therefore must be lost. This is ridiculous. The customer, end user, loses time and money they can't afford, debugging these errors, when, on the user end, nothing appeared wrong (Seldom are any of the issues described in these updates actually seen by the end user). What ever happened to the customer being right? There is the ol expression "If it ain't broken, don't fix it!" "Broken" is what is perceived broken, not what actually is broken, so you can't tell a marginally computer literate person - who OWNS the business for which you are working, that something is needed, especially when this something costs time and money, that cannot be shown or seen on the spot, overriding what they are telling you they want. The consensus is to wait "til I get this problem" then fix it. Most times they don't get the described problem for which the upgrade is intended at all. Again if it ain't broke . . . ! Many end users see all these patches and updates as just more ways to extract money, upgrading products that need to work better in their present versions, no matter how well intended the manufacturer says it is or how good the patch or upgrade is, instead of being upgraded to some new version with new problems.

My prime example of un-needed upgrades is a business that uses a 1980s DOS program to do its cash registers and bookkeeping. When the program breaks, it's easy to fix. It is so simple new employees can use it in minutes. It satisfies the IRS! When approached about the latest suite for this kind of business, the question of what the improvements were, naturally, came up. Overall there were not enough solid reasons to spend the $3000 package price, even though it was a bargain, for something that would be difficult to learn and do no more than the old DOS program. Plus when it broke or had problems, they were difficult, time consuming, and costly to fix. Their company had to be called for a fee. The old program could be fixed at any time by lots of street alcoholics who knew DOS, for a 12 pack (It is a liquor store POS program). The upgrade was seen for what it actually was, an expensive step backward.

Personally I have to keep a computer that is not connected to the internet at all - with the network card disabled - in order to stop automatic upgrades that can't easily be turned off. I run old software that works fine. In particular there is an old program (Windows 98 vintage) that works fine on XP SP1 but not SP2. Upgrading that program costs over $1000!!! What you get in the new version requires cloud backbone and won't operate at the independent desktop level period- not an improvement at all - a downgrade for a much higher price. It is the only program that does this job in this manner and the new version is unusable. It can be run in a virtual partition.

Realize too that as a technician, the final word comes from those who pay the money. From experience, it is seen that the owner has final say, no matter what the manufacturer suggests, no matter what you tell them works. Most individuals and small businesses use the "If it ain't broke, don't fix it" philosophy. Argue with them and lose the business ($$$). No matter what the internet would like to see, the reality is what people actually do. And especially, you can't convince an end user the upgrade you installed is "better" when you have to spend hours to days getting it to work with their stuff and invariably, lose some functionality or especially, perceived, functionality. The internet has attempted to produce an atmosphere where the customer is never right. When you hit the streets, in this environment, the customer is still right - They pay the money!

What is needed are answers to these questions as asked, and not ridicule or thread closure, for having perfectly valid reasons for not wanting to upgrade.

Viva Freedom of choice!

I am among MANY people who want CHOICE in whether or not to upgrade software on THEIR machines. After following many threads about this, all the statements say upgrade, no matter what the questions actually asked. Realize the FINAL WORD about our machines is ours. WE OWN THEM, NOT THE SOFTWARE MANUFACTURERS. This makes the bottom line OUR choice. If we don't want to upgrade, it's OUR FINAL word, not the software manufacturers. This is in response to the question of getting rid of upgrade nagging. The thread has always been closed without any answer to the question as asked. Invariably, when an upgrade occurs, there are incompatibilities which are left for the user to sort out, many times taking hours to days, some not ever being fixed and therefore must be lost. This is ridiculous. The customer, end user, loses time and money they can't afford, debugging these errors, when, on the user end, nothing appeared wrong (Seldom are any of the issues described in these updates actually seen by the end user). What ever happened to the customer being right? There is the ol expression "If it ain't broken, don't fix it!" "Broken" is what is perceived broken, not what actually is broken, so you can't tell a marginally computer literate person - who OWNS the business for which you are working, that something is needed, especially when this something costs time and money, that cannot be shown or seen on the spot, overriding what they are telling you they want. The consensus is to wait "til I get this problem" then fix it. Most times they don't get the described problem for which the upgrade is intended at all. Again if it ain't broke . . . ! Many end users see all these patches and updates as just more ways to extract money, upgrading products that need to work better in their present versions, no matter how well intended the manufacturer says it is or how good the patch or upgrade is, instead of being upgraded to some new version with new problems. My prime example of un-needed upgrades is a business that uses a 1980s DOS program to do its cash registers and bookkeeping. When the program breaks, it's easy to fix. It is so simple new employees can use it in minutes. It satisfies the IRS! When approached about the latest suite for this kind of business, the question of what the improvements were, naturally, came up. Overall there were not enough solid reasons to spend the $3000 package price, even though it was a bargain, for something that would be difficult to learn and do no more than the old DOS program. Plus when it broke or had problems, they were difficult, time consuming, and costly to fix. Their company had to be called for a fee. The old program could be fixed at any time by lots of street alcoholics who knew DOS, for a 12 pack (It is a liquor store POS program). The upgrade was seen for what it actually was, an expensive step backward. Personally I have to keep a computer that is not connected to the internet at all - with the network card disabled - in order to stop automatic upgrades that can't easily be turned off. I run old software that works fine. In particular there is an old program (Windows 98 vintage) that works fine on XP SP1 but not SP2. Upgrading that program costs over $1000!!! What you get in the new version requires cloud backbone and won't operate at the independent desktop level period- not an improvement at all - a downgrade for a much higher price. It is the only program that does this job in this manner and the new version is unusable. It can be run in a virtual partition. Realize too that as a technician, the final word comes from those who pay the money. From experience, it is seen that the owner has final say, no matter what the manufacturer suggests, no matter what you tell them works. Most individuals and small businesses use the "If it ain't broke, don't fix it" philosophy. Argue with them and lose the business ($$$). No matter what the internet would like to see, the reality is what people actually do. And especially, you can't convince an end user the upgrade you installed is "better" when you have to spend hours to days getting it to work with their stuff and invariably, lose some functionality or especially, perceived, functionality. The internet has attempted to produce an atmosphere where the customer is never right. When you hit the streets, in this environment, the customer is still right - They pay the money! What is needed are answers to these questions as asked, and not ridicule or thread closure, for having perfectly valid reasons for not wanting to upgrade. Viva Freedom of choice!

Modifié le par bbhank

Toutes les réponses (2)

more options

sigh.. too long to read word after word...

You can always run two different versions as in Firefox 26.0 and the old Firefox 3.6 in separate installs and separate Profiles for each.

If you must use Firefox 3.6 only at least use the last security update which was 3.6.28 (3.6.twenty-eight) to be slightly less vulnerable. http://download.cdn.mozilla.net/pub/mozilla.org/firefox/releases/3.6.28/win32/en-US/

Note that Firefox 3.6.28 and more so 3.6.11 is behind on a long list of security fixes. http://www.mozilla.org/security/known-vulnerabilities/

Modifié le par James

more options

You must have missed reading the support threads here that actually mention how to turn off Firefox program updates.

I have this code in a user.js file that I put in every new Profile that I create.

// turn off application updates:
user_pref("app.update.enabled", false);

http://kb.mozillazine.org/User.js_file

You can also toggle app.update.enabled to false in about:config to turn off updates, too.