tuktu camargo

rafal
I'm glad to hear you found the source of the problem. Also, it could be just the file permissions on /usr/bin/python that need to be adjusted.

I tried to fix my .profile path as well as the symbolic link in my usr/bin/python without much luck. Houdini would install without giving me an error message, but then it would fail to launch.
So in the end I did a system restore to have a fresh new start and I'm happy to report that 11.0.504 is now up and running and fully licensed. 8)

I hope this thread serves as a lesson to all about what NOT to do to your system if you don't really know what you are doing. ops:

Thanks rafal once again!

rafal

…..but we already do that in our script, namely, #!/usr/bin/python

As soon as I read /usr/bin/python I knew exactly what the problem was. About a week ago I tried upgrading to Python 2.7 by following these instructions:

“Step1. Install the version of python that you are going to use for example im going to be using python 2.7 so i did the following:

sudo port install python27


Step2. Once your version of python is installed its not to point to that version by doing the following steps:

1. cd /usr/bin
2. sudo rm python
3. sudo ln -s /opt/local/bin/python2.7 python
4. python -V (Tells you the version of python you are using which in this case im using python 2.7 )


Step3. Enjoy your new version of python happy hacking”


After realizing that IDLE was no longer operational I decided to rollback to 2.6 and everything seemed to be going fine up until Houdini came along.
I'm probably going to have to reimage my mini to fix this mess which my “happy hacking” caused. ops:

Thanks rafal for shedding some light!

My Mac mini should definitely be able to handle H11 as I was just able to install 11.0.504 and run it under Windows 7 (which I'm running under bootcamp) :?
That's great and all, but I'd really like to be able to run this in OS X since that's my primary system.

thanks in advance