Mapped drives / $HSITE

   2268   4   1
User Avatar
Member
2624 posts
Joined: Aug. 2006
Offline
Hi list,

I am having a torrid time with $HSITE ! . I have mapped a drive on windows 10 ie

S: \\somemachine\Users\someuser\project

Then is the Houdini.env file I set $HSITE to be $HSITE = //somemachine/Users/someuser/project/Pipeline/houdini

No matter what I try booting up Houdini it fails to find the path to some site wide tools > The folder structures and version numbers match.

can anyone give me a how to for this ?

Rob
Edited by circusmonkey - Aug. 26, 2016 21:27:01
Gone fishing
User Avatar
Member
7717 posts
Joined: July 2005
Online
Mapped drives on Windows aren't too great in general. Some ideas to check out:
  • Try setting HSITE into the OS Environment Variables instead of houdini.env
  • Ensure that your mapped drive is on the same user that's using Houdini since they're user specific
  • When you map the drive, ensure that the option to have it available at logon time is enabled. Re-logon to double-check.
  • Now check that your UNC path is correct. Start up Command Line Tools and cd to it, taking care to use backslashes instead of forward slashes since this is a Windows shell. eg. cd \\somemachine\Users\someuser\project\Pipeline\houdini
  • Now run “hconfig -ap | more” and double-check that your $HSITE is being picked up.
Edited by edward - Aug. 27, 2016 00:04:28
User Avatar
Member
2624 posts
Joined: Aug. 2006
Offline
Hi Edward, thanks for all those tips >

Rob
Gone fishing
User Avatar
Member
2624 posts
Joined: Aug. 2006
Offline
Hi Edward I get this in a shell, when trying to Cd

CMD does not support UNC paths as current directories.

Rob
Gone fishing
User Avatar
Member
7717 posts
Joined: July 2005
Online
Er, try opening a text file from there using notepad?
  • Quick Links