Thank you for the reply, I appreciate it.
Now, interesting thing is, I know of two other Macpro's one 2013, and one an older quad-core macpro 4,1 both running 10.10.2 and neither of those have this issue?
and the other confusing part to me about this, is why would friend's 2013 Macpro NOT have this issue until using THIS prefs file, if it was an Apple thing?
thanks for your help!
Bill