Author |
Message |
cata Guest
|
Posted: Thu Jan 03, 2008 2:51 am Post subject: Huge mess |
|
|
Hello,
Trying to see how ViceVersa works for me, I lunched an Backup execution from on filder on on local disk to another folder on another local disk. Surprisingly all the files which contain the character "~"(tilda) in their name create the same problem like:
[The size, attributes or timestamp of "G:\Email Mirror\Signet\ATTACHuntil291102\1MALAD~1" have changed after comparison. For data security reasons this file will be skipped. Press 'Refresh' to recompare Source and Target.] [ERROR].
More there are a lot of messed backuped files: right names different lenth or even completelly different content.
If I oped an copied letter which is supposed to be addressed to Jon I found an invoice or whatever crazzy content.
Why this huge mess? and what about tilda in names?
I am on XP which works very well in general. |
|
Back to top |
|
|
cata Guest
|
Posted: Thu Jan 03, 2008 4:10 am Post subject: Big Mess |
|
|
Well, in fact, not all the files containing tilda given that kind of error but the error when it appears comes only from that kind of file... |
|
Back to top |
|
|
cata Guest
|
Posted: Thu Jan 03, 2008 5:44 am Post subject: Big Mess |
|
|
Is it a bug? It seems so...
Do the next experience using windows file explorer/XP
1) Make a new folder "Source"
2) Make a new folder "Destination"
3) In "Source" folder create a file named "long file name.txt. You may write someting in, not to let it empty.
4)In the same "Source" folder create a file name "longfi~1.txt". Also write something in.
Now try to backup "Source", containing two valid files in "Destination" and you will see it refuses and gives messed alarms.
It seems like ViceVersa checks the time and other sinchronization params based on the SFN converted in its mind on similar rules as Windows. Thus, probably, to check the modifications for the LFN, e.g. for "long file name.txt", in fact it inquires the OS for the guessed SFN "longfi~1.txt". Windows would manage "longfi~2.txt" as the "1" index is already occupied (this is visible in a CMD window after dir /x.) Here it confuses the first file with the second one and drop in the situation to "re-write" the same file.
This scenario is just a guess to explain the huge mess obesrved on my computer.
Am I closer or far? |
|
Back to top |
|
|
TGRMN Software Site Admin
Joined: 10 Jan 2005 Posts: 8763
|
Posted: Thu Jan 03, 2008 12:54 pm Post subject: |
|
|
Yes, ViceVersa is having problems if there is a file with a log file name and a file with a abbreviated path in the same folder. This needs to be fixed in the next release. thanks _________________ --
TGRMN Software Support
http://www.tgrmn.com
http://www.compareandmerge.com |
|
Back to top |
|
|
|
|
You can post new topics in this forum You can reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
Powered by phpBB © phpBB Group
|