The real problems [I have] are:
A.) The config.pro file our company uses as a starting template for new employees and users in general was created many years ago. As such, a lot of the configs that are in there work for Pro/E Wildfire 1, but not for Creo 3.
B.) Along with many configs being removed, many have just changed in name; PTC changed the format of a lot of configs. For example, a given option for controlling display quality may still be possible, but it won't work with the current config in Creo 3 because at some point PTC changed the name of it between versions.
C.) For some reason, and I'm not sure what, whenever we copy a config.pro file for new users many lines duplicate at random. Based off of my cleaning so far, I estimate that our actual config.pro file is about 300 lines without any extra junk in it. Before I started this cleaning effort, it had 900 lines, so 600 of those were random duplicates comprised of real, duplicate options in addition to other options that fall into A and B above.
D.) Conflicts. We have conflicts due to C above, along with the fact that our config.sup file is overriding options in the config.pro because it all got too messy and even our admin lost track of what did what and which file it was located in. I spent several days trying to figure out how to turn shaded line display on and had a good number of folks and pros on this forum stumped. In the end it turns out I'd found the correct configuration name towards the beginning of my search. I changed it and it had no effect so I kept trying to figure it out for days. The simple solution is that the same option was being forcibly overwritten by the config.sup file. I would have found that a lot earlier if I'd had a clean set of config files and/or tools to get there more easily.
E.) The built-in configuration editor is not the be-all and end-all solution. A large portion of configuration options are hidden and do not display in the editor, so you have to know what you're looking for explicitly and either add it to the editor, or insert it into the file manually. I may be mistaken, but I think there may even still be some options in effect that don't display in the editor period, but again am not sure about that part.
In short, a document like the one that Martin linked to is great. Ideally, PTC would publish some sort of utility to verify your config.pro so a guy like me doesn't have to spend a few hours going through 900 lines of config.pro to figure out what works for a given Creo version and what doesn't. The link to the utility I posted in my original post does an okay job, but I've found a few items it has missed in addition to the fact that it gives a few false positives as well.
