Progress:

1. After I updated and retested the cwRsync version running on XP, it reproduced the problem I saw when I ran the current version of cwRsync on Vista. So, the updated versions introduced changes, even though I was using only very simple commands, and the problem I encountered wasn't Vista vs. XP after all. I apologize for overlooking this possibility.

2. Among other things, the newer versions require a different way of writing Windows paths - colons and backslashes cause problems with rsync. The standard example is to replace C:\WORK\* with /cygdrive/c/work/*. It's in the batch file template that comes with the current download - a very useful resource. There are still issues I'm testing (e.g., dealing with permissions), but I just want to get things working on Vista.

Related question: When using FTP, has anybody noticed any differences after moving from XP to Vista?

Thanks.

-Andy


Andy Gallant wrote:

I'm having trouble using cwRsync (from itefix) on Vista to keep local copies of some remote directories. The files are out there, but I can't write them to my local drives. The same commands used to work on XP. I've Googled, checked itefix, and tried a few things, but so far I've failed. My knowledge of both cwRsync and Vista is limited - I'm probably doing something stupid or not doing something obvious. Any suggestions? Has anyone out there gotten this to work?

Problem summary: (1) cwRsync works without a local destination: just using the remote source provides a list of the remote files, as it should. (2) When I add a local destination "c:\ftp-files\" I get an error: "The source and destination cannot both be remote. rsync error: syntax or usage error (code 1) at main.c(1127) [receiver=3.0.2]"

Config summary:  Vista Home Prem, cwRsync 2.1.3, Norton 360.

TIA.

-Andy



*************************************************************************
**  List info, subscription management, list rules, archives, privacy  **
**  policy, calmness, a member map, and more at http://www.cguys.org/  **
*************************************************************************

Reply via email to