General software updates

[Sebby]

Usually I'd agree, but these new versions of NOD32 seem to have issues, whereas I've updated quite a few Vista machines for people to SP2, running different antivirus programs (Kaspersky, AVG, etc) with no issues.

[Rik]

It seems the best programs always slide sooner or later.

[Lance]

I've updated my laptop to sp2 tonight and have had no problems with nod32. I've not tried acronis yet though.

[Lance]

I should have added that is v4 nod32.

[Sebby]

Don't quote me on this, but I think it might only be the 64-bit edition of NOD32 that is having trouble with Vista SP2.

[DarkStar]

The official Eset info release on this here:

http://kb.eset.com/esetkb/index?page=content&id=SOLN2254

[Rik]

Thanks for that, Ian.  I wonder how they let themselves get into that position?

[Noreen]

So once again it seems that NOD32 v3 is better than v4.

[Rik]

Worrying, isn't it.

[Noreen]

And the maker's seem to be admitting it too.

[Rik]

They've known SP2 was coming for a long time, that they've not tested it thoroughly is very worrying.

[Gary]

CCleaner 2.20.920 released

--------------------------------------------
- Added support for Google Chrome recently closed tabs.
- Disabled removal of most recent System restore point.
- Fixed bug with Internet Explorer 8 Compatibility View settings.
- Improved uninstaller support for Windows 7.
- Enhanced right-click menu options for Cleaner screen tree.
- Added extra information under title for Options and Tools screens.
- Added right-click menu to Registry screen tree.
- Added support to multi-select items in Include, Exclude and System Restore screens.
- Added language support for Estonian and Farsi.
- Internal 64-bit improvements.
- Minor bug fixes.

[Rik]

Thanks, Gary. 

[Gary]

They've known SP2 was coming for a long time, that they've not tested it thoroughly is very worrying.

This seems to be happening more and more, Rik. Not just with Nod but other vendors are rushing out security apps that are buggy, its the race to climb all over each other to the top of the pile it seems and quality is not an issue so much as brownie points for being able to show off the latest and greatest at a convention somewhere. Alas we are the ones that suffer as Beta testers even though the project is termed a release  It gets to the point that by the time you upgrade the new product is halfway though its life cycle already.

[Rik]

The problem is that, as long as they are all doing it, we are stuck with the problem, Gary. It shouldn't be that way, would we accept new cars with the same degree or readiness and functionality? Of course not. 

[Gary]

The problem is that, as long as they are all doing it, we are stuck with the problem, Gary. It shouldn't be that way, would we accept new cars with the same degree or readiness and functionality? Of course not. 

I agree, Rik. In the last few months I have dreaded new updates, even CCleaner which is normally reliable rushed an update that deleted passwords in FF, I was shocked that Vista SP2 went in so easily, mind you not much changed. Eset had months to do this testing, Kaspersky have a technical release of their new suite that has a built in Sandbox for program's such as a browsers you can launch from the app sandboxed ready to go, but it was not tested with SP2 they say  they released it as a TR the day before Vista SP2 came out, now my 2009 version of Kaspersky seems to be ticking along fine, but the new 2010 build could be tested with a service pack at source. Its the way vendors seem to be heading and that's bad news for the pc consumer as we start to wonder how well protected we really are, considering they slam home about Phishing exploits etc so often they should make sure products are tested, who wants issues like the Nod one. As you say, if it was our cars, and a a wheel fell off as it was not quiet a polished build yet there would be outcry, it would be dangerous, as is Esets V4 on the net or possibly Kasperskys 2010 suite, although as its not released to the public yet they could always tweak it, which I doubt. Patches seem to be the way to go, or multiple releases of new versions in the first few months 

[Gary]

Perfect disc build 108 released

Bug Fixes
1. Add control over Welcome Wizard via config.ini and Group Policy.
2. A schedule set via Group Policy has time with seconds always equal to minutes.
3. Status is not updated when defragmentation was resumed.
4. Space Reports graphs are 1 day off.
5. Multiple PDAgentS1 processes.
6. High CPU usage when selecting a drive with excluded folder.
7. A few features are missing when user language is set to Japanese.
8. Auto Update file download is not cancelled by Cancel button on Raxco Software Auto Update dialog.
9. PerfectDisk for VMware does not provide exclusion list for a virtual machine.
10. Duplicates - If Other files selected, doesn't require input of file extension.
11. Recycler reports double number of files cleaned in Recycler Bin on Vista.
12. List of temporary folders for Recycler once saved never updated.
13. Recycler pane does not preserve drive selection and option selection.
14. When Recycler run is stopped the results report 0 files cleaned.
15. "Can not connect to Exchange.." message on system tray icon launch.
16. Exchange pane: label "Storage Group" is missing and Next Run drop-down menu is disabled.
17. Send Test Email reports success with all empty fields.
18. PD/Settings/Exchange - tab order is not as expected.
19. Windows Home Server Plugin uses old PD10 icon.
20. Need to have column width persistent in the log viewer.
21. Sort indicator does not conform to Windows specifications in a number of column header.
22. What do dark blocks mean?
23. Daily schedule does not display error "Invalid Maximum duration value".
24. Calendar on weekly schedule wizard get truncated when error messages displayed.
25. Space Explorer - During Analysis, strange graphics issue is displayed.

