KAV 6 and .pst files

Discussion in 'other anti-virus software' started by Howard Kaikow, Nov 14, 2006.

Thread Status:
Not open for further replies.
  1. Howard Kaikow

    Howard Kaikow Registered Member

    Joined:
    Apr 10, 2005
    Posts:
    2,802
    Anybody know what KAV is doing to change the size of ALL .pst files on a computer?

    An AV program must not modify ANY file unless so directed by the user.
     
  2. Howard Kaikow

    Howard Kaikow Registered Member

    Joined:
    Apr 10, 2005
    Posts:
    2,802
    I've got a multiboot system, with a different version of Office in each OS.

    OS on C has Office 97
    OS on F has Office 2000
    OS on G has Office XP
    OS on J has Office 2003.

    Main OS is on J and has NAV 2006.

    Last week, I installed Kaspersky AV 6 in the OS on the G drive.
    While running a full system scan with KAV, I noticed that each of the 4
    outlook.pst files changed in size.

    outlook.pst on C changed from 353KB to 384KB.
    outlook.pst on F changed from 513KB to 560KB.
    outlook.pst on G changed from 480KB to 512KB.
    outlook.pst on C changed from 761KB to XXXKB, not yet finished..

    Sue Mosher's tyo2kp.pst changed from 624KB to 640KB.
    "Building Microsoft Outlook 2002 Applications.pst" changed from 7696KB to
    7744KB.

    Is it really necessary for an AV program to change the size of a PST when
    scanning?
    KAV did not change the PST file sizes when KAV was installed. Tools |
    Options, in Outlook 2002, does get a Kaspersky AV tab.

    Of course, since KAV is installed in the OS on the G drive, Outlook 2002 is
    the current Outlook.
    Does this mean that the outlook.pst installed on C and F have to get changed
    when looked at with the Outlook on G?
    Even if so, why would the outlook.pst on G change size as it is native to
    the Outlook on G?
    Scan has not yet gotten to the J drive, so I am wondering what is going to
    happen when KAV tries to use Outlook 2002 to examine an Outlook 2003 PST file.

    Yes, there are bigger problems in the world, but my feeling is that I may
    need to restore each PST to its pre-scan condition.
     
  3. Howard Kaikow

    Howard Kaikow Registered Member

    Joined:
    Apr 10, 2005
    Posts:
    2,802
    Corrected text.
    ---------------
    I've got a multiboot system, with a different version of Office in each OS.

    OS on C has Office 97
    OS on F has Office 2000
    OS on G has Office XP
    OS on J has Office 2003.

    Main OS is on J and has NAV 2006.

    Last week, I installed Kaspersky AV 6 in the OS on the G drive.
    While running a full system scan with KAV, I noticed that each of the 4
    outlook.pst files changed in size.

    outlook.pst on C changed from 353KB to 384KB.
    outlook.pst on F changed from 513KB to 560KB.
    outlook.pst on G changed from 480KB to 512KB.
    outlook.pst on J did not change in size.

    Sue Mosher's tyo2kp.pst changed from 624KB to 640KB.
    "Building Microsoft Outlook 2002 Applications.pst" changed from 7696KB to
    7744KB.

    Is it really necessary for an AV program to change the size of a PST when
    scanning?
    KAV did not change the PST file sizes when KAV was installed. Tools |
    Options, in Outlook 2002, does get a Kaspersky AV tab.

    Of course, since KAV is installed in the OS on the G drive, Outlook 2002 is
    the current Outlook.
    Does this mean that the outlook.pst installed on C and F have to get changed
    when looked at with the Outlook on G?
    Even if so, why would the outlook.pst on G change size as it is native to
    the Outlook on G?
    pst on J drive did not change, likely because it is from Outlook 2003 and G drive uses Outlook 2002.

    Yes, there are bigger problems in the world, but my feeling is that I may
    need to restore each PST to its pre-scan condition.
     
Thread Status:
Not open for further replies.
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.