treelog.txt: Is TC creating it?

[wanderer]

Lately i've noticed a file named treelog.txt in C:\. A sample of its contents:

Code: Select all

----------------------------------------
d - lock failed!!!!!!!!!!!!!!!!!
d - request lock
d - locked
d - request lock
d - lock failed!!!!!!!!!!!!!!!!!
d - request lock
d - locked
d - request lock
d - lock failed!!!!!!!!!!!!!!!!!
d - request lock
d - locked
d - request lock
d - lock failed!!!!!!!!!!!!!!!!!
n - request lock
n - locked
t - request lock
t - locked
s - request lock
s - locked
j - request lock
j - locked
n - request lock
n - locked
t - request lock
t - locked
s - request lock
s - locked
...

Is it created by TC?

[SanskritFritz]

2wanderer
Google treelog.txt: http://support.microsoft.com/kb/245438

[wanderer]

2wanderer
Google treelog.txt: http://support.microsoft.com/kb/245438

Thanks for the info but this is not my case. I thought it might be TC because this file has started appearing the last few months, after i started using TCpb1. Anyway, Christian will certainly know!

[SanskritFritz]

2wanderer
Is the file still changing? Process Explorer can give you a hint, which program has it open. And there is FileMon as well.
I severily doubt, that Christian will grab his hair screaming oh, no! i left some debug info in the TC release!

[wanderer]

2wanderer
Is the file still changing? Process Explorer can give you a hint, which program has it open. And there is FileMon as well.
I severily doubt, that Christian will grab his hair screaming oh, no! i left some debug info in the TC release!

Me too, but you never know. Since there is a "treeinfo.wc" file, why not a "treeinfo.txt"? And after all, TC is still in beta phase so...

Whenever i notice this file, it happens to have a creation date of at least 2-3 hours behind. Apparently it is created under certain circumstances that do not occur very often. When i delete it, it just gets deleted without any delays (so no app has it locked). It is not recreated after a while, not even after i reboot the PC. There is no indication of an application using it. It seems it's created under some circumstances, the app writes some lines in it and then it closes it and that's all.

Anyway...

[petermad]

Since there is a "treeinfo.wc" file, why not a "treeinfo.txt"

I thought it was a treelog.txt file you were talking about?

[wanderer]

Since there is a "treeinfo.wc" file, why not a "treeinfo.txt"

I thought it was a treelog.txt file you were talking about?

Right. My mistake. The power of copy/paste!

[wanderer]

Well, after some research with FileMon, TCpb4 IS creating this file ("c:\treelog.txt").

Code: Select all

