tleave2000

Thanks for all your advice, it's very much appreciated. Unfortunately driver 77.56 wouldn't install and I'm officially giving up on my computer, but not on Houdini.

My pc's a thorough mess for a couple of reasons and I guess it's pretty likely that's why none of this stuff is working. So I'm going to reorganise and format my hardisk, maybe see if i can sort out a dual boot with debian. Got some work to do too, so like the man said, I may be some time.

Thanks again

Thanks. I put the variable in and Houdini ran really slowly, so I know I did it right now. But houdini still crashes in all the same places.

So I guess it could be any single piece of hardware, or any piece of software on my computer, that's messing up houdini. That sucks.

If I have to clean my hard drive and start again, then I'd like to go over to linux, but well I duno. I think I'll get into linux sometime, but I'll have to get on with some other stuff for the time being.

That's pretty weird about “hconfig” working in the command line tools. The help file is pretty specific about it working in the textport, and doesn't mention the command line tools, but you're right ofcourse.

The dodgy help sentence is in help-reference-environment variables. The second Green Tip on that page, if you're interested:
“Use the hconfig command in the textport to show which environment variables you've set and their current value.”

I typed hconfig in the command line tool, and it listed some other environment variables that don't appear under My Computer, for instance HSITE and HOME. How can environment varisbles exist but not appear under My Computer?

All these questions must get annoying for you, maybe I should buy a book about windows or linux, or just buy a computer that works.

hm, 61.82 is missing from the nVidia drivers archive. 61.77 is the closest so I've gone with that one.