I have the directory on the remote computer, like \\c1\c$ in the "favourites" (ctrl-d, the "star" menu) and the computer is sometimes off. If I then try to reach it from ctrl-d, I get a delay, then "Connect" dialog. If I press Cancel, the dialog will appear again, if I press cancel, it will appear once more. After third cancel, the TC stops redrawing itself (like without ThreadFindFirst) and once the typical period passes it behaves like before.
I saw ThreadFindFirst mentioned in Beta 4 change log so I just wanted to report that the behaviour haven't changed. Before, I got that behaviour with tabs too. I haven't tried with tabs now but I guess it's still the same.
Still, thanks a lot for a good work.
TC7 b4 ThreadFindFirst issues
Moderators: Hacker, petermad, Stefan2, white
TC7 b4 ThreadFindFirst issues
(user licence #64081)
- ghisler(Author)
- Site Admin
- Posts: 50386
- Joined: 2003-02-04, 09:46 UTC
- Location: Switzerland
- Contact:
Thanks for your detailed report, I will check what the problem is.
Author of Total Commander
https://www.ghisler.com
https://www.ghisler.com
Confirm. I have met such behaviour earlier, but could not find a way to reproduce it...
Flint's Homepage: Full TC Russification Package, VirtualDisk, NTFS Links, NoClose Replacer, and other stuff!
Using TC 11.03 / Win10 x64
Using TC 11.03 / Win10 x64
- sqa_wizard
- Power Member
- Posts: 3893
- Joined: 2003-02-06, 11:41 UTC
- Location: Germany
I have seen it too, but I found that the PC is never really OFF !... and the computer is sometimes off
Well the OS is off for sure, but the network card is still ON, somehow answering to requests (may waiting for the magic packet - Wake Up On LAN)
Maybe this is interpreted as real ON by some functions ?
#5767 Personal license
to anybody who develops or tests:
In case you can't reproduce something related to this bug, I would gladly test any build you'd like me to test for that behaviour, since I can easily reproduce it anytime and on different networks.
to sqa_wizard:
When the card waits for magic packet, it can't (and shouldn't) do anything else than detect the magic packet. AMD has detailed specs since 1995, like this one:
http://www.amd.com/us-en/assets/content_type/white_papers_and_tech_docs/20213.pdf
In case you can't reproduce something related to this bug, I would gladly test any build you'd like me to test for that behaviour, since I can easily reproduce it anytime and on different networks.
to sqa_wizard:
When the card waits for magic packet, it can't (and shouldn't) do anything else than detect the magic packet. AMD has detailed specs since 1995, like this one:
http://www.amd.com/us-en/assets/content_type/white_papers_and_tech_docs/20213.pdf
(user licence #64081)
- ghisler(Author)
- Site Admin
- Posts: 50386
- Joined: 2003-02-04, 09:46 UTC
- Location: Switzerland
- Contact:
I think that I found a solution now.
To the private beta testers: This should be fixed already in the non-public beta, can you confirm that?
To the private beta testers: This should be fixed already in the non-public beta, can you confirm that?
Author of Total Commander
https://www.ghisler.com
https://www.ghisler.com