I regularly compare a local folder structure on my company supplied laptop with a backup structure on my desktop accessed via a network share - e.g. Net Use X: \\DeskTopPC\C$ then compare C:\MyStuff with X:\MyStuff. Most of the time the subsequent copies of new/changed files in selected folders proceed without any problem but about one in ten times a copy operation hangs. Whenever this happens, the hang is unrecoverable and whilst I can continue to use other applications on the laptop, I can't shut it down gracefully even if I "force" BC3 to be killed during the Windows 7 shutdown. It does not matter how long I wait, the system never shuts down until I hit the OFF switch.
I can't determine any pattern and it is not Windows 7 specific. The same thing used to happen on XP on a previous (corporate) laptop. Sadly, it's not reliably repeatable. Typically the same copy, when restarted after a hard stop and restart, completes without a hiccup. If it's any help, the pattern seems to be...
On checking the desktop, the stalled XYZ file copy is invariably complete which suggests that the stall is not really a stall at all. The real annoyance, of course, is the need to do a hard restart. I didn't think applications were able to cause that to happen under Windows 7. (BTW, using Process Explorer to kill BC3 doesn't help. Still needs a hard restart.)
Regards, AB
I can't determine any pattern and it is not Windows 7 specific. The same thing used to happen on XP on a previous (corporate) laptop. Sadly, it's not reliably repeatable. Typically the same copy, when restarted after a hard stop and restart, completes without a hiccup. If it's any help, the pattern seems to be...
- Compare then select a folder, or folders, with new/changed files.
- Click the button to copy to other side.
- Files start to copy but operation stalls on file XYZ, apparently part way through.
On checking the desktop, the stalled XYZ file copy is invariably complete which suggests that the stall is not really a stall at all. The real annoyance, of course, is the need to do a hard restart. I didn't think applications were able to cause that to happen under Windows 7. (BTW, using Process Explorer to kill BC3 doesn't help. Still needs a hard restart.)
Regards, AB
Comment