Long way with plastic SCM and node.js project

I am using Plastic SCM v4.x (on windows 7/8) and have projects that use node.js. Modules and module dependencies in a project generate a path length that is> 259 characters. Windows explorer has problems with this when I try to access files on a mapped drive. I change the UNC path and Windows browser had no problem. Git, node.js and RoboCopy have no problem accessing files.

I created a repository with local path as UNC (for example \ MyMachine \ c $ \ source \ project). When I check for pending changes, files show up, when I try to check them out, the client complains that the file cannot be found. (ASSUMPTION: Plastic allows UNC for local path and tries to use local path in API call to get files)

I hope someone else is having this problem and have a work-around, a fix, or maybe can tell me that updating to version 5 will work.

I will try to share Windows on my local machine and map the repository to a named share (assuming the GUI allows UNC for the local path) to force the GUI to use the UNC path.

Any help would be greatly appreciated.