Strangely, I've got a problem where some scripts aren't working: it's not that there are any errors, and I can run the scripts in Poser 6 and Poser 7 (on another machine), but they just won't work for Poser 7 on this one.  Either running the script from the file menu, or adding it as a button tot he Python popup, or adding it to the script menu, none work.

Semidieu's automatic-load-and conform (and the other one he posted over at RDNA to expand the actor name dropdown) are the two I've noticed having problems with right now.  I know there are a few others, but those are the ones that caught my attention recently.  It's as if Poser says "Enh, don't want to do it" and completely ignores them.

Have the same service releases been applied to both Poser 7's?

Does the script write any files? If so are you logged in to your computer with sufficient privileges to allow programs to write files? What OS? Vista is notorious for being security conscious.

No error messages at all?

Both Poser 7's at SR 2.1, XP on the system (both computers), admin-level privileges on both, and nada for error messages.

As I said, it's damn peculiar.

You might compare the underlying Python stuff on both computers.  Do a directory
listing of the runtime/python/DLLs and runtime/python/Libs directories, and see if 
the 'lazy' computer has something missing or older in those areas.

Poser (at least 7 does, as I've been playing with this lately) seems to only run one script at a time. If you run a script, and it's looping but letting Poser have some time slices to keep the user interface active, it seems that you are clicking buttons or menus to run scripts, but Poser ignores you, silently. You get no error message or anything - it just seems like the script does nothing.

Perhaps, on the machine you're having issues with, there is a startup script permanently invoked? As in, have you installed some "background" type of script that loads automatically at Poser startup ? (check Runtime:Python:poserScripts:poserStartup.py) Or is there a script associated with the scene, perhaps even your default scene?

In either case, this would prevent you from running any Python at all, because the another one is still running.

Just a guess.

That's not it.  Aside from nothing strange being in the startup file, some scripts do work: for instance one that I have (I forget if it's with the program or one I downloaded) that lets you mass-delete a selection of objects, actors and what not at once.  It works fine.  Similarly the deleteLights script has no issues, the Netherworks cloth kit package of scripts works fine, but I just downloaded Wardrobe Wizard 2, and none of its scripts do anything, but Semidieu's Shaderworks scripts, and SpiderShader seems to be fully functional.

I am honestly at a loss.

Alright, got it to function.  Deciding on the brute force approach, I copied over the working Python DLL and lib folders and replaced the questionable ones.

Everything now works.

The problem wasn't something missing, it was having something there that shouldn't have been.  Comparing the directories, I had extra files in the Python library and I don't know what they do or where they came from.  I saved them just in case to try and work it out.

How bout sharing that list of guilty extra files incase someone else runs into the problem and comes searching the forums for an answer?

Running a file comparison on them, I noticed that the working directory not only had fewer files, they had newer dates.

I'm thinking that I might have, at some point when I updated and was moving content from older installations to Poser 7, accidentally copied the Python folder and hauled old crap over.