PDA

View Full Version : Project Files Search Path



Avatart
2004-06-30, 09:37 AM
I have a problem; we specify a huge number of Project File Search Paths, as the projects we are doing have been set up this way. Now, I am told by our AutoCad development guys that there is a buffer of 1000 characters in all search paths added together, we are over 2500 characters. This causes AutoCad to crash out, without saving work, at every autosave. Now, I am not going to turn off the autosave (as it has autosaved my butt a few times!), does anyone know of a way to stop this happening by increasing this buffer? Or will I have to go through all 15,000 drawings and change the Xref paths?

I'll email a beer for the first correct answer.

(AutoCad 2004 on W2000Pro)

Mike.Perry
2004-06-30, 10:27 AM
Hi

Check out the following Technical Documents on the Autodesk web site under the Knowledge Base section -

ID: TS48958 - Support file problems when combined support path for Windows® and AutoCAD® software is too long (http://usa.autodesk.com/adsk/servlet/ps/item?siteID=123112&id=2884947&linkID=2475323)

ID: TS27235 - Define alias for AutoCAD® path (http://usa.autodesk.com/adsk/servlet/ps/item?siteID=123112&id=2881390&linkID=2475323)

Regarding Xref's check out the system variable PROJECTNAME -

ID: TS69565 - Set up PROJECT feature (http://usa.autodesk.com/adsk/servlet/ps/item?siteID=123112&id=2867918&linkID=2475323)

Regarding changing Xref paths, if you have the Express Tools take a look at the ReDir command -

ID: TS20596 - Changing embedded paths of AutoCAD files (http://usa.autodesk.com/adsk/servlet/ps/item?siteID=123112&id=2897398&linkID=2475323)

ID: TS65354 - Use AutoCAD® Express Tools software to change absolute xref paths to relative paths (http://usa.autodesk.com/adsk/servlet/ps/item?siteID=123112&id=2886307&linkID=2475323)

ID: TS44346 - Using AutoCAD® Express Tools to update directories for xrefs, images, rtext, styles, and shapes (http://usa.autodesk.com/adsk/servlet/ps/item?siteID=123112&id=2875708&linkID=2475323)

OR

ID: TP00110 - Making Use of the Reference Manager (http://usa.autodesk.com/adsk/servlet/ps/dl/item?siteID=123112&id=3225324&linkID=2475176)

Have a good one, Mike

Avatart
2004-06-30, 10:57 AM
Haven't read them all yet, but the beer is in the post! Thanks.

jpaulsen
2004-07-01, 02:37 PM
Mike,

I checked out the first two links. Very useful info. According to the first link the path limit is around 800 characters.

Do you know how to determine the total length of the support path variable?

The first link explained how to determine the AutoCAD path length by using the following lisp expression (strlen (getenv "ACAD")).

To determine the Windows path length I went to Run, typed CMD and then typed PATH at the command prompt. Is that the path variable I'm looking for?

My total path length is 497+455=952 (acad + win=total).

I assume the path variable gets truncated when the character limit has been reached. I also assume the Acad path variable is set after the Windows path variable. Are these good assumptions?

Mike.Perry
2004-07-01, 05:42 PM
Hi

From Technical Document ID: TS48958 (http://usa.autodesk.com/adsk/servlet/ps/item?siteID=123112&id=2884947&linkID=2475323) -

<snip>
This registry entry for support paths is also shared by the Windows operating system.
</snip>

I don't fully understand what is meant with the above statement; as the AutoCAD Search Path (Environment variable ACAD) is stored within it's own registry entry, UNLESS they mean this entry can also contain paths from Windows system variables that have been used within the AutoCAD Search Path (Any Windows system variable that contains valid paths can be used within the AutoCAD Search Path).

But with my above thinking (strlen (getenv "ACAD")) returns the value you're after; as any Windows system variables (paths they contain) used within the AutoCAD Search Path are included in the returned value obtained from (strlen (getenv "ACAD")).

I don't think the path gets "truncated" as such, I believe the characters after the limit (whatever that magical number is) are just not read (ie They're ignored).

Hopefully someone with greater Windows knowledge (Hint, hint, Robert Bell) will step forward and clear-up the mess I've written.

Have a good one, Mike