Updated July, 2007
To install and set up the Maine DOT MicroStation V8 customization
on a PC that is not connected to the State of Maine Wide Area
Network:
1) These instructions assume you have MicroStation V8 installed
and running properly first. The minimum required version to
run MDOT's V8 configuration is MicroStation V8.1 (08.01.00.07).
Earlier versions do not have the functions required to run some
of our macros. MicroStation can be either on C: or D: and must
be in the current Bentley standard folder structure.
2) Extract !ms2004conf.zip to the root of same drive that MicroStation
is installed in (usually C:, but can be D:). This should create
an \!ms2004conf\ folder on that drive, which will contain our
custom workspace and resource files.
3) Rename \Program Files\bentley\program\microstation\config\mslocal.cfg
to preserve it in case you want to change back to your current
setup. You could call it "mslocal.save_cfg" for instance.
4) Copy \!ms2004conf\standards\config\standards\mslocal\mslocal.cfg
in to replace the file that you renamed in Step 4) above -
\Program Files\Bentley\program\microstation\config\mslocal.cfg.
5) Extract !msv8user.zip to the root of same drive that MicroStation
is installed in (usually C:, but can be D:). This should create
an \!msv8user\ folder on that drive, which will contain "user
profiles" specific to each MicroStation user.
The "common" user profile will allow other users (who do not
yet have a MicroStation user profile set up) to run MicroStation.
The "!template" user profile can be copied and pasted to create
individualized user profiles.
6) Copy the "!template" user folder tree, then rename the copied
"!template" to be the same as your Windows login name.
(See note below re Windows 98/ME.)
7) When starting MicroStation, you should see "normal" as the
"User" selected in the Workspace box at the bottom of the
MicroStation Manager screen. This is correct. The first time
in, you may see a blank in the Interface field. If so, use the
pull-down button to select "mdot."
Other notes:
a) This configuration is very much a "work in progress" and some
things may not function as intended. Please inform us of
problems that you encounter.
b) We are making continual changes and improvements to our MDOT
configuration. You should update your copy to keep up. We
recommend checking our web site once a month for newer versions
of these files.
c) Our system is designed to work with a User Profile named the
same as the Windows NT, 2000 or XP login ID of the user. If
someone runs MicroStation that does not yet have their own
Profile, they get the profile called "Common." We have an
autoexec macro that notifies the user of this when they open
MicroStation.
d) To make your own User Profile, Copy the !Template user in
Windows Explorer, Paste, then Rename it to the same name as
your Windows login ID. Alternatively, you can use the
MAKEUSER.BAT located in \!msv8conf\setup\.
e) If you are using Windows 98/ME, MicroStation probably will
not pick up a login id. To work around this problem, edit the
\!ms2004conf\standards\config\standards\!initialize.cfg
to override the definition of WIN_USERNAME to match your User
Profile. (It should also work to just use the "common" User
Profile.)
f) We now keep our project .PCF files in a folder separate from
\!ms2004conf. A number of project-related variables are defined
in this file. If you wish to replicate our system of .PCF's,
extract \!msproj folder to the root of same drive that MicroStation
is installed in (usually C:, but can be D:).
To avoid a search for a non-existent mapped drive and folder
during the MicroStation load, you can edit the
\Program Files\bentley\program\microstation\config\mslocal.cfg
file to avoid the "if exists" clause in the definition of
_USTN_PROJECTSROOT. (Use the definition in the "else" section.)
g) We use a variable, PROJDISK1, to designate the disk (or
mapped drive) that the project files are located on. This
variable is defined in the user's normal.ucf file and is
normally set to Y: in our configuration. If you set up a
\PIN folder structure for projects on your local hard drive,
you can set the definition of PROJDISK1 accordingly.
