08-13-2017, 08:24 AM
(This post was last modified: 08-13-2017, 09:34 AM by rich2005.
Edit Reason: typo
)
That error has cropped up several times over the years, invariably caused by a broken resource usually too many brushes or a broken font... but some people never seem to get it fixed, so a bit of try and see.
Do not like the look of those postscript fonts, this is a comparison (in Win7) of the stock Gimp and Partha's Gimp
http://i.imgur.com/IdvUpTr.jpg not much in the way of fonts there.
You might be able to check that Gimp does work by using the command line switches --no-fonts --no-data (note the two dashes / one dash)
That should start Gimp up with no resources. Might indicate if fonts are the problem. Normally I would use a terminal but Parth's Gimp being virtually a 'portable' version, I would edit the shortcut and tack the switches on after the quote mark
looks like this http://i.imgur.com/F0RglOc.jpg The same applies to a stock Gimp.
If you can get Gimp up and running, then time to explore
edit: Just had a look at those postscript fonts included in the zip. These are 'Nimbus' typeface not included in my Gimp 2.8.22 / Partha 2.9.5 installations.
Do not like the look of those postscript fonts, this is a comparison (in Win7) of the stock Gimp and Partha's Gimp
http://i.imgur.com/IdvUpTr.jpg not much in the way of fonts there.
You might be able to check that Gimp does work by using the command line switches --no-fonts --no-data (note the two dashes / one dash)
That should start Gimp up with no resources. Might indicate if fonts are the problem. Normally I would use a terminal but Parth's Gimp being virtually a 'portable' version, I would edit the shortcut and tack the switches on after the quote mark
looks like this http://i.imgur.com/F0RglOc.jpg The same applies to a stock Gimp.
If you can get Gimp up and running, then time to explore
edit: Just had a look at those postscript fonts included in the zip. These are 'Nimbus' typeface not included in my Gimp 2.8.22 / Partha 2.9.5 installations.