14:03:03	TOTALCMD.EXE:2332	OPEN	C:\treelog.txt	SUCCESS	Options: Open  Access: All	
14:03:03	TOTALCMD.EXE:2332	QUERY INFORMATION	C:\treelog.txt	SUCCESS	FileNameInformation	
14:03:03	TOTALCMD.EXE:2332	QUERY INFORMATION	C:\treelog.txt	SUCCESS	FileNameInformation	
14:03:03	TOTALCMD.EXE:2332	DIRECTORY	C:\	SUCCESS	FileBothDirectoryInformation: TREELOG.TXT	
14:03:03	TOTALCMD.EXE:2332	QUERY INFORMATION	C:\treelog.txt	SUCCESS	Length: 4530	
14:03:03	TOTALCMD.EXE:2332	READ 	C:\treelog.txt	SUCCESS	Offset: 4402 Length: 128	
14:03:03	TOTALCMD.EXE:2332	WRITE	C:\treelog.txt	SUCCESS	Offset: 4530 Length: 18	
14:03:03	TOTALCMD.EXE:2332	CLOSE	C:\treelog.txt	SUCCESS		
14:03:03	TOTALCMD.EXE:2332	OPEN	C:\treelog.txt	SUCCESS	Options: Open  Access: All	
14:03:03	TOTALCMD.EXE:2332	QUERY INFORMATION	C:\treelog.txt	SUCCESS	FileNameInformation	
14:03:03	TOTALCMD.EXE:2332	QUERY INFORMATION	C:\treelog.txt	SUCCESS	FileNameInformation	
14:03:03	TOTALCMD.EXE:2332	DIRECTORY	C:\	SUCCESS	FileBothDirectoryInformation: TREELOG.TXT	
14:03:03	TOTALCMD.EXE:2332	QUERY INFORMATION	C:\treelog.txt	SUCCESS	Length: 4548	
14:03:03	TOTALCMD.EXE:2332	READ 	C:\treelog.txt	SUCCESS	Offset: 4420 Length: 128	
14:03:03	TOTALCMD.EXE:2332	WRITE	C:\treelog.txt	SUCCESS	Offset: 4548 Length: 12	
14:03:03	TOTALCMD.EXE:2332	CLOSE	C:\treelog.txt	SUCCESS		
14:03:03	TOTALCMD.EXE:2332	OPEN	C:\treelog.txt	SUCCESS	Options: Open  Access: All	
14:03:03	TOTALCMD.EXE:2332	QUERY INFORMATION	C:\treelog.txt	SUCCESS	FileNameInformation	
14:03:03	TOTALCMD.EXE:2332	QUERY INFORMATION	C:\treelog.txt	SUCCESS	FileNameInformation	
14:03:03	TOTALCMD.EXE:2332	DIRECTORY	C:\	SUCCESS	FileBothDirectoryInformation: TREELOG.TXT	
14:03:03	TOTALCMD.EXE:2332	QUERY INFORMATION	C:\treelog.txt	SUCCESS	Length: 4560	
14:03:03	TOTALCMD.EXE:2332	READ 	C:\treelog.txt	SUCCESS	Offset: 4432 Length: 128	
14:03:03	TOTALCMD.EXE:2332	WRITE	C:\treelog.txt	SUCCESS	Offset: 4560 Length: 18	
14:03:03	TOTALCMD.EXE:2332	CLOSE	C:\treelog.txt	SUCCESS		
14:03:03	TOTALCMD.EXE:2332	OPEN	C:\treelog.txt	SUCCESS	Options: Open  Access: All	
14:03:03	TOTALCMD.EXE:2332	QUERY INFORMATION	C:\treelog.txt	SUCCESS	FileNameInformation	
14:03:03	TOTALCMD.EXE:2332	QUERY INFORMATION	C:\treelog.txt	SUCCESS	FileNameInformation	
14:03:03	TOTALCMD.EXE:2332	DIRECTORY	C:\	SUCCESS	FileBothDirectoryInformation: TREELOG.TXT	
14:03:03	TOTALCMD.EXE:2332	QUERY INFORMATION	C:\treelog.txt	SUCCESS	Length: 4578	

I assume it is a debugging remnant. I hope it will be removed in the final version.

[roentgen]

2wanderer
As I don't see anything like this with my TC I can only suggest:

1. run TC with a fresh wincmd.ini for a while,
2. monitor explorer.exe actions also,
3. check for services and shell extensions other than those that come in Windows by default,
4. compare totalcmd.exe integrity with the original exe found in the installation setup

[Dark-Star]

It's definitely TC itself. These strings can be found inside the TC executable:

Code: Select all

c:\treelog.txt
- request lock
- locked
- request lock
- lock failed!!!!!!!!!!!!!!!!!

Seems like debugging stuff. The question is: Why does it get activated on your system, but not on anyone else's?

[wanderer]

The question is: Why does it get activated on your system, but not on anyone else's?

Good question . It happens randomly. This time i had opened 1 instance of TC at some point, a second instance after about 1 hour and i was working on the second instance in several tabs in both local and network drives. I'm guessing it has something to do with the refresh of the separate tree. I have 1 sep tree always open.

[roentgen]

It's definitely TC itself. These strings can be found inside the TC executable:

Code: Select all

c:\treelog.txt
- request lock
- locked
- request lock
- lock failed!!!!!!!!!!!!!!!!!

Seems like debugging stuff. The question is: Why does it get activated on your system, but not on anyone else's?

I am just wondering... what did you use to find such "strings" in totalcmd.exe? If Lister in Hex view is the answer, then I must say that its hex search algorithms don't look too sane IMO.
On the right side (ASCII view) of the hex view you should see 'treelog.txt', which is not the case, Lister shows 2 garbage characters.

[ZoSTeR]

I am just wondering... what did you use to find such "strings" in totalcmd.exe?

You either have to unpack TC with UPX (or get the unpacked version from the site) or you have to search within the running process (eg with Process Explorer).

[roentgen]

2ZoSTeR
Yes. I have manages to see those strings in Process Explorer. Thanks for the info.

As a side note: the strings are not present in TC 6.56.

[ghisler(Author)]

Indeed this file is created when acessing the separate tree fails, for example because it is locked by a background thread. This can happen when updating the tree takes a very long time. I will remove this debugging function from the next beta.