borisb2 0 Posted July 11, 2015 (edited) I installed a new NAS (Synology 1815+) - all good with all programs, just houdini shows me a partly grayed out file browser. I can load and save files but I can't click on them or create a new folder. The old NAS or saving on C: doesnt show that issue. Is that still a premission issue? has anybody seen this? .. very strange and very annoying. Edited July 11, 2015 by borisb2 Share this post Link to post Share on other sites
mikelyndon 12 Posted July 11, 2015 You need to add this to Houdini.env HOUDINI_ACCESS_METHOD = 2 Thursday, May 9, 2002 Houdini 5.0.117: Adding new environment variable, HOUDINI_ACCESS_METHOD. This value can be 0, 1, or 2. It specifies what method Houdini will use to check file permissions. 0 uses the default method, which does a real check of file permissions using the proper NT security model. But this method can be quite slow on systems which use a login server elswhere in their network. Method 1 uses the NT security model again, and is much faster than method 0, but doesn't work on Win2k SP2 (Microsoft broke an important function in that release). Method 2 just checks the file attributes, which is fast and works, but ignores all the NT security stuff, so files and directories which are read only because of NT security permissions will report that they can be written to. 6 Share this post Link to post Share on other sites
borisb2 0 Posted July 12, 2015 solved! .. perfect! .. Thanks! Share this post Link to post Share on other sites
ndeboar 11 Posted July 14, 2017 Bumping this becouse I just had this exact issue. Thanks for the fix! Share this post Link to post Share on other sites
Richard Costin 0 Posted October 15, 2019 On 11/07/2015 at 8:35 PM, mikelyndon said: You need to add this to Houdini.env HOUDINI_ACCESS_METHOD = 2 Thursday, May 9, 2002 Houdini 5.0.117: Adding new environment variable, HOUDINI_ACCESS_METHOD. This value can be 0, 1, or 2. It specifies what method Houdini will use to check file permissions. 0 uses the default method, which does a real check of file permissions using the proper NT security model. But this method can be quite slow on systems which use a login server elswhere in their network. Method 1 uses the NT security model again, and is much faster than method 0, but doesn't work on Win2k SP2 (Microsoft broke an important function in that release). Method 2 just checks the file attributes, which is fast and works, but ignores all the NT security stuff, so files and directories which are read only because of NT security permissions will report that they can be written to. Many thanks @mikelyndon Most helpful. Share this post Link to post Share on other sites