I know about this option, and I also know that showing icons for exe's can be disabled for networks. However, my network is gigabit, so it has no problems at all with this.
The thing is, it's possible to make (very) slow connections in addition to the regular LAN, like a VPN-connection to a DSL-hosted server, or simple the shares on \\tsclient when connection via Remote Desktop. Those connections, and especially the latter one, are usually (very) slow.
So, here it comes: is there a way to disable exe icons for slow networks only, but keep them enabled on fast networks?
If not, is it possible to detect network speed and add this option in a future version?
/edit
I discovered that it *might* be possible to detect \\tsclient going through a Remote Desktop connection. In the "entire network" within windows, this computer is in the "Microsoft Terminal Services" network, while others are in the "Microsoft Windows Network" network. THat might be a way to distinguish one from the other.
No icons for exe/lnk, but only for *slow* networks
Moderators: Hacker, petermad, Stefan2, white
- ghisler(Author)
- Site Admin
- Posts: 50937
- Joined: 2003-02-04, 09:46 UTC
- Location: Switzerland
- Contact:
No, unfortunately not, sorry.is there a way to disable exe icons for slow networks only, but keep them enabled on fast networks?
Author of Total Commander
https://www.ghisler.com
https://www.ghisler.com
- ghisler(Author)
- Site Admin
- Posts: 50937
- Joined: 2003-02-04, 09:46 UTC
- Location: Switzerland
- Contact:
The question is how should TC distinguish between slow and fast networks?
Author of Total Commander
https://www.ghisler.com
https://www.ghisler.com
Good question...
Maybe it can look at the network provider. Terminal services is usually slow, but okay, not nearly always. You could also look at the connection speed of the connecting interface for a certain computer, but again, it could just say "100Mbps" even though the actual bandwidth is much lower. Maybe you could do a simple ping and determine that anything above, say, 50ms is "slow", but then again not every host can be pinged (like tsclient).
It really is a good question
Maybe it can look at the network provider. Terminal services is usually slow, but okay, not nearly always. You could also look at the connection speed of the connecting interface for a certain computer, but again, it could just say "100Mbps" even though the actual bandwidth is much lower. Maybe you could do a simple ping and determine that anything above, say, 50ms is "slow", but then again not every host can be pinged (like tsclient).
It really is a good question

2ghisler(Author)
http://blog.speedproject.de/2005/01/06/langsame-laufwerke/
You can find some useful thoughts on this here:The question is how should TC distinguish between slow and fast networks?
http://blog.speedproject.de/2005/01/06/langsame-laufwerke/
- ghisler(Author)
- Site Admin
- Posts: 50937
- Joined: 2003-02-04, 09:46 UTC
- Location: Switzerland
- Contact: