| Author |
Message |
thomprt
Guest
|
 Posted:
Fri Mar 05, 2004 2:38 am Post subject:
Configuration Files |
|
|
Does anyone know how to alter the configuration files to point them to a
network directory as the primary search path for project files, reference
files, etc.? My main goal is to not have to store the full path of a
reference file while still providing a directory structure that is easy to
navigate. Any help would be appreciated. Thanks in advance.
|
|
| Back to top |
|
 |
Thomas Voghera
Guest
|
| Posted:
Fri Mar 05, 2004 5:47 am Post subject:
Re: Configuration Files |
|
|
Have a look for _DGNDIR
It reads the path/folder for you active dgn and uses that in the path for
references etc.
Go to WORKSPACE>CONFIGURATION and find MS_REFDIR enter _DGNDIR and look at
the readout.
A snip from my ucf
MS_IMAGE > $(_DGNDIR)
MS_IMAGEOUT = $(_DGNDIR)/bilder/
MS_RENDERLOG = $(_DGNDIR)/bilder/render.log
MS_RFDIR > $(_DGNDIR)/snitt/
MS_RFDIR > $(_DGNDIR)/../snitt/
MS_RFDIR > $(_DGNDIR)/../modell
MS_RFDIR > $(_DGNDIR)/../modell/snitt/
MS_RFDIR > $(_DGNDIR)/A/
MS_RFDIR > $(_DGNDIR)/K/
MS_RFDIR > $(_DGNDIR)/V/
MS_RFDIR > $(_DGNDIR)/L/
MS_RFDIR > $(_DGNDIR)/bef
TFDIR_PART = $(TFDIR)/part/
TF_DRAWINGS = $(_DGNDIR)/snitt/
... is old dos for UPDIR
You enter this once and everything works if you open a file in another
project, provided ! you keep the filestructure.
Barry B wrote a msm-article two? years ago about it.
A ggole serach will also find old posts about this.
hth
--
regards / Thomas Voghera
"thomprt" <rthompson@aai-dayton.com> wrote in message
news:40464be5_3@newsfeed.slurp.net...
| Quote: | Does anyone know how to alter the configuration files to point them to a
network directory as the primary search path for project files, reference
files, etc.? My main goal is to not have to store the full path of a
reference file while still providing a directory structure that is easy to
navigate. Any help would be appreciated. Thanks in advance.
|
|
|
| Back to top |
|
|
Jeffrey Malter
Guest
|
| Posted:
Fri Mar 05, 2004 10:39 am Post subject:
Re: Configuration Files |
|
|
Hello thomprt,
In order to keep all project files in one location, it is only necessary to
define one line in one file of each install. Open the mslocal.cfg file in a
texteditor, you will find it in <bentleyroot>\Program\MicroStation\config\ -
add this line immediately before the the line that begins "%include
$(MSDIR)..."
_USTN_PROJECTSROOT = <path>/
<path>/ might be something like //servername/partitonsharename/foldername/
where <path> locates your projects dir on the network drive (although it
could also relocate the \projects\ dir to another location on the same
computer). The part of this statement to the right of the = is the
'definition', in uStn cfg syntax all backslash chars must be written as
forwardslash chars. This particular cfg variable definition defines a
directory, and must end with a forwardslash. Move the contents of your
<bentleyroot>\Workspace\projects\ dir to this network folder. All
<projectname>.pcf folders must also live in this dir. Once you've got this
working for one install, make the change to mslocal.cfg on all installs and
wipe out the local \Workspace\projects\ dirs (after mining them for orphan
project files :).
As far as storing ref files, the cfgvar _DGNDIR is equivalent to
_USTN_PROJECTSROOT\<projectname>\dgn\ - uStn always looks here for reference
files. I believe you're right in not wishing to 'save full path' (hardcode)
each reference file's location. Unlike Mr. Voghera, I don't believe that the
ucf file is the best place to create search paths for ref files. I've found
it more flexible to define MS_RFDIR in each pcf file so that projects may be
structured differently as required, and when a change is made, only one file
(the pcf file in the network _USTN_PROJECTSROOT dir) needs to be changed,
rather than all the individual (local) ucf files. The downside occurs when
users, while in a particular file and project, open a new file from a
different project with File > Open instead of using File > Close and opening
the new file AND its correct projectname in the MicroStation manager dialog.
Of course you will be the best judge of whether ucf or pcf definitions best
suit your needs, but let me warn you against trying to mix the two. In my
experience, any definition of MS_RFDIR in the ucf file 'overrides' the
definitions that exist in the pcf file, regardless of the use of the < or >
operators.
hth and best regards,
Jeffrey Malter
"thomprt" <rthompson@aai-dayton.com> wrote in message
news:40464be5_3@newsfeed.slurp.net...
| Quote: | Does anyone know how to alter the configuration files to point them to a
network directory as the primary search path for project files, reference
files, etc.? My main goal is to not have to store the full path of a
reference file while still providing a directory structure that is easy to
navigate. Any help would be appreciated. Thanks in advance.
|
|
|
| Back to top |
|
|
Jeffrey Malter
Guest
|
| Posted:
Fri Mar 05, 2004 10:39 am Post subject:
Re: Configuration Files |
|
|
Hello thomprt,
In order to keep all project files in one location, it is only necessary to
define one line in one file of each install. Open the mslocal.cfg file in a
texteditor, you will find it in <bentleyroot>\Program\MicroStation\config\ -
add this line immediately before the the line that begins "%include
$(MSDIR)..."
_USTN_PROJECTSROOT = <path>/
<path>/ might be something like //servername/partitonsharename/foldername/
where <path> locates your projects dir on the network drive (although it
could also relocate the \projects\ dir to another location on the same
computer). The part of this statement to the right of the = is the
'definition', in uStn cfg syntax all backslash chars must be written as
forwardslash chars. This particular cfg variable definition defines a
directory, and must end with a forwardslash. Move the contents of your
<bentleyroot>\Workspace\projects\ dir to this network folder. All
<projectname>.pcf folders must also live in this dir. Once you've got this
working for one install, make the change to mslocal.cfg on all installs and
wipe out the local \Workspace\projects\ dirs (after mining them for orphan
project files :).
As far as storing ref files, the cfgvar _DGNDIR is equivalent to
_USTN_PROJECTSROOT\<projectname>\dgn\ - uStn always looks here for reference
files. I believe you're right in not wishing to 'save full path' (hardcode)
each reference file's location. Unlike Mr. Voghera, I don't believe that the
ucf file is the best place to create search paths for ref files. I've found
it more flexible to define MS_RFDIR in each pcf file so that projects may be
structured differently as required, and when a change is made, only one file
(the pcf file in the network _USTN_PROJECTSROOT dir) needs to be changed,
rather than all the individual (local) ucf files. The downside occurs when
users, while in a particular file and project, open a new file from a
different project with File > Open instead of using File > Close and opening
the new file AND its correct projectname in the MicroStation manager dialog.
Of course you will be the best judge of whether ucf or pcf definitions best
suit your needs, but let me warn you against trying to mix the two. In my
experience, any definition of MS_RFDIR in the ucf file 'overrides' the
definitions that exist in the pcf file, regardless of the use of the < or >
operators.
hth and best regards,
Jeffrey Malter
"thomprt" <rthompson@aai-dayton.com> wrote in message
news:40464be5_3@newsfeed.slurp.net...
| Quote: | Does anyone know how to alter the configuration files to point them to a
network directory as the primary search path for project files, reference
files, etc.? My main goal is to not have to store the full path of a
reference file while still providing a directory structure that is easy to
navigate. Any help would be appreciated. Thanks in advance.
|
|
|
| Back to top |
|
|
Thomas Voghera
Guest
|
| Posted:
Sat Mar 06, 2004 5:58 pm Post subject:
Re: Configuration Files |
|
|
Jeffrey
You are probably right about the location of configurations.
I copied from a single machine with no ustn things networked.
Project level, or why not "site" level if we are talking about using _DGNDIR
--
regards / Thomas Voghera
"Jeffrey Malter" <jmalter@nospam.earthlink.net> wrote in message
news:koU1c.22244$aT1.5908@newsread1.news.pas.earthlink.net...
| Quote: | Hello thomprt,
In order to keep all project files in one location, it is only necessary
to
define one line in one file of each install. Open the mslocal.cfg file in
a
texteditor, you will find it in
bentleyroot>\Program\MicroStation\config\ -
add this line immediately before the the line that begins "%include
$(MSDIR)..."
_USTN_PROJECTSROOT = <path>/
path>/ might be something like //servername/partitonsharename/foldername/
where <path> locates your projects dir on the network drive (although it
could also relocate the \projects\ dir to another location on the same
computer). The part of this statement to the right of the = is the
'definition', in uStn cfg syntax all backslash chars must be written as
forwardslash chars. This particular cfg variable definition defines a
directory, and must end with a forwardslash. Move the contents of your
bentleyroot>\Workspace\projects\ dir to this network folder. All
projectname>.pcf folders must also live in this dir. Once you've got this
working for one install, make the change to mslocal.cfg on all installs
and
wipe out the local \Workspace\projects\ dirs (after mining them for orphan
project files :).
As far as storing ref files, the cfgvar _DGNDIR is equivalent to
_USTN_PROJECTSROOT\<projectname>\dgn\ - uStn always looks here for
reference
files. I believe you're right in not wishing to 'save full path'
(hardcode)
each reference file's location. Unlike Mr. Voghera, I don't believe that
the
ucf file is the best place to create search paths for ref files. I've
found
it more flexible to define MS_RFDIR in each pcf file so that projects may
be
structured differently as required, and when a change is made, only one
file
(the pcf file in the network _USTN_PROJECTSROOT dir) needs to be changed,
rather than all the individual (local) ucf files. The downside occurs when
users, while in a particular file and project, open a new file from a
different project with File > Open instead of using File > Close and
opening
the new file AND its correct projectname in the MicroStation manager
dialog.
Of course you will be the best judge of whether ucf or pcf definitions
best
suit your needs, but let me warn you against trying to mix the two. In my
experience, any definition of MS_RFDIR in the ucf file 'overrides' the
definitions that exist in the pcf file, regardless of the use of the < or
operators.
hth and best regards,
Jeffrey Malter
"thomprt" <rthompson@aai-dayton.com> wrote in message
news:40464be5_3@newsfeed.slurp.net...
Does anyone know how to alter the configuration files to point them to a
network directory as the primary search path for project files,
reference
files, etc.? My main goal is to not have to store the full path of a
reference file while still providing a directory structure that is easy
to
navigate. Any help would be appreciated. Thanks in advance.
|
|
|
| Back to top |
|
|
|
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in