[wecpcs]

I agree, Rik. In the last few months I have dreaded new updates, even CCleaner which is normally reliable rushed an update that deleted passwords in FF, I was shocked that Vista SP2 went in so easily, mind you not much changed. Eset had months to do this testing, Kaspersky have a technical release of their new suite that has a built in Sandbox for program's such as a browsers you can launch from the app sandboxed ready to go, but it was not tested with SP2 they say  they released it as a TR the day before Vista SP2 came out, now my 2009 version of Kaspersky seems to be ticking along fine, but the new 2010 build could be tested with a service pack at source. Its the way vendors seem to be heading and that's bad news for the pc consumer as we start to wonder how well protected we really are, considering they slam home about Phishing exploits etc so often they should make sure products are tested, who wants issues like the Nod one. As you say, if it was our cars, and a a wheel fell off as it was not quiet a polished build yet there would be outcry, it would be dangerous, as is Esets V4 on the net or possibly Kasperskys 2010 suite, although as its not released to the public yet they could always tweak it, which I doubt. Patches seem to be the way to go, or multiple releases of new versions in the first few months 

I have had problems with Vista SP2. I had been using the RC1 version previously and it had found my Logitech Pro 5000 webcam without any problem or even the Logitech software. Upon uninstalling the RC1 version (which you had to) and then reinstalling the official version, my webcam disappeared, so I then I had to install the Logitech software with all the extra stuff I did not really want. A backward step I think.

Colin

[Gary]

I have had problems with Vista SP2. I had been using the RC1 version previously and it had found my Logitech Pro 5000 webcam without any problem or even the Logitech software. Upon uninstalling the RC1 version (which you had to) and then reinstalling the official version, my webcam disappeared, so I then I had to install the Logitech software with all the extra stuff I did not really want. A backward step I think.

Colin

I never touch Logitech software, they are renown for buggy drivers and software some webcams had to be plugged in everytime you booted to make them work other wise the software did not recognise the things  , I use my Pro 9000 as a UVC complaint webcam without the need for drivers and the awful issues people sometimes get, I would not be surprised this was a Logitech issue as well. Check the Logitech forum out, the list of issues with webcams is never ending sadly 

[Gary]

Java runtime 6 update 14 released http://java.sun.com/javase/downloads/index.jsp "This release is Windows 7 support-ready and includes support for Internet Explorer 8, Windows Server 2008 SP2, and Windows Vista SP2. New features include the G1 garbage collector, plus performance and security enhancements"

[Sebby]

I have had problems with Vista SP2. I had been using the RC1 version previously and it had found my Logitech Pro 5000 webcam without any problem or even the Logitech software. Upon uninstalling the RC1 version (which you had to) and then reinstalling the official version, my webcam disappeared, so I then I had to install the Logitech software with all the extra stuff I did not really want. A backward step I think.

No doubt a fresh install of Vista then SP2 would get the camera working how it was originally without the Logitech bloatware.

[Gary]

No doubt a fresh install of Vista then SP2 would get the camera working how it was originally without the Logitech bloatware.

Its possible using the release candidate and uninstalling and reinstalling could well have messed things up Sebby, mine works as it was using Microsofts drivers not Logitechs, but I never had the RC1 installed, who knows 

[wecpcs]

No doubt a fresh install of Vista then SP2 would get the camera working how it was originally without the Logitech bloatware.

I agree, but I only did that back in February, for a nice clean start. I do not want to go through all that hassle again. I will wait for Windows 7 RTM than go for it. In the meantime I am going to have a play with Windows 7 RC1 (64-bit) on a separate drive. I did try the Beta version (32-bit) and was impressed but I did that on a dual boot, which I lost when I reinstalled Vista in February for other reasons.

Colin

[Niall]

The problem is that, as long as they are all doing it, we are stuck with the problem, Gary. It shouldn't be that way, would we accept new cars with the same degree or readiness and functionality? Of course not. 

This is what was happening with software firewalls, so I ended up using the windows firewall as there were some form of issue with every one I tried. The most annoying thing about NOD32 having problems is that they started after I bought it! Typical!

[Rik]

Life's like that, Niall.