I was disappointed by Windows! Example: When I try to read..

[majkinetor]

Hmm, in this thread - http://ghisler.ch/board/viewtopic.php?t=3051 , Christian is quoted as saying,
"...I was disappointed by Windows! Example: When I try to read a directory from a server on the net which has crashed, this will hang not only the current thread, but also all other threads of the same program which call any directory function, even with local folders - until the hanging connection times out! Yes, I tried all kinds of things ....

I don't know if this problem is dealt with, but if not :

Why don't you create fast, small application that will access the network and communicate with TC via, lets say some API procedures. It can be memory mapped on TC start to be able to start it fast, and if it block, or any of it's threads, than you just start another clone of it, since, as I know, you can't even KILL application when it is stucked on network (or CD). Or if you can KILL it some way, then you can just restart it and keep up the good work [/quote]

[majkinetor]

I know that some purist will tell me that there is no way they will consider starting 2 apps instead one. But, as my understanding of Win OS goes, I see no other solution to this problem. This thing can be done sophisticately and very transparent. It can be also done for you to switch it of and use original TC Networking engine.

Personaly, I have 2 many frozings because of this thing and because of CD thing that I found any workaround to it very usefull.

[SanskritFritz]

The idea sounds great! I support it.
On the other hand, Christian did not promise us, but he might be willing to implement the Speed Commander method of KillThread, which is working as far we know.

[majkinetor]

KillThread? What is that? Are you sure it is working all the time ? You say speed commander is implemented that way ? What about CD or even better DVD ?

My experience is that when some application hang for the network timeout you can't do anything about it be it TC, Explorer or whatever. You can't close it, kill it or anything (I must admit that I didn't try to kill threads but Ghisler mentioned in original post that it will block all threads for whole application, as I understand). The same is true for CD especially DVD, except timeout is much shorter but on other hand, you get performance of whole PC degraded.

My idea was that even if helper app is hang, and you can't do anything about it, it can't block callling application. You can do all network communication via helper app, and when it block, you just live it to wait it's deadend and start another clone of your helper app.

[SanskritFritz]

KillThread? What is that?

Ok, TerminateThread:
http://ghisler.ch/board/viewtopic.php?p=23273#23273

Are you sure it is working all the time ?

No, because:
http://ghisler.ch/board/viewtopic.php?p=24037#24037
but:
http://ghisler.ch/board/viewtopic.php?p=24464#24464

But if this is not a solution, then I'm afraid your solution is also faulty, if windows really waits with all subsequent calls even across processes.

[majkinetor]

It doesn't. Windows is bad, but it's not so bad.

If I think a little bit more about this thing, I must say that I am very positive that helper app will solve all of TC network problems. I have experienced too many times TC hang on network but some other app is doing fine. Just code the damn thing. And when new Windows arrives which will solve ugly thing, u can just drop it... but we will have some another beast.... Extrapolate. It's a good general idea to have in mind for all other similar isues.

damn... why I don't switch to Linux already.

Oh, I forgot, it's becouse of Fruity Loops.


PS: Maybe, just maybe, you could ask Mark Rusinovich about opinion
He already answered some of mine questions.

[majkinetor]

and you didn't answer my DVD question. I am sure you know what I am talking about. I have seen it on every computer. DVD is bad medium (except DVD-RAM) and it has very long time of TOC access, sometimes I wait whole eternity for it to display damn philes. Not to mention the time to read the file, etc...

[rockballad]

Hmm, in this thread - http://ghisler.ch/board/viewtopic.php?t=3051 , Christian is quoted as saying,
"...I was disappointed by Windows! Example: When I try to read a directory from a server on the net which has crashed, this will hang not only the current thread, but also all other threads of the same program which call any directory function, even with local folders - until the hanging connection times out! Yes, I tried all kinds of things ....

I don't know if this problem is dealt with, but if not :

Why don't you create fast, small application that will access the network and communicate with TC via, lets say some API procedures. It can be memory mapped on TC start to be able to start it fast, and if it block, or any of it's threads, than you just start another clone of it, since, as I know, you can't even KILL application when it is stucked on network (or CD). Or if you can KILL it some way, then you can just restart it and keep up the good work

[/quote]

I agree with him, looking possible. Could you try it, please?

This timeout problem seems to exist too long, is there any solution yet?
http://www.ghisler.ch/board/viewtopic.php?t=3850
http://www.ghisler.ch/board/viewtopic.php?t=6114
http://www.ghisler.ch/board/viewtopic.php?t=8048
... (do searching with 'network timeout')

This problem occurs in daily use, please check it out.

Thanks, and best regards,

[ghisler(Author)]

This has been added as an experimental function to Total Commander 7.

Please add the following line to section [Configuration] in wincmd.ini, and then restart Total Commander:
ThreadFindFirst=1

[rockballad]

Thanks, ghisler! Have a nice weekend!