Eraser, Windows 7 64-bit and TEMP folder

You don't believe in my words?
Problem file (in that case - dir) - hsperfdata_yur
Code: 
 Том в устройстве C не имеет метки.
 Серийный номер тома: 826B-6111

 Содержимое папки C:\TEMP

22.03.2011  16:48    <DIR>          .
22.03.2011  16:48    <DIR>          ..
12.03.2011  14:44    <DIR>          111
22.03.2011  16:48                 0 111.txt
18.03.2011  14:45    <DIR>          124
15.03.2011  13:11    <DIR>          22
28.02.2011  13:33             9 556 AdbeReaderBroker.log
21.03.2011  10:10            15 528 AdobeARM.log
19.03.2011  12:34               906 AUCHECK_CORE.txt
19.03.2011  12:34               222 AUCHECK_PARSER.txt
16.03.2011  10:27                 0 B782.tmp
01.03.2011  09:33    <DIR>          Bonus.SSR10
01.03.2011  12:51                 0 C716.tmp
01.03.2011  09:32    <DIR>          comtypes_cache
28.02.2011  13:31    <DIR>          Cookies
16.03.2011  10:27                 0 D261.tmp
18.03.2011  15:31    <DIR>          Ebooka
28.02.2011  16:50                 0 etilqs_35imfPtybUAlau73qlpO
22.03.2011  15:37                 0 etilqs_8armgGu5DGUxigUGOcyf
28.02.2011  17:30                 0 etilqs_E3khrstqpvX4DzCaVohz
28.02.2011  18:01                 0 etilqs_kK5RB9pMvjI0WfSdoECN
28.02.2011  14:12                 0 etilqs_nZpP5f2hiQT6Ezi5dNal
22.03.2011  16:48                 0 etilqs_p85qDl5flOceJIWmgmPj
22.03.2011  16:46                 0 etilqs_Xe0q0c4EPcbLNDyeOzb8
06.01.2011  09:26                 0 FXSAPIDebugLogFile.txt
28.02.2011  13:31    <DIR>          History
21.03.2011  16:50    <DIR>          hsperfdata_yur
04.03.2011  19:54                 0 jinstall.cfg
04.03.2011  19:53           885 536 jre-6u24-windows-i586-iftw-rv.exe
21.03.2011  10:14            13 051 jusched.log
01.03.2011  09:33    <DIR>          Low
22.03.2011  03:53            37 452 MpCmdRun.log
22.03.2011  03:53    <DIR>          MPTelemetrySubmit
04.03.2011  12:50    <DIR>          msohtml1
15.03.2011  16:10    <DIR>          msohtmlclip
15.03.2011  16:10    <DIR>          msohtmlclip1
22.03.2011  11:10    <DIR>          nsq3CEE.tmp
02.03.2011  11:27                 0 qtsingleapp-Golden-86bf-1-lockfile
15.03.2011  16:57        10 189 824 Reports.dll
21.03.2011  15:04             5 422 StructuredQuery.log
01.03.2011  17:28    <DIR>          temp
28.02.2011  13:31    <DIR>          Temporary Internet Files
28.02.2011  13:22    <DIR>          VBE
08.03.2011  11:42               389 wmsetup.log
21.03.2011  10:09    <DIR>          WPDNSE
16.03.2011  17:12    <DIR>          ~GetFbInfoTmp
28.02.2011  12:52    <DIR>          ~prj
21.03.2011  17:31           777 728 Наполнение базы-1.doc
21.03.2011  17:00           777 728 Наполнение базы.doc
              26 файлов     12 713 342 байт
              23 папок  55 052 816 384 байт свободно
 
I am sure that this is not an issue of Joel not believing, but of trying to get as much information as possible about the problem folder and the behaviour of your system. Reports of symptoms like those you describe are not common, and in that past have, in my recollection, always turned out to be not directly related to Eraser. But, if you have found a previously undiscovered bug in Eraser, Joel will want to know about it.

Joel's last post began with the word 'also', that is, he wished you to try the suggestions in my last post. Did you do so?

What we are trying to work out is
  • can the folder be deleted in Windows? If it can, does it immediately reappear, or reappear when you run some program?
  • if the folder can't be deleted or erased normally, and it be deleted or erased with a program that is run 'as Administrator'?
  • if it can't be deleted even then, is it locked, and, if so, what by (you can use Lockhunter or a similar program to determine this)?
With this information, Joel can then hopefully work out why no report is appearing in the Eraser log. Only then will we know for sure whether there's a bug in Eraser.

David
 
DavidHB said:
I am sure that this is not an issue of Joel not believing, but of trying to get as much information as possible about the problem folder and the behaviour of your system. Reports of symptoms like those you describe are not common, and in that past have, in my recollection, always turned out to be not directly related to Eraser. But, if you have found a previously undiscovered bug in Eraser, Joel will want to know about it.

Joel's last post began with the word 'also', that is, he wished you to try the suggestions in my last post. Did you do so?

What we are trying to work out is
  • can the folder be deleted in Windows? If it can, does it immediately reappear, or reappear when you run some program?
  • if the folder can't be deleted or erased normally, and it be deleted or erased with a program that is run 'as Administrator'?
  • if it can't be deleted even then, is it locked, and, if so, what by (you can use Lockhunter or a similar program to determine this)?
With this information, Joel can then hopefully work out why no report is appearing in the Eraser log. Only then will we know for sure whether there's a bug in Eraser.

David
Click to expand...

David, I already given all-all-all necessary info.

"Undeletable" file/folder - hsperfdata_yur. This file is created by java-applications. It can't be deleted in normal way - by Explorer or any commander-like shell (FAR, TotalCommander etc). It can be deleted if no java application is running or with special software - Unlocker by example (yes, Eraser can delete this file by terminating corresponding apps). So this is normal locked file, not more.
But problem not with this file, problem is with Eraser which can't erase directory with such "undeletable" files.
Below is log of program ProcessMonitor from SystemInternals, which show us the error:
Code: 
0:04:00,3588250	Eraser.exe	2752	QueryNetworkOpenInformationFile	C:\TEMP\History\History.IE5\index.dat	SUCCESS	CreationTime: 21.01.2011 16:29:17, LastAccessTime: 21.01.2011 16:29:17, LastWriteTime: 26.01.2011 14:34:44, ChangeTime: 28.01.2011 0:00:36, AllocationSize: 01.01.1601 2:00:00, EndOfFile: 01.01.1601 2:00:00, FileAttributes: HSANCI
0:04:00,3588364	Eraser.exe	2752	CloseFile	C:\TEMP\History\History.IE5\index.dat	SUCCESS	
0:04:00,3589218	Eraser.exe	2752	CreateFile	C:\TEMP\hsperfdata_yur\2784	SHARING VIOLATION	Desired Access: Generic Read, Disposition: Open, Options: Synchronous IO Non-Alert, Non-Directory File, Attributes: n/a, ShareMode: Read, Write, AllocationSize: n/a
After last exception Eraser simply stop "erasing" and write "completed succefully" in own log instead of skip this file and erase others. Old version of Eraser (3 year old as i remember) was managed this problem, but it not worked under Vista etc.
I have Windows 7 64-bit and working under account with administrative rights.
I run a task in manual, scheduled and context-menu mode.
IMO this information is very sufficient for developers.

P.S. That post - last that I can and want to do for support this app. Sorry, but this thread is really senseless at this moment
 
I understand now what you are saying; I did not, I am afraid, understand it as clearly from what you said in earlier posts. So thank you for the clarification.

If the folder is not unusual, it is difficult to see why Eraser does not discover the lock, attempt (and probably fail) to release it, and place a report to that effect in the log. That is what it does on every occasion I have encountered a problem with file locking. If we were dealing with an obvious bug, it would surely have been discovered and fixed by now.

While I understand your frustration, I urge you not to give up on the case. The issues are complex, and it is often difficult (even for native English speakers) to find unambiguous terms in which to describe them. The problem you have reported seems on the face of it to be genuinely unusual, and in the interest of all users it would be good to get to the bottom of it.

David
 
Perhaps you can try disabling the force unlock feature in the Eraser settings? Save settings before running the task again.
 
You must log in or register to reply here.
Back
Top