file locations

file locations

jdcho
Advocate Advocate
440 Views
4 Replies
Message 1 of 5

file locations

jdcho
Advocate
Advocate
A question on 32 bit systems vs 64 bit systems. I have 5 new machines using 64 bit and 10 using the 32 bit systems. Can I deploy the 32 bit systems to look at the same files the 64 bit systems uses ... i.e. templates, families .... I want it so that all the machines will be looking in the same path for templates and families, so I don't have to do it twice .....

Any and all help is greatly appreciated. Thanks in advance ....
0 Likes
441 Views
4 Replies
Replies (4)
Message 2 of 5

Anonymous
Not applicable
Project files, family files, templates and such don't care about bit version. .Net coded dlls will not care ONLY IF you set them to compile for ANY CPU.

jvj
0 Likes
Message 3 of 5

Anonymous
Not applicable
On Mon, 1 Mar 2010 10:09:24 -0800, JamieVJohnson <> wrote:

>Project files, family files, templates and such don't care about bit version. .Net coded dlls will not care ONLY IF you set them to compile for ANY CPU.
>
>jvj

Note that there are differences in file locations between Windows XP and Windows
7/Vista.

32-bit XP Revit installs OOTB (out of the box) content at C:\Documents and
Settings\All Users\Application Data\Autodesk\RAC 2010. Logically, this is
%AllUsersProfile%\Application Data\Autodesk\RAC 2010.

However, in a 32- and 64-bit Windows Vista and 7, this path is
C:\ProgramData\Autodesk\RAC 2010, or %ProgramData%\Autodesk\RAC.

In Vista/7, there is a "compatibility" variable where %AllUsersProfile% =
%ProgramData%, however, the two aren't interchangeable for Application Data.

In other words,

In XP, this path:
%AllUsersProfile%\Application Data\Autodesk\RAC 2010.

Is this path in Windows Vista/7:
%AllUsersProfile%\Autodesk\RAC 2010.

So, long story short, you need to check the target OS to determine where content
is installed.

Matt
matt@stachoni.com
0 Likes
Message 4 of 5

Anonymous
Not applicable
That is a very valid point Matt. I discovered similar disparities when using 64 bit about the 'program files' folder. The good thing is that the Revit.ini file allows you to remap to any point. With that said, place your installations (which you can controll during install as well) on all bit types in the same 'path' to simplify things. Keep all your templates and families on the server (and lock them down so you don't get accidental modifications, read only attribute is fine if you trust your crew). Then tell the revit.ini file where everything is.

jvj
0 Likes
Message 5 of 5

Anonymous
Not applicable
On Mon, 1 Mar 2010 12:25:38 -0800, JamieVJohnson <> wrote:

>That is a very valid point Matt. I discovered similar disparities when using 64 bit about the 'program files' folder. The good thing is that the Revit.ini file allows you to remap to any point. With that said, place your installations (which you can controll during install as well) on all bit types in the same 'path' to simplify things. Keep all your templates and families on the server (and lock them down so you don't get accidental modifications, read only attribute is fine if you trust your crew). Then tell the revit.ini file where everything is.

Exactly. Here's some additional info you might find helpful:

http://www.cadapult.net/blog/2010/02/scripting-network-installations-of.html

Matt
matt@stachoni.com
0 Likes