Support File Search Path

Can the Support File Search Path be set with a batch file? I have 20+ CAD
stations to add new paths for custom blocks.

 

I don't know about a batch file, but you can do that via an auto-loaded
lisp file. (if you do a search of this NG, you should see the code).

 

Thanks, but I don't want this to load every time. I need to update the path
only once.

 

BR,
Attached may get it done.

Bob

 

If the profiles are not different you can create one profile (.arg) file and
copy it to each computer, making sure icon on desktop references the
profile.

 

They can be set by importing a profile.

 

You don't need the whole profile, and would probably upset users since any
of their personal preferences would be gone. Just cut the support path line
out of the .arg file, save it to its own file, and rename the extension to
..reg, upon which double clicking it will instantly update the profile. If
you want to run this in a batch file, use regedit /s filename.reg.

John

 

As you wish. I was thinkking "long-term". for when you need to add
more (you wouldn't need to re-run it, as it's done for you).

 

Thanks for the info, John. We set the search paths, among other things, in
the initial setup of a station. This starts everybody from the same point.

In practice, aside from toolbar positioning, there really haven't been that
many "preferences" that vary from person to person. I have one (new) user
out of 20, for instance, who prefers the default crosshair size -- the first
person we've ever had who didn't prefer 100%. One other person wants to fool
with the right-click settings, and several of them insist on ridiculously
short autosave intervals. None of these would take any time to change if
they were forced to revert back to the original default profile. The
brighter ones know how to export their current profile for safekeeping.

I've never had occasion to change the search path, or reorganize our
standard block libraries to add new folders, within a given release of Acad.
Those are the kinds of things I do while we're going through a version
change. If we were somehow forced to do a substantial reorganization which
was out of synch with the product cycle, I'd probably treat it as a version
change anyway, and give everyone the same profile again as a starting point.

Actually, my likeliest use of the technique you suggest would be to enforce
compliance/uniformity on the few items where we really don't want to allow
personal preference settings, but persuasion has failed. Thanks again.

 

Check out the thread "Adding to Options:Files tab without changing whole
Profile" on July 29, 2004, or do a Google groups search for "+addpath
+changepath". You can add the function call to each acaddoc.lsp file, or have
the adaddoc.lsp file load/run another lisp file on the network.

I change and monitor all the installations at work by changing one network .lsp
file.
BTW, the acaddoc.lsp file has just one line...
(load "<network path>\\<company name>.lsp")

Of course it contains a healthy S::STARTUP function which makes the calls to
various functions.

For major pre-launch changes, we use a network batch routine for updating
installations.

 

I believe you can export the particular registry key / value that stores the
support paths and then add them to the 'new' computer's registry. Assuming
same Op Sys and cad version.


"Tom Smith" <nospam> wrote in message Thanks for the info, John. We set the search paths, among other things, in
the initial setup of a station. This starts everybody from the same point.

In practice, aside from toolbar positioning, there really haven't been that
many "preferences" that vary from person to person. I have one (new) user
out of 20, for instance, who prefers the default crosshair size -- the first
person we've ever had who didn't prefer 100%. One other person wants to fool
with the right-click settings, and several of them insist on ridiculously
short autosave intervals. None of these would take any time to change if
they were forced to revert back to the original default profile. The
brighter ones know how to export their current profile for safekeeping.

I've never had occasion to change the search path, or reorganize our
standard block libraries to add new folders, within a given release of Acad.
Those are the kinds of things I do while we're going through a version
change. If we were somehow forced to do a substantial reorganization which
was out of synch with the product cycle, I'd probably treat it as a version
change anyway, and give everyone the same profile again as a starting point.

Actually, my likeliest use of the technique you suggest would be to enforce
compliance/uniformity on the few items where we really don't want to allow
personal preference settings, but persuasion has failed. Thanks again.

 

Thanks Casey, that really helped.