Page 1 of 1
Problem Editing tag.dat
Posted: 15 May 2012 19:27
by Steel
Hello,
I moved several tagged files to another disk (F-->Z) and than had to change that disk letter (Z-->X).
The tagged files don't have the tags anymore: is this because of the disk letter change?
The tags are still present in the tag.dat file pointing to the old location meaning that even the move to the new disk (Z) had not been registered.
Anyway I wished to manually point the tags to the new location but for as many times I edit the file it still reverts to the old location: what am I doing wrong?
Thank you
Re: Problem Editing tag.dat
Posted: 15 May 2012 19:42
by highend
When does the file revert, after restarting XYplorer, or in between?
Tried to quit XY and then edit that file?
Re: Problem Editing tag.dat
Posted: 15 May 2012 20:42
by Steel
highend wrote:When does the file revert, after restarting XYplorer, or in between?
Tried to quit XY and then edit that file?
I did close XY before doing the editing but I was too quick to act as XY was probably still in memory thus preventing a real edit of the file.
It has worked now.
Any idea why the tags were lost and did not register the moving to another disk?
I want to prevent this from happening again.
Thanks
Re: Problem Editing tag.dat
Posted: 16 May 2012 01:18
by PeterH
Steel wrote:highend wrote:When does the file revert, after restarting XYplorer, or in between?
Tried to quit XY and then edit that file?
I did close XY before doing the editing but I was too quick to act as XY was probably still in memory thus preventing a real edit of the file.
It has worked now.
Any idea why the tags were lost and did not register the moving to another disk?
I want to prevent this from happening again.
Thanks
Now you talk about moving - but in the beginning you said you changed the drive letter.
I think that's quite a different thing, isn't it?
Re: Problem Editing tag.dat
Posted: 16 May 2012 01:42
by Steel
PeterH wrote:Steel wrote:highend wrote:When does the file revert, after restarting XYplorer, or in between?
Tried to quit XY and then edit that file?
I did close XY before doing the editing but I was too quick to act as XY was probably still in memory thus preventing a real edit of the file.
It has worked now.
Any idea why the tags were lost and did not register the moving to another disk?
I want to prevent this from happening again.
Thanks
Now you talk about moving - but in the beginning you said you changed the drive letter.
I think that's quite a different thing, isn't it?
I think I explained clearly how I proceeded in my first post: I moved files from F to Z than, few days later, I changed Z to X.
Even if changing a drive letter interferes with tags (and I am asking confirmation of this) tags should still have registered the move from F to Z while in the tag.dat database they are all still pointing to F.
Re: Problem Editing tag.dat
Posted: 16 May 2012 08:20
by admin
Moving items within XY preserves the tags.
Changing a drive letter (which you cannot do within XY) does not.
Tip: To manually edit tags.dat open it from Configuration / Tags / Advanced Options / Edit Tagged Items...
Re: Problem Editing tag.dat
Posted: 16 May 2012 10:02
by PeterH
admin wrote:Changing a drive letter (which you cannot do within XY) does not.
That's what I expected.
admin wrote:Moving items within XY preserves the tags.
Steel wrote:
Even if changing a drive letter interferes with tags (and I am asking confirmation of this) tags should still have registered the move from F to Z while in the tag.dat database they are all still pointing to F.
I think Steel says that "moving" tags with moving files didn't happen, too?
(But maybe he looked into tag.dat before saving, i.e. by ending XY?)
Re: Problem Editing tag.dat
Posted: 16 May 2012 10:18
by highend
Changing a drive letter (which you cannot do within XY) does not
Sure you can *grin* Ok, it requires a bit of "external" work, but at least you can do it from within XY...
http://www.xyplorer.com/xyfc/viewtopic.php?f=7&t=6860
Re: Problem Editing tag.dat
Posted: 16 May 2012 13:29
by TheQwerty
admin wrote:Changing a drive letter (which you cannot do within XY) does not.
I've wondered if it would make more sense to replace drive letters with the volume's serial number when available in tags.dat?
That's one of those extremely nice options in
SyncBack to avoid the headaches of external backup drives being assigned different letters, along with identifying drives by label.

- SyncBack Alternatives.png (4.88 KiB) Viewed 3557 times
Re: Problem Editing tag.dat
Posted: 16 May 2012 15:08
by calude
TheQwerty wrote:admin wrote:Changing a drive letter (which you cannot do within XY) does not.
I've wondered if it would make more sense to replace drive letters with the volume's serial number when available in tags.dat?
That's one of those extremely nice options in
SyncBack to avoid the headaches of external backup drives being assigned different letters, along with identifying drives by label.
SyncBack Alternatives.png
yeah last time I proposed this it went unnoticed so yesssss
Calude
Re: Problem Editing tag.dat
Posted: 16 May 2012 15:14
by Steel
PeterH wrote:admin wrote:Changing a drive letter (which you cannot do within XY) does not.
That's what I expected.
admin wrote:Moving items within XY preserves the tags.
Steel wrote:
Even if changing a drive letter interferes with tags (and I am asking confirmation of this) tags should still have registered the move from F to Z while in the tag.dat database they are all still pointing to F.
I think Steel says that "moving" tags with moving files didn't happen, too?
(But maybe he looked into tag.dat before saving, i.e. by ending XY?)
Yes I meant that even if tags are not preserved with a drive letter's change my tags should have been updated with the move (F to Z) and than lost with the drive letter's change (Z to X).
So I expected the F drive tags to at least point to Z.
It doesn't change that even if they pointed to Z I still had to update them manually but I just wish to understand how the tagging process works.
It might also well be that I did something wrong since I had 2 drive failures in a very short time so it was a constant moving of files.
Thanks for all the tips.