Without using the batch files, I've done everything you have by hand using fossil 1.19 2011 07 22. When I go back to the server, and write fossil open ops, I correctly get the client1.txt file on the server side. Therefore, it is either a windows XP vs. 7 issue, or a fossil vs. 1.18 vs 1.19 issue.
Please update to 1.19 and try the same script. One other possibility is that there is something related to the shell you are using. Are you running this on powershell or the cmd.exe? Two other confusing pieces to note: D:\client>fossil commit --comment client1 You can see: The first ‘Autosync’ will poll repo from server. Autosync: http://y00122496@y00122496:8080 Bytes Cards Artifacts Deltas Sent: 130 1 0 0 Received: 170 4 0 0 Total network traffic: 321 bytes sent, 345 bytes received New_Version: 11de786c5c9d689c798399f2c37d98f5b5602c89 You can see: The second ‘Autosync’ will push repo to server. Autosync: http://y00122496@y00122496:8080 Bytes Cards Artifacts Deltas Sent: 539 9 0 0 Received: 264 6 0 0 Total network traffic: 459 bytes sent, 397 bytes received First, you can notice that on the push, no artifacts are sent. On my tests, there are two artifacts sent (I imagine it is the manifest and the file). Therefore, it is not surprising that the server never shows the client file. Second, I assume that you have y00122496 defined as 127.0.0.1 in your hosts file somewhere, since you can successfully clone from it. Same question as last time though: have you tried these same commands BY HAND to ensure that the batch file itself isn't the problem? Tomek
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
