Another alternative, if you want to dig further, is to use Process Monitor (http://technet.microsoft.com/en-us/sysinternals/bb896645). Run that, filter on "gimp", and look at what it accesses during startup. Somewhere in that last is a) a file it reads that is corrupt, or b) a file that's missing. Either way, you'll see exactly what files gimp touches on startup, and there might be some surprises there.
I've used that before to find startup problems with programs accessing files in places I did not suspect. Very useful. -James _______________________________________________ gimp-user-list mailing list gimp-user-list@gnome.org http://mail.gnome.org/mailman/listinfo/gimp-user-list
