PDA

View Full Version : BUG: Moving files!


Thorz
August 4th, 2004, 08:04 AM
Email sent to ESET today:

{QUOTE-> NOD32 Antivirus System information
Virus signature database version: 1.833 (20040803)
Dated: tirsdag 3. august 2004
Virus signature database build: 4731

Information on other scanner support parts
Advanced heuristics module version: 1.007 (20040309)
Advanced heuristics module build: 1053
Internet filter version: 1.002 (20040708)
Internet filter build: 1013
Archive support module version: 1.018 (20040727)
Archive support module build version: 1093

Information on installed components
NOD32 For Windows NT/2000/XP/2003 - Base
Version: 2.000.11b
NOD32 For Windows NT/2000/XP/2003 - Internet support
Version: 2.000.11b
NOD32 for Windows NT/2000/XP/2003 - Standard component
Version: 2.000.11b

Operating system information
Platform: Windows XP
Version: 5.1.2600 Service Pack 1
Version of common control components: 5.82.2800
RAM: 1023 MB
Processor: Intel(R) Pentium(R) 4 CPU 3.00GHz (2998 MHz) (HT enabled)


I was moving a a big folder (4.3GB) with lots of subfolders and files inside it from my HD to my external WD Firewire HD. Windows XP has abort the process with this message: "cannot delete xxxx, The folder is not empty". I was very sorprised because I have never had problems moving big folders before, and after trying several times I found that the only application that is running in the background is NOD32. I have unloaded all the resident scanners and inmediatly the problem went away.

I cannot understand what is happening here, maybe NOD32 is not releasing the files when they are been moved making impossible for Windows to delete them (as a move process is just a normal copy followed by a delete command).

I hope you can fix this problem. <-QUOTE}

Blackspear
August 4th, 2004, 08:41 AM
Please keep us in the loop as to replies from Eset...

Cheers ;D

Thorz
August 4th, 2004, 02:01 PM
I received this from ESET:
{QUOTE->
the second problem, the only workaround for now is to decrease the
value of all instances of "WaitToKillServiceTimeout" in the registry.
<-QUOTE}.

But another post here has been made telling that after the installation of SP2 the problem has dissapeared. Let's all hope that this would be the light at the end of the tunnel to this long time problem.

EDIT: Sorry, this answer didn't belong to this thread. :o :-[ :-[

Thorz
August 8th, 2004, 06:18 AM
{QUOTE-> Please keep us in the loop as to replies from Eset...

Cheers ;D <-QUOTE}

I can confirm that all the beta versions that I have tested (sent from ESET) present this critical bug. I hope they can fix it on the final version. For now It's no more beta testing for me, I am back with the safe official version. Sucess in moving files is critical for me. I recommend all the beta testers to run some test moving a folder arround 500MB full of files and subfolders between 2 partitions or hard disks (small .exe's trigger the problem easily) and posting the results here to see if we can nail the problem to a speciffic hardware configuration (I am on Intel P4 with hyperthreading enabled, maybe that makes any difference to NOD32?)

NOD32 Antivirus System information
Virus signature database version: 1.835 (20040806)
Dated: fredag 6. august 2004
Virus signature database build: 4737

Information on other scanner support parts
Advanced heuristics module version: 1.008 (20040804)
Advanced heuristics module build: 1057
Internet filter version: 1.001 (20031104)
Internet filter build: 1012
Archive support module version: 1.018 (20040727)
Archive support module build version: 1093

Information on installed components
NOD32 For Windows NT/2000/XP/2003 - Base
Version: 2.000.9
NOD32 For Windows NT/2000/XP/2003 - Internet support
Version: 2.000.9
NOD32 for Windows NT/2000/XP/2003 - Standard component
Version: 2.000.9

Operating system information
Platform: Windows XP
Version: 5.1.2600 Service Pack 1
Version of common control components: 5.82.2800
RAM: 1023 MB
Processor: Intel(R) Pentium(R) 4 CPU 3.00GHz (2998 MHz)

SaphireX
August 9th, 2004, 04:56 PM
I concur with Thorz conclusion that this indeed is a serious "bug" and needs to be rectified in the final code. As a semi work-around I open a directory in WinRAR and am able to delete-copy and move files around for the most part. However, using explorer I find that moving files to other directories or attempting to delete files poses serious problems......

Regards

Saphire
--------------------------------------------
NOD32 Antivirus System information
Virus signature database version: 1.836 (20040809)
Dated: Monday, August 09, 2004
Virus signature database build: 4739
Information on other scanner support parts
Advanced heuristics module version: 1.008 (20040804)
Advanced heuristics module build: 1057
Internet filter version: 1.002 (20040708)
Internet filter build: 1013
Archive support module version: 1.018 (20040727)
Archive support module build version: 1093
Information on installed components
NOD32 For Windows NT/2000/XP/2003 - Base
Version: 2.000.11b
NOD32 For Windows NT/2000/XP/2003 - Internet support
Version: 2.000.11b
NOD32 for Windows NT/2000/XP/2003 - Standard component
Version: 2.000.11b
Operating system information
Platform: Windows XP
Version: 5.1.2600 Service Pack 1
Version of common control components: 5.82.2800
RAM: 1023 MB
Processor: AMD Athlon(tm) 64 Processor 3200+ (2002 MHz)

