Title says it - Ran low on space on my Poser Drive (D:), so I migrated ProPak to my H: drive just a few weeks ago. All working fine, until I tried to fire up PhilC's Wardrobe Wizard and found nothing happened when I tried. Re-initialized Python, still no go. Messed around a several hours trying various things, but no go. Discovered no Python scripts would run, so it's not just WW. Is this Something anyone's encountered before? Needless to say, everything was working fine on the D: drive, all updates installed. Any thoughts or suggestions??????

You might have to reinstall propack.

Tried that already - full re-install, P4, PPak, updates. No improvement.

Try deleting the python library in Poser prior to reinstalling.. Perhaps it helps? Not sure though, a general reinstall should have fixed it :o/ you haven't by chance installed other python interpreters?

FREEBIES! | My Gallery | My Store | My FB | Tumblr |
You just can't put the words "Poserites" and "happy" in the same sentence - didn't you know that? LaurieA
  Using Poser since 2002. Currently at Version 11.1 - Win 10.

Do you have Python installed as a separate installation as well as the version that is included in Poser? When you migrated the files did you copy/paste them to their new position or did you uninstall/reinstall?

I'm wondering if Poser Python makes a registry or other call to find out where it thinks it is.

Are you trying to run Python scripts from the scripts palette, or do you run them from File->Run Python script? In the first case, the xxxButtons.py scripts might point to the wrong (old) script locations. Fix up those scripts and the Python palette will work again. In the second case I wouldn't know what's wrong.

The pen is mightier than the sword. But if you literally want to have some impact, use a typewriter

My gallery   My freestuff

Okay, chalk this one up to just plain Poser Weirdness. I just checked the python button scripts to verify they had relative paths. They did. I was going to try a new reinstall for the 3rd time (frustrated? . . . keep trying the same thing over again hoping for a different result - irrational, but at least it was something to do ;-), and I started by renaming my Poser 4PP folder to Backup-Poser4-FULL. Took a phone call from a friend with a question, and I needed to rename the folder back to what it was originally to start up PP so I could answer the question (other than python, PP'd been working fine). Started PP, finished helping my friend, decided to try ONE MORE TIME to bring up the Python Palette, and suddenly there it was - scripts running fine again! (at least those I've tried so far. . . ). The only other thing I'd done in the meantime was to do a find in my registry to verify all Poser references now pointed to the H: drive instead of the D: drive (they did). Didn't even reboot in between. Weirdness . . . Anyway, I want to thank you for the suggestions. Jerry leather-guy

I had a similar thing that happened when python suddenly stopped working but it didn`t get fixed till I reinstalled propack months later.