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

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č 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

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