Well, that proved interesting. After verifying no folder dependencies inthe preferences of the resident Gimp install, I deleted the entire .gimp-2.8 folder,.....and the resident gimp 2.10.30 continues to work just fine.
Additionally, the Partha Portable gimp I had installed on a flash drive that used the configuration info from the 2.8 folder, had produced a series of 6 error messages each time I started it. Not so severe that gimp refused to start, I just had to acknowledge each error on the way to launching the portable version. Problems such as nufraw-gimp and webexport being unable to start, and procedure browser, print, photocopy, and pagecurl plugins being non-compatible....
So, it occurred to me that those problems could very well be from that old legacy folder with it's obsolete configuration files, etc. so I did a completely new install of the Portable gimp,..and all of those error messages went away.
Runs like a charm now. Thanks again for your guidance.
It was interesting that during the re-install,... with no legacy .gimp2.8 folder to draw upon, the install process DID NOT seek out alternate configuration from inside the resident 2.10.30 AppData\Roaming\GIMP\2.10\... folder, (which I expected) but instead just doing a rudimentary, default install with minimal brushes, patterns, gradients and such. And upon first launch took forever as it queried default folders for resources. But, after that first time, it now runs very well.
Additionally, the Partha Portable gimp I had installed on a flash drive that used the configuration info from the 2.8 folder, had produced a series of 6 error messages each time I started it. Not so severe that gimp refused to start, I just had to acknowledge each error on the way to launching the portable version. Problems such as nufraw-gimp and webexport being unable to start, and procedure browser, print, photocopy, and pagecurl plugins being non-compatible....
So, it occurred to me that those problems could very well be from that old legacy folder with it's obsolete configuration files, etc. so I did a completely new install of the Portable gimp,..and all of those error messages went away.
Runs like a charm now. Thanks again for your guidance.
It was interesting that during the re-install,... with no legacy .gimp2.8 folder to draw upon, the install process DID NOT seek out alternate configuration from inside the resident 2.10.30 AppData\Roaming\GIMP\2.10\... folder, (which I expected) but instead just doing a rudimentary, default install with minimal brushes, patterns, gradients and such. And upon first launch took forever as it queried default folders for resources. But, after that first time, it now runs very well.