--------------------------------------------
My System (running Cool n' Quiet):

Processor
Model : AMD Athlon(tm) 64 Processor 3200+
Speed : 801MHz
Model Number : 3200 (estimated)
Performance Rating : PR1202 (estimated)
Type : Standard
L2 On-board Cache : 1024kB ECC Synchronous Write-Back (16-way, 64 byte line size)
Mainboard
Bus(es) : ISA AGP PCI IMB USB FireWire/1394 i2c/SMBus
MP Support : 1 CPU(s)
MP APIC : Yes
System BIOS : American Megatrends Inc. 1008.008
System : To Be Filled By O.E.M. To Be Filled By O.E.M.
Mainboard : ASUSTeK Computer Inc. K8V
Total Memory : 1023MB DDR-SDRAM
Chipset 1
Model : ASUSTeK Computer Inc Apollo K8HTB CPU to PCI Bridge
Front Side Bus Speed : 2x 800MHz (1600MHz data rate)
Chipset 2
Model : Advanced Micro Devices (AMD) Athlon 64 / Opteron HyperTransport Technology Configuration
Front Side Bus Speed : 2x 800MHz (1600MHz data rate)
Total Memory : 1024MB DDR-SDRAM
Memory Bus Speed : 2x 200MHz (400MHz data rate)
Video System
Monitor/Panel : ViewSonic P70f
Adapter : NVIDIA GeForce FX 5200
Imaging Device : Lexmark X74-X75
Physical Storage Devices
Removable Drive : Floppy disk drive
Hard Disk : VIA SATA RAID 0 SCSI Disk Device (223.6GB)
CD-ROM/DVD : LITE-ON DVDRW LDW-411S (CD 40X Rd, 40X Wr) (DVD 5X Rd)
Logical Storage Devices
1.44MB 3.5" (A:) : N/A
(C:) : 223.6GB (212.4GB, 95% Free) (NTFS)
CD-ROM/DVD (D:) : N/A
Peripherals
Serial/Parallel Port(s) : 3 COM / 1 LPT
USB Controller/Hub : VIA Rev 5 or later USB Universal Host Controller
USB Controller/Hub : VIA Rev 5 or later USB Universal Host Controller
USB Controller/Hub : VIA Rev 5 or later USB Universal Host Controller
USB Controller/Hub : VIA Rev 5 or later USB Universal Host Controller
USB Controller/Hub : Standard Enhanced PCI to USB Host Controller
USB Controller/Hub : USB Root Hub
USB Controller/Hub : USB Root Hub
USB Controller/Hub : USB Root Hub
USB Controller/Hub : USB Root Hub
USB Controller/Hub : USB Root Hub
USB Controller/Hub : Generic USB Hub
USB Controller/Hub : USB Printing Support
FireWire/1394 Controller/Hub : VIA OHCI Compliant IEEE 1394 Host Controller
Keyboard : Standard 101/102-Key or Microsoft Natural PS/2 Keyboard
Mouse : Microsoft PS/2 Mouse
Human Interface : USB Human Interface Device
MultiMedia Device(s)
Device : AVerMedia, AVerTV WDM Video Capture
Device : AVerMedia, AVerTV WDM Audio Capture
Device : SoundMAX Integrated Digital Audio
Communication Device(s)
Device : SoftV92 Voice Modem with SmartCP
Printers and Faxes
Model : SnagIt 7
Model : pdfFactory Pro
Model : Microsoft Office Document Image Writer
Model : Lexmark X74-X75
Model : FinePrint
Model : Fax
Model : CAPTURE FAX BVRP
Power Management
AC Line Status : On-Line
Battery No 1 : 100%
Operating System(s)
Windows System : Microsoft Windows XP/2002 Home (Win32 x86/IA32) 5.01.2600 (Service Pack 1)
Network Services
Adapter : 3Com Gigabit LOM (3C940)

Thorz
August 9th, 2004, 05:32 PM
Ok, this confirms that the problem is not linked only to Intel hardware. I hope that ESET puts attention to this issue, it is indeed very critical.
On the other hand the official NOD32 is working fine.

tosbsas
August 10th, 2004, 07:04 AM
Have you tried any other explorer - like total commander or else too?? Could be a windows explorer thing

Ruben

nonmirecordo
August 10th, 2004, 07:34 AM
{QUOTE-> (small .exe's trigger the problem easily) <-QUOTE}

Moving .exes using Directory Opus presents no problems.

Thorz
August 10th, 2004, 12:19 PM
{QUOTE-> Have you tried any other explorer - like total commander or else too?? Could be a windows explorer thing

Ruben <-QUOTE}

It doesn't matter if it works or not with a explorer replacement. 98% of the Windows people out there uses Windows explorer for working with their files. It is a NOD32 AMON beta thing. With the official version, or with AMON disabled in the beta the problem dissapears.

My drives are 2: 1 WD120 connected to SATA and WD external Media Center Firewire disk.

SaphireX
August 10th, 2004, 07:29 PM
Thorz hit the nail on the head! 99% of windows users use explorer to manipulate their files and this "bug" in the beta version needs to be corrected as soon as practicable by Eset (who I hope reads the threads here....)

A work-around or a 3rd party app is not the solution.

Speaking of registry change that was mentioned earlier in this thread
"to decrease the value of all instances of "WaitToKillServiceTimeout" in the registry" to "fix" this problem. What value should it be changed to?

Regards

Saphire

ronjor
August 10th, 2004, 07:36 PM
{QUOTE->
Speaking of registry change that was mentioned earlier in this thread
"to decrease the value of all instances of "WaitToKillServiceTimeout" in the registry" to "fix" this problem. What value should it be changed to?

Regards

Saphire <-QUOTE}



http://www.wilderssecurity.com/showthread.php?p=232182#post232182