Readme
for the Autodesk Building Systems 2005
Service Pack 2
The
Autodesk Building Systems 2005 Service Pack 2 includes updates that resolve
several issues discovered after the product was released.
This Readme contains the latest information regarding the
installation and use of this service pack. It is strongly recommended that you
read this entire file before you apply the service pack to your product. For
future reference, we recommend that you save a copy of this Readme
to your hard drive or print a copy.
Autodesk
Building Systems 2005 is required to install Service Pack 2.
Autodesk
Building Systems 2005 Service Pack 1 is not required prior to installing
Service Pack 2.
General
Information
It is
recommended that you create a backup of all custom MNU, MNS, MNR, MNL and MNC
files before installing the service pack.
During the
installation of this update, you will be prompted for the original installation
media (CDs, DVD or the network image) that you installed from.
Once this
service pack is applied, you cannot run an automatic uninstall to remove the
service pack.
User Privileges
This
Service Pack must be installed by a user with Administrative Privileges. The
installation process will stop with an error message if it was attempted by a
user without Administrative Privileges.
Content
files will be updated by this patch, therefore you will need to have read and
write permissions to the Remote Content folders while you apply the patch.
Defects Fixed by Autodesk
Building Systems 2005 Service Pack 2
Catalog
Editor
- There
was a script error in Internet Explorer when opening a part that was
published from the Catalog Editor to a web server that is case sensitive
(UNIX based servers). This issue has been fixed.
Content
– Duct
- Takeoffs for round Ducts have been modified in Autodesk Building
Systems 2005 Content.
Content
– MvPart
- The MvParts Parallel Fan Powered VAV Box
and Series Fan Powered VAV Box, had different
elevation defined for the connectors. This has been corrected.
Content
– Templates
- All linetypes with the description (.5x) had been assigned an incorrect scale in the Metric
US and Metric UK templates. This has been corrected.
Content
Builder
- All the connection types appeared in the Add dialog, even if there
was no content to match that connection type. Now it only displays the
Connection Types that exist in the content. You will need to run the
command CatalogRegen to update the Content.
- In Content Builder, a Fatal error might
occur when placing a coincident constraint between two fixed point. This
has been fixed.
Duct Fitting
- Fatal error when opening
earlier versions of Building Systems drawings. When opening a drawing
saved in earlier versions of Building System, the program could stop
responding or crash with a Fatal error. This
happened if objects in the drawing contained Duct fittings with an angle
of 0.0 degrees. This has been fixed.
- Switching between different parts
in Modify Duct Fitting is improved. In previous release values on
parameters such as angle could change when switching part type.
Duct
Hatch
- Duct hatch did not use Display overrides for
Layer and Line weight. This has been fixed in this Service Pack (SP2).
Duct Layout
- When exiting the Add Duct command, the Osnap
on/off setting was reset to the value it had when the tool was started.
This is now corrected.
Duct
Layout – Improvement
- When adding a duct from an
existing duct, you can now select if the duct will merge or if it will be
added as a separate duct. If you want to add the duct as a separate
segment, press the CTRL key when pointing out the end point for that
segment. This improvement has been implemented for Add Duct, Pipe, CableTray and Conduit.
Duct
Modify
- When modifying a duct made with
a different Layer standard than current, the Duct changed its properties
to the current Layer standard. This has now been corrected.
Duct
Sizing
- Resizing a system containing
fittings with values mixed between the connectors broke the layout. The
main problem was that the calculated sizes set on the connectors of the
elbow were switched. We are now taking advantage of the SizeDependency parameter in PartCatalogData
for all the fittings. The program checks if calculated sizes (width and
height independently) are different for connectors which have size
dependency and synchronizes them.
- When
running the Resize command in some drawings, an eWasOpenForRead message might appear, terminating the
resizing command. This has now been corrected.
Flex
Duct
- In the Object Viewer, a Fatal error might occur when displaying a FlexDuct in Top view. This has been fixed.
- A
Fatal error might occur in a drawing with Flex Duct during a save or when
switching to a Plan view. This
is now fixed.
Labels
- Duct
Label Rotations now always display as right read or horizontal regardless
of the view direction.
- Building Systems tags
and schedules could display "? Proxy (AecbDbDuct)?"
when open in Architectural Desktop 2005 and AutoCAD 2005.This has been corrected.
Schematic
Pipe
- When connecting
a schematic pipe from an existing schematic pipe to a fixture the flow
could be reversed on the pipe, this has been corrected.
Electric Wire
- When looking up the highest rating for a 3-pole
circuit in Wire sizing, the value was incorrectly divided by a square root
of 3.
MvPart
- Converted
MvParts did not automatically add Fixture units
to the engineering data for plumbing parts. This is now fixed.
- The
Convert MvPart command failed when an Xref was selected before running the command. This is
corrected.
Object Properties – Improvements
- You
can now change the Lining Thickness or the Insulation Thickness in the
Properties palette at the same time on a Duct and on a Duct Fitting. This
has been improved for Ducts, Duct Fittings, Pipe, Pipe Fittings, Duct Flex
and Pipe Flex.
Framework
- Schematic
Symbols, Schematic Fittings and Electrical Devices did not store the value
for ProxyGraphics. This has been fixed.
- The
Elevation list did not sort in alphabetical order. Now the Elevation list
is displayed in alphabetical order.
Engineering
Space
- When
running the Autogenerate Engineering Space
command through Xrefs no progress bar was
displayed. This
has been fixed.
- Using
Edit Adjacencies on numerous eSpaces awhile the
Properties palette was displayed could cause a long delayed response from
the program. This
has been fixed.
- Opening
added to a floor or ceiling was not correctly shown. This has been fixed.
- The Temperature was not converted when
changing the drawing units. Now the temperature in Metric drawings is
Celsius and Fahrenheit in Imperial drawings.
System
- If
you used the function Export to AutoCAD2004/2000 in Tilemode
0 (Paperspace), all the Schematic Symbols,
Devices, MvPart Annotation Blocks and Labels
were rescaled incorrectly. This is now fixed.
- Object snap would not snap to devices
when PROXYGRAPHICS was set to 1. This is now corrected.
Defects Fixed by Autodesk Building
Systems 2005 Service Pack 1
Defects fixed by Autodesk Building Systems 2005
Service Pack 1 are included in Service Pack 2 as well.
Duct
Layout
- Issues
with broken Duct layout after modifying the slope. Sometimes when modifying the
slope on a Duct, you could get problems with broken Duct layout. This has
now been fixed.
Duct
Modify
- Modifying
the height of a Duct connected to an elbow which had it size locked could
result in switched height and width.
- When
modifying the Duct size in drawings that were created in earlier releases
of Building Systems, the height and width could become switched.
Flex
Duct
- Fatal
error when opening earlier versions of Building Systems drawings. When you opened drawings
saved in earlier versions of the program, Building Systems could stop
responding or crash with a Fatal error: Unhandled
Access Violation. This happened if objects in the drawing contained zero
length segments. If such segments exist in the drawing, they will now be
deleted.
Duct
Sizing
- Resize
System sometimes removed round to rectangular transitions if the connected
ducts had the same Height and Diameter.
- Fatal
error when you selected to “highlight and zoom objects” after running
Resize System. Sometimes
you could get a Fatal error message when you were in shaded mode and
selected to “highlight and zoom objects” from the Event Log dialog. This
has been fixed.
- When
importing a Duct System Xml in Metric drawings, you got a message about
the length of the duct segment no longer being the same and the import was
broken.
- Resize
System did not resize fittings that did not have the “transition_flag”
specified.
- The
"Do not Resize" option was ignored when
a system was resized.
- The
Resize System command could sometimes switch Height and Width on the
transitions in the system.
- Sometimes
extra transitions were inserted after running Resize System. It now prevents duplicate
transitions from being inserted.
Electric
Wire
- Fatal
error when auto-generating Wires Connecting to Devices that
were Node Anchored. You got a Fatal error message
when you automatically generated wires that connected to Devices that had
been node anchored.
Framework
- The
Regenerate model dialog did not display when opening an Autodesk Building
Systems Release 3 drawing. Now the Regenerate dialog displays for all drawings
created with earlier Building Systems releases. Two dialog boxes now
display if the drawing was last saved in Autodesk Building Systems 3 or
earlier.
- When opening a drawing made in
an earlier release of Building Systems where the drawing was saved in
TILEMODE 0 (Paperspace), the graph for plumbing
objects did not update automatically.
MvPart
- The
Details Tab for MvParts Properties did not read
the flow direction from the actual MvPart. It read the flow direction from
the Part Catalog. This has been corrected.
- Issues
when converting user-defined blocks to MvParts. When the function Convert to MvPart was used, only the Top and Schematic views were
created. The 3D Model view is now being created as well.
There was also an issue if you had specified a 3D rotation to the
original block/MvBlock the converted MvPart did not respect that rotation. This has now
been fixed.
- VAV
Units – Outlet Plenum Cross 42x11 inch. Two of the connectors were created within this MvPart. This has now been corrected.
- Adding/Removing
Valves resulted in a broken layout. Sometimes when you added or removed valves in a
drawing, the pipes did not heal up.
- “Export
to AutoCAD” did not export the associated layers for MvParts. When a drawing was exported
using the command “Export to AutoCAD”, the layers associated with MvParts were not exported to the new drawing. The
objects resided on Layer 0.
Engineering
Space
- Amount
of Units displayed in the Engineering Space dialog. The data in the Engineering
Space dialog is now rounded to 3 significant digits.
- Multiple
properties on Engineering data with the same Property Name displayed as
*VARIES*. The
position of the Property and Description columns has been switched and the
Property Column has been renamed to Type.
gbXML
- It is
now possible to set “Building Type” when running “-aecbgbXMLExport”.
- It is
now possible to select more then one Zone when running “-aecbgbXMLExport”.
- gbXML Import does now import more then one value per
Result Type.
Previously the gbXML import only imported one of
each result stored on eSpaces. Now it imports
all of the results for the object.
- The
setting Metric Results (useSIUnitsForResults) is
now set to True for Metric gbXML files. Metric gbXML
files specify that they expect the results back in metric.
ddXML
- The
command ddXML import will now remove previously
calculated sizes from all objects in the system before it applies the new
values. ddXML import did not apply new calculated size onto junction fittings.
Previous calculated sizes on junction fittings were left untouched.
- It is
now possible to write your own file path when exporting a Duct system to ddXML. There was a problem when writing a user-defined ddXML file path that should create dictionaries. This
is now fixed.
- Section
Numbering has been altered.
- Wrong
Section Connections in the System have been corrected.
- Dampers
now exports as an inline fitting. Dampers were treated as an end section when exported to
ddXML, which was incorrect.
- Wrong
direction on the connector, when exporting a Duct system as a Supply or
Exhaust system.
The first object of a system got the same direction on all of its
connectors.
- Elbows
that change shape or size were not treated as transition fittings when
running ddXML export. Now there is a check of the
connectors size/shape. Elbows that change shape or size are actually
transition fittings, and should end the section.
- Louvers
were not exported to the ddXML file.
- Unknown
MvParts with two connectors now exports as
Inline Fittings with Fitting Type set to Equipment.
- Duct
Plenums always got the fixed property set to true.
- Problems
with the section directions in some cases when connected with tee.
- Diffusers
on branches connected to the same plenum sections sometimes got exported
connected to the same branch.
Additional
Known Issues in Autodesk Building Systems 2005
These are
problems identified in the original release of ABS 2005 and have not been
corrected with this service pack.
- When resizing a Duct system with Flex Ducts
connected to Air Terminals, the Flex Ducts disconnect from the Air
Terminals.
- Viewing Multi-view Parts or Multi-view Blocks
in the Object Viewer can fail with a Fatal error. This happens when you zoom and
pan repeatedly, using the mouse wheel.
Engineering
Data Communication
Autodesk Building Systems 2005 enables engineering data flow
communication with alliance partner products.
Elite Software
·
Fire - The Elite Fire application enables you to read
Autodesk Building Systems sprinkler systems, perform hydraulic calculations,
and update the Autodesk Building Systems model with performance and
sizing information. The calculated sizes can be used to resize the entire
system.
·
Duct
Size – The Elite Ductsize application enables you to
read Autodesk Building Systems Duct systems, size them using equal friction or
static regain analyses, and then update the Autodesk Building Systems model
with performance and sizing information. The calculated sizes can be used to
resize the entire system.
GeoPraxis
·
Green
Building Studio – Autodesk Building Systems enables you to upload your building
space plan directly into Green Building Studio where you can perform energy and
load analyses including building cost of operation, heating and cooling loads
and fuel use/year. The transfer of data is through gbXML,
which means that any application that can read gbXML
is now compatible with Autodesk Building Systems.
Trane
·
Trace
700 – Autodesk Building Systems enables you to upload your building space plan
directly into Trane Trace 700 through gbXML to perform detailed heating and cooling load
calculations. The results can then be uploaded into Autodesk Building Systems
making heating and cooling airflows available on a room by room basis to assist
you with your duct layouts.
·
Varitrane – Autodesk Building Systems enables you to upload duct
systems directly into Trane Varitrane
Duct Designer and perform static regain and equal friction analyses. The
information can then be brought back into Autodesk Building Systems where it
can be used to resize the entire system. The transfer of data is through ddXML, which means that any application that can read ddXML is now compatible with Autodesk Building Systems.
Defect
Fixed by Architectural Desktop 2005 Service Pack 1
- AEC Dimensions behave properly with Maximum and
Minimum settings.
- Callout Tool View Scale value now displays
properly regardless of current drawing unit settings.
- Detail Callout Tools no longer create multiple
unnecessary instances of Xrefs when placing the
Views in Existing View drawings.
- Placing Callouts from the Sheet Set Manager now
works when running “ADT as AutoCAD 2005” and ADT modules have been loaded.
- Placing Callouts referencing dimension styles that
use True Type Fonts no longer crashes.
- Stability when working with the Project
Navigator has been greatly improved.
- Use of comma as a decimal separator no longer
interferes with level heights in Project Navigator.
- Accessing Architectural Desktop Sheets in
AutoCAD Sheet Set Manager no longer crashes.
- Manual Xrefs in a
project environment no longer interfere with project repathing.
- Stair Edit Turn trigger grip no longer crashes
for multi-landing stairs with manual winder styles.
- Background plotting no longer displays the
“Previous Version AEC Objects Detected” message.
- Windows Installer no longer starts when some VBA
applications are run.
- Several memory leaks have been addressed.
- Errors in Door Schedules using quantity column
have been fixed.
- Leaderless Reference Keynotes that reference
dimension styles that do not have leader settings now display proper text
height.
- Layer Manager Performance has been fixed. NOTE:
The previously released HOTFIX is
not required.
- New Layer From Standard
now sets plot styles properly.
- AecLayerAdd from the command line works
properly even after Layer Manager has been run.
- Saving Snapshots within Layer Manager group filters no longer crashes.
- Adding Interferences to multiple walls no longer
crashes.
- Mass Element Cut Plane components display
properly.
- Context Menu support in the Object Modeling
Framework SDK has been fixed.
- Preset values for Width, Length, and Area in the
Space Tool are properly being applied to spaces.
- Constrain and Area values for Space Tool now
persist.
- Apply Tool Properties to Elevation Sketch and
selecting Curtainwalls and Door/Window
Assemblies no longer crashes.
- Crashes using Apply Structural Grid to Linework have been fixed.
- Object components that are on layers set to OFF
no longer plot.
- Crashes using Multiple to tag block references
have been fixed.
- MVBlocks containing solids no longer
crash when Proxygraphics is set to 1.
- Crashes working with Structural Grids and
Perpendicular OSNAP have been fixed.
- Crashes when Grip editing Elevation lines have
been fixed.
- Crashes Panning and Zooming while Grip editing have been fixed.
- Tools’ Monochrome option now saves the linework as black.
Additional Known Issues in Architectural Desktop 2005
These are problems that
have been identified in the original release of Architectural Desktop 2005 that
are not corrected with this Service Pack.
Project Creation and
Modification in certain network environments
In some network environments, projects cannot be
created or modified when located on the servers. We have found that when the
network shares have only the servers’ local administrator account with full
permissions, our tests failed. If the servers’ local administrator group (which
the local administrator account is a member) had full permissions to the share,
our tests worked.
Publishing Multiple Sheets
Within Project Navigator
When working with a project loaded from a mapped drive, publishing multiple
sheets from the Sheets tab of the Project Navigator should be done using the
"Publish Sheet Set" button at the bottom of this tab. If you select Publish > Publish Dialog
Box... from the right-click menu, a fatal error will occur.
Norton SystemWorks
WinDoctor
Norton
SystemWorks WinDoctor
incorrectly identifies certain ADT registry keys as invalid. If you use Norton WinDoctor
to clean your registry, do not scan Active X Com Sections and Active X Com Sub
Key Sections. If you inadvertently
corrupt these sections with Norton WinDoctor, you may
restore the ADT portions of ActiveX by running the ADT reinstall and selecting
"Repair Registry".
Object Snaps
When you
add a Multi-landing Stair, you may encounter a Fatal Error if the Stair snaps
to text in a Dimension, Leader (in the current drawing), or any Text in an Xref. To avoid this, temporarily turn off OSNAPS for
Intersection and Apparent Intersection while adding the stair.
Service Pack Installation Issues
Side by side install with AutoCAD
2005
If an
Autodesk application is running when you apply the Service Pack, you may be
prompted to shut down the product. If you click Ignore, the product will not be
updated correctly, and Architectural Desktop will corrupt certain drawings.
To fix
this:
- Rename the file C:\Program
Files\Common Files\Autodesk Shared\acdb16.dll to acdb16.dll.bak.
- Run a reinstall for Autodesk
Architectural Desktop 2005 from the Control panel. Select Add or Remove
program - Autodesk Architectural Desktop 2005 – Change – Reinstall or
Repair Autodesk Architectural Desktop 2005 – Next – Reinstall Autodesk Architectural
Desktop 2005 – Next – Next.
The correct File Version of Acdb16.dll should be 16.1.84.3
Support
File Search paths
If you add content to your installation via Add/Remove Programs
after Service Pack 2 has been installed you will need to add support search
paths for Layer, Pats, Printer and Template Search paths to these newly updated
profile(s).
To do
this:
·
Options dialog > Files tab > Support File Search
Paths – add the path to the Layer folder and to the Support/Pats folder.
·
Options dialog > Files tab >Printer Support File Path
> Printer Configuration Search Path – add the path to the Plotters folder.
·
Options dialog > Files tab > Printer Support File
Path > Plot Style Table Search Path – add the path to Plot Styles folder.
·
Options dialog > Files tab > Template Settings >
Drawing Template File Location – add the path to Template folder.
Patching Network deployments
When
applying the patch to deployment clients, please ensure no other clients are
accessing the remote content directories. If the remote content directories are
accessed by another user the service pack installation will roll back with an
error message.
Autodesk Building Systems deployments that already has been
updated with Service Pack 1
It is recommended
that you recreate the deployment with Service Pack 2 if you already have a
deployment updated with Autodesk Building Systems Service Pack 1. Otherwise you
could discover some issues when running 3rd party applications that
are using .Net.
NIW and Deployments with Additional
Files
Issue: An
existing deployment that installs Additional Files can be patched, but a new
deployment that adds the patch and installs additional files will fail with the
error “2602” on the client machine.
Solutions:
If you have an existing deployment that installs Additional Files, just modify
the deployment with the patch. If you wish to create a deployment that is both
patched and installs Additional Files, first create a standard deployment with
the patch then modify the deployment to add the Additional Files.
ABS Tools (UK)
Applicable only if you install ABS Tools with UK Terminology after installing Autodesk
Building Systems 2005 SP2.
ABS Tools
adds UK Terminology by updating two Autodesk Building Systems 2005 files. If
you install ABS Tools after applying Autodesk Building Systems 2005 Service
Pack 2, the updated files will be incorrect. The files can be corrected by
manually replacing AecbElec45enu.dll and AecbEnumMap45enu.dll with the
corresponding UK versions.
To do this:
1. Go to
the Autodesk Building Systems 2005 program folder and replace AecbElec45Enu.dll
with a copy of AecbElec45Enu.dll.uk.
2. Go to the
Autodesk Shared folder, (C:\Program Files\Common Files\Autodesk Shared) and
replace AecbEnumMap45Enu.dll with a copy of AecbEnumMap45Enu.dll.uk.
Note: These steps will need to be
performed after every reinstall.
Applying
this Service Pack to a Stand-Alone Installation
- Download
the service pack and save it to any folder.
- Insert
your Autodesk Building Systems 2005 CD 1 or DVD into your CD/DVD drive. If
the Autodesk Building Systems 2005 installation has been made from a
network location or a deployment you will need to access that media.
- Navigate
to the folder where you saved the service pack.
- Double-click
the executable file to install the service pack.
Applying this Service Pack through Your Local Network Using a Patch List
Use the following
procedure if you want to use Communication Center
to apply this service pack through your local network.
To apply
this service pack through Communication Center using local patch list
functionality
- Insert
the Autodesk Building Systems 2005 CD 1 or DVD into your local computer's
CD/DVD drive.
- From
the Autodesk Product Support website, download < Autodesk
Building Systems 2005 Service
Pack 2.exe > and < Autodesk
Building Systems 2005 Service
Pack 2 Readme.htm > to a local server.
NOTE: Make sure that all users who need to apply the service pack have
access to this server.
- On
the Start menu (Windows), click Run. Enter the following information, and
then click OK:
\\<local server name>\<patch name>\ /p <patch
list location name>\<patch list name>
For example:
c:\abs2005swlsp2enu.exe /p c:\patchlist.txt
The contents of the patch list file are similar to the
following:
*****
ProductCode= {5783F2D7-0306-0409-0002-0060B0CE6BBA}
ProductVersionCandidate= 4.5.116.0
PatchTitle= Autodesk Building Systems 2005
Service Pack 2
PatchGUID= {2FE99BBC-F979-4E91-A637-DA3B0FD17B69}
PatchFileLocation=\\\\your_server_name\\your_share_name\\subfolders\\patch_name.exe
or ftp://your_server_name/your_share_name/your_path/patch_name.exe
PatchSize= 1098240
PatchDesc= Autodesk Building Systems 2005 Service
Pack 2
PatchDescLocation=\\\\your_server_name\\your_share_name\\subfolders\\readme_nam.html
or ftp://your_server_name/your_share_name/your_path/readme_name.html
NOTE: If a patch list file already exists in this location, the new patch
list information is added to the end of that file. The original file is not
overwritten.
- Open
the patch list file. If there is more than one patch list, the lists are
separated by asterisks (*****).
- Change
the fifth line in step 3, PatchFileLocation,
from:
PatchFileLocation=\\\\<your_server_name>\\<your_share_name>\\<subfolders>\\<patch_name>.exe
or
ftp://<your_server_name>/<your_share_name>/<your_path>/<patch_name>.exe
to one of the following:
- If you want to make the service
pack available from a file server, enter:
PatchFileLocation=\\\\<your_server_name>\\<your_share_name>\\<subfolders>\\<patch_name>.exe
- If you want to make the
service pack available from an FTP server, enter:
ftp://<your_server_name>/<your_share_name>/<your_path>/<patch_name>.exe
Change the last line in step 3, PatchDescLocation,
from:
PatchDescLocation=\\\\<your_server_name>\\<your_share_name>\\<subfolders>\\<readme_name>.html
or
ftp://<your_server_name>/<your_share_name>/<your_path>/<readme_name>.html
to one of the following:
- If you want to make the Readme available from a file server, enter: PatchDescLocation=\\\\<your_server_name>\\<your_share_name>\\<subfolders>
\\<readme_name>.html
- If you want to make the Readme available from an FTP server, enter: ftp://<your_server_name>/<your_share_name>/<your_path>/<readme_name>.html
- Save
and close the patch list file.
- On
the Start menu (Windows), click Run. Enter the following:
<your_CD-ROM
drive:>\CDROM:\ABS\Support\CADManagerControl
- Double-click
CMControl.exe.
- In
the CAD Manager utility, in the product list, select Autodesk Building
Systems 2005, and then click OK.
- In
the CAD Manager utility, on the Communication Center
tab, do the following:
- In the Live Update
Configuration list, select Enable Using Local Patch List.
- In the Local Patch List
Location box, enter the same local patch list location that you entered
in step 3.
- Click Apply to save these
settings to your own system.
- At
the bottom of the CAD Manager utility, in the drop-down list, select
Create .reg Registry File. Then click OK.
- In
the Save As dialog box, save the file to your system. Make note of this
location.
The registry file is now ready to be made available to
users. Distribute and execute the file to users by implementing the method of
your choice.
NOTE: You must execute the service pack
on each workstation that is running Autodesk Building Systems 2005.
Applying
this Service Pack to an Autodesk Building
Systems 2005 Network Administrative Image
The following
two methods of distributing Autodesk Building Systems 2005 Service Pack 2 apply
only to administrative images created with the Autodesk Building Systems 2005
Network Installation Wizard. After you complete these procedures, any new
deployments of Autodesk Building Systems 2005 will have the service pack
applied automatically.
NOTE: Once an administrative image has
been updated with Service Pack 2, you will not be able to apply Service Pack 2
to clients previously installed from this administrative image; thus it is
important that you first update all previously installed clients with Service
Pack 2 before modifying the administrative image with Service Pack 2.
NOTE: In both of
the following procedures, the patch (service pack) file that you download
contains an MSP (Microsoft Patch) file. You must extract that file from the
executable file. If you want to extract the MSP file from the
executable, use the /e ("extract") switch.
To add Autodesk
Building Systems 2005 Service Pack 2
to a new Autodesk Building
Systems 2005 administrative image
- From
the Autodesk Product Support website, download < Autodesk
Building Systems 2005 Service
Pack 2.exe > to your local computer.
- On
the Start menu (Windows), click Run. Enter the following information, and then
click OK:
<local drive:>\<patch
name>\ /e <local drive:>\<patch name.msp>
- On
the computer where you installed the Network Installation wizard, on the
Start menu (Windows), click Autodesk > Network Installation Wizard.
- In
the Network Installation Wizard, on the Welcome page, select Create an
Administrative Image, and then click Next.
- On
the Create Administrative Image page in the Select Autodesk Installer
(MSI) File box, enter the path to ABS.msi, the
MSI file you use as the basis for your administrative image. This file is
found on your product CD-ROM, in CDROM:\ABS.
- In
the Administrative Image Location box, enter an existing shared network
location where you want to create an administrative image or click Browse
to navigate to a location. Users install Autodesk Building Systems from
this location.
- Select
the Apply a Patch (Service Pack) to This Image option.
- In
the Select Patch box, enter the path to the patch location (the location
you entered in step 2, including the extension .msp).
You can also Browse to locate the MSP file.
- Click
Next and follow the instructions in the Network
Installation wizard to complete the deployment of this service pack.
To apply
Autodesk Building
Systems 2005 Service Pack 2 to an existing Autodesk
Building Systems 2005 administrative
image
- From
the Autodesk Product Support website, download < Autodesk
Building Systems 2005 Service
Pack 2.exe > to your local computer.
- On
the Start menu (Windows), click Run. Enter the following information and
then click OK.
<local drive:>\<patch name>\ /e <local
drive:>\<patch name>.msp
- On
the computer where you installed the Network Installation Wizard, on the
Start menu (Windows), click Autodesk > Network Installation Wizard.
- In
the Network Installation Wizard, on the Welcome page, select Modify an
Administrative Image and then click Next.
- On
the Modify Administrative Image page, in the Select an MSI File box,
select an existing Autodesk installer file (MSI) from an existing shared
network location that contains the administrative image you want to
modify. Users install Autodesk Building Systems from this location.
- Select
the Apply a Patch (Service Pack) to This Image option.
- In
the Select Patch box, enter the path to the patch location (the location
you entered in step 2, including the extension .msp).
You can also Browse to locate the MSP file.
- Click
Next and follow the instructions in the Network
Installation Wizard to complete the deployment of this service pack.
Files Changed by Autodesk Building Systems Service Pack 2
This patch should
not affect any of your customized files. However, if you are using a file that
has a date earlier than the date of the file originally installed by ABS 2005,
it will be replaced. For example, if you have simply copied acad.pgp
from ABS 2004, it will have a modified date that is before the release of ABS
2005 and will be replaced. To avoid this issue, simply re-save the customized
file, which will give it a later date, thus preventing its replacement.
NOTE:
This
patch will restore files that have been removed (or moved) after the original
installation.
Installation Folder
- acad.exe
- acad.exe.config
- acadres.dll
- AcBGPlot.arx
- acblock.arx
- acdbmgd.dll
- acDcFrame.arx
- AcDim.arx
- acdorder.arx
- aceplotx.arx
- aceTransmitui.arx
- AcField.arx
- acgs.dll
- AcLayer.dll
- acmgd.dll
- acmted.arx
- acmted2.arx
- acopm.arx
- AcPEXCtl.arx
- AcPlotGui.arx
- AcPublish.arx
- AcRevCloud.arx
- AcSmNav.arx
- AcSmWizard.arx
- AcStd.arx
- AcVba.arx
- adlmdll.dll
- ADPCatalogEditor45.dll
- ADPCatalogEditor45.tlb
- adui16.dll
- AecArchDACH45.arx
- AecArchDACH45enu.dll
- AecArchX45.arx
- AecArchX45enu.dll
- AecArchXM45.arx
- AecArchXM45enu.dll
- AecAreaCalculation45.arx
- AecAreaCalculation45enu.dll
- AecCB45.exe
- AecCBrowser45enu.dll
- AecCBTc45.dll
- AecCBTc45.tlb
- AecCBUtil45.dll
- AecDCArch45.arx
- AecDcArch45.tlb
- AecDcArch45enu.dll
- AecDtl45.arx
- AecDtl45enu.dll
- AecDtlDb45.dll
- AecGfc45.dll
- AecGuiBase45.arx
- AecGuiBase45enu.dll
- AecLayerManagerEx.dll
- AecLayerManagerUI45.arx
- AecLayerManagerUI45enu.dll
- AecLMgrLisp45.arx
- AecLMgrLisp45enu.dll
- AecLoader45.arx
- AecObjExplode45.arx
- AecObjExplode45enu.dll
- AecProject45.arx
- AecProject45enu.dll
- AecProjectPalette45.arx
- AecProjectPalette45enu.dll
- AecPublish45.arx
- AecPublish45enu.dll
- AecRcpBase45.arx
- AecRcpBase45enu.dll
- AecStartup45.arx
- AecStartup45enu.dll
- AecStructure45.arx
- AecStructure45enu.dll
- AecsXBase45.dll
- AecsXBase45.tlb
- AecsXBase45enu.dll
- AecsXBaseHelp45.dll
- AecsXBaseLoader.dll
- AecsXStyleGen45.dll
- AecsXStyleGen45.tlb
- AecsXStyleGen45enu.dll
- AecsXStyleGenHelp45.dll
- AecsXStyleGenLoader.dll
- AecSystemTools45.dll
- AecUiBase45.arx
- AecUiBase45enu.dll
- AecUiSchedule45.arx
- AecUiSchedule45enu.dll
- AecUiScheduleData45.arx
- AecUiScheduleData45enu.dll
- AecUiStatusBar45.arx
- AecUiStatusBar45enu.dll
- AecUtilities45.arx
- AecUtilities45enu.dll
- AecXArchBase45.dll
- AecXArchBase45.tlb
- AecXArchBase45enu.dll
- AecXArchBaseHelp45.dll
- AecXArchBaseLoader.dll
- AecXArchDACHBase45.dll
- AecXArchDACHBase45.tlb
- AecXArchDACHBase45enu.dll
- AecXArchDACHBaseHelp45.dll
- AecXArchDACHBaseLoader.dll
- AecXAreaCalculationBase45.dll
- AecXAreaCalculationBase45.tlb
- AecXAreaCalculationBase45enu.dll
- AecXAreaCalculationBaseHelp45.dll
- AecXAreaCalculationBaseLoader.dll
- AecXBase45.dll
- AecXBase45.tlb
- AecXBase45enu.dll
- AecXBaseHelp45.dll
- AecXBaseLoader.dll
- AecXDcContent45.dll
- AecXDcContent45.tlb
- AecXDcContent45enu.dll
- AecXDcContentLoader.dll
- AecXDtl45.dll
- AecXDtl45.tlb
- AecXDtl45enu.dll
- AecXDtlHelp45.dll
- AecXDtlLoader.dll
- AecXDynProps45.dll
- AecXDynProps45.tlb
- AecXDynProps45enu.dll
- AecXDynPropsHelp45.dll
- AecXDynPropsLoader.dll
- AecXExtendedData45.dll
- AecXExtendedData45.tlb
- AecXExtendedData45enu.dll
- AecXExtendedDataLoader.dll
- AecXGuiArch45.dll
- AecXGuiArch45enu.dll
- AecXGuiArchLoader.dll
- AecXGuiAreaCalculation45.dll
- AecXGuiAreaCalculation45enu.dll
- AecXGuiAreaCalculationLoader.dll
- AecXGuiBase45.dll
- AecXGuiBase45enu.dll
- AecXGuiBaseLoader.dll
- AecXGuiScheduleData45.dll
- AecXGuiScheduleData45.tlb
- AecXGuiScheduleData45enu.dll
- AecXGuiScheduleDataLoader.dll
- AecXGuiStructure45.dll
- AecXGuiStructure45enu.dll
- AecXGuiStructureLoader.dll
- AecXGuiUtilities45.dll
- AecXGuiUtilities45enu.dll
- AecXGuiUtilitiesLoader.dll
- AecXmlBase45.dll
- AecXmlBase45enu.dll
- AecXProject45.dll
- AecXProjectLoader.dll
- AecXRm45.dll
- AecXSchedule45.dll
- AecXSchedule45.tlb
- AecXSchedule45enu.dll
- AecXScheduleHelp45.dll
- AecXScheduleLoader.dll
- AecXToolClass45.dll
- AecXToolClassLoader.dll
- AecXUIArchBase45.dll
- AecXUIArchBase45.tlb
- AecXUIArchBase45enu.dll
- AecXUIArchBaseHelp45.dll
- AecXUIArchBaseLoader.dll
- AecXUIBase45.dll
- AecXUIBase45.tlb
- AecXUIBase45enu.dll
- AecXUIBaseHelp45.dll
- AecXUIBaseLoader.dll
- AecbCatalog45.dll
- AecbCatalog45enu.dll
- AecbCatalogEditor45.exe
- AecbCatalogEditor45enu.dll
- AecbContentBuilder45.arx
- AecbContentBuilder45enu.dll
- AecbElec45.arx
- AecbElec45enu.dll.uk
- AecbElec45enu.dll
- AecbHost45.arx
- AecbHost45enu.dll
- AecbHvac45.arx
- AecbHvac45enu.dll
- AecbPartDef45.arx
- AecbPartDef45enu.dll
- AecbPipe45.arx
- AecbPipe45enu.dll
- AecbPlumbing45.arx
- AecbPlumbing45enu.dll
- AecbUiBldSrv45.arx
- AecbUiBldSrv45enu.dll
- AecbUiCol45.arx
- AecbUiCol45enu.dll
- AecbXBldSrv45.dll
- AecbXBldSrv45.tlb
- AecbXBldSrv45enu.dll
- AecbXBldSrvHelp45.dll
- AecbXBldSrvLoader.dll
- AecbXPlumbingBase45.dll
- AecbXPlumbingBase45.tlb
- AecbXPlumbingBase45enu.dll
- AecbXPlumbingBaseHelp45.dll
- AecbXPlumbingBaseLoader.dll
- AecbXUIBldSrv45.dll
- AecbXUIBldSrv45.tlb
- AecbXUIBldSrv45enu.dll
- AecbXUIBldSrvHelp45.dll
- AecbXUiBldSrvLoader.dll
- appload.arx
- Battman.arx
- CaptureLines.hdi
- dswhip.dll
- heidi8.dll
- lbsysn.dll
- ladtn.dll
- psizewiz.dll
<Installation Folder>\en-US
- AecDtlDb45.resources.dll
- AecLayerManagerEx.resources.dll
<Installation Folder>\UserDataCache
- adtMenus.cab
- adtRootCat.cab
- absImperial.cab
- absMenus.cab
- absMetric.cab
- absShrdCnt.cab
- absTemplatesm.cab
- absTemplatesu.cab
- absUK.cab
- absUKCat.cab
DRV Folder
- dwfplot8.hdi
- szb8.hdi
- wopengl8.hdi
Autodesk Shared Folder
- acdb16.dll
- AcGe16.dll
- AcSmComponents16.dll
- ad16asm80.dll
- atlst16.dll
- iepictrd80.dll
- modlr16.dll
- AecArchBase45.dbx
- AecArchBase45enu.dll
- AecArchDACHBase45.dbx
- AecArchDACHBase45enu.dll
- AecAreaCalculationBase45.dbx
- AecAreaCalculationBase45enu.dll
- AecBase45.dbx
- AecBase45enu.dll
- AecModeler45.dbx
- AecProjectBase45.dbx
- AecProjectBase45enu.dll
- AecResMgr45.dll
- AecResMgr45enu.dll
- AecResUi45.dll
- AecResUi45enu.dll
- AecSchedule45.dbx
- AecSchedule45enu.dll
- AecScheduleData45.dbx
- AecScheduleData45enu.dll
- AecStructureBase45.dbx
- AecStructureBase45enu.dll
- AecbBldSrv45.dbx
- AecbBldSrv45enu.dll
- AecbCol45.dbx
- AecbCol45enu.dll
- AecbEnumMap45.dll
- AecbEnumMap45enu.dll.uk
- AecbEnumMap45enu.dll
- AecbPlumbingBase45.dbx
- AecbPlumbingBase45enu.dll
Autodesk Shared Thumbnail Folder
- AcDwfThmb16.dll
- AcDwfThmbPrxy16.dll
<Windows Installation
Folder>\assembly
- Autodesk.AEC.Interop.ArchBase.dll
- Autodesk.AEC.Interop.AreaCalculation.dll
- Autodesk.AEC.Interop.Base.dll
- Autodesk.AEC.Interop.DACHBase.dll
- Autodesk.AEC.Interop.Details.dll
- Autodesk.AEC.Interop.Schedule.dll
- Autodesk.AEC.Interop.Structural.dll
- Autodesk.AEC.Interop.UIArchBase.dll
- Autodesk.AEC.Interop.UIBase.dll
- Autodesk.AECB.Interop.Building.dll
- Autodesk.AECB.Interop.Plumbing.dll
- Autodesk.AECB.Interop.UIBuilding.dll