File locked

Discussion in 'NOD32 Early v2 Beta' started by Q Section, May 28, 2003.

Thread Status:
Not open for further replies.
  1. Q Section

    Q Section Registered Member

    Joined:
    Feb 5, 2003
    Posts:
    771
    Location:
    Headquarters - London & Field Offices -Worldwide
    Hello Everyone

    Doing a scan we got 2 log files we never saw before. Please advise how to fix the situation.

    C:\WIN386.SWP - error opening (file locked) [4]
    C:\WINDOWS\TEMP\JET7207.TMP - error opening (file locked) [4]

    Regarding the latter - we recently downloaded a file from MS called MS JET 4.0 Service Pack 3 Update

    http://www.microsoft.com/downloads/details.aspx?FamilyID=af693865-2bab-4ae5-b001-42840473ef39&DisplayLang=en

    The question is this - what can we do to enable NOD32 to scan these files and get them unlocked?

    Thank you.
     
  2. JimIT

    JimIT Registered Member

    Joined:
    Jan 22, 2003
    Posts:
    1,035
    Location:
    Denton, Texas
    Those are Windows swap (temporary memory space) and (looks like) HP JetDirect files, which go into use when Windows loads up. Windows won't let you scan them, but that's normal for most av's.

    You might try running the scan after booting in safe mode.

    I'm sure Eset will be along to help quickly. :D
     
  3. MegaHertz

    MegaHertz Registered Member

    Joined:
    Nov 28, 2002
    Posts:
    69
    Location:
    U.S.A.
    QSection,

    This is a 0Kb temp file that is created by Outpost v2 it is tied to the logging system. Everytime OP is started a new one is created and the numerical portion of the name is always different. If you shutdown Outpost you can scan it.
     
  4. Q Section

    Q Section Registered Member

    Joined:
    Feb 5, 2003
    Posts:
    771
    Location:
    Headquarters - London & Field Offices -Worldwide
    Thank you JimIT and MegaHertz. Yes we knew the one was the swap file and the other one does have 0kb size now that we looked. :)
     
Thread Status:
Not open for further replies.