Re: Aw: Re: GpgEX for 64 bit Windows test version
On Mon, 15 Jul 2013 19:51, jo...@netpage.dk said: I have the same problem on my german 64bit Windows 8 with Version 2.2.0-beta31 Are you shure that you are using the new version; i.e. did you reboot your machine? Salam-Shalom, Werner -- Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz. ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: Aw: Re: GpgEX for 64 bit Windows test version
On Tue, 16 Jul 2013 10:28, jo...@netpage.dk said: Yes I am sure. I even uninstalled it completely right now, rebooted and then reinstalled! Thanks. Well, there is a problem we need to figure out. Using my Windows versions (no Windows8 here right now), I can't replicate the problem. Thus I build debug versions for Andre who then tested the fix confirmed that the fix is correct. The last step was to remove the debug output and use this updated fix. Something might have gone wrong during the build process - we need to check. Strangely, the gibberish now changed somehow (it is shorter now), but That is expected without the fix. Shalom-Salam, Werner -- Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz. ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: GpgEX for 64 bit Windows test version
On Tue, 16 Jul 2013 12:09, w...@gnupg.org said: remove the debug output and use this updated fix. Something might have gone wrong during the build process - we need to check. We figured out what has gone wrong: The problem affects only the 64 bit version of gpgex. The gpg4win installer uses some extra code to build 64 bit versions of some packages. The build process consists of - unpack the source - apply patches - run configure - run make - stow the results Patches are taken from a patches/PACKAGENAME-VERSION/ directory. For 64 bit the patches are taken from patches/PACKAGENAME-VERSION-ex/ directory. I was not aware of that separate directory and put my fix only into the 32 bit patch directory. Thus the 64 bit version was build without the fix. Given that there is currently no need for separate 64 and 32 bit patches, we will now change this to use only one patch directory. A new Beta version will be released in a few hours. Thanks for beta testing. Salam-Shalom, Werner -- Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz. ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: Aw: Re: GpgEX for 64 bit Windows test version
On Fri, 12 Jul 2013 09:46, fisch@gmx.de said: good point and thanks for this hint. Will try to use the gpg4win-light-2.1.2-beta20.exe and let you know when i still have this Actually there is a bug I am currently fixing. We will release a new beta in a few hours. Shalom-Salam, Werner -- Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz. ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: Aw: Re: GpgEX for 64 bit Windows test version
I have the same problem on my german 64bit Windows 8 with Version 2.2.0-beta31 Mit freundlichen Grüßen, Josef Schneider On Mon, Jul 15, 2013 at 3:02 PM, Werner Koch w...@gnupg.org wrote: On Fri, 12 Jul 2013 09:46, fisch@gmx.de said: good point and thanks for this hint. Will try to use the gpg4win-light-2.1.2-beta20.exe and let you know when i still have this Actually there is a bug I am currently fixing. We will release a new beta in a few hours. ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Aw: Re: GpgEX for 64 bit Windows test version
Hi, That might be the cause for the problem. The translations (*.mo) files from the old installer may not match the newer gettext version as used by gpgex. good point and thanks for this hint. Will try to use the gpg4win-light-2.1.2-beta20.exe and let you know when i still have this problem. Thanks again for your help! ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: GpgEX for 64 bit Windows test version
On Mon, 8 Jul 2013 19:39, fisch@gmx.de said: I've installed gpg4win-2.1.1.exe which fails to register the gpgex and then installed the gpgex from the archive: ftp://ftp.g10code.com/g10code/gpgex/gpgex-1.0.0-beta24-bin.zip That might be the cause for the problem. The translations (*.mo) files from the old installer may not match the newer gettext version as used by gpgex. Shalom-Salam, Werner -- Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz. ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: GpgEX for 64 bit Windows test version
Hi, thanks for your reply. I can' replicate it on my German Windows 7 Home Premium 64 bit (6.01.7600). However, I recall that I noticed such a behaviour during development. My windows version here is 6.1.7601. - Did you just install a gpgex DLL or is that the one from gpg4win-light-2.1.2-beta20.exe ? I've installed gpg4win-2.1.1.exe which fails to register the gpgex and then installed the gpgex from the archive: ftp://ftp.g10code.com/g10code/gpgex/gpgex-1.0.0-beta24-bin.zip with the regsrv32 command as an admin. - What codepage are you using? It is different from the default? I'm using the default codepage Deutsch (Deutschland) of a German win7 installation. - Did you set one of the environment variables: LANG, LC_ALL, or LS_MESSAGES? Just checked my environment variables with SET and none of the above is set. If you need the whole output of SET i can send it to you via a direct e-mail. Thanks Chris ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: GpgEX for 64 bit Windows test version
On Wed, 3 Jul 2013 23:21, fisch@gmx.de said: just want to let you know that using the latest gpgex-1.0.0-beta24 on a german windows 7 professional sp1 64bit system leads to some strange context menus [1]. I can' replicate it on my German Windows 7 Home Premium 64 bit (6.01.7600). However, I recall that I noticed such a behaviour during development. - Did you just install a gpgex DLL or is that the one from gpg4win-light-2.1.2-beta20.exe ? - Anyone else seeing this problem? - What codepage are you using? It is different from the default? - Did you set one of the environment variables: LANG, LC_ALL, or LS_MESSAGES? Shalom-Salam, Werner -- Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz. ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: GpgEX for 64 bit Windows test version
Hi, just want to let you know that using the latest gpgex-1.0.0-beta24 on a german windows 7 professional sp1 64bit system leads to some strange context menus [1]. Using beta19 doesn't translate the context menu to german but the context menu is not broken. [1] http://s1.directupload.net/images/130703/iobbaatv.png ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: GpgEX for 64 bit Windows test version
On Wed, 3 Jul 2013 23:21, fisch@gmx.de said: just want to let you know that using the latest gpgex-1.0.0-beta24 on a german windows 7 professional sp1 64bit system leads to some strange context menus [1]. Thanks. I'll check what is going wrong. Salam-Shalom, Werner -- Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz. ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: GpgEX for 64 bit Windows test version
On Wed, 26 Jun 2013 04:25, markr-gn...@signal100.com said: If you run any 32bit programs at all (i.e. most applications) then the system-supplied file open/save dialogs for those programs with be 32bit and so these will use 32bit Explorer extensions. I was not ware that GpgEX is also used by the open and save dialogs. Just tried it with DbgView and indeed - after registering the 32 bit version of gpgex it works. They currently share the same registry entries - maybe I need to use different ones so that it is possible to load both. -- Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz. ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: GpgEX for 64 bit Windows test version
On Mon, 24 Jun 2013 20:18, old...@oldbob.co.uk said: On my Window 7 64bit system, GnuPG 1.4.13 installed itself in c:\Program Files (x86)\GNU\GnuPG\ - the 32bit section. When I installed Gpg4win, Yep, that is the default on English Windows systems. the installer offered install GPG2 in that same directory, but I added a 2 to keep the two separate, ie. it was installed in That may lead to conflicts with the registry - better don't do it. Two version of Gpg4win are not yet supported. I am working on a portable application feature in GnuPG which will allow that. Program Files directory, not the 32bit. I assumed that I needed to have gpgex.dll along with the other files and installed it in the \bin Actually it doesn't really matter. The plan to put them into bin is merely so that we can easily provide a 32 bit and a 64 bit version of gpgex.dll instead of providing two sets of installers. But even that is not yet set into stone. gpgex.dll should work fine in .../GNU/GnuPG or in .../GNU/GnuPG/bin. regsvr32 c:\Program Files (x86)\GNU\GnuPG2\bin\gpgex.dll it just caused an error, saying The module c:\program failed to load. You have to use quotes around it. The Windows tab completion feature usually does this for you. It might be easier to cd to the directory first and then run just regsvr32 gpgex.dll As I can't run the 32 bit version of GPGex anyway on this system, can I not just overwrite the existing copy of gpgex.dll with the 64 bit one and reboot? Yes, you can. The regsvr32 call is still required. Salam-Shalom, Werner -- Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz. ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: GpgEX for 64 bit Windows test version
On 25/06/2013 12:53 AM, Henry Hertz Hobbit wrote: On 06/24/2013 06:18 PM, Bob Henson wrote: When I ran regsvr32 c:\Program Files (x86)\GNU\GnuPG2\bin\gpgex.dll it just caused an error, saying The module c:\program failed to load. Make sure the binary is stored at the specified path or debug it to check for problems with the binary or dependant .dll files. The specified module could not be found. Try putting double quotes at the start and end of the string, e.g.: regsvr32 c:\Program Files (x86)\GNU\GnuPG2\bin\gpgex.dll I can NOT assure you that this will work but it probably will. That was my problem - thank you for the explanation. I wished Microsoft had used just C:/Programs/ instead of C:\Program Files\ for %ProgramFiles%. I don't know what to say about 64 bit other than don't mix / match. Microsoft could have used C:/Programs/64/ but that would have made too much sense. Microsoft wants back-slashes instead of slashes and a nice mix of punctuation marks in addition to dot . plus space characters in all folder and file names. It doesn't work very well, especially for something done from cmd.exe instead of the GUI. How bad is it? I COPY 7za.exe to use it in scripts because I don't want to make registry changes (%Path%) just to make it work from where it is at. Sigh I can see your points. I have only recently started using Linux, and the command line functions are much more logical - however, using two sets is even more confusing. Now I can't remember which way to slash :-) I blame old age - but I get there in the end, with the help of my friends. GpgEx is now working just fine. I used to use another explorer extension ( I forget the name - I think it used to be in Gpg4win?) which stopped being developed so it will be handy to have one again. Regards, Bob ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: GpgEX for 64 bit Windows test version
On 24/06/2013 9:01 AM, Werner Koch wrote: Now you may want to test it out. Note that I also added an About menu which should always work, even if no UI-server is running. The translations are not yet included in the ZIP file. Having finally solved my problem with installation, I've been trying GpgEX this morning and so far all seems to be fine. I've tried all the functions separately, and had no problems at all yet - obviously I'll report back if I get any. Thanks for the help. Regards, Bob ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: GpgEX for 64 bit Windows test version
On Tue, Jun 25, 2013 at 9:50 AM, Werner Koch w...@gnupg.org wrote: On Mon, 24 Jun 2013 20:18, old...@oldbob.co.uk said: As I can't run the 32 bit version of GPGex anyway on this system, can I not just overwrite the existing copy of gpgex.dll with the 64 bit one and reboot? Yes, you can. The regsvr32 call is still required. But if you do this, the extension won't be available in 32bit processes! (32bit explorer.exe, file selection dialogues in 32bit programs, 32bit file managers...) Best regards, Josef Schneider ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: GpgEX for 64 bit Windows test version
On 25/06/2013 9:40 AM, Josef Schneider wrote: On Tue, Jun 25, 2013 at 9:50 AM, Werner Koch w...@gnupg.org wrote: On Mon, 24 Jun 2013 20:18, old...@oldbob.co.uk said: As I can't run the 32 bit version of GPGex anyway on this system, can I not just overwrite the existing copy of gpgex.dll with the 64 bit one and reboot? Yes, you can. The regsvr32 call is still required. But if you do this, the extension won't be available in 32bit processes! (32bit explorer.exe, file selection dialogues in 32bit programs, 32bit file managers...) I put it in a separate directory in the end, so I should have the best of both worlds. I don't think I have any 32bit processes in use - but I'm covered anyway. Regards, Bob ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: GpgEX for 64 bit Windows test version
On Tue, 25 Jun 2013 10:25, old...@oldbob.co.uk said: GpgEx is now working just fine. I used to use another explorer extension ( I forget the name - I think it used to be in Gpg4win?) which stopped being developed so it will be handy to have one again. GpgEE. We replaced it by GpgEX because GpgEE was written in Delphi and there was no way to build it with a free tools chain or even cross-build. Salam-Shalom, Werner -- Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz. ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: GpgEX for 64 bit Windows test version
On Tue, 25 Jun 2013 10:40, jo...@netpage.dk said: But if you do this, the extension won't be available in 32bit processes! (32bit explorer.exe, file selection dialogues in 32bit Windows 7 64 bit has no more option to use a 32 bit explorer. This the the very reason for the 64 bit GpgEX ;-) Shalom-Salam, Werner -- Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz. ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: GpgEX for 64 bit Windows test version
On 25/06/2013 09:56, Bob Henson wrote: I put it in a separate directory in the end, so I should have the best of both worlds. I don't think I have any 32bit processes in use - but I'm covered anyway. If you run any 32bit programs at all (i.e. most applications) then the system-supplied file open/save dialogs for those programs with be 32bit and so these will use 32bit Explorer extensions. (Oops, forgot to reply to list previously). -- MarkR PGP public key: http://www.signal100.com/markr/pgp Key ID: C9C5C162 ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: GpgEX for 64 bit Windows test version
On 25/06/2013 14:31, Werner Koch wrote: On Tue, 25 Jun 2013 10:40, jo...@netpage.dk said: But if you do this, the extension won't be available in 32bit processes! (32bit explorer.exe, file selection dialogues in 32bit Windows 7 64 bit has no more option to use a 32 bit explorer. This the the very reason for the 64 bit GpgEX ;-) It is true that 32bit Windows Explorer cannot be run on 64bit Windows 7 and later but what Josef said about file open/save dialogs in 32bit programs and 32bit file managers running on 64bit Windows is correct -- these still use 32bit shell extensions Windows. -- MarkR PGP public key: http://www.signal100.com/markr/pgp Key ID: C9C5C162 ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: GpgEX for 64 bit Windows test version
On 26/06/2013 03:25, Mark Rousell wrote: On 25/06/2013 09:56, Bob Henson wrote: I put it in a separate directory in the end, so I should have the best of both worlds. I don't think I have any 32bit processes in use - but I'm covered anyway. If you run any 32bit programs at all (i.e. most applications) then the system-supplied file open/save dialogs for those programs with be 32bit and so these will use 32bit Explorer extensions. (Oops, forgot to reply to list previously). And I see that Josef Schneider already said the same thing. Apologies for the repetition. -- MarkR PGP public key: http://www.signal100.com/markr/pgp Key ID: C9C5C162 ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: GpgEX for 64 bit Windows test version
On 24/06/2013 9:01 AM, Werner Koch wrote: Hi! I just uploaded a test version of GpgEX (the GnuPG Explorer Plugin) for Windows 64 bit. This is just the bare standalone DLL without an installer. If you are using a 64 bit Windows system with Gpg4win, you may want to test this DLL: ftp://ftp.g10code.com/g10code/gpgex/gpgex-1.0.0-beta19-bin.zip ftp://ftp.g10code.com/g10code/gpgex/gpgex-1.0.0-beta19-bin.zip.sig To install the DLL please unzip the ZIP file and as Admin store the DLL as c:\Program files\GNU\GnuPG\bin\gpgex.dll On my Window 7 64bit system, GnuPG 1.4.13 installed itself in c:\Program Files (x86)\GNU\GnuPG\ - the 32bit section. When I installed Gpg4win, the installer offered install GPG2 in that same directory, but I added a 2 to keep the two separate, ie. it was installed in c:\Program Files (x86)\GNU\GnuPG2\ Your instructions above point to the \bin directory under the 64 bit Program Files directory, not the 32bit. I assumed that I needed to have gpgex.dll along with the other files and installed it in the \bin directory with the rest of my gpg2 files ie. under c:\Program Files (x86)\GNU\GnuPG2\bin\gpgex.dll. Should I have created a new directory under the 64bit Program File directory just for the one new file? When I ran regsvr32 c:\Program Files (x86)\GNU\GnuPG2\bin\gpgex.dll it just caused an error, saying The module c:\program failed to load. Make sure the binary is stored at the specified path or debug it to check for problems with the binary or dependant .dll files. The specified module could not be found. It looks to me as though the regsvr command is looking for a program to run called c:\program? As I can't run the 32 bit version of GPGex anyway on this system, can I not just overwrite the existing copy of gpgex.dll with the 64 bit one and reboot? What should I try if not, please? Regards, Bob ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: GpgEX for 64 bit Windows test version
On 2013.06.24. 21:18, Bob Henson wrote: it just caused an error, saying The module c:\program failed to load. Make sure the binary is stored at the specified path or debug it to check for problems with the binary or dependant .dll files. The specified module could not be found. It looks to me as though the regsvr command is looking for a program to run called c:\program? As I can't run the 32 bit version of GPGex anyway on this system, can I not just overwrite the existing copy of gpgex.dll with the 64 bit one and reboot? What should I try if not, please? Paths with spaces needs to be escaped. Put that C:\program files... in quotes. (). ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: GpgEX for 64 bit Windows test version
On 06/24/2013 06:18 PM, Bob Henson wrote: When I ran regsvr32 c:\Program Files (x86)\GNU\GnuPG2\bin\gpgex.dll it just caused an error, saying The module c:\program failed to load. Make sure the binary is stored at the specified path or debug it to check for problems with the binary or dependant .dll files. The specified module could not be found. Try putting double quotes at the start and end of the string, e.g.: regsvr32 c:\Program Files (x86)\GNU\GnuPG2\bin\gpgex.dll I can NOT assure you that this will work but it probably will. I wished Microsoft had used just C:/Programs/ instead of C:\Program Files\ for %ProgramFiles%. I don't know what to say about 64 bit other than don't mix / match. Microsoft could have used C:/Programs/64/ but that would have made too much sense. Microsoft wants back-slashes instead of slashes and a nice mix of punctuation marks in addition to dot . plus space characters in all folder and file names. It doesn't work very well, especially for something done from cmd.exe instead of the GUI. How bad is it? I COPY 7za.exe to use it in scripts because I don't want to make registry changes (%Path%) just to make it work from where it is at. Sigh ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
