Exiftool not working on Win 7

[Archive]

[Originally posted by abramley on 2009-11-07 00:39:32-08]

Ok - bed now.

I've updated to v 7.99 and I've not noticed any difference.  Dragging XMLs onto the batch still results in Exiftool running the help line - the only difference being that because I've not authed the new version to run as admin it now asks me if I want to do so.  Thanks for your persistance - I'll be back in the morning!  Adam

[Archive]

[Originally posted by exiftool on 2009-11-07 11:22:46-08]

Hi Adam,

I hope you had a good sleep.  I did.

Please let me know if you have any lenses that exiftool does not
yet support and I will add them to the list.  Otherwise, if there are
ambiguous lenses and you are just tuning exiftool to select the
proper lens, you can do this with any version of exiftool by adding
user-defined lenses to the config file.  See the
sample
config file for details.  The user-defined lens example is
near the bottom of the page.  This feature was added in version
7.50, so it would have also worked with your old exiftool.

If the user-defined lenses don't do exactly what you want, you can
may still be able to play with Minolta.pm with the Windows exe version.
When you run the exe version for the first time it unpacks the Perl
source code into your temporary directory and runs it from there.
So you should be able to just edit Minolta.pm in the temporary
directory.  With a normal XP system the temporary directory is
"C:\Documents and Settings\USER\Temp\par-USER", but I don't know where
it would be in Windows 7.  (If you find out, please let me know.)

I think trying the Windows executable would be a good idea
because that should eliminate any potential problems with the Perl
installation.

- Phil

[Archive]

[Originally posted by bogdan on 2009-11-07 12:24:42-08]

Hi,

Just jumping here-in (for where's Exiftool's temp files on Win7 64-bit)... It's inside:

c:\Users\YourName\AppData\Local\Temp\par-YourName

Sidenote: From my expirience, Exiftool (Win-executable) works on Win7 64-bit as expected.

Greetings,

Bogdan

[Archive]

[Originally posted by wyant on 2009-11-07 14:08:21-08]

Yes, this is an interruption to the way this troubleshooting session is going, but:

When you are running the Perl file, are you doing

Code:

perl c:\exiftool\exiftool.pl

?

Or are you just doing

Code:

c:\exiftool\exiftool.pl

, and letting the file type association figure out to run Perl? In the latter case, you do not get at least some features of the shell -- redirection for sure, and maybe command line arguments as well. At least, this is true under XP. I haven't touched Windows since Vista came out, so can't tell about more recent versions, but this was a "feature" of earlier versions of Windows.

So if at some point it seems desirable to run exiftool.pl rather than exiftool.exe, this might be a thing to try.

[Archive]

[Originally posted by abramley on 2009-11-07 14:58:48-08]

Hi!

I've cleared my machine of perl and the perl version of exiftool and I've replaced everything with the latest .exe.  When I drag an XMP onto the .exe it correctly displays the exif of the file.  I now need help making the exe do what I want it to!

I've started off by simply replacing the reference to exiftool.pl with exiftool.exe in my bat file - I get the error that 'C:\exiftool\exiftool is not recognised as a valid executable or batch file'.  Is the error because the .exe is not being picked up for some reason?  My batch reads like so:

Code:

@echo off
   :begin
   if _%1_==__ goto end
   echo Processing %1...
   C:\exiftool\exiftool(-k).exe -TagsFromFile %%d%%f.arw "-lensId>lens" -ext XMP %1 -overwrite_original -r
pause
   shift
   goto begin
   :end

I have replaced the temp minolta.pm with my custom version - however if this is going to be deleted every time windows decides to clear its temp files then maybe I'll look into the custom file.  Look forwards to getting this one working - thanks again for your continued support!

[Archive]

[Originally posted by exiftool on 2009-11-07 18:00:14-08]

Thanks Bogdan,

I suggest renaming the executable to "exiftool.exe".  The
"(-k)" in the name is for the drag-n-drop feature and
just confuses things when running from the command line.
Once renamed (and in the c:\exiftool\ directory), this
should work with:

Code:

@echo off
   :begin
   if _%1_==__ goto end
   echo Processing %1...
   C:\exiftool\exiftool -TagsFromFile %%d%%f.arw "-lensId>lens" -ext XMP %1 -overwrite_original -r
pause
   shift
   goto begin
   :end

(fingers crossed).

If this doesn't work, then I think we have narrowed it down to a problem
with the batch file.

- Phil

[Archive]

[Originally posted by abramley on 2009-11-07 22:50:10-08]

Fantastic - that seems to have worked!  I'll keep on testing and I'll be back if I discover anything that's not working.  Thanks very much for helping me with this Phil, and thanks also for writing such a great little program - there's a fair few Sony/Minolta users who appreciate your work.  Enjoy your weekend!  Adam

[Archive]

[Originally posted by exiftool on 2009-11-08 11:16:00-08]

Excellent!!

Now that we have it working I will make a suggestion.
Your batch file can be simplified and made more efficient
by processing all images with a single call to exiftool:

Code:

@echo off
   C:\exiftool\exiftool -TagsFromFile %%d%%f.arw "-lensId>lens" -ext XMP %* -overwrite_original -r
pause

The "%*" represents all arguments passed to the batch file,
instead of processing them one at a time with "%1" and "shift".

- Phil

[Archive]

[Originally posted by abramley on 2009-11-09 14:53:18-08]

Great stuff - that little update also works fine - just had to put .exe on the end of the path.

Thanks once more for your help - I'll pass my experience onto the folks at Dyxum too.  Even after Adobe supported abbreviated lens IDs in LR 2.5, many people still seem to be using exiftool.