Problem with large files

Discussion in 'ESET NOD32 Antivirus' started by qwer1304, Aug 20, 2008.

Thread Status:
Not open for further replies.
  1. qwer1304

    qwer1304 Registered Member

    Joined:
    Jun 24, 2005
    Posts:
    16
    Hi,

    NOD32 v3.0.669 is having HUGE problems with LARGE files (tested with .rar (650MB) and .avi (1GB)). It takes forever to open them. This happens with local drives (HDD), removable media (CD/DVD) and networked drives.

    Configuration:
    Dell XPS M1210, 1GB
    Win32 XP SP3 + latest patches
    NOD32 AV v3.0.669, latest updates and signature file
    AH and Runtime packers options disabled
    Temp directories cleaned with CCleaner (latest version)

    Scenario 1:
    1.NOD32 enabled
    2.Double click .rar or .avi file takes MANY MINUTES to open

    Scenario 2:
    1.NOD32 disabled
    2.Double click .rar or .avi file takes SECONDS to open

    Scenario 3:
    1.NOD32 enabled with the file extension excluded
    2.Double click .rar or .avi file takes SECONDS to open

    Practically, I need to disable NOD32 before trying to open a large file making NOD32 unusable.

    IMHO, this should be a PRIMARY most URGENT issue to solve BEFORE moving on with other features. An unusable product loaded with features is unusable no matter how many features you add.

    Thx,
    D
     
  2. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,375
    A log from System monitor or File monitor might shed more light. Try running it with the operations for ekrn.exe filtered out and watch the log while replicating the problem.
     
  3. qwer1304

    qwer1304 Registered Member

    Joined:
    Jun 24, 2005
    Posts:
    16
    Attached is the Filemon log file.

    Lot's of creations of temp files and writes to $ConvertToNonresident.

    Don't ask me what that is.
     
  4. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,375
    $ConvertToNonresident refers to the swap file (pagefile.sys). If you still experience the problem, would it be possible to convey us an example of such a file? (at least the first 1 MB would be enough to start with)
     
  5. qwer1304

    qwer1304 Registered Member

    Joined:
    Jun 24, 2005
    Posts:
    16
    After I uninstalled and installed again NOD32 the situation seems to have improved. Let me monitor the behavior and if the problem reappears I'll re-post.

    Obviously, there were zero indications that anything was wrong with NOD32 installation.
     
Thread Status:
Not open for further replies.