Page 3 of 3 FirstFirst 123
Results 21 to 25 of 25

Thread: On my XP Pro SP2 PC's, chkdsk c: verified that ZAISS 7.0.377 seems to be causing file corruption.

  1. #21
    zaswing Guest

    Default Re: Issue resolved - Kaspersky engine in ZAISS 7.0.377 does not cause any disk problems.

    On XP-home SP2
    I do get those errors but not always. I had a lot of them last fall when I had bad RAM.Recently all passes were without errors.
    One of the articles indicates it applies to XP as well.On my XP ZA runs, but not at reboot when the scan runs.I think the only way to experiment there is to totally remove ZA. Totally clean up the computer (remaining files, CCleaner, all cache items),
    GUI chkdsk
    again, defrag and then GUI chkdsk once more. Kinda laborious. Can you think of an easier way?
    I have nowhere near the limit of files they speak of.

  2. #22
    wstern Guest

    Default Re: Issue resolved - Kaspersky engine in ZAISS 7.0.377 does not cause any disk problems.

    Hi Zasuiteuser,

    I can be affected by this bug, as I have 1 terabyte of disk space and a huge # of files.

    After reading those Microsoft Knowledge base articles you provided:

    http://support.microsoft.com/kb/831374
    http://support.microsoft.com/kb/831375/
    According to this one http://support.microsoft.com/kb/255008

    I'm trying to figure out if I need to apply an additional hotfix to Windows XP SP2 to fix this chkdsk bug,
    or if XP SP2 already his the fixed chkdsk.exe?

    Bill

  3. #23
    zaswing Guest

    Default Re: Issue resolved - Kaspersky engine in ZAISS 7.0.377 does not cause any disk problems.

    I have no idea whether one should apply any such patch. I never can get that clear due to their confusing links and confusing dating. Considering they continue updating the kb article, and considering that W2K SP4 and XP SP2 have been around for a while I have no idea what to think. Patching would be last resort for me.
    Few theories if you still want to follow it
    1. Your initial thought about cleaning/not cleaning the cache daily
    2. Shut off the indexing service (search command will be slower, everything else will be faster). But now that I think of it, two months ago I've shut off my indexing service on XP. It is also off on W2K of which I posted the log. So no ZA, no indexing, still errors. Hmmmmm
    3. Perhaps more clues here
    http://support.microsoft.com/kb/327009
    http://support.microsoft.com/kb/873437
    http://support.microsoft.com/kb/315688
    enjoy!
    4. Do you set file permissions by hand (not automatic inheritance)? They might not be deleting the manual entry in some db and then cleanup after themselves???
    That reminds me of something. Their examples include index numbers (as if I knew what they are!!). The log I posted earlier had no such numbers. When my RAM on XP was bad, I saw those index numbers as as well. I wish Bill Gates would tell us what they are

  4. #24
    Join Date
    Jun 2006
    Location
    The 3rd Coast - South Central Texas
    Posts
    10,466

    Default Re: Issue resolved - Kaspersky engine in ZAISS 7.0.377 does not cause any disk problems.

    Thank you for your informative bit of research..---------------------------------------
    My Configuration:
    Operating System: Windows XP SP2 Home with IE7 MS Outlook 2003
    HP Pavilion 1025c Intel Pentium IV 3.0 GHz 2GB DDR2

    ZoneAlarm Pro version:7.0.337.000
    TrueVector version:7.0.337.000
    Driver version:7.0.337.000
    Anti-spyware engine version:5.0.162.0
    Anti-spyware signature DAT file version:01.200704.1485

    Kaspersky Anti_Virus 6.0.2.614a
    GeorgeV
    ZoneAlarm® Extreme Security


    Click here for ZA Support
    Monday-Saturday__ 6am to 10pm Central time
    Closed Sundays and Holidays

  5. #25
    wstern Guest

    Default chkdsk.exe bugs - Windows XP SP2 already includes the fixed chkdsk.exe

    Hi Zasuiteuser,

    This is just a follow up to our conversation about the chkdsk.exe bugs we saw on Microsoft's knowledge base articles.

    I had raised the question as to whether Windows XP SP2 included a fixed chkdsk.exe,
    or whether it was necessary to download and install hotfixes to fix the chkdsk.exe

    You had found issues on the knowledge base regarding chkdsk's incorrect handling of security descriptors
    for NTFS volumes containing a large # of files, and also "Cannot Open Volume for Direct Access Error Message When Chkdsk Runs at Startup".

    The good news is that I verified that Windows XP SP2 already includes the fixed chkdsk.exe.

    See the list of fixes included in Microsoft Windows XP SP2 from the link below, and search on that page for chkdsk.

    http://support.microsoft.com/kb/327009

    Bill

Page 3 of 3 FirstFirst 123

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •