I just installed the 64 bit version on my machine and the UI did not
come up in the language I choose. I had a look in the documentation
and there is was stated that the reg keys are place in
I look there, found nothing, search the registry and found the keys at
After I copied the keys to the "32-bit" location, gwyddion finally
started in the right language.
So it seems that the 64 bit version write the keys into a
different location than it try to read them from.
Can anyone confirm this?
I don't have Win64 to verify this. But the problem appears to be that the Win64 installer is a 32bit program itself. The "Wow6232Node" thing is in fact a separate registry subtree for 32bit programs
where their registry keys are `redirected'. What you call "32-bit location" is the normal (64bit) location.
It seems fixable in the installer:
Yes, i was wrong about the labeling of the locations.
If you have time to fix this and are in need of an guinea pig with a 64 bit system, feel free to contact me.
I've rebuilt the today's development snapshot with an installer fix, fetch it at
It will say it's 2.31 (instead of 2.31.20130904), ignore that.
Moreover, if the fix works it will not detect your existing installation if it has the registry keys under Wow6432Node because it will look only for the correct keys. But if you copied/moved them all it should find the keys and offer the previously selected language.
The creation of the keys seems to be working, but this version is not running in my maschine (libgcc_s_seh1-1.dll missing).
The language detection works the ways you describe. The only thing is that the installer does not recognize the old version (but perhaps this is normal) and does not suggest to uninstall it, like it normally would. But this is a minor issue.
Hm, there was a toolchain change affecting only the 64bit version. It needs to pack a slightly different set of DLLs. Hopefully I corrected that. Please try tomorrow's development snapshot (with build date 2013-09-05).
I was wrong about the detection of already installed version. It requires some info in HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall which you probably didn't move from Wow6432Node to the correct place. While I could try to make the installer look into both the right and wrong locations in the registry this is rather error prone. So I'll probably won't try to handle this.
This one is working fine! Thanks!
I agree that the detection of an "old" 64-bit version is not so important.
But I have a minor suggestion:
At the moment the 64 bit version wants to install to "C:\Program Files (x86)" by default, and not "C:\Program Files" as a 64 bit program "should". If you have the 32 bit version installed, it will not detect this and will overwrite this version.
If you could change the default path (again something that stems from the 32-bit installer??) and perhaps also rename the link for the start menu to something like "Gywddion (64-bit)", one could have the two version side by side without any conflict.
Not that this is absolutely necessary, but I do not see any disadvantage.
Thanks for your great work, by the way :-))
I rebuilt today's development snapshot again, please try. It should use the correct installation directories. The link now includes "(32bit)" or "(64bit)" though I'm not sure how welcome this will be generally...
When the 32 bit version is already installed, it still suggests "C:\Program Files (x86)" as default, otherwise it works.
I don't know why this happens since each should take the path from own set of registry keys. Also you may have some stray entries in the registry after all the experimentation. I'll probably leave it as it is for now...
I look carefully for any "gwyddion" entries.
But I agree, it is really not that important.
Log in to post a comment.