Nah, it was something more subtle than that.

I was using print statements for debugging a script. It had four print statements. I would open Poser, load my scene, run the script -- and three prints would work. I would rerun the script and the print box would not even open, not for that script nor for any of my other scripts. I would relaunch Poser and the script would print again. Three statements printed. The fourth did not, and, as before, the script would no longer even open the print box. I would have to relaunch Poser again.

Inexplicably enough, changing the line, "str = input.Value()", gleamed from working code, to use "x" as the variable name instead of "str" -- and the problem went away. Makes no sense at all, but, trust me, I have over 50 years experience as a programmer. Changing that line of code (which is *still* in another working piece of code) did the magic. No clue. Maybe there was a non-printing character in the statement or somesuch, but whatever was going on, it screwed scripts royally, requiring closing and reopening Poser to clear it.

Thank you for your suggestions however. This forum really works well for getting answers, suggestions, clues, etc., and I love it.