Creating a share per installation is erroneous and ridiculous. The issue isn't the customer producing pathes too long, it's the fact Autodesk is producing pathes too long.
In our case, putting the installation folder to a share would only save 19 characters of 255 (bypassing two folders), or less than 7% of the characters.
I tried these 2 paths for the 3DS Max Design 2013 AdminImage folder location of which the first failed and the second succeeded:
The first is 58 characters and the second 49.
So for those of you installing 3DS Max Design, you can use at least 49 characters to designate where your AdminImage folder is but 58 is right out.
So Travis, you are saying I should do this:
But really the paths are longer because I have to include the product's year as a subdirectory (+5 characters) or multiply the number of shares with the year as part of the name (+4 characters).
So is this long list of shares an advantage over browsing through a logical hierarchy of subfolders like \\server\software\company\product\year? (This doesn't get anywhere near 243 characters as you are implying some of us doing. It probably could be done in less than 75 but the 50 Autodesk gives is tight.)
When Autodesk creates file names like "Create Universal Constraint - PxCreateUniversalConstraintMS_PhysX - 32.png" (75 characters where 1/2 are repetative) and uses the exact same name for both a child and parent folder like "...\Essential_Skills_Movies\3dsMax_Design_2013\de
Yes, that is exactly what I am saying to do. And that is what I do - thus I have never had any of these problems. I agree that the Autodesk filenames are long and ridiculous and they need to be changed. But it is what it is. This is how to get your deployments working. Whether you have one share with multiple folders to traverse inside, or multiple shares for all the products, it's all the same. One way works, the other doesn't.
Actually both work, just 1 won't work if you go beyond a certain character limit like 50.
I like the heirachy better than your suggestion though because we have numerous software and in that case a flat system is more confusing than a heirarchy. We will just have to stay under 50 characters, which is doable but with extra attention required.
The heirarchy can exist in the same physical folder fashion, just share the last folder with the name. Whether you go to a server and drill down thru multiple folders, or go to a server and see a list of shares, the result is the same. If I wanted to install AutoCAD 2013, I could go to \\servername and then locate the \ACAD2k13 folder. Or I could go to \\servername and then find \APPS\ and then find \Autodesk\ and then find \AutoCAD\ and then find \2013\. Personally, \\servername\sharename makes more sense and it easier. It could still exist at D:\Apps\Autodesk\AutoCAD\2013, but just share out the last folder and send the link out to your users.
It's 6 of one, half a dozen of the other. I mean, it's all how you look at it. Ultimately, the filepath length needs to be addressed. But as for now, this is all we can do as a work-around.
It is 6 of one, half a dozen the other, yes. But as you say it's a matter of perspective. I don't think anyone wants to add their 2 cents to debate with you but to voice their frustration at Autodesk in a public format. As you conceded, there IS a problem with filename length in Autodesk products that exacerbate this situation... so, here we are... people are letting Autodesk know how frustrating it is. Can't it just be left at that?
True, but at the same time, how is it any better for the end user to create a folder structure that consists of multiple characters and many levels deep? I agree that there are some Autodesk filenames that are simply too long, but I also see that too many end users are creating filepaths that are also too long. Thus, the only recourse for this instance, until Autodesk creates smaller filenames in subsequent releases, is simply to create short share paths. Arguing beyond this point is moot.
But we are the ones paying for the software. If we want to have it on a server with a single share that is catagorized and sorted by a folder tree we should be able to.
When you buy a car no one tells you that you can only drive it when you wear blue pants and a hat.
You have an opinion about how folder structures should be created, thats fine but it has NOTHING to do with this conversation. The point here is that the way they have created the software is limiting us and we would like them to correct that.
Access a broad range of knowledge to help get the most out of your products and services.