reducing waiting time on locked files
Moderators: white, Hacker, petermad, Stefan2
reducing waiting time on locked files
Hello.
When i try to delete or move or something on a locked file, TC hangs for a while and after some time display "Skip, retry....." box.
Is there a way to reduce this waiting time, i.e. if the operation cannot be performed, the box to show up after a second or two.
I guess that this can be windows, not TC issue, but anyway some solution is welcome.
When i try to delete or move or something on a locked file, TC hangs for a while and after some time display "Skip, retry....." box.
Is there a way to reduce this waiting time, i.e. if the operation cannot be performed, the box to show up after a second or two.
I guess that this can be windows, not TC issue, but anyway some solution is welcome.
As you guessed in your post: It is Windows related and no, sorry, it can't be helped. As workaround you may use a second instance of TC.
sheepdog
sheepdog
"A common mistake that people make when trying to design something
completely foolproof is to underestimate the ingenuity of complete fools."
Douglas Adams
completely foolproof is to underestimate the ingenuity of complete fools."
Douglas Adams
- majkinetor
- Senior Member
- Posts: 369
- Joined: 2005-11-20, 10:36 UTC
- Location: Belgrade, Serbia
- Contact:
German thread:
http://www.ghisler.ch/board/viewtopic.php?t=4451
ghisler said that he tries to delete first via recycle bin and if this fails he tries to delete directly, this means that the waiting time doubles:
In Explorer it is five seconds, in TC it is 10 seconds.
He has shown no interest to fix that, resp. he has told something about that some drives don't work with recycle bin and that's why needs to do it both way.
It still sucks, I agree.
Workaround is to use Explorer deletion method which is way faster anyway but also very dangerous if you are working with junctions and it doesn't support descript.ion files of course.
Icfu
http://www.ghisler.ch/board/viewtopic.php?t=4451
ghisler said that he tries to delete first via recycle bin and if this fails he tries to delete directly, this means that the waiting time doubles:
In Explorer it is five seconds, in TC it is 10 seconds.
He has shown no interest to fix that, resp. he has told something about that some drives don't work with recycle bin and that's why needs to do it both way.
It still sucks, I agree.
Workaround is to use Explorer deletion method which is way faster anyway but also very dangerous if you are working with junctions and it doesn't support descript.ion files of course.
Icfu
This account is for sale
- majkinetor
- Senior Member
- Posts: 369
- Joined: 2005-11-20, 10:36 UTC
- Location: Belgrade, Serbia
- Contact:
@ Sheepdog
It certanly can be fixed, like anything else in the world.
On my machine unlocker can instantly say if file is locked or not. Also other utilities, like console tool handle by SysInternals can show you locked file in a realtime. Procedure like this (pseudocode)
if FileLocked(file) then Unlock(file)
delete(file)
can be implemented... I can do this in batch faster then TC with handle.exe. Something like
will do the trick faster then TC
So.. Ghisler just think it is not so big problem. I found this pattern in his behavior.
It certanly can be fixed, like anything else in the world.
On my machine unlocker can instantly say if file is locked or not. Also other utilities, like console tool handle by SysInternals can show you locked file in a realtime. Procedure like this (pseudocode)
if FileLocked(file) then Unlock(file)
delete(file)
can be implemented... I can do this in batch faster then TC with handle.exe. Something like
Code: Select all
set FNAME=%1
handle "%FNAME%"| find "%FNAME%"
if ERRORLEVEL 0 handle -close %FNAME%
del %FNAME%
So.. Ghisler just think it is not so big problem. I found this pattern in his behavior.