#1Submitted by Anonymous on Thu, 07/10/2008 - 07:07.
I'm sure nobody likes programs that do things with your computer you don't know about, and then you see later, surprised that something changed on your computer. We consider that the archive bit method is exactly like that. Here's how this metod works: it unsets the archive bit of each and every file on your computer, when Windows changes a file it will set the archive bit back. Some backup programs use this archive bit to see if a file has changed . We don't like the ideea to have our program go around and make changes to all your files ( too intrusive ), expecially when there are better ways to do this. Also the archive bit method cannot handle exclusively opened files, and those will be copied over and over again since the program cannot set the archive bit. Another problem with this method is that it doesn't check the destination, it always considers that the destination is untouched and everything it copied before should be there ( which is not always the case ).
I'm sorry if my attempt to clear things in the previous post was not received as intended. We do appreciate any feedback, positive or negative, and we thank you for that. We've been reading all posts on this thread. Also we think that it's our resposability to advise when the program isn't used as intended. In this case by "improper use" I meant the user tried to accomplish something using the wrong media type. Based on your comments, we'll give our best to make it easier and easier to use. We'll also write some use-cases scenarios on our Blog, and describe each media type and how it is best used.
I'm sure nobody likes programs that do things with your computer you don't know about, and then you see later, surprised that something changed on your computer. We consider that the archive bit method is exactly like that. Here's how this metod works: it unsets the archive bit of each and every file on your computer, when Windows changes a file it will set the archive bit back. Some backup programs use this archive bit to see if a file has changed . We don't like the ideea to have our program go around and make changes to all your files ( too intrusive ), expecially when there are better ways to do this. Also the archive bit method cannot handle exclusively opened files, and those will be copied over and over again since the program cannot set the archive bit. Another problem with this method is that it doesn't check the destination, it always considers that the destination is untouched and everything it copied before should be there ( which is not always the case ).
I'm sorry if my attempt to clear things in the previous post was not received as intended. We do appreciate any feedback, positive or negative, and we thank you for that. We've been reading all posts on this thread. Also we think that it's our resposability to advise when the program isn't used as intended. In this case by "improper use" I meant the user tried to accomplish something using the wrong media type. Based on your comments, we'll give our best to make it easier and easier to use. We'll also write some use-cases scenarios on our Blog, and describe each media type and how it is best used.
Adrian Gheara
http://www.titanbackup.com