>> UPDATES <<

[Jahn]

SUPERAntiSpyware Portable Scanner 01/14/2010 (I don't recall this being posted previously)

The scanner does not need to be installed or uninstalled and contains our full scanning and removal engine. More...

Download: http://www.superantispyware.com/portablescanner.html

[harman123]

Microsoft has released a critical Security Update for various versions of Internet Explorer in Windows. This update addresses a recently discovered security vulnerability. It is available from the link above or via Windows Update.

[harman123]

Microsoft has released the Windows Experience Pack. This Pack allows you to customize a theme for Windows Live Messenger and/or your Windows Desktop.

http://windowsteamblog.com/blogs/windowsexperience/archive/2010/01/20/introducing-the-windows-experience-pack.aspx

[Hermite15]

delete 

[Alan Baxter]

It would be nice if there was a means of testing the current add-ons for compatibility with FF 3.6 before committing to the update.

There is!  If your profile has any extensions that aren't compatible with Fx 3.6, the updater will list them in the Software Update dialog and allow you to abort the install.  Here's the procedure (which I just verified in a test Fx 3.5.7 installation):
- Help > Check for Updates should offer you Firefox 3.6
- Click Get the New Version (It would be nice if it informed you you'd be given a chance to abort if you have any incompatible extensions.)
Result: A list of all your incompatible extensions is displayed.  Isn't that neat?
- Click the Back button in the dialog and then click Ask Later or No Thanks

I've tested all my incompatible extensions in Fx 3.6.  They all work (a welcome surprise).  I used the MR Tech Toolkit extension to disable compatible checking for the evaluation, but it's sufficient to use about:config to create the extensions.checkCompatibility.3.6 preference and set it to false.  FYI, here is the list of incompatible extensions I use that work after all in Fx 3.6:

Generated: Sat Jan 23 2010 17:16:45 GMT-0700 (Mountain Standard Time)
User Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2) Gecko/20100115 Firefox/3.6
Build ID: 20100115144158
- Aardvark 2.97
- AniDisable 1.2
- Digger 3.5.2
- DM BBCode Extension 2.1
- keywordManager 0.7.3
- PopupSound 0.1.6
- repagination 2006.4.5
- replayanimation 0.2.2
- Update Bookmark 0.0.5.1
- Update Notifier 0.1.5.5
- Work Offline 1.5

After I installed and tested them, I used MR Tech Local Install to make all of them compatible in one swoop.  No editing of the .rdf files necessary.  I then turned compatibility checking back on.

[DavidR]

I was of the opinion that the compatibility checks were carried out after the update and before firefox was opened. At least that is my recollection of earlier updates, finding out after the fact that some of your add-ons were disabled.

I don't use any of those supposed incompatible ones, I currently use BBCodeXtra as my BB add-on.

[DavidR]

OK checked that out and at last a really useful function tell you what isn't compatible up front.

My list of incompatible ones:
CookieSafe 3.0.5
CustomizeGoogle 0.76
CuteMenus2 3.1

gTranslate 0.6 *** this one I had to .modify the .rdf file as it is no longer developed, a great little tool that you can select a bunch of test on a page and just have it automatically detected and translated into English.

IE Tab 1.5.20090525
Noia 2.0 (eXtreme) 3.69
translator 1.0.4.4
Tweak Network 1.3
View Cookies 1.9

Some of these although not security I use a lot, as I said I don't like to hack or force compatibility if it can be avoided, so it looks like I will wait a while and let them catch up.

Even though I backed out of the update those appear to have been marked incompatible already, see image. I guess I need to close and reopen firefox to get back to square one.

[Alan Baxter]

I replaced CookieSafe with Cookie Monster. CookieSafe has been abandoned and probably will never be updated again.
You should replace CustomizeGoogle with OptimizeGoogle. That's the fork and it's currently maintained.

Even though I backed out of the update those appear to have been marked incompatible already, see image. I guess I need to close and reopen firefox to get back to square one.

Not sure what you mean here. I don't see anything marked incompatible in your screenshot. None of the incompatible extensions that were in my Fx 3.5.7 test profile were disabled or marked incompatible after I aborted the Fx 3.6 install. No restart was necessary. I hope things look right to you after a restart.

[harman123]

Microsoft has released Version 7.1 of its IntelliType Pro keyboard drivers.

http://www.microsoft.com/hardware/download/download.aspx?category=MK

Realtek has released Version 2.41 of its HD Audio drivers.

http://www.realtek.com.tw/downloads/downloadsCheck.aspx?Langid=1&PNid=14&PFid=24&Level=4&Conn=3&DownTypeID=3&GetDown=false

[Hermite15]

Realtek has released Version 2.41 of its HD Audio drivers.

already had issues with 2.40, MS drivers through winupdates (actually more basic, but realtek drivers too) work better.

[DavidR]

I replaced CookieSafe with Cookie Monster. CookieSafe has been abandoned and probably will never be updated again.
You should replace CustomizeGoogle with OptimizeGoogle. That's the fork and it's currently maintained.

Thanks for those Alan.

Even though I backed out of the update those appear to have been marked incompatible already, see image. I guess I need to close and reopen firefox to get back to square one.

Not sure what you mean here. I don't see anything marked incompatible in your screenshot. None of the incompatible extensions that were in my Fx 3.5.7 test profile were disabled or marked incompatible after I aborted the Fx 3.6 install. No restart was necessary. I hope things look right to you after a restart.

If you expand the image, you can see in the context menu some of them have been marked "Compatibility" (not the physical add-ons). Whilst a restart wasn't necessary I did so to remove that from the context menu, once restarted these reverted to normal.

[Alan Baxter]

You're welcome.

Not sure what you mean here. I don't see anything marked incompatible in your screenshot. None of the incompatible extensions that were in my Fx 3.5.7 test profile were disabled or marked incompatible after I aborted the Fx 3.6 install. No restart was necessary. I hope things look right to you after a restart.

If you expand the image, you can see in the context menu some of them have been marked "Compatibility" (not the physical add-ons). Whilst a restart wasn't necessary I did so to remove that from the context menu, once restarted these reverted to normal.

I see now in the screenshot that you had the word "compatibility" highlighted.  That caused the associated context menu entries.  Turning off the highlight by clicking elsewhere on the page should have been sufficient, but if it wasn't, then I'm glad a browser restart worked.

[Chris Thomas]

IMMUNET 1.0.24

http://www.immunet.com

[Hermite15]

flashgot 1.2.1.10

https://addons.mozilla.org/en-US/firefox/addon/220
http://flashgot.net/

[YoKenny]

WinPatrol PLUS for 99 cents on January 29th starting midnight EST

The Great 99 Cent Software Experiment of 2010

Have you noticed that most of the software you’re buying these days is only 99 cents?

The traditional software industry, like many, has been hit hard by slumping economic times. At least that’s what appears to be happening. I can’t help but notice traditional software distribution is in a state of flux not unlike the media and publishing industries.

http://billpstudios.blogspot.com/2010/01/great-99-cent-software-experiment-of.html