NOD32 version 1.812 (20040716) NT Command line: C:\WINDOWS Checking CRC of the NOD32.EXE file: status OK Operating memory is OK. date: 16.7.2004 time: 20:16:38 Scanned disks, directories and files: C:\WINDOWS\ C:\WINDOWS\system32\config\system.LOG - error opening (file locked) [4] C:\WINDOWS\system32\config\software.LOG - error opening (file locked) [4] C:\WINDOWS\system32\config\default.LOG - error opening (file locked) [4] C:\WINDOWS\system32\config\SECURITY - error opening (file locked) [4] C:\WINDOWS\system32\config\SAM - error opening (file locked) [4] C:\WINDOWS\system32\config\SAM.LOG - error opening (file locked) [4] C:\WINDOWS\system32\config\SECURITY.LOG - error opening (file locked) [4] C:\WINDOWS\system32\config\SYSTEM - error opening (file locked) [4] C:\WINDOWS\system32\config\SOFTWARE - error opening (file locked) [4] C:\WINDOWS\system32\config\DEFAULT - error opening (file locked) [4] C:\WINDOWS\Temp\JETDA5.tmp - error opening (file locked) [4] number of files scanned: 49671 number of viruses found: 0 time of completion: 20:28:24 total scanning time: 706 sec (00:11:46) Notes: [4] File cannot be open. It is being exclusively used by another application or operating system. These files are always locked during scan.
dear hohoho, are you Santa? anyway they are all harmless except one for which i'm not taking any responsibility. the last one residing in your TEMP folder. i think you're using RAM resident tool for RAM management or something like that. it doesn't mean that the file is malicious .its just that it is not encountered generally. if you're suspicious then copy it to a new location and scan it again. it won't be locked now