[Gimp-user] Misleading reply to a FAQ for installing a GIMP2.6 Windows 7-32 executable
>On Thu, 29 Dec 2011 11:09:34 +, Rene Grognard wrote: >> I simply cannot understand why GIMP does not look first into its own >> version in ProgramFiles\GIMP-2.0\bin which of course it finds once the >> Windows version is renamed. >Because the DLL search path in Windows is roughly "executable directory, >Windows\System32, Windows, %PATH%". Unfortunately, GIMP's plug-ins are all >individual executables, but they don't reside in the same directory as >gimp.exe, and as such look for DLLs in the System32 directory before >looking in GIMP's install dir. The simple hack/solution is to copy intl.dll from the bin folder to the plug-ins folder. For my installation, here are the two paths. Copy from: C:\Program Files (x86)\GIMP-2.0\bin\intl.dll Copy to: C:\Program Files (x86)\GIMP-2.0\lib\gimp\2.0\plug-ins\intl.dll I did this and didn't get the startup errors I was seeing before -- urbite (via gimpusers.com) *** Good shot, Pilot! - Parsec 2002 ___ gimp-user-list mailing list gimp-user-list@gnome.org http://mail.gnome.org/mailman/listinfo/gimp-user-list
[Gimp-user] Misleading reply to a FAQ for installing a GIMP2.6 Windows 7-32 executable
Thanks - help much appreciated - I am going to try and deinstall - rename the file - reinstall- return the renamed file to it's original name upon installation of Gimp - as someone (perhaps you) kindly suggested - hope it works. >Evan Neumann writes: >> Let the kids finger paint over the cracked walls. >> >> As far as Gimp. I don't know about the other issues, but rename intl dll >> intl-old.dll >> >> Then re-install Gimp. >> >> There is no feasible way to hold someone's hand through troubleshooting Gimp >> though. Because it is open source there are morose bugs that a user must >> muddle through when things go wrong. >Perhaps that generalisation has merit, perhaps not, but in this case the >fault lies with HP. I note that >Renatus writes: >> However intl.dll in folder Windows\System32 was hardly placed there by some >> broken >> application. It is used by LoginUI.exe, the user interface for the logon >> screen! >– well, the assumption is wrong. LoginUI.exe is in fact a broken >application, part of HP's "personalisation", and it places a broken >version of intl.dll in the Windows system directory. This overrides the >file that GIMP expects to be there. >If anything, the problem is that GIMP expects the Windows install not to >be screwed up by HP. If you own an HP computer, it might help to >complain to them. >Anyway, if you use PortableGIMP, this comment seems to give a solution: >http://portableapps.com/node/1598#comment-11104 >-Kevin -- NoviceGimper (via gimpusers.com) ___ gimp-user-list mailing list gimp-user-list@gnome.org http://mail.gnome.org/mailman/listinfo/gimp-user-list
Re: [Gimp-user] Misleading reply to a FAQ for installing a GIMP2.6 Windows 7-32 executable
Jernej Simončič writes: > On Wed, 18 Jan 2012 10:32:36 +0100, Kevin Brubeck Unhammer wrote: > >> – well, the assumption is wrong. LoginUI.exe is in fact a broken >> application, part of HP's "personalisation", and it places a broken >> version of intl.dll in the Windows system directory. This overrides the >> file that GIMP expects to be there. > > Actually, GIMP expects intl.dll to be in it's installation directory. > However GIMP's plug-ins are separate executables which have to be placed in > another directory, but due to the way Windows loads DLLs, they try to load > intl.dll from the System32 directory before trying the installation > directory. Does that mean you could circumvent it copying GIMP's intl.dll into any subdirectory containing a plug-in? (Alternatively, find ut where loginui.exe presides, and move the broken intl.dll from system32 into that directory.) -Kevin ___ gimp-user-list mailing list gimp-user-list@gnome.org http://mail.gnome.org/mailman/listinfo/gimp-user-list
Re: [Gimp-user] Misleading reply to a FAQ for installing a GIMP2.6 Windows 7-32 executable
On Wed, 18 Jan 2012 10:32:36 +0100, Kevin Brubeck Unhammer wrote: > – well, the assumption is wrong. LoginUI.exe is in fact a broken > application, part of HP's "personalisation", and it places a broken > version of intl.dll in the Windows system directory. This overrides the > file that GIMP expects to be there. Actually, GIMP expects intl.dll to be in it's installation directory. However GIMP's plug-ins are separate executables which have to be placed in another directory, but due to the way Windows loads DLLs, they try to load intl.dll from the System32 directory before trying the installation directory. -- < Jernej Simončič ><><><><>< http://eternallybored.org/ > ___ gimp-user-list mailing list gimp-user-list@gnome.org http://mail.gnome.org/mailman/listinfo/gimp-user-list
Re: [Gimp-user] Misleading reply to a FAQ for installing a GIMP2.6 Windows 7-32 executable
Evan Neumann writes: > Let the kids finger paint over the cracked walls. > > As far as Gimp. I don't know about the other issues, but rename intl dll > intl-old.dll > > Then re-install Gimp. > > There is no feasible way to hold someone's hand through troubleshooting Gimp > though. Because it is open source there are morose bugs that a user must > muddle through when things go wrong. Perhaps that generalisation has merit, perhaps not, but in this case the fault lies with HP. I note that Renatus writes: > However intl.dll in folder Windows\System32 was hardly placed there by some > broken > application. It is used by LoginUI.exe, the user interface for the logon > screen! – well, the assumption is wrong. LoginUI.exe is in fact a broken application, part of HP's "personalisation", and it places a broken version of intl.dll in the Windows system directory. This overrides the file that GIMP expects to be there. If anything, the problem is that GIMP expects the Windows install not to be screwed up by HP. If you own an HP computer, it might help to complain to them. Anyway, if you use PortableGIMP, this comment seems to give a solution: http://portableapps.com/node/1598#comment-11104 -Kevin ___ gimp-user-list mailing list gimp-user-list@gnome.org http://mail.gnome.org/mailman/listinfo/gimp-user-list
Re: [Gimp-user] Misleading reply to a FAQ for installing a GIMP2.6 Windows 7-32 executable
Let the kids finger paint over the cracked walls. As far as Gimp. I don't know about the other issues, but rename intl dll intl-old.dll Then re-install Gimp. There is no feasible way to hold someone's hand through troubleshooting Gimp though. Because it is open source there are morose bugs that a user must muddle through when things go wrong. Good luck! Evan Sent from my shoe. On Jan 17, 2012, at 4:10 AM, NoviceGimper wrote: > > Hi - I was wondering if you managed to resolve this issue. I have the same > problem - and I have an HP Probook4530s with a CORE i5 processor. I am not > that clued up with computers or how they work so I need someone to hold my > hand through this process. I also get the "The procedure entry point > libintl_snprintf could not be located in the dynamic link library intl.dll." > error when I try to start GIMP. > I went into System 32 files and found the intl.dll file - but what exactly > must I rename itto (as advised by the FAQ section). > > And as I see in this post - it causes some other logon problem - and I dont > know what this means or what he is even talking about. But whatever it is I > dont want it to do the same on my pc. > > Can some kind person please walk me through the fix process step-by-step > (like you are talking to someone who is a real idiot). > > Please - I do like GIMP and I am using it to make posters and images for my > classroom - so it will be great if someone can help me outand the > children will have something better to look at than broken and cracked walls > > > > > > > >> I just got started with GIMP2.6 but only after reading (and acting on the >> advice of) the following item in the FAQ list: > FAQ: I'm getting The >> procedure entry point libintl_snprintf could not be located in the dynamic >> link library intl.dll. when I try to run GIMP or use plug-ins. How do I fix >> it?>> Some broken application placed a file named intl.dll to your >> Windows orWindows\System32 directory. Rename it, and GIMP will work fine. On >> my HP under Windows 7-32 it is true that GIMP2.6 was installed only when >> intl.dll was renamed and then it worked fine. However intl.dll in folder >> Windows\System32 was hardly placed there by some broken application. It is >> used by LoginUI.exe, the user interface for the logon screen! When intl.dll >> is restored to recover the use of that interface then GIMP2.6 ceases to >> function. Is there a better and safe way out of that predicament (which IMO >> should then replace the unwise FAQ reply reproduced above)? Many thanks for >> any reply or for in > dicating a way to search the archives of this mail list for some answers. > > > > > -- > NoviceGimper (via gimpusers.com) > ___ > gimp-user-list mailing list > gimp-user-list@gnome.org > http://mail.gnome.org/mailman/listinfo/gimp-user-list ___ gimp-user-list mailing list gimp-user-list@gnome.org http://mail.gnome.org/mailman/listinfo/gimp-user-list
[Gimp-user] Misleading reply to a FAQ for installing a GIMP2.6 Windows 7-32 executable
Hi - I was wondering if you managed to resolve this issue. I have the same problem - and I have an HP Probook4530s with a CORE i5 processor. I am not that clued up with computers or how they work so I need someone to hold my hand through this process. I also get the "The procedure entry point libintl_snprintf could not be located in the dynamic link library intl.dll." error when I try to start GIMP. I went into System 32 files and found the intl.dll file - but what exactly must I rename itto (as advised by the FAQ section). And as I see in this post - it causes some other logon problem - and I dont know what this means or what he is even talking about. But whatever it is I dont want it to do the same on my pc. Can some kind person please walk me through the fix process step-by-step (like you are talking to someone who is a real idiot). Please - I do like GIMP and I am using it to make posters and images for my classroom - so it will be great if someone can help me outand the children will have something better to look at than broken and cracked walls >I just got started with GIMP2.6 but only after reading (and acting on the >advice of) the following item in the FAQ list: > FAQ: I'm getting The >procedure entry point libintl_snprintf could not be located in the dynamic >link library intl.dll. when I try to run GIMP or use plug-ins. How do I fix >it?>> Some broken application placed a file named intl.dll to your >Windows orWindows\System32 directory. Rename it, and GIMP will work fine. On >my HP under Windows 7-32 it is true that GIMP2.6 was installed only when >intl.dll was renamed and then it worked fine. However intl.dll in folder >Windows\System32 was hardly placed there by some broken application. It is >used by LoginUI.exe, the user interface for the logon screen! When intl.dll is >restored to recover the use of that interface then GIMP2.6 ceases to function. >Is there a better and safe way out of that predicament (which IMO should then >replace the unwise FAQ reply reproduced above)? Many thanks for any reply or >for in dicating a way to search the archives of this mail list for some answers. -- NoviceGimper (via gimpusers.com) ___ gimp-user-list mailing list gimp-user-list@gnome.org http://mail.gnome.org/mailman/listinfo/gimp-user-list
Re: [Gimp-user] Misleading reply to a FAQ for installing a GIMP2.6 Windows 7-32 executable
On Thu, 29 Dec 2011 11:09:34 +, Rene Grognard wrote: > I simply cannot understand why GIMP does not look first into its own version > in ProgramFiles\GIMP-2.0\bin which of course it finds once the Windows > version is renamed. Because the DLL search path in Windows is roughly "executable directory, Windows\System32, Windows, %PATH%". Unfortunately, GIMP's plug-ins are all individual executables, but they don't reside in the same directory as gimp.exe, and as such look for DLLs in the System32 directory before looking in GIMP's install dir. -- < Jernej Simončič ><><><><>< http://eternallybored.org/ > ___ gimp-user-list mailing list gimp-user-list@gnome.org http://mail.gnome.org/mailman/listinfo/gimp-user-list
Re: [Gimp-user] Misleading reply to a FAQ for installing a GIMP2.6 Windows 7-32 executable
Thanks to Jernej Simončič for his prompt reply. I never claimed it was a GIMP bug only that the FAQ reply was misleading and downright dangerous as you could get locked out of your own PC.HP's support also claims "that's the other guy's fault". The user is not the winner in such conflicts! *** The problem is that LoginUI.exe resides in the same Windows\System32 directory as intl.dll and intl.cpl (Control Panel item). I simply cannot understand why GIMP does not look first into its own version in ProgramFiles\GIMP-2.0\bin which of course it finds once the Windows version is renamed. It's only a matter of search path. I use many other programs (mostly Computer Algebra Software) which allows you in case of such conflicts to edit their search path.Clearly such facilities are required since conflicts of names could only be avoided by omniscient developpers and illimited alphabets or names. Is there any such "customer's tune-up" possibility with GIMP and if not is there any hope for a patch? Meanwhile I have to give up using GIMP which seems to be a first rate program. > To: gimp-user-list@gnome.org > From: jernej|s-gm...@eternallybored.org > Date: Thu, 29 Dec 2011 11:00:19 +0100 > Subject: Re: [Gimp-user] Misleading reply to a FAQ for installing a GIMP2.6 > Windows 7-32 executable > > On Thu, 29 Dec 2011 07:37:39 +, Renatus wrote: > > > However intl.dll in folder Windows\System32 was hardly placed there by some > > broken application. It is used > > by LoginUI.exe, the user interface for the logon screen! > > It's well known that some of HP's logon "enhancements" are broken - this is > not a GIMP bug, it's HP's bug, and you should contact their support. > > > Is there a better and safe way out of that predicament (which IMO should > > then replace the unwise FAQ reply reproduced > > above)? > > You could find out where the program that needs that other intl.dll > resides, and move intl.dll from System32 to that directory. > > -- > < Jernej Simončič ><><><><>< http://eternallybored.org/ > > > ___ > gimp-user-list mailing list > gimp-user-list@gnome.org > http://mail.gnome.org/mailman/listinfo/gimp-user-list ___ gimp-user-list mailing list gimp-user-list@gnome.org http://mail.gnome.org/mailman/listinfo/gimp-user-list
Re: [Gimp-user] Misleading reply to a FAQ for installing a GIMP2.6 Windows 7-32 executable
On Thu, 29 Dec 2011 07:37:39 +, Renatus wrote: > However intl.dll in folder Windows\System32 was hardly placed there by some > broken application. It is used > by LoginUI.exe, the user interface for the logon screen! It's well known that some of HP's logon "enhancements" are broken - this is not a GIMP bug, it's HP's bug, and you should contact their support. > Is there a better and safe way out of that predicament (which IMO should > then replace the unwise FAQ reply reproduced > above)? You could find out where the program that needs that other intl.dll resides, and move intl.dll from System32 to that directory. -- < Jernej Simončič ><><><><>< http://eternallybored.org/ > ___ gimp-user-list mailing list gimp-user-list@gnome.org http://mail.gnome.org/mailman/listinfo/gimp-user-list
[Gimp-user] Misleading reply to a FAQ for installing a GIMP2.6 Windows 7-32 executable
I just got started with GIMP2.6 but only after reading (and acting on the advice of) the following item in the FAQ list: > FAQ: I'm getting The procedure entry point libintl_snprintf could not be located in the dynamic link library intl.dll. when I try to run GIMP or use plug-ins. How do I fix it?>> Some broken application placed a file named intl.dll to your Windows orWindows\System32 directory. Rename it, and GIMP will work fine. On my HP under Windows 7-32 it is true that GIMP2.6 was installed only when intl.dll was renamed and then it worked fine. However intl.dll in folder Windows\System32 was hardly placed there by some broken application. It is used by LoginUI.exe, the user interface for the logon screen! When intl.dll is restored to recover the use of that interface then GIMP2.6 ceases to function. Is there a better and safe way out of that predicament (which IMO should then replace the unwise FAQ reply reproduced above)? Many thanks for any reply or for indicating a way to search the archives of this mail list for some answers. ___ gimp-user-list mailing list gimp-user-list@gnome.org http://mail.gnome.org/mailman/listinfo/gimp-user-list
