vps 100811-2 fix

Hi all,

recent 100811-2 fixes previous ‘package broken’ errors, please update. Sorry for any inconvenience.

Excellent. Thanks. :slight_smile:

/bow

thanks, works like a charm!

Spline64

Yeah, worked here also. Although I never pay that much attention to ‘package broken’ errors as they, generally, were due to temporary glitches :slight_smile:

Did I miss anything? I was asleep ???

Some people had trouble updating and got the error “Package broken.” Good to hear it’s fixed though. :slight_smile:

Thanks Gloobygoob. It was night here, so missed it. Any ways good that is fixed now.

nmb

Thank you, all is well now. The virus data base (VPS 100812-0 ) has been automatically generated at
4:2-am on 12/08/2010. My version is Avast 4.8 free. Do I need to upgrade to
Avast 5 free???

You should if your OS is supported (win9.x and winME aren’t) as it provides more protection than avast 4.8, plus support for avast 4.8 is due to end at the end of this year.

http://files.avast.com/iavs5x/setup_av_free.exe - Avast! Free antivirus Quick Start Guide http://files.avast.com/files/documentation/quick-start-guide-free-en-ww.pdf

[quote author=DavidR link=topic=62733.msg529865#msg529865 date=1281639303]
You should if your OS is supported (win9.x and winME aren’t) as it provides more protection than avast 4.8, plus support for avast 4.8 is due to end at the end of this year.

http://files.avast.com/iavs5x/setup_av_free.exe - Avast! Free antivirus Quick Start Guide [url=http://files.avast.com/files/documentation/quick-start-guide-free-en-ww.pdf]

Thank you for this information. Will I be reguired to uninstall Avast 4.8 before I run the above Avast 5 version download. If so what would be the url or link for this proceedure. Cheers , athome34GBK

Usually not…
The installer takes care of that, but if you should run into problems…
You can use the uninstall utility in safe mode: http://www.avast.com/uninstall-utility
asyn

@ athome34GBK

Welcome fellow Canadian avast! user.

I have avast! V5 and it works great.

Mmmmm. I never got that error. I guess I was just lucky again.