compiler opened this issue on May 01, 2003 ยท 32 posts
Larry F posted Fri, 02 May 2003 at 11:42 AM
Good morning, ockham. "Could it be that your Python folders were installed as read-only or some other non-standard mode?" Can't say. Could be. If that is the case, though, then it is how they - my Python folders - came because they are like they were set up in Poser and/or ProPack when I installed it. I have seen a remark somewhere about "making sure the MainButton.py wsa unlocked". What does that mean, do you know, and how do I go about that? Could this be referring to "read only"? About the Python folders being installed as "read-only", I can't see how I would be the only person with such a problem/configuration. Further, would this folder configuration be something that was peculiar to a particular (version of) either the OS - Win98SE - or ProPack or some other system characteristic or something similar? Looking at it this way, I installed ProPack on a PC I use only for work - mostly word processing and spreadsheet stuff at home - but has the same OS and all the problems are exactly the same. I did e-mail pcbos but have not heard back yet. Frankly, I'm not all that far from giving up on this for awhile. It's making me want to go walk the back streets and cry, LOL. Also, looking around on the web I found www.python.org and a url for downloading Python 2.0. I D/L'ed it but did not run it yet. Should I? What version of Python would I already have in Poser ProPack, seeing as how I only have what came with it? Thanks very much again though, ockham. You're outstanding so I'm still hopeful. Larry F