Bug in v7.73 XPAuthor not visible Win XP.

[Archive]

[Originally posted by charly on 2009-04-03 20:09:17-07]

I don't know where to put this bug I found. So I put it here.

I was using ExifTool v7.71 to update XPAuthor. My coments where always visible in the file propertys.

Afther I upgraded to v7.73 the XPAuthor tag is not visible anymore in windows XP file propertys. It is still visable in ExifTool however.

When downgrading to v7.71 and rewriting the tags, the propertys are availabe in both windows XP and ExifTool.

Commandline in both cases: ExifTool -P -XPAuthor=TestP file.jpg

Note: When I'm not using the -P option writing the XPAuthor tag. The tag is visable in XP no matter which ExifTool version was used.

Ie: Commandline in these cases: ExifTool -XPAuthor=NoP file.jpg

[Archive]

[Originally posted by exiftool on 2009-04-04 00:02:17-07]

If I were to guess, I would say this is because Windows isn't updating
the properties after you write the file.  It could be that Windows is
caching these properties and updates the cache only if the file modification
date changes (which it doesn't with the -P option).

That being said, I can not reproduce your problem with ExifTool 7.73
running in Windows XP (Service pack 2) from a cmd.exe shell.  And I
can't imagine that anything I changed between 7.71 and 7.73 could
possibly affect this.

I am very confident that exiftool is writing the file properly.

Try this test:  Copy the file after exiftool writes XPAuthor, then look
at the properties of the copied file.  I would guess they should be
correct.  Or copy the file to another disk then back again.  There
should be a way to make Windows re-scan the file to get the new
XPAuthor value.

Another possibility is that Windows ignores the XPAuthor tag if
the EXIF Artist tag exists.  However, from what you describe it
sounds like this isn't the problem.

- Phil

[Archive]

[Originally posted by charly on 2009-04-05 14:27:27-07]

Phil,

Your explanation sounds logical. I'll try your suggestions. If I find something odd I'll post again.

No bug, just windows caching.

Thanx!