This Must be a Bug ... [SOLVED]

[Cheemag]

Version 7.55a. Windows XP SP2.

If I have the network listed in a pane and I click on a network machine which is inactive/not presently available, TC locks the machine up completely, necessitating a resort to Task Manager to kill the programme. Even this is not 100% effective and it takes a long time to stop TC.

[Cheemag]

Version 7.55a. Windows XP SP2.

If I have the network listed in a pane and I click on a network machine which is inactive/not presently available, TC locks the machine up completely, necessitating a resort to Task Manager to kill the programme. Even this is not 100% effective and it takes a long time to stop TC.

Posted in the wrong forum?

[karlchen]

Hello, Cheemag.

Version 7.55a. Windows XP SP2.

Can be reproduced using the current version of T.C., v7.56, as well. Can be (partially) reproduced on Windows 7 as well.

If I have the network listed in a pane and I click on a network machine which is inactive/not presently available, TC locks the machine up completely, necessitating a resort to Task Manager to kill the programme.

It takes a long time here till T.C. displays that the machine is not available.
Yet, it does not lock up the machine at any time.

Even this is not 100% effective and it takes a long time to stop TC.

Nope. Not reproducible here. Process Hacker terminates T.C. pretty fast.

The delay which you complain about and which I can reproduce occurs whenever we use the Windows network neighborhood inside T.C., navigate to a machine which has been switched off e.g., but which is still listed and double click on it.

In case, however, we enter a command like "cd \\machinename\C$", T.C. will display a dialogue box which will allow us to abort the attempt to contact the machine. No hang, no lockup or similar nuisance in this case.

Personally I tend to assume that the long delay which we see when using the network neighborhood is brought about more by the Windows network neighborhood itself than by T.C. The Windows network neighborhood can be really slow, in particular in large LANs.

So if this must be a bug, then I wonder a bit whose bug it really is ...

Kind regards,
Karl

[Balderstrom]

I can reproduce it for a Drive thats a network drive, and mapped to Z. When that drive isn't available TC freezes whenever I try to go to "\\My Computer\", - granted so does Explorer, but don't we expect more from TC

[ghisler(Author)]

User mode programs like TC cannot lock the entire machine, that would be a big security hole. Only drivers can cause such a lock. I assume that it's caused by a background virus scanner or firewall trying to scan the drive when TC tries to access it.

[Cheemag]

Hello, Cheemag.

Version 7.55a. Windows XP SP2.

Can be reproduced using the current version of T.C., v7.56, as well. Can be (partially) reproduced on Windows 7 as well.

Yes. I have an unregistered copy on a Windows 7 machine. I listed the directories on the XP machine in TC, then disabled net access to the XP machine via ZoneAlarm. Tried looking at a directory on the XP and TC locked up for 40 seconds. Could not be minimised or stopped - system showing it as 'not responding'.

So it would be more correct to say that in these circumstances TC locks itself up, not the system. Recovery via the registered version on the XP machine is much slower however.

It takes a long time here till T.C. displays that the machine is not available. Yet, it does not lock up the machine at any time.

Yes. I concur.

In case, however, we enter a command like "cd \\machinename\C$", T.C. will display a dialogue box which will allow us to abort the attempt to contact the machine. No hang, no lockup or similar nuisance in this case.

Not understood, but a similar delay will be encountered if something like 'dir \\aa\download' is issued from a command prompt when 'aa' is unavailable or '\download' doesn't exist or is not shared.

So if this must be a bug, then I wonder a bit whose bug it really is ...

Quite so! We shall just have to put up with it.

[5h17h34d]

Version 7.55a. Windows XP SP2.

If I have the network listed in a pane and I click on a network machine which is inactive/not presently available, TC locks the machine up completely, necessitating a resort to Task Manager to kill the programme. Even this is not 100% effective and it takes a long time to stop TC.

I reported this same issue, minus the "locks the machine" part. I get the transparent white "not responding" window.

http://ghisler.ch/board/viewtopic.php?p=212725#top

[edit] I reported this issue before 756a was released. Still acts same in new version.

[Cheemag]

Version 7.55a. Windows XP SP2.

If I have the network listed in a pane and I click on a network machine which is inactive/not presently available, TC locks the machine up completely, necessitating a resort to Task Manager to kill the programme. Even this is not 100% effective and it takes a long time to stop TC.

I reported this same issue, minus the "locks the machine" part. I get the transparent white "not responding" window.

http://ghisler.ch/board/viewtopic.php?p=212725#top

[edit] I reported this issue before 756a was released. Still acts same in new version.

It's a Windows problem - the behaviour is the same no matter what application tries to access an unavailable network share.