bbarry wrote:
Maybe I am wrong, but I don't think my problems were caused by SyncToy itself.
Nope -- you are not wrong. It is likely a Task Scheduler issue with the way SyncToy via command line works.
I agree, and that begs the question.....is Task Scheduler a program that Microsoft will continue to support, or is it another toy no longer of interest to them.
I'm pleased that Jay's solution worked and I hope that it continues to work.
Me too, and I will be checking it daily for awhile. I think Jay and I have both concluded that SyncToy just needed time to properly close out via either the pause or the timeout command.
And, finally, yes the forum is a graveyard of unanswered questions from SyncToy users as I imagine that the developers of the program have long since moved on to other things and just don't have time to visit the forum for their ancient baby.
I like your graveyard description. But I hate that Microsoft threw the baby out with the bathwater. IMHO, SyncToy is a good tool. Thanks again for staying with me on this issue.
-steve
