Geosetter Error since beyond Exif 12,57

Started by daveextreme2, July 27, 2024, 06:00:03 AM

Previous topic - Next topic

daveextreme2


Error in Geosetter- "could not find .... exiGeoSetter_beta\tools\ftool_files\perl5*.dll"

Ref. https://geosetter.de/mantis/view.php?id=2547
Ref. https://www.geosetter.de/mantis/view.php?id=2548

There has been no clear description as to how to solve the issue thus far. From what I can gather from the amalgamating the various forum posts the solution so far is to download Windows 32-bit: exiftool-12.92_32.zip (10.8 MB) or 64-bit: exiftool-12.92_64.zip (10.6 MB) and unzip then copy the entire exiftool-12.92_64 or exiftool-12.92_34 folder and its subfolders into C:\Users\Username\AppData\Roaming\GeoSetter_beta\tools. The extracted zip is something like exiftool-12.92_64\exiftool-12.92_64\etc or exiftool-12.92_34\exiftool-12.92_64\etc so I copied just the exiftool-12.92_64\etc part or exiftool-12.92_64\etc part so we only have one exiftool-12.92_64 or exiftool-12.92_32 folder in C:\Users\Username\AppData\Roaming\GeoSetter_beta\tools so the folder structure is C:\Users\Username\AppData\Roaming\GeoSetter_beta\tools\exiftool-12.92_64\etc or C:\Users\Username\AppData\Roaming\GeoSetter_beta\tools\exiftool-12.92_32\etc (hope all that makes sense just trying to make it as clear as possible). Once this is done then this solves the error, and the GPS Coordinates Exif data is inserted into each image file.

BUT now when Geosetter Beta and I guess it to be the same for the non-beta encourages me to install the latest version but trying to do this results in no update, so I get prompted each and every time to update stating "you current version of ExifTool is 12.57.

Looking in C:\Program Files (x86)\GeoSetter beta\tools (yes, another tools folder to add to confusion), there are files .ExifTool_config, consoleStartHelper and exiftool.exe, if I look in the properties for exiftool.exe it states in the details tab that I am using file version 12.57.0. Unfortunately, Geosetter is a Project that Friedemann Schmidt is no longer running so we are left to fend for ourselves or try this forum for a solution. I am unable to use the Geosetter Forum I guess because the project is now no longer running. Reference is made at the beginning to this forum.

obetz

your private mail told me you got an error "Can't locate strict.pm". It's not completely clear to me what you did and what happened when.

As I wrote before, "exitool.exe" and the "exiftool_files" folder with all subfolders needs to be in the folder where Geosetter expects ExifTool. You should not put the exiftool-12.92_64 or exiftool-12.92_34 folder there but it's contents.

If there is more than one folder searched by Geosetter, make sure to have ExifTool only in one of these folders.

Also check whether another ExifTool installation is in the PATH. If so, Geosetter will use this and you don't need another installation for Geosetter.

@Phil: I'm not sure whether the additional folder in your ZIP file makes it more complicate for users to use the new package. Maybe it's better to put exiftool.exe and exiftool_files in the root of the ZIP file.

Phil Harvey

Quote from: obetz on July 27, 2024, 06:35:29 AM@Phil: I'm not sure whether the additional folder in your ZIP file makes it more complicate for users to use the new package. Maybe it's better to put exiftool.exe and exiftool_files in the root of the ZIP file.

I'm not strongly against this if other people would like it this way.  My concern is that people may unzip into a directory with other files a not notice the other files that were extracted.  (The readme and exiftool_files.)

- Phil
...where DIR is the name of a directory/folder containing the images.  On Mac/Linux/PowerShell, use single quotes (') instead of double quotes (") around arguments containing a dollar sign ($).

obetz

Quote from: Phil Harvey on July 27, 2024, 01:37:06 PMMy concern is that people may unzip into a directory with other files a not notice the other files that were extracted.  (The readme and exiftool_files.)

It depends on how people unzip the file. The "extract" option of Windows Explorer offers as default a directory with the name of the ZIP file. So if the user doesn't change the default, he creates a exiftool-12.xx_64 directory containing another exiftool-12.xx_64 directory.

7-Zip offers "unzip to exiftool-12.xx_64" and "unzip here" (not sure whether the English text is correct). Maybe 7-Zip users are aware that "unzip here" can cause a mess.

In addition to remove one level, you could also rename README.txt to ExifTool_README.txt to make clear where it belongs to.

Oliver

FrankB

@Phil and @Olliver

I'm not really in favor for a specific method, there are arguments pro and contra. I do have 2 considerations:

- If you feel it should change, dont wait to long. The longer you wait the more people get used to the current format.
- I would like a sort of an announcement when it will change, so it will not come as a surprise.

And I'll be happy to help out, if you think I can contribute. Currently the ExifToolGui installer can check the current and available versions, optionally download, unzip, install and add it to the PATH.

Frank

Phil Harvey

I'm inclined just to leave it.  I think most of the confusion is just because the package changed.  Once people get used to the new format I think things will go more smoothly.

- Phil
...where DIR is the name of a directory/folder containing the images.  On Mac/Linux/PowerShell, use single quotes (') instead of double quotes (") around arguments containing a dollar sign ($).

daveextreme2

#6
Ignore the private email I don't get the "Can't locate strict.pm" error anymore. I would just concentrate on the first of my post in this forum now. Geosetter has the ExifTool Folder set as C:\Users\Username\AppData\Roaming\GeoSetter_beta\tools, I have pasted just the "exiftool_files" in tools now but still Geostetter constantly want me to update to the latest version.

Please read this in connjunction with my original post. Also why don't I get any notification when I get a reply to my posts?

https://1drv.ms/i/c/022025c16d1696e2/Efgk_qtbnCVFlvsr8QIrOSoBBqFCHMzA9PYvdJP2Mc6ndg?e=VYYLb0

Phil Harvey

From this post:

Quote from: ET on July 15, 2024, 08:58:18 PMAh ok, sorted, nice work guys!
I wasn't copying files to AppData dir.

Previously, I just dropped exe into the Program Files (x86)\Geosetter\tools dir and everything worked.
When I did that this time, the exiftool perl launcher copied itself to AppData\Roaming\GeoSetter\tools but without the additional exiftool_files folder. Once I moved the exiftool_files folder over, it worked.

Program Files (x86)\Geosetter\tools folder doesn't seem to be used by Geosetter at all any more, as the program runs fine without it.

Perhaps previously the self-extracting version worked because extracted temp files would be found in the path. This new install procedure needs files in the right spot (or added to path variable I suppose). In any case, I hope this post helps some other noob out with the changes in 12.88 and newer versions of exiftool.

For info to others, the 64 bit exiftool files work fine with the 32 bit Geosetter program (running on a 64 bit OS).

- Phil
...where DIR is the name of a directory/folder containing the images.  On Mac/Linux/PowerShell, use single quotes (') instead of double quotes (") around arguments containing a dollar sign ($).

daveextreme2

I still have problems where I can't update through GeoSetter Beta and it says I am still running from Exif 12.57. When I do try and update then a whole load of files are put in C:\Users\Username\AppData\Roaming\GeoSetter_beta\tools and it continues to tell me I am running Exif 12.57.

Phil Harvey

Quote from: daveextreme2 on July 31, 2024, 07:47:56 AMI can't update through GeoSetter Beta

This sounds like you are using a GeoSetter update feature.  This certainly won't work with the new ExifTool packaging.  You must move the files yourself to the proper directory.  And delete the old version and the ExifTool files in the TEMP directory.  Here is a description of how to delete the temporary files:

Drag the directory "par-XXX" from your temporary directory to the Recycle bin. Here "XXX" is your user name (in ASCII-hex for ExifTool 10.21 or later) and the location of the temporary directory depends on the value of the TEMP environment variable (typically "C:\Documents and Settings\USER\Local Settings\Temp" for Windows XP, or "C:\Users\USER\AppData\Local\Temp" for Windows 7 or later). Alternately, this (rather dangerous) command may be used to delete these files:

for /D %d in (%TEMP%\par-*) do rmdir /s /q %d


- Phil
...where DIR is the name of a directory/folder containing the images.  On Mac/Linux/PowerShell, use single quotes (') instead of double quotes (") around arguments containing a dollar sign ($).

daveextreme2

#10
I have deleted "par-XXX" and GeoSetter still thinks I need to update.
Screenshot 2024-07-31 112725.png
Screenshot 2024-07-31 132152.png



Phil Harvey

I'll state the obvious:  If it thinks you need to update then the old version still exists.  Find it and replace it with the new version and the exiftool_files directory.

- Phil
...where DIR is the name of a directory/folder containing the images.  On Mac/Linux/PowerShell, use single quotes (') instead of double quotes (") around arguments containing a dollar sign ($).

daveextreme2

I have emptied
C:\Users\Username\AppData\Roaming\GeoSetter_beta\tools (apart from the recently place "exiftool_file" folder)and
C:\Program Files (x86)\GeoSetter beta\tools
and GeoSetter still wants me to update. I don't know what else to delete.

Phil Harvey

C:\Users\Username\AppData\Roaming\GeoSetter_beta\tools should also contain the new "exiftool.exe"

- Phil
...where DIR is the name of a directory/folder containing the images.  On Mac/Linux/PowerShell, use single quotes (') instead of double quotes (") around arguments containing a dollar sign ($).

daveextreme2

#14
It does have it.
Screenshot 2024-07-31 141426.png