N
Nick Mirro
I use briefcase over a wireless network and often have to reboot the laptop
to get a valid list of files needing synchronization. Not doing this can
cause incorrect file deletion. At least briefcase warns you that it will do
this. 3rd party "Second Copy" works similarly, but without warning, causing
a serious situation I narrowly escaped. They state that there is a bug in
the Windows xp networking software (as described below). Is this true?
Nick
_______________
We are thankful that a near catastrophe was averted by your use of archive
folders.
This problem was apparently caused due to a bug in the Microsoft Windows
networking software.
When Second Copy (SC) runs a profile that is set to synchronize files, first
it tries to make a connection to the destination computer. If the connection
fails, it logs an error message and quits the profile. If the connection
succeeds then it lists the files in the source and destination folder to
compare and decide which files should be copied.
In your situation, Windows (erroneously) reported to SC that the connection
is successful but there are no files in the destination folder. This tells
SC that the files existed the previous time when they were synched but the
user has since deleted the files from destination. If the "Synchronize file
deletion also" is selected (as seems to be the case with your profile
setup). SC deletes the corresponding files.
The culprit is the Windows networking connection that erroneously reports
that there are no files in the destination folder instead of reporting that
the destination can not be reached. We don't know a solution to this bug in
Windows.
To avoid this in future you can uncheck the "Synchronize file deletion also"
option.
--------------------------------------------
Centered Systems Support
(e-mail address removed)
Winner of People's Choice Award 2000, 2001, 2002, 2004
Best Overall Utility
-------------------------------------------
to get a valid list of files needing synchronization. Not doing this can
cause incorrect file deletion. At least briefcase warns you that it will do
this. 3rd party "Second Copy" works similarly, but without warning, causing
a serious situation I narrowly escaped. They state that there is a bug in
the Windows xp networking software (as described below). Is this true?
Nick
_______________
We are thankful that a near catastrophe was averted by your use of archive
folders.
This problem was apparently caused due to a bug in the Microsoft Windows
networking software.
When Second Copy (SC) runs a profile that is set to synchronize files, first
it tries to make a connection to the destination computer. If the connection
fails, it logs an error message and quits the profile. If the connection
succeeds then it lists the files in the source and destination folder to
compare and decide which files should be copied.
In your situation, Windows (erroneously) reported to SC that the connection
is successful but there are no files in the destination folder. This tells
SC that the files existed the previous time when they were synched but the
user has since deleted the files from destination. If the "Synchronize file
deletion also" is selected (as seems to be the case with your profile
setup). SC deletes the corresponding files.
The culprit is the Windows networking connection that erroneously reports
that there are no files in the destination folder instead of reporting that
the destination can not be reached. We don't know a solution to this bug in
Windows.
To avoid this in future you can uncheck the "Synchronize file deletion also"
option.
--------------------------------------------
Centered Systems Support
(e-mail address removed)
Winner of People's Choice Award 2000, 2001, 2002, 2004
Best Overall Utility
-------------------------------------------