+1 "do folder in /A:D *" results in "Usage : DO [n | FOREVER]" A lot of my scripts are hitting this as well. Like others have said, removing the /A:D fixes the error. I can change my scripts to do a attribute check inside the loop for now, like @thedave mentions.

I sent you some credentials in email. It doesn't seem to be related to any 260 character limits. I've tried various folders on both sides, but it also happens just going from the root of my SFTP server to the root on my local C drive. Anyway, hope that helps.

I looked into this some more and am finding the crash occurs when a directory contains a file name with 100 characters or longer. I did some tests doing a simple copy * from a sftp folder to my local machine. 99 character file names copy fine, but 100 character file names crash TCC. I don't...

By exiting quickly, I mean there is no crash dialog or anything that pops up (I've seen this in the past with 32-bit 4NT). The TCC console window just vanishes. As for the line of output, it is coming from an OutputDebugString call from within the TCC process and not from the debugger...

Running TCC 12.01.44 x64 Windows 7 [Version 6.1.7601] I'm doing the following... iftp sftp://user:[email protected]/ move /hz /s /e "sftp:/folder/*" C:\Drop\ TCC quickly exits with no error. I ran it under the debugger, and saw this in the log. The first line looks like it comes from...