Micro Station File Fixer

User’s Guide

FileFixer

Fix any MicroStation file automatically!

Version 7.2

Axiom International1805 Drew StreetClearwater, Florida 33765727-442-7774 voice727-442-8344 [email protected]

Page 2 FileFixer

Copyright © 1989-1999 Axiom International.All rights reserved.

This document was last modified on 17 March 1999 10:21 AM.

This software and manual are provided “as is” without warranty of any kind, eitherexpressed or implied, including, but not limited to the implied warranties of

merchantability and fitness for a particular purpose. The entire risk as to the quality andperformance of this program is with you. You are advised to test the program thoroughly

before you rely on it. Should the program prove defective, you (and not the seller normanufacturer) assume the entire cost of all necessary servicing, repair or correction. Anyliability of seller or manufacturer of this software will be limited exclusively to product

replacement or refund of the purchase price. Venue for the resolution of any disputerelated to this license or the use of this product shall be Pinellas County, Florida.

Intergraph is a registered trademark of Intergraph Corporation.MicroStation and MDL are registered trademarks of Bentley Systems, Incorporated.

Everlock is a registered trademark of AZ Tech Software, Incorporated.FileFixer, Problem Element Viewer and SafetyCheck are trademarks of Axiom

International.

Table of Contents Page 3

Table of Contents

Chapter 1 — Introduction ----------------------------------------------------------------------9Summary of features and benefits---------------------------------------------------------------------9Fully automatic repair of Words-to-follow errors ------------------------------------------------ 10Fully automatic repair of Words-in-description errors ------------------------------------------ 10Automatic cell level mask repair -------------------------------------------------------------------- 10How to prevent MicroStation users from causing further damage to problem design files11Recovering elements after the End-Of-Design marker------------------------------------------ 11Automatic element range adjustment--------------------------------------------------------------- 12Replacing the Type 9 element------------------------------------------------------------------------ 12Replacing the cell library header-------------------------------------------------------------------- 13System administrator control over search and repair options---------------------------------- 14

Chapter 2 — Installation --------------------------------------------------------------------- 15Installation for DOS and Windows ----------------------------------------------------------------- 15Installation for CLIX ---------------------------------------------------------------------------------- 15Installation for Sun------------------------------------------------------------------------------------- 15

Chapter 3 — Uninstalling -------------------------------------------------------------------- 16Why you might uninstall an Axiom product------------------------------------------------------ 16How to do it --------------------------------------------------------------------------------------------- 16Stop MicroStation from running an Axiom product--------------------------------------------- 16Identifying your Axiom Base Directory----------------------------------------------------------- 16Removing products from the Axiom menu-------------------------------------------------------- 17Removing the Axiom menu -------------------------------------------------------------------------- 17Removing files from your hard-disk---------------------------------------------------------------- 18Axiom.cfg file ------------------------------------------------------------------------------------------ 18

Chapter 4 — Quick Start --------------------------------------------------------------------- 19Your first run -------------------------------------------------------------------------------------------- 19Demo versions ------------------------------------------------------------------------------------------ 21Sample test files ---------------------------------------------------------------------------------------- 21

Chapter 5 — Running FileFixer ------------------------------------------------------------ 22The main dialog box----------------------------------------------------------------------------------- 22The File menu and FileFixer’s resource file ------------------------------------------------------ 22The options menu -------------------------------------------------------------------------------------- 23Help | About--------------------------------------------------------------------------------------------- 23The main command------------------------------------------------------------------------------------ 23Which files ---------------------------------------------------------------------------------------------- 23Report file ----------------------------------------------------------------------------------------------- 24<Start>---------------------------------------------------------------------------------------------------- 24<Display report> --------------------------------------------------------------------------------------- 24

Chapter 6 — The Options Menu ----------------------------------------------------------- 26

Page 4 FileFixer

Application…------------------------------------------------------------------------------------------- 26General…------------------------------------------------------------------------------------------------ 26Load factory defaults…------------------------------------------------------------------------------- 27Repair… ------------------------------------------------------------------------------------------------- 27

Backup/repaired file extensions--------------------------------------------------------------- 27Search… ------------------------------------------------------------------------------------------------- 29

Chapter 7 — Design File Diagnosis ------------------------------------------------------ 30Basic design file diagnosis --------------------------------------------------------------------------- 30Advanced design file diagnosis---------------------------------------------------------------------- 31

Detecting element range problems------------------------------------------------------------ 33

Chapter 8 — Sample Report File ---------------------------------------------------------- 35

Chapter 9 — Design File Repair ----------------------------------------------------------- 39Using yesterday’s backup----------------------------------------------------------------------------- 39Basic design file repair-------------------------------------------------------------------------------- 40Advanced repair of “EOF Not Found” and “I/O” errors---------------------------------------- 40

Setting the filter factor -------------------------------------------------------------------------- 42Enabling BackScanning ------------------------------------------------------------------------ 42Additional data about automatic repair------------------------------------------------------ 43Summary of rules on fixing Words-To-Follow errors: ------------------------------------ 43

How to recover elements after the End-Of-Design marker------------------------------------- 44How to fix complex bit errors------------------------------------------------------------------------ 44How to fix element range errors--------------------------------------------------------------------- 45How to fix FIT problems ----------------------------------------------------------------------------- 46How to fix Words-In-Description errors ----------------------------------------------------------- 46The steps of manual file fixing ---------------------------------------------------------------------- 47

Chapter 10 — Which Error M essages are Generated by Which Option ----- 49Search-type error messages sorted by category -------------------------------------------------- 49Search-type error messages sorted by error number--------------------------------------------- 54Repair-type error messages sorted by category--------------------------------------------------- 60Repair-type error messages sorted by error number --------------------------------------------- 63

Chapter 11 — Batch Mode------------------------------------------------------------------- 67What do we mean by Batch Mode?----------------------------------------------------------------- 67When you should use Batch Mode----------------------------------------------------------------- 67How to run FileFixer in Batch Mode--------------------------------------------------------------- 67Using the “AT” Command under Windows NT 4.0--------------------------------------------- 69

Chapter 12 — SafetyCheck ------------------------------------------------------------------ 70Ensure your design files meet FileFixer’s standards! ------------------------------------------- 70The FileFixer Seal-of-Approval --------------------------------------------------------------------- 70How to test SafetyCheck------------------------------------------------------------------------------ 71What SafetyCheck is used for ------------------------------------------------------------------------ 71Disclaimer ----------------------------------------------------------------------------------------------- 71

Chapter 13 — Miscellaneous --------------------------------------------------------------- 73


Everything you always wanted to know about corruption-------------------------------------- 73What FileFixer won’t do------------------------------------------------------------------------------ 76Don’t kill the messenger ------------------------------------------------------------------------------ 76Does this documentation seem hard to read? ----------------------------------------------------- 77How to test FileFixer ---------------------------------------------------------------------------------- 77Problem Element Viewer------------------------------------------------------------------------------ 78Helpful hints -------------------------------------------------------------------------------------------- 78Give Us Your Tired, Your Poor, Your Corrupted...------------------------------------------------ 80

Chapter 14 — Error Messages ------------------------------------------------------------- 82Operational errors and messages-------------------------------------------------------------------- 82Suspicious Conditions — Usually not Important ------------------------------------------------ 84Minor Errors — Usually Won’t Cause Problems ------------------------------------------------ 96Future Problems — File is in Danger -------------------------------------------------------------109Serious Errors — Problems are Very Possible---------------------------------------------------115Fatal Errors — File is Probably Unusable--------------------------------------------------------127

Chapter 15 — The File List Editor ------------------------------------------------------- 129The File List Editor Dialog Box--------------------------------------------------------------------129The List menu------------------------------------------------------------------------------------------129

File list only (text) ------------------------------------------------------------------------------130All data (binary)---------------------------------------------------------------------------------130List | Import --------------------------------------------------------------------------------------130List | Export--------------------------------------------------------------------------------------131

Files------------------------------------------------------------------------------------------------------131Standard mode-----------------------------------------------------------------------------------131Extended mode ----------------------------------------------------------------------------------132

<Add> ---------------------------------------------------------------------------------------------------133<Remove>----------------------------------------------------------------------------------------------133<Replace>----------------------------------------------------------------------------------------------133Drive -----------------------------------------------------------------------------------------------------133Path ------------------------------------------------------------------------------------------------------134Available files------------------------------------------------------------------------------------------134Directories ----------------------------------------------------------------------------------------------135<Add> ---------------------------------------------------------------------------------------------------135<Remove>----------------------------------------------------------------------------------------------135<OK>----------------------------------------------------------------------------------------------------135<Cancel>------------------------------------------------------------------------------------------------136Select files by date ------------------------------------------------------------------------------------136

Earliest date --------------------------------------------------------------------------------------136Latest date ----------------------------------------------------------------------------------------136<Add by dates>----------------------------------------------------------------------------------136<Remove by dates>-----------------------------------------------------------------------------137

Selected files -------------------------------------------------------------------------------------------137Number of files selected -----------------------------------------------------------------------------137Special note about UNC pathnames---------------------------------------------------------------137Messages------------------------------------------------------------------------------------------------137

Chapter 16 — Glossary --------------------------------------------------------------------- 139

Chapter 17 — New Features and Fixes ------------------------------------------------ 143

Page 6 FileFixer

7.2a — 16 March 1999-------------------------------------------------------------------------------1437.1a — 8 February 1999-----------------------------------------------------------------------------1447.0a — 31 December 1998--------------------------------------------------------------------------1456.8c — 26 November 1998--------------------------------------------------------------------------1466.8b — 1 October 1998------------------------------------------------------------------------------1466.8a — 22 September 1998-------------------------------------------------------------------------1476.7a — 19 August 1998------------------------------------------------------------------------------1476.6d — 10 August 1998------------------------------------------------------------------------------1476.6c — 6 July 1998-----------------------------------------------------------------------------------1486.6b — 27 June 1998---------------------------------------------------------------------------------1486.6a — 11 June 1998---------------------------------------------------------------------------------1496.5f — 22 May 1998---------------------------------------------------------------------------------1506.5e — 2 April 1998----------------------------------------------------------------------------------1506.5c — 15 March 1998-------------------------------------------------------------------------------1506.5b — 31 October 1997-----------------------------------------------------------------------------1516.5a — 28 August 1997------------------------------------------------------------------------------1516.4b — 12 June 1997---------------------------------------------------------------------------------1536.3e — 21 March 1997-------------------------------------------------------------------------------1546.3d — 14 February 1997---------------------------------------------------------------------------1546.2a — 28 August 1996------------------------------------------------------------------------------1546.1a — 12 July 1996----------------------------------------------------------------------------------1546.0c — 2 April 1996----------------------------------------------------------------------------------1556.0b — 21 March 1996------------------------------------------------------------------------------1555.1o — 15 March 1996------------------------------------------------------------------------------1556.0a — 16 January 1996-----------------------------------------------------------------------------1555.1l — 8 June 1995-----------------------------------------------------------------------------------1555.1k — 1 May 1995----------------------------------------------------------------------------------1555.1j — 11 January 1995------------------------------------------------------------------------------1555.1h — 8 November 1994---------------------------------------------------------------------------1565.1g — 25 September 1994-------------------------------------------------------------------------1565.1f — 17 August 1994------------------------------------------------------------------------------1565.1e — 21 July 1994----------------------------------------------------------------------------------1565.1c — 9 July 1994-----------------------------------------------------------------------------------1565.1b — 1 June 1994----------------------------------------------------------------------------------1565.1a — 30 March 1994-------------------------------------------------------------------------------1565.0h — 25 March 1994------------------------------------------------------------------------------1575.0g — 25 February 1994---------------------------------------------------------------------------1575.0e — 10 December 1993--------------------------------------------------------------------------1575.0a — 6 September 1993---------------------------------------------------------------------------1574.8i — 27 July 1993----------------------------------------------------------------------------------1584.8c — 26 March 1993-------------------------------------------------------------------------------1584.8b — 24 March 1993------------------------------------------------------------------------------1584.8a — 23 February 1993---------------------------------------------------------------------------1584.7c — 16 January 1993-----------------------------------------------------------------------------1594.7b — 5 January 1993------------------------------------------------------------------------------1594.7a — 18 December 1992--------------------------------------------------------------------------1594.6c — 22 November 1992--------------------------------------------------------------------------1594.6b — 20 November 1992-------------------------------------------------------------------------1604.6a — 17 October 1992-----------------------------------------------------------------------------1604.5e — 15 November 1992--------------------------------------------------------------------------1614.5d — 6 October 1992------------------------------------------------------------------------------1614.5c — 10 August 1992------------------------------------------------------------------------------1614.5b — 12 July 1992---------------------------------------------------------------------------------161


4.5a — 11 July 1992----------------------------------------------------------------------------------1624.4f — 8 July 1992------------------------------------------------------------------------------------1624.4e — 11 June 1992---------------------------------------------------------------------------------1624.4d — 28 May 1992---------------------------------------------------------------------------------1634.4c — 9 May 1992-----------------------------------------------------------------------------------1634.4b — 18 April 1992--------------------------------------------------------------------------------1634.4a — 5 March 1992--------------------------------------------------------------------------------1634.3a — 10 August 1991------------------------------------------------------------------------------1654.2o — 22 June 1991---------------------------------------------------------------------------------1664.2n — 26 May 1991---------------------------------------------------------------------------------1674.2m — 21 April 1991-------------------------------------------------------------------------------1674.2l — 29 March 1991-------------------------------------------------------------------------------1674.2k — 26 March 1991------------------------------------------------------------------------------1674.2j — 21 March 1991-------------------------------------------------------------------------------1684.2i — 7 March 1991---------------------------------------------------------------------------------1684.2h — 5 February 1991-----------------------------------------------------------------------------1684.2g — 28 January 1991-----------------------------------------------------------------------------1684.2f — 15 January 1991-----------------------------------------------------------------------------1694.2e — 1 January 1991-------------------------------------------------------------------------------1694.2d — 15 December 1990--------------------------------------------------------------------------1694.2c — 13 December 1990--------------------------------------------------------------------------1694.2b — 24 November 1990-------------------------------------------------------------------------1694.2a — 20 October 1990-----------------------------------------------------------------------------1694.1a — 4 October 1990------------------------------------------------------------------------------1714.0c — 29 September 1990-------------------------------------------------------------------------1714.0b — 17 August 1990------------------------------------------------------------------------------1724.0a — 1 June 1990-----------------------------------------------------------------------------------1723.4n — 10 December 1990--------------------------------------------------------------------------1733.4m — 27 May 1990--------------------------------------------------------------------------------1733.4l — 21 April 1990---------------------------------------------------------------------------------1733.4j — 29 March 1990-------------------------------------------------------------------------------1733.4i — 18 March 1990-------------------------------------------------------------------------------1743.4h — 3 March 1990--------------------------------------------------------------------------------1743.4g — 20 January 1990-----------------------------------------------------------------------------1743.4f — 18 January 1990-----------------------------------------------------------------------------1743.4e — 4 January 1990-------------------------------------------------------------------------------1743.4d — 23 December 1989--------------------------------------------------------------------------1743.4c — 14 December 1989--------------------------------------------------------------------------1743.4b — 13 December 1989--------------------------------------------------------------------------1753.4a — 5 December 1989---------------------------------------------------------------------------1753.3a — 5 November 1989---------------------------------------------------------------------------1753.2a — 30 October 1989-----------------------------------------------------------------------------1763.1a — 14 October 1989-----------------------------------------------------------------------------1763.0a — 5 October 1989------------------------------------------------------------------------------176

Chapter 1 — Introduction Page 9

Chapter 1 — Introduction

MicroStation users are fortunate. MicroStation is perhaps the most robust CAD packageever developed. The fact that MicroStation ordinarily saves its working data to disk as itworks spares the MicroStation user from the drawing size limitations and unreliabilitywell known to the users of other CAD packages.

But even the most reliable CAD package in the world sometimes needs a little help. Ahardware problem, a network glitch, an untimely power failure or an error in yourfavorite programmer’s latest MDL application can easily destroy an important design file.Far less dramatic, but no less annoying, are the minor problems that can crop up in adesign file — the element that can’t be deleted, the element that displays oddly as youzoom in on it, elements that seem to magically disappear, the element that just can’t behighlighted no matter how hard you try.

MicroStation comes with a utility called EdG that can be used to repair damaged designfiles. The problem with using EdG for design file repair is fourfold:

1. To be used effectively EdG requires considerable skill and an intimate knowledge ofthe structure of MicroStation design files.

2. Using EdG to repair a design file, even for a skilled user, can take a considerableamount of time.

3. No matter how skilled the operator, EdG is not capable of detecting all of the thingsthat can be wrong with a design file.

4. EdG in semi-skilled hands can cause extraordinary damage.

File corruption (both the obvious kind and the subtle kind) affects nearly everyMicroStation user. No MicroStation shop of any size can afford to ignore it. For over tenyears, MicroStation users worldwide have relied on FileFixer to repair design file andcell library corruption automatically.

FileFixer embodies Axiom International’s hard-won knowledge about MicroStation filecorruption. Read on to see how you can benefit from owning and using FileFixer.

Summary of features and benefits• Works on 2D and 3D design files.

• Works on design files and cell libraries.

• Diagnoses errors that cannot be detected using EdG.

• Tells you the exact element number of the problem element and related elements.

• Automatically recovers elements after an improperly placed End-Of-Design marker.

• The first day you use it, FileFixer can diagnose and repair enough design files andcell libraries to pay back your entire investment.

• And that’s just the beginning — read on!

Page 10 FileFixer

Fully automatic repair of Words-to-follow errors The most serious kind of design file error is a Words-To-Follow error. In computerese, a“word” is not a collection of letters, but rather a fixed number of bits of information. Inthe case of a MicroStation element, a word is 16 bits. In MicroStation, words-to-follow isthe number of words to the next element in the design file. It can be thought of as a“distance”. When an element has a words-to-follow error, the “distance” to the nextelement is wrong. When FileFixer encounters an element with an incorrect words-to-follow value, it uses an artificial intelligence algorithm to determine the right distance tothe next valid element. Like a complex chess-playing program, FileFixer examinesthousands of potential fixes and, using its unique internal scoring system, chooses the onethat produces the most optimum result. A words-to-follow error is the most serious kindof MicroStation file error. Such errors, until repaired, can leave a design file useless.Until the condition is corrected, the design file cannot even be viewed. For each repairedfile, FileFixer produces a report of exactly what was wrong with the file and what it didto correct the problem.

Fully automatic repair of Words-in-description errorsA complex element header is a non-displayable element that groups displayable elementstogether. All complex element headers have a words-in-description. Just as words-to-follow describes how long an individual element is, words-in-description tells how longthe entire complex element is (the header element and all its components). When thewords-in-description of a complex element header is wrong, you can get individualelements left out of cell and complex shape manipulations. Words-in-descriptionproblems can be tricky. Days, weeks, or months can go by without the words-in-description error causing a problem. Then one day, unaware of the problem, the usermanipulates the element containing the error. Suddenly his or her entire design file isgone. Fixing words-in-description errors, even for those experts who know how, is verytedious and time-consuming. FileFixer can automatically repair words-in-descriptionerrors without user intervention.

Automatic cell level mask repairEvery cell has, as part of its definition, a list of the levels on which the cell has elements.This list is called the “cell level mask”. If this list gets out of sync with the actualelements in the cell, serious problems can result. For example, if the cell level maskshows elements on levels 6 and 9, but the cell actually has elements on levels 6 and 15,the elements on level 15 might not display, or they might not plot, or they might not beselectable. FileFixer can scan design files and cell libraries for cells with this problemand automatically regenerate the cell level mask for those cells that need it.


How to prevent MicroStation users from causing furtherdamage to problem design files

When MicroStation detects a design file with severe damage, it pops up a window saying,“End of file missing, attempt repair?”

If the user selects “No.” Everything is okay. FileFixer will be able to recover all or mostof the damaged design file. However, if an inexperienced user answers “yes.” All data inthe design file may become unrecoverable by any process!

This is because MicroStation fixes this problem by putting an end-of-file marker beforethe first corrupted element it finds. If that is only 10% into the file, you will lose 90% ofyour work!

The solution is to make the following simple change to MicroStation:

1. Use a simple text editor like Notepad to create a text file called (for example)c:\eofmsg.txt. This file should contain something like, “This file is severelycorrupted. Run FileFixer on it immediately!”

2. Start up MicroStation.

3. Select Workspace | Configuration | Operation.

4. Set the “No EOF Message” setting to c:\eofmsg.txt.

5. Test the message by opening the file in the FileFixer directory call 1badwtf.dgn andsee if it displays the message, as you want.

6. Adjust the message in the text file until it displays the way you want.

7. Do the above on each workstation in the office that has MicroStation 95 loaded. Youmay want to put the eofmsg.txt file on a shared disk to make the process easier.

This simple procedure could save you tens of thousands of dollars a year in design filedamage. Axiom technical support staff urge you to make this change right away.

If you have any questions about this procedure simply e-mail [email protected].

Recovering elements after the End-Of-Design markerSometimes elements in a design file will seem to disappear. Many times the missingelements are still there in the design file, but an unwanted end-of-design marker wassomehow written into the middle of the file. Since any elements after the end-of-design

Page 12 FileFixer

marker are now “hidden” from MicroStation, these elements become permanently lost.The repair of this error requires scanning past the unwanted end-of-design marker,finding all the valid elements and then placing a new end-of-design marker at the end ofthe last non-corrupt element. This method retains as many non-corrupt elements aspossible. FileFixer does all of this automatically.

Automatic element range adjustment It is not known exactly how element ranges get corrupted. One type of element rangecorruption comes from the fact that IGDS and MicroStation use slightly differentalgorithms for cell placement. IGDS ignores the element ranges stored in the cell libraryand recalculates the range of each element every time the cell is placed. MicroStationuses the range information stored in cell libraries. This makes cell placement faster andmore efficient, but can propagate element range errors into many design files. The rangeof an element is given by the lower-left and upper-right coordinates of the smallest boxthat will contain the element. Element range errors can cause elements not to display orbe selectable. Elements with this type of error may be accidentally left out of plots andfence manipulation commands. Some programs handle text and text node ranges in a waythat causes range errors. For example, with most fonts a “W” character takes up morespace than an “i”. FileFixer uses this information to set the range of your text elements asprecisely as possible. By opening and analyzing the user’s font library, FileFixerdetermines the size and spacing of each individual character in text elements and uses thisinformation to correct the element ranges.

Replacing the Type 9 element

The type 9 header element is the first element in a MicroStation design file. It stores avariety of vital information such as the largest graphic group number in the file or thehighest text node number in the file.

Unfortunately, most MicroStation users at one time or another have encountered a“weird” design file. A “weird” design file can be described as one whose elements get


rotated, mirrored or disappear altogether when a user zooms in. Other weird files haveregular line segments turn into infinite length lines. Still others have views that displaynothing, no matter what is done. Such oddities (and a variety of other problems) aretypically caused by an error in the type 9 element of the design file.

In the past, some of the more experienced MicroStation users have realized this and haveattempted to “transplant” a type 9 from a healthy design file into an ailing design file. Ifnot done properly, this can have disastrous consequences. The real danger is that such aremedy will appear to have worked. Unfortunately, the user may have introduced a newand much more serious problem that won’t show up until weeks or months later.

For example, let’s say that the “donor” design file has fewer graphic groups than the“recipient” design file. If the graphic group number counter (GRAFIC) in thetransplanted file is not properly updated, the recipient design file may appear to beperfectly cured. But the next time the user tries to create a new graphic group, instead ofcreating a new group he will just be appending to a graphic group that already exists.Usually, he or she won’t know this is happening.

These are called “cross-linked graphic groups”. This means two or more graphic groupsshare the same graphic group number. The two (ill-fated) graphic groups will bemanipulated simultaneously whenever the graphic group lock is on. Since they may bewidely separated in the design file, it is easy to unintentionally delete or alter one group,off screen, while the user manipulates the other on screen.

When FileFixer “transplants” a type 9, it always scans the recipient design file lookingfor the highest graphic group number and the highest text node number. This informationis then transferred to the “transplanted” type 9, allowing it to operate in harmony with itsnew host.

Replacing the cell library header

With FileFixer (version 6.4b or later) you have the ability to replace the cell libraryheader. Previously if the cell library header got corrupted you would have to copy thecells from the corrupted cell library to a new cell library, otherwise, you couldn’t use it.

Page 14 FileFixer

System administrator control over search and repair options You can disable having the search and repair options being changed by other users inyour office. This can be done only under any operating system or a network that allowsyou to have file permissions. When FileFixer is installed, the file “fixer.sec” is installedin the same directory as the file “fixer.ma”. Once you have set up all the search and repairoptions that you want everybody to use and you save the options in a resource file(fixer.rsc for example) then you need to set the permissions of the fixer.sec file so that itis not readable by anybody else. When the fixer.sec file cannot be read then the searchand repair options from the Options pull-down menu on the FileFixer dialog box cannotbe accessed.

Chapter 2 — Installation Page 15

Chapter 2 — Installation

Installation of FileFixer is quick and easy. Just follow the instructions below for theoperating system on which it is being installed.

Installation for DOS and Windows Insert the distribution diskette in your floppy drive.

From within MicroStation enter the command:

MDL LOAD A:\INSTALL

The installation routine will guide you through the process of setting up FileFixer onyour computer.

Installation for CLIXNote: The FileFixer files are shipped to you on a DOS floppy formatted floppy. Use thedtu utility to copy them to your workstation. Don’t forget the -p option for the dtucommand.

Copy the install files to a temp directory:

dtu -p "a:install.*" /tmp

From within MicroStation enter the command:

mdl load /tmp/install

The installation routine will guide you through the process and set up FileFixer on yourmachine.

Installation for Sun Insert the distribution diskette in the floppy drive and mount it by entering the followingcommand at the operating system prompt:

volcheck

From within MicroStation run the install program by entering the command:

mdl load /floppy/floppy0/install

The installation routine will guide you through the process and set up FileFixer on yourmachine.

Note: If your system has been customized with a mount command other than volcheckor a mount point other than /floppy/floppy0, contact your system administrator.

Page 16 FileFixer

Chapter 3 — Uninstalling

Why you might uninstall an Axiom productThere are a few reasons you may want to uninstall an Axiom product:

1. You have run a demo and want to remove it from your computer.

2. You have moved the product to another computer and need to remove the productfrom the original computer.

3. You have a site or corporate license and want your users to have access to only someof the many Axiom products that you have already installed on their computers.

There may be other reasons.

How to do itThere are three basic stages to un-installing an Axiom product:

1. Stopping MicroStation from trying to automatically run the Axiom product.

2. Removing the Axiom product from MicroStation’s Axiom menu or entirelyremoving the Axiom menu from MicroStation’s menu bar.

3. Removing the Axiom files from your hard disk.

Stop MicroStation from running an Axiom productSome Axiom products such as Version Manager and PopMenu are usually set up to runautomatically whenever MicroStation is started up. You can stop this from happening bygoing into MicroStation | Workspace | Configuration and looking for the variableMS_DGNAPPS. Edit the value of this variable and remove any references to the Axiomproduct that you no longer want to run automatically, when running MicroStation. ExitMicroStation, re-start MicroStation, and check that MS_DGNAPPS is clear of thatAxiom product name.

Identifying your Axiom Base DirectoryYou will need to identify where your Axiom Base Directory is. Go into the MicroStationconfiguration dialog box (in MicroStation 95 it is “Workspace | Configuration”) and lookfor the “AXI” configuration variable. The value of AXI will be your Axiom BaseDirectory. It is usually something simple like “c:\win32app\axiom\”.

Chapter 3 — Uninstalling Page 17

Removing products from the Axiom menuThis is an optional step. If you want to skip this step, go on to the section “Removing theAxiom menu” on page 17. This step is included here because some customers wanted tobe able to “customize” their Axiom menu to exclude some programs from some of theircomputers. The Axiom menu is found on the MicroStation menu bar and looks like this:

To remove a product from the Axiom menu, edit the file “aximenu.txt” (found in theAxiom Base Directory) and remove the number sign (“#”) from the beginning of the linethat refers to the product you want to remove from the Axiom menu.

A small sample from the “aximenu.txt” file looks like this:

#Active~Zactivez#~CellManagercellmgr#CellRa~ndomizercellrand

and a sample of the same file now modified to show only CellManager is:

Active~Zactivez#~CellManagercellmgrCellRa~ndomizercellrand

If you have multiple Axiom products and are removing only one product, you don’t haveto remove this product’s name from the Axiom menu. If you remove just that program’sfiles from your disk (see section “Removing files from your hard-disk” on page 18) butleave the entry on the Axiom menu, and a user selects that program off the Axiom menu,they will get a text-style dialog box which will describe the product. The user will not getany errors or failures.

Removing the Axiom menuIf you intend to remove all Axiom products from your computer, you would want to dothis step. The “Axiom menu” is actually a program that is run whenever MicroStation isstarted up. You can stop this menu from appearing in MicroStation by going intoMicroStation | Workspace | Configuration and looking for the variable MS_DGNAPPS.Edit the value of this variable and remove the entry “aximenu.ma”. When you have donethis, next time you start MicroStation the menu bar will look like this:

Notice that the word “Axiom” no longer appears to the right of “Help”.

Page 18 FileFixer

Removing files from your hard-diskIf you are removing an Axiom product, you’ll probably want to delete that product’s filefrom your hard-disk drive.

Go to your Axiom Base Directory by using Windows Explorer or File Manager or DOSor something similar. Each Axiom product is in its own directory under the Axiom BaseDirectory.

For example, CellManager is in the “cellmgr” subdirectory, and Cell Randomizer is inthe “cellrand” subdirectory. To delete the files of an individual Axiom product, justdelete its specific subdirectory. To delete all the files of all Axiom products, delete theentire Axiom Base Directory and all of its product subdirectories.

If you have other Axiom products but are removing one product, you don’t need toremove this product’s name from the Axiom menu. If you remove that program’sdirectory of files from your disk but leave the entry on the Axiom menu, and a userselects that program off the Axiom menu, they will get a text-style dialog box which willdescribe the product. The user will not get any errors or failures.

Axiom.cfg fileIf you are removing all Axiom products from your computer and if you are runningMicroStation 95 or MicroStation SE, you should also delete the file “axiom.cfg” fromMicroStation’s …\config\appl\ directory. This step will also delete the MicroStation AXIconfiguration variable.

Chapter 4 — Quick Start Page 19

Chapter 4 — Quick Start

Once FileFixer has been installed as described above you are ready to run it.

Your first runIn MicroStation, open the sample file “badele.dgn” that was installed with FileFixer.Now select “FileFixer” from the Axiom pulldown menu in MicroStation. You will seethe first dialog box of FileFixer:

Select the “Options” menu and then select the “Load Factory Defaults…” option:

You will see the following dialog box:

Press <OK> to continue.

Now press the <Start> button. You will see FileFixer working away with this dialog box:

Page 20 FileFixer

When FileFixer is complete, it will display this dialog box:

Press <OK> to remove that dialog box. Then press the <Display Report> button to seeyour report file. It should look similar to this:

Of course your report file is a simple ASCII report file and can be printed on most anyprinter.

You have now run FileFixer for the first time. It is that simple!

Chapter 4 — Quick Start Page 21

Demo versionsThe demonstration version of FileFixer will only process the first 100KB of each file.About half the errors are not reported.

Sample test filesThere are several sample files that come with FileFixer that you can use while learningFileFixer. Badtype.dgn, badlevel.dgn and badwtf.dgn are just a few of the many filesincluded with FileFixer’s installation.

Page 22 FileFixer

Chapter 5 — Running FileFixer

Once FileFixer has been installed as described above, then select FileFixer from theAXIOM pulldown menu on the MicroStation menu bar.

FileFixer is so easy to use you’ll probably be able to diagnose and repair design fileswithout even reading the rest of this documentation. You will, however, find thatFileFixer is more valuable to you if you have a greater understanding of the features itoffers. When you get a chance, please take the time to read this documentationthoroughly.

The main dialog box

This is the main dialog box of FileFixer. You will see more options depending on yourselection of the main “tool” which in this picture shows as “Automatic Design FileRepair”.

The File menu and FileFixer’s resource file

The search and repair options are saved in this file. The default file is fixer.rsc and isinstalled in the same directory as fixer.ma.

On the File pull-down menu you can create a new resource file, open a different resourcefile, save the current resource file or save the current resource file with a new name.

Chapter 5 — Running FileFixer Page 23

The current resource file name is displayed as the top item in the File Menu.

Note: Beginning with version 6.4b FileFixer no longer automatically saves the searchand repair options to the resource file when FileFixer is unloaded. You now need to do itfrom the File pull-down menu.

The options menu

For more information about these options, see “Chapter 6— The Options Menu” startingon page 26.

Help | About

The Help|About option displays the FileFixer product, company, and license information.

The main command

Use this button to select a main FileFixer command function. The default is “AutomaticDesign File Repair”. Other options are:

Which files

This is where you specify which file you want FileFixer to process.

Page 24 FileFixer

You can use the <Edit List…> button to select an individual file or a list of files to beprocessed. For detailed information on the File List Editor dialog box that will appear,see Chapter 15 — The File List Editor starting on page 129.

The “Search for Problems” command will examine any set of design files you select. Toselect a single design file, just enter that file’s name. You can also select groups of filesusing wildcards. If you add /S after a filename wildcard, the subdirectories under thespecified directory will also be searched for matching filenames. For example D:\*.DGN/S would analyze every design file on disk D:. You can also enter an at sign (“@”)followed by the name of a file that contains a list of design file names, one file name perline.

@C:\AXIOM\LISTFILE.LIS

If you entered the above in the “Which files?” field on the FileFixer dialog box, all thefile names specified in the LISTFILE.LIS file will be processed.

Report file

This is where you specify which file FileFixer should put the output report into. Use the<Select…> button to fine tune your report file options with this dialog box:

<Start>

Press the <Start> button when you have selected all of your options and are ready to haveFileFixer process your file(s).

<Display report>

Chapter 5 — Running FileFixer Page 25

Press the <Display Report> button to show a dialog box with FileFixer’s output report.Since the output file is a simple ASCII file, you can use any editor to view the file. Thisbutton is provided here for your convenience.

Page 26 FileFixer

Chapter 6 — The Options Menu

The Options Menu has several high-powered functions within it:

All are described below.

Application…This is where you select FileFixer options that pertain to specific applications. Forexample, the Modeler application.

General…This is where you specify the most general option of all:

Chapter 6 — The Options Menu Page 27

Load factory defaults…This function will reset all of FileFixer’s options back to a “factory default”. These arethe options that your FileFixer came with when you first installed it. This is useful if youhave been changing several options and want to restart afresh.

Repair…This is where you specify FileFixer’s repair-specific options. Each item in the left list(category) has its own specific options which you will see on the right side of the dialogbox as you move through each catagory.

Backup/repaired file extensions FileFixer has the option to work on the original design while first backing up the designfile, or to create a repaired design file while leaving the original unchanged. Using eitherfeature you have the ability to specify the final extension and directory where the backupfile or repaired file will be placed.

This option is under Design File on the repair option menu. After specifying whether towork on the original design file or to create a repaired file you will be prompted for theextension name and the directory where to place the backup file or repaired file.

Page 28 FileFixer

When specifying the extension FileFixer will use there are a couple of special symbols,asterisk “*” and question mark “?”.

Note: When using FileFixer in Demo Mode with the Backup file option set, design files(.dgn’s) that are larger than the Demo limit of 102,400 bytes are not restored. However abackup of the design file is made.

Asterisk “*” The asterisk is a way of copying any character of the original file extension to the backupfile extension or the repaired file extension. For example:

Original design file name: axiom.dgn

Backup or repaired file extension: *kp

Final backup or repaired file name: axiom.dkp

Question mark “?” This allows you to create a variable extension. A variable extension is defined as anextension that can change depending upon which files already are created. Let’s say youhave two design files that have the same name but have a different extension,“axiom.f01” and “axiom.f02”. If you had a fixed backup extension, say “bkp” then youwould only have the backup file “axiom.bkp” after both files were backup. The file“axiom.f01” would backup to “axiom.bkp”, and the file “axiom.f02” would also backupto “axiom.bkp”. This means that the backup file for “axiom.f02” would overlay on top ofthe backup file for “axiom.f01” and you would lose the backup file for “axiom.f01”.

The backup extension can have a special character “?” (question mark) at the end of it,which would be converted into an integer digit when the backup extension is created.Lets again look at our earlier example of two files, “axiom.f01” and “axiom.f02”, beingbacked up, but this time the backup extension is “bk?”. The backup files would now be

Chapter 6 — The Options Menu Page 29

named “axiom.bk1” and “axiom.bk2”. If these files were again backed up then theywould be named “axiom.bk3” and “axiom.bk4”, as the “axiom.bk1” and “axiom.bk2”files already exist. Once the file “axiom.bk9” was created then you would get an errormessage telling you that no more valid backup extensions are available.

File extension limitations You can use up to three question marks in the extension “???”. This would allow up to999 backup files.

The backup file extension is limited to three characters on all platforms.

The only other restriction is that the question marks must be at the end of the extension.This means that the extension “b?k” is not valid as a variable extension.

Search…This is where you specify FileFixer’s search-specific options. Each item in the left list(category) has its own specific options which you will see on the right side of the dialogbox.

Page 30 FileFixer

Chapter 7 — Design File Diagnosis

The next several sections of this document describe FileFixer’s Search for Problemscommand.

There are two situations in which you will probably use the Search for Problemscommand. One situation might be called “PREVENTIVE MAINTENANCE” mode. Inthis mode you have FileFixer scan a large group of design files looking for anything thatmight cause subtle (or not so subtle) problems with your design files. You could thencorrect these problems before your operators encountered them and wasted a lot of timetrying to figure out what was going on.

When a file is undisplayable, not making it through some translator or plotting software,or is behaving oddly you would use FileFixer in “EMERGENCY” mode. The intentionhere would be to quickly discover what is wrong with this one file so that it can berepaired on an immediate basis.

Basic design file diagnosis When someone tells you he spent 4 hours repairing a design file with EdG, he’s actuallytold a lie of sorts. The truth is, usually, that he spent 3 hours and 59 minutes using EdG tofigure out what was wrong with his design file, and 1 minute with the modify commandactually fixing it!

The Search for Problems command addresses the real problem with using EdG to repairdesign files: finding the bug. Using the report generated by the FileFixer’s Search forProblems command, most design file problems can be corrected in very little time.

The purpose of the FileFixer’s Search for Problems command is to detect the followingbroad categories of errors:

• FATAL ERRORS. These are errors that completely prevent the design file frombeing displayed at all.

Chapter 7 — Design File Diagnosis Page 31

• FUTURE ERRORS. Design files don’t always get “sick” all of a sudden. Certainconditions in a design file can indicate that its “resistance” is down or that it issusceptible to future corruption. The Search for Problems command can detect suchconditions so you can correct the file before the problem becomes more serious.

• COMPATIBILITY ERRORS. It is not uncommon for a design file to work correctlywith one piece of software (such as MicroStation), yet have problems with anotherpiece of software (such as a translator). The Search for Problems command can tellyou when a design file is not “ANSI standard” or that certain programs may haveproblems reading this design file.

Advanced C programmers might note a similarity between the FileFixer’s Search forProblems command and the “lint” utility that locates errors in C programs. (Now if wecould only get “lint” to automatically repair our C programs the way FileFixer repairs ourdesign files, we’d have it made.)

Advanced design file diagnosis Many users will never need to use the advanced customizable analysis features ofFileFixer. But for those expert users who want greater control over exactly what errorsFileFixer searches for, FileFixer provides some special controls. These are accessedunder the Options menu by selecting “Search…”.

Tip: Note that these settings also affect the Automatic Design File Repair command.Under certain circumstances, elements that fail the tests established by these settings,may be omitted from the repaired version of the design file. This may or may not be whatyou want.

Telling FileFixer what types of application elements you use

This feature is found at “Options | Search… | Type/Level”. FileFixer contains an internaltable telling it how common each application element type is. For example, type 51s(APDP elements) are relatively common, while type 101s (unassigned) are nearly non-existent. The table uses broad averages, taking into account all IGDS and MicroStationusers as a whole. The application element type(s) used in your design files may have avery low frequency value. This could cause three problems:

1) The FileFixer’s Search for Problems command may list these elements withwarnings or errors.

2) These elements may be left out of your repaired files.

3) FileFixer will be able to fix Words-To-Follow errors more accurately if it knowsmore specifically what element types to expect at your site, instead of relying entirelyon its internal table.

Any application elements you use, even if they are fairly common ones, should be listedwith this question.

Page 32 FileFixer

Telling FileFixer what types of elements you NEVER use

This feature is found at “Options | Search… | Type/Level”. Telling FileFixer whichelement types it should never find in a design file at your site will:

1) enable FileFixer to flag such unwanted elements with warnings, and

2) help FileFixer perform better repairs of your design file.

Telling FileFixer what level displayable elements can appear on

This feature is found at “Options | Search… | Type/Level”. You can also tell FileFixer onwhich levels you allow displayable elements. Whenever FileFixer finds a displayableelement on a level you haven’t listed, it writes a message to its report file.

Assume MicroStation is using 127 levels?

This feature is found at “Options | Search… | Design File”. Versions of MicroStationafter 4.0 support up to 127 levels. (As of October 1991, this is an undocumented featureused principally in electronics applications.) This is accomplished using the previouslyunassigned Reserved-Bit in the first word of the element.

Turning this option ON does the following:

1) turns off Reserved-Bit checking, and

2) uses the Reserved-Bit as part of the levels indicator.

Don’t forget that if you want elements above level 63 not to be flagged as errors, youmust also change the “acceptable levels” field on the “Type/Level” screen.

Kind of errors to be reported on

This feature is found at “Options | Search… | Design File”. FileFixer assigns a severitylevel to each error it detects. The most severe errors are called “Fatal Errors”. The leastsevere are called “Suspicious Conditions”. By default, all possible errors (suspiciousconditions and worse) are reported. If you want FileFixer to ignore the less serious errorconditions, modify this option. Valid selections are:

Chapter 7 — Design File Diagnosis Page 33

Setting the minimum unused (empty) design file border

This feature is found at “Options | Search… | Element”. Some plotting software has beenshown to be problematic when plotting design files with elements near the edge of thedesign plane. FileFixer can help you detect elements that are near the edge of the designplane. The Minimum Unused Border setting is used to determine how close an elementmust be to the edge of the design plane before it is flagged as a possible problem byFileFixer. A Minimum Unused Border of 1% means that if an element comes within 1%(of the entire size of the design plane) to the edge of the design plane, it will be flaggedwith a warning in the FileFixer output report file.

Detecting element range problems FileFixer can detect errors in the range block of all displayable element types. In fact,FileFixer’s ability to detect element range errors is more sensitive than IGDS’s orMicroStation’s ability to set the element range.

The range of an element (X-High, X-Low, Y-High, Y-Low, Z-High, and Z-Low) can beeither too small or too large. The range block being too large is a relatively minor error.MicroStation will run less efficiently, but in most cases no serious errors will occur. Therange of an element being too small, however, is a more serious problem. In this case,elements may become unselectable or undisplayable, and may be improperly omittedfrom plots and fence manipulation commands.

Needless to say each part of the range block (X-High, X-Low, Y-High and Y-Low) canbe off by a lot or off by a little. FileFixer measures the amount of error with a fractionexpressed as a percentage. The numerator of the fraction is the number of UORs therange block component is off by. The denominator is the correct size of the range blockin the specified dimension. Example:

Let’s say the range block should be for (0, 10) in the x direction and (20, 40) in the ydirection. The range stored in the element is (-1, 8) in the x direction and (21, 40) in the ydirection. The percentage errors for each range block component would be:

X-Low +10% (position of X-Low makes the box too big)

X-High -20% (position of X-High makes the box too small)

Y-Low -5% (position of X-Low makes the box too small)

Y-High 0% (Y-High is exactly what it should be) For the purposes of determining the error percentage, the minimum range block size isassumed to be 1 UOR. This adjustment is needed so that zero area/volume elements suchas points do not generate divide by zero errors.

Element ranges are used primarily as a filter by design file scanning hardware andsoftware. They help the system quickly weed out elements that are nowhere near the areaof interest. (For example, when trying to snap to “Chicago” on a map of the USA, therewould be no reason to do a detailed analysis of whether “New York” should behighlighted.) Once an element passes the “filter”, it still must undergo additional testsbefore it is snapped to or included in a fence contents manipulation commands. Theseaddition tests are why absolutely precise element range blocks are not vital.

Page 34 FileFixer

Although FileFixer will let you verify element ranges down to a tolerance of 0 UORs,doing so is not recommended. Too many elements that are functionally normal will beflagged as problem elements. The lowest you should ever set FileFixer’s element rangetolerance is .0001 (and even that’s EXTREME). Only when the element range is 20% ormore too small are you likely to encounter any problems with an element.

At present, FileFixer does not detect or correct the range of type 7 (text node) elementswhen they contain no text elements. The range of other type 7 elements are verified andcorrected. Range errors in (raster header) elements are also not detected or corrected.

Chapter 8 — Sample Report File Page 35

Chapter 8 — Sample Report File

FileFixer 7.2aCopyright (c) 1985-1992 David Greenbaum.Copyright (c) 1992-1999 Axiom International.Saturday, 23 January 1999 6:15 pm

Files: c:\dgn\*.dgnMode: Search Mode

c:\dgn\1badwtf.dgn *** -- No seal-of-approval was found. 4 -- WTF for this type 5 with A-bit off should be 31, not 34. [354]. 5 -- WTF for this type 5 with A-bit off should be 31, not 34. [354]. 6 -- WTF for this type 5 with A-bit off should be 31, not 34. [354]. 7 -- WTF for this type 5 with A-bit off should be 31, not 34. [354]. 8 -- WTF for this type 5 with A-bit off should be 31, not 34. [354]. 9 -- WTF for this type 5 with A-bit off should be 31, not 34. [354]. 10 -- WTF for this type 5 with A-bit off should be 31, not 34. [354]. 11 -- WTF for this type 5 with A-bit off should be 31, not 34. [354]. 12 -- WTF for this type 5 with A-bit off should be 31, not 34. [354]. 13 -- WTF for this type 5 with A-bit off should be 31, not 34. [354]. 15 -- Siamese element. WTF should be 31, not 19. [758]! 20 -- WTF for this 2D type 11 with A-bit off should be 61, not 62. [754]! 21 -- Unwanted element type <type 0> detected. [380]! 22 ~~ Fatal error. File ended before element did. [997]! *** -- Seal-of-approval not written because end-of-file not found.This file originally had 21 elements. FileFixer found 14 errors in it.

c:\dgn\3derror.dgn *** -- No seal-of-approval was found. 4 -- 3D only element <type 19> in 2D file. [776]! 5 ~~ Complex bit not set for component of type 19 (4). [703]. 6 -- Complex element (4) doesn't end on element boundary. [520]. 1 -- GRAFIC is 108, but it should be 109. [534]. 1 -- CANODE is 19, but it should be 1. [135]. 1 -- Design file range is low=867000, -744000, -2147483648, high=2304000, 222000, 2147483647 should be low=0, 0, 0, high=0, 0, 0. [111]. *** -- Seal-of-approval showing 6 errors added/updated.This file originally had 5 elements. FileFixer found 6 errors in it.

c:\dgn\canodehi.dgn *** -- No seal-of-approval was found. 1 -- CANODE {65111} is suspiciously high. [126]. 1 -- CANODE is 65111, but it should be 1. [135]. 1 -- Design file range is low=-66000, -62000, -2147483648, high=87000, 63000, 2147483647 should be low=0, 0, 0, high=0, 0, 0. [111]. *** -- Seal-of-approval showing 3 errors added/updated.This file originally had 4 elements. FileFixer found 3 errors in it.

c:\dgn\grafic0.dgn *** -- No seal-of-approval was found. 1 -- GRAFIC should never be 0. [329]. 1 -- GRAFIC is 0, but it should be 1. [534]. 1 -- CANODE is 65111, but it should be 1. [135]. 1 -- Design file range is low=-66000, -62000, -2147483648, high=87000, 63000, 2147483647 should be low=-31916, -14664, -2147483648, high=28102, 8267, 2147483647. [111]. *** -- Seal-of-approval showing 4 errors added/updated.This file originally had 11 elements. FileFixer found 4 errors in it.

c:\dgn\grafichi.dgn *** -- No seal-of-approval was found. 1 -- GRAFIC {65000} is suspiciously high. [128]. 4 -- Font 0 text "1" range is off by 269.1%. [325]. 5 -- Font 0 text "W" range is off by -50.1%. [325]. 6 -- Font 1 text "i" range is off by 2092.9%. [725]. 7 -- Font 1 text "W" range is off by -50.1%. [325]. 8 -- Font 41 text "i" range is off by 252.4%. [325]. 9 -- Font 41 text "W" range is off by -49.9%. [325]. 1 -- GRAFIC is 65000, but it should be 65001. [534]. 1 -- CANODE is 2, but it should be 1. [135]. 1 -- Design file range is low=-66000, -62000, -2147483648, high=87000, 63000, 2147483647 should be low=-34250, -20000, -2147483648, high=40088,

Page 36 FileFixer

27000, 2147483647. [111]. *** -- Seal-of-approval showing 10 errors added/updated.This file originally had 10 elements. FileFixer found 10 errors in it.

c:\dgn\missing9.dgn *** -- No seal-of-approval was found. 1 -- Can't determine file type. User picked 2D design file. [701]. 2 -- 2nd element of design file is not active type 8. [713]. 3 -- 3rd element of design file is not active type 10. [714]. 7 -- Text element has zero characters. [390]. 8 -- Text element has zero characters. [390]. 9 -- Text element has zero characters. [390]. 10 -- Text element has zero characters. [390]. 11 -- Text string overflows element length. [560]. 12 -- Text string overflows element length. [560]. 13 -- Text element has zero characters. [390]. 14 -- Possible 3D type 3 with A-bit off found in 2D file. [362]. 15 -- Text string overflows element length. [560]. 16 -- Possible 3D type 3 with A-bit off found in 2D file. [362]. 17 -- Possible 3D type 3 with A-bit off found in 2D file. [362]. 18 -- Text element has zero characters. [390]. 19 -- Possible 3D type 4 with A-bit off found in 2D file. [362]. 20 -- Possible 3D type 4 with A-bit off found in 2D file. [362]. 21 -- Possible 3D type 4 with A-bit off found in 2D file. [362]. 22 -- Possible 3D type 6 with A-bit off found in 2D file. [362]. 23 -- Possible 3D type 6 with A-bit off found in 2D file. [362]. 24 -- Possible 3D type 6 with A-bit off found in 2D file. [362]. 25 -- Possible 3D type 6 with A-bit off found in 2D file. [362]. 26 -- Possible 3D type 6 with A-bit off found in 2D file. [362]. 27 -- Possible 3D type 6 with A-bit off found in 2D file. [362]. *** -- Seal-of-approval showing 24 errors added/updated.This file originally had 28 elements. FileFixer found 24 errors in it.

REPORT SUMMARY -- The number on the left indicates how many of each kind oferror were found in this report: 4 -- Design file range (DFRANG) is incorrect. [111]. 1 -- CANODE is suspiciously high. [126]. 1 -- GRAFIC is suspiciously high. [128]. 4 -- CANODE is higher than it should be. [135]. 5 -- Range of text element is incorrect. [325]. 1 -- GRAFIC should never be 0. [329]. 10 -- Words-To-Follow warning. [354]. 12 -- Possible 2D element in 3D file or vice versa. [362]. 1 -- Illegal element type detected. [380]. 6 -- Text element has zero characters. [390]. 1 -- Complex element doesn't end on element boundary. [520]. 3 -- GRAFIC is dangerously low. [534]. 3 -- Text string overflows element length. [560]. 1 -- Can't tell if file is 2D or 3D. [701]. 1 -- Complex bit is not set for a component element. [703]. 1 -- Second element of design file is not an active type 8. [713]. 1 -- Third element of design file is not an active type 10. [714]. 1 -- Range of text element is incorrect. [725]. 1 -- Words-To-Follow error. [754]. 1 -- Siamese element. Words-To-Follow is too small. [758]. 1 -- 3D only element found in 2D file. [776]. 1 -- Fatal error. File ended before element did. [997].

6 of the 6 files analyzed are in danger.

Search Options: Y -- 2D element found in 3D file Y -- 3D element found in 2D file Y -- A-bit is turned on, but there's no attribute linkage Y -- Active angle is invalid (-360 <= angle <= 360) Y -- Active level is out of range Y -- An EDF extends past the end of the text string Y -- An EDF has a length of zero Y -- An EDF has an unrecognized justification Y -- An EDF is out of sequence Y -- Arc or ellipse axis is too long Y -- Arc or ellipse origin is off the design plane Y -- Arc's sweep angle is invalid (-360 <= angle <= 360) Y -- B-spline component is not part of a b-spline header Y -- B-spline has illegal number of one type of component Y -- Bad element type-level combination N -- Bad text height to width or width to height ratio Y -- CANODE not equal to highest text node number plus 1 Y -- Cell header's diagonal is invalid

Chapter 8 — Sample Report File Page 37

Y -- Cell is nested within itself Y -- Cell library header length must be 23 words Y -- Complex bit is off for a component element Y -- Complex bit is on for a non-component element N -- Complex bit is on for an element with database linkage Y -- Complex element contains disallowed element type Y -- Complex header range doesn't match components' range Y -- Component graphic group doesn't match header Y -- Component on different level than its header Y -- Component symbology doesn't match header Y -- Curve or conic with consecutive identical vertices N -- Curves and conics within complex shapes and curves Y -- Dangerous element (WTF may be unreliable) N -- Deleted phantom element detected Y -- Deleted type 9, 8 or 10 detected Y -- Design file header length must be 766 words Y -- Design file range doesn't match the range of the graphical elements N -- Don't delete the seal-of-approval if it exists Y -- Duplicate reference file attachment encountered Y -- Duplicate reference file logical name encountered Y -- Duplicate shared cell or library cell definition Y -- Element class is illegal Y -- Element has tag linkage but no matching type 37 tag element was found Y -- Element is locked Y -- Element is too close to edge of design plane Y -- Element of this type should never have its A-bit set Y -- Elements in b-spline are in wrong sequence Y -- Error in type 9 header element Y -- Extra design file header (type 9 level 8) Y -- File size is not a multiple of 512 bytes Y -- First and last vertex of type 6 shape don't match Y -- GGBASE (graphic group base number) is greater than GRAFIC Y -- GRAFIC is not equal to highest graphic group plus 1 N -- Graphic group number equals or exceeds GRAFIC Y -- H-bit (orphan flag) not set in orphan cell Y -- H-bit is set when it shouldn't be Y -- Illegal element type (0, 20, 127, etc.) Y -- Incorrect Number-Of-Components in complex header Y -- Index-To-Attributes error Y -- Line string is missing from complex chain N -- Linkage area is suspiciously long Y -- List report options in the report file Y -- Low range greater than high range N -- MicroStation is using 127 levels? Y -- Missing reference file Y -- Missing vital element (like type 9, 8 or 10) Y -- Multiple instances of line style linkage Y -- NNBASE (text node base number) is greater than CANODE Y -- Nesting level is too deep Y -- Non-shared cell header is not on level 0 Y -- Non-shared cell level or class map is incorrect Y -- Null filled linkage Y -- Null name in cell library Y -- One EDF overlaps another Y -- Pattern scale is zero N -- Put report summary information at the beginning of the report file Y -- Questionable (not recognized) element type Y -- Range of graphic element is wrong N -- Range of graphic elements is causing a fit problem Y -- Report new seal-of-approval summary to the report file Y -- Report previous seal-of-approval information to the report file Y -- Reserved bit is set Y -- Reserved nibble is non-zero N -- Rotation angle (2D only) is 360 degrees Y -- Shared cell definition with no shared cell instance Y -- Shared cell instance has no shared cell definition Y -- Shared cell level or class mask is incorrect N -- Shared instance level doesn't match definition Y -- Siamese attributes linkage N -- Skip file if first element is not a valid element N -- Skip text range validation Y -- Stray elements between type 1 cells in cell library Y -- Tag element different than definition in tag set Y -- Tag not associated with any element Y -- Tag set missing Y -- Tag set not used Y -- Text element has more EDFs than characters Y -- Text element has zero characters Y -- Text element has zero height or width multipliers Y -- Text element uses non-existent character-font combination Y -- Text element uses non-existent font N -- Text height or width too large or too small

Page 38 FileFixer

N -- Text node number equals or exceeds CANODE Y -- Text rotation does not match its text node Y -- Text string overflows the element length Y -- Too few vertices on line string, shape, curve, etc. Y -- Too many Enter-Data-Fields Y -- Too many vertices on line string, shape, curve, etc. N -- Treat deleted elements with RLIDs as though active Y -- Type 2 in cell library is not part of a type 1 Y -- User linkage is not a multiple of 4 words Y -- Words-In-Description error Y -- Words-To-Follow error Y -- Working units must be non-zero N -- Write a message to the report file for files with no anomalies Y -- Write seal-of-approval information to the design file Y -- Write summary statistics to the report file Y -- Zero components in complex element

What the first digit of the error number [in square brackets] means: 9 -- Fatal error -- It is unlikely that any IGDS/MicroStation related processor will process this file in its entirety without a severe error. 7 -- Serious error -- There is a significant possibility that the elements involved will manifest problems of some kind. 5 -- Future danger -- Continued use of this file without handling this problem will probably eventually cause a severe corruption problem. 3 -- Warning -- This element violates a rule of IGDS/MicroStation file construction, it may eventually cause problems. 1 -- Suspicious -- This element may not violate any "official" IGDS/MicroStation rules, but something about it doesn't look quite right. 0 -- User error -- This message concerns something the user or programmer did wrong. It does not reflect upon the design file being processed. More information about each listed error can be found in the FileFixer User's Guide.

If the punctuation at the very end of a message is an exclamation mark ("!"),rather than a period ("."), FileFixer considers the Words-To-Follow of thiselement to be less than 100% trustworthy. Note: it is possible for FileFixerto consider the Words-To-Follow of an element questionable for reasons otherthan the one reported.

Deleted elements can be spotted by the fact that tildes ("~") separate the EDGelement number from the error message instead of dashes.

Special symbols used in this report include: [] -- FileFixer error numbers are shown in square brackets. <> -- Element types are shown in angle brackets. () -- The EDG element number of the earlier element that is really causing the problem is shown in parentheses.

Abbreviations used in this report include: EDF -- Enter-Data-Field EOD -- End-Of-Design marker EOF -- physical End-Of-File ITA -- Index-To-Attributes MS -- MicroStation NOC -- Number-Of-Components VI -- View Independent WID -- Words-In-Description WTF -- Words-To-Follow

Chapter 9 — Design File Repair Page 39

Chapter 9 — Design File Repair

The following sections discuss the types of problems FileFixer can repair automaticallyand how to use FileFixer to make such repairs.

Keep in mind that, although FileFixer can repair more than one type of corruption at atime, in many cases it is better to repair just one type of problem at a time. In general, thefollowing rules should be observed:

• The options FIX EOF NOT FOUND AND DESIGN FILE I/O ERRORS andRECOVER ELEMENTS PAST THE END-OF-DESIGN MARKER bothaddress Words-To-Follow types of problems.

• When repairing EOF NOT FOUND errors, always use the DELETEUNWANTED ELEMENTS option.

Using yesterday’s backupProbably the most common method of “repairing” design files in use in the world todayis deleting the damaged file and reloading yesterday’s backup.

The most obvious problem with this “technique” is that you can lose up to a full day’sworth of work. With a day’s worth of operator and workstation time costing between$100 and $600 a day, clearly this should be a last resort.

But there is a more important reason for not going back to yesterday’s backup. The errorthat caused your file to become corrupted today might be dormant in yesterday’s backup.

Design files don’t always die a sudden death. A design file can be infected with a hiddenillness that won’t manifest itself until a later date. For example, if a design file has aWords-In-Description error, everything in that design file will probably seem perfectlynormal. But, if anyone uses IGDS to delete the element that has the Words-In-Description error, the entire design file may become completely corrupted.

Page 40 FileFixer

Likewise, if the graphic group counter (GRAFIC) in the type 9 header element is setincorrectly (too low), every time the user tries to create a new graphic group, IGDS andMicroStation, instead of creating a new graphic group, will append elements to anexisting graphic group. These “crossed linked” graphic groups can later cause elements to“mysteriously” disappear and manifest other problems.

The salient fact is this — you don’t know if the cause of today’s disaster was dormant inyesterday’s backup. The safest solution is to analyze crashed design files, and fully repairthem whenever possible.

Basic design file repairEven if you know absolutely nothing about IGDS/MicroStation file structure you can stilluse FileFixer to repair corrupted design files. Just start the program, select AutomaticDesign File Repair, enter the name of the file you want to repair, and press the Startbutton. Most design file I/O Errors and END OF FILE NOT FOUND errors will becorrected automatically.

RULE — Don’t try to fix words-to-follow errors unless you are getting a “DESIGN FILEI/O ERROR” or an “EOF NOT FOUND” error. Repairing a Words-To-Follow error (aVERY serious error) sometimes leaves complex bit and Words-In-Description errors inthe design file (a relatively minor error). The tradeoff is worth it. But there is no point increating minor errors if you’re not eliminating more serious errors in return.

URGENT NOTE — Because no program that automatically repairs design files will everbe totally perfect, it is important to create a backup copy of a design file before repairingit with FileFixer. There are two reasons for this.

1. If anything non-optimal is later discovered about the fixed file, you will still have theoriginal file to work with. Although FileFixer generally does a good job of repairingdesign files, the user is still the final judge as to whether the “fixed” file is trulysuperior to the original file.

2. Only if we receive a copy of the original (unfixed) design file can our technicalsupport staff determine what, if anything, went wrong with a fix.

Advanced repair of “EOF Not Found” and “I/O” errorsEven though FileFixer can repair the majority of Words-To-Follow errors all by itself,there are times when a little human help can go a long way. In order for you to be able toprovide that help, it is necessary to have at least a rudimentary idea of how FileFixerrepairs Words-To-Follow errors.

Every element in a valid design file (or cell library) contains a pointer to the beginning ofthe next element. When an element has a Words-To-Follow error, this pointer isconsidered to be unreliable and unusable. Therefore some other method must be used tofigure out where the next element starts.

When FileFixer encounters an element whose Words-To-Follow it believes to be in error,it tries every possible block/byte offset looking for the start of a valid element chain (twoor more sequential, valid MicroStation elements). FileFixer uses a statistical method to


determine if each starting point could be the start of a valid element chain. The algorithmcan take any random string of bits and bytes and assign a statistical likelihood that thissequence of binary data is a valid IGDS/MicroStation element. After each potentialelement starting point is analyzed, the algorithm adjudicates that (1) This is definitely notthe start of a valid element. (2) This probably is the start of a valid element chain. (3) Wedon’t have enough information to decide (in which case it will scan ahead looking formore information).

Depending on the statistical probability of each block/byte offset encountered being thestart of a valid IGDS/MicroStation element, FileFixer will scan up to 2560 blocks beyondthe original block/byte offset to help it determine if the original candidate block/byteoffset is the start of a valid IGDS element. Discovery of even one well-tested, highcertainty element (like a type 17) may be all that is needed to recover from a Words-To-Follow error. But even 10, apparently valid, low certainty elements, (like types 39, 65,and 82) in a row might not be considered enough to constitute a valid element chain.

Telling FileFixer What Types of Application Elements You Use or Don’t Use — Theelement types from 1 to 28 as well as some of the application elements are wellstandardized and well known. This makes it fairly easy for FileFixer to determine if acertain location in a design file is the start of a valid instance of one of these elementtypes. But for many non-graphic element types, very little is known. This can make itvery difficult for FileFixer to determine if these elements are valid.

As an example, it’s very easy to determine if a type 17 element (text) is valid. FileFixercan compare the number of characters, Enter-Data-Fields, attribute linkages, elementrange, text height, text width, property bits, and other information to determine if theelement is valid. If a type 17 passes all of these tests, we can be pretty well sure it’s avalid element.

But we know almost nothing about a type 39. There are some tests we can do (checkingthe reserve bit for example) to determine if a type 39 is valid, but even when a type 39passes the limited tests we do have, we can’t be very certain that it is a valid element.

When you specify which element types you use and don’t use, FileFixer is greatlyassisted. You are providing information regarding elements about which we know theleast.

In general it is highly recommended that DELETE ILLEGAL ELEMENT TYPES beselected whenever you are attempting to repair Words-To-Follow errors. Type 0 (andpossibly other illegal elements) will likely be found in the output (.fix) file, if this is notdone.

Telling FileFixer which element types are and aren’t acceptable can help FileFixermaximize the number of valid elements and minimize the number of invalid elementsthat are recovered from a damaged design file.

See the documentation section ADVANCED DESIGN FILE DIAGNOSIS for moreinformation about how FileFixer uses the information about legal and illegal elementtypes.

Telling FileFixer What Levels Displayable Elements Can Appear On — TellingFileFixer on which levels displayable elements can validly exist helps it recover desiredelements and weed out invalid elements.

Page 42 FileFixer

Setting the filter factor

In most cases the default Filter Factor does a fairly good job. Since the default FilterFactor works so well, changing the Filter Factor has only a relatively small chanceimproving the repair of a design file. But for some design files, experimenting with theFilter Factor might just save the day.

The Filter Factor determines how selective FileFixer is in determining when it hasencountered a valid element chain. If the Filter Factor is too low, FileFixer may think ithas encountered a valid element chain when it has not. If the Filter Factor is too high,FileFixer might ignore a valid element chain.

Basically, the Filter Factor is how many “points” a chain must score before it isconsidered “valid”.

Setting the Filter Factor too low usually results in invalid elements being added to therepaired version of the design file. It can also (less frequently) cause recoverableelements to be left out of the repaired design file.

Setting the Filter Factor too high can result in recoverable elements being left out of therepaired design file.

The more accurately you set the list of valid element types and levels, the lower the FilterFactor that can be tolerated.

This option is found under the “Options menu | Repair… | WTF/WID”.

Enabling BackScanning

This is found at “Options menu | Repair… | WTF/WID”.

It’s one thing to miss your exit on the freeway, it’s another thing entirely to not turnaround and go back when you realize your error. FileFixer does a pretty good job atdetecting Words-To-Follow errors. But, some Words-To-Follow errors are difficult orimpossible to detect. For example, determining the accuracy of the Words-To-Follow of adeleted complex element header is next to impossible. Sometimes, despite the bestintentions of its author, FileFixer will pass a Words-To-Follow error and find itself lostin the middle of a corrupted design file uncertain whether it has already gone past valid,recoverable elements. BackScanning gives FileFixer the ability to retrace its steps, getback on the road, and continue its mission of repairing your design file or cell library.

If BackScanning is enabled and FileFixer cannot find a valid End-Of-Design marker atthe end of a design file (and under certain other circumstances), FileFixer assumes it hasdone something wrong (like let an undetectable Words-To-Follow error slip by). It thengoes back to the point in the design file where it was POSITIVE it had a good elementand scans forward (very carefully and slowly) looking for valid elements it might havemissed. This helps ensure that no stone is left unturned in recovering valid elements fromyour damaged design file.

Question: If BackScanning is so good, why is it just an option? Why isn’t it enabled allthe time?


Answer: BackScanning can recover unwanted elements. The components of deletedcomplex elements (whose delete bits are not set) are particularly prone to being broughtback to life by the BackScanning option.

Only occasionally will BackScanning recover additional, desired elements. But if youfind that FileFixer hasn’t recovered all the elements you expected, give it a try. Thesample file, backscan.dgn, is an example of a damaged design file that benefits fromBackScanning.

Note: As of version 4.2a of FileFixer, the standard (Non-Back-Scanning) Words-To-Follow repair algorithm has been so enhanced that BackScanning is now nearly obsolete.Most files which previously required the BackScanning option to recover the maximumnumber of elements are now fully recovered even without BackScanning. BackScanningis nonetheless retained as there are still (theoretically, at least) some files that will benefitfrom it.

Additional data about automatic repairSometimes the .fix file created by FileFixer will have fewer elements than the original.dgn file. Why is this? When FileFixer is trying to determine where the next validelement starts after encountering an element with a corrupt Words-To-Follow, it makesvery certain not to include any elements that are not COMPLETELY valid. In actual fact,you may want to include elements that are slightly corrupted. At this time FileFixer doesnot, when trying to find the first valid element after a corrupt Words-To-Follow,differentiate between slightly corrupt elements and very corrupt elements. This stillrequires human intelligence. If there are certain types of minor corruption you don’t mindhaving in your design file, turn off the validation check that checks for that type ofcorruption. Future versions of FileFixer will address this issue in a more automatedfashion.

Summary of rules on fixing Words-To-Follow errors:1. If a design file produces an “EOF not found” or a “Design file I/O error”, fix this

problem first. Turn off all other types of repair and press the Start button.

2. If step 1 produces a valid design file, but many elements seem to be missing, turnon the BackScanning option and repeat step 1.

3. If many elements are still missing from the file, additionally select the “RecoverElements After The End-of-Design Marker” option and repeat step 1.

4. If many elements are still missing, reduce the Filter Factor option to 50 or so.With these settings FileFixer should recover nearly all recoverable elements (butalso some “elements” that are either not completely valid or which you don’twant). Repeat step 1.

5. If you’re still missing lots of elements, try turning off some of the validationrules, you don’t mind your elements violating. For example, you may not care ifyour elements have H-Bit or complex bit errors in them. Repeat step 1.

Page 44 FileFixer

6. If you’re still missing lots of elements, you can be certain that a good portion ofthe file cannot be salvaged — even by FileFixer. Retrieve the most recent backupcopy of the file you can use.

Tip: It may be possible that an earlier copy, even if corrupt, is less corrupt than yourcurrent file and FileFIxer may succeed in repairing that one.

How to recover elements after the End-Of-Design markerSometimes an End-Of-Design marker will get written right into the middle of your designfile. When that happens, all the elements after the misplaced End-Of-Design marker willdisappear. It is even possible for more than one End-Of-Design marker to get written tothe middle of a design file.

To recover elements after a misplaced End-Of-Design marker, follow these instructions:

• Select FileFixer’s Automatic Design File Repair menu.

• Turn on the toggle for the repair option “Recover Elements Past the End-Of-Design Marker” (found at “Options menu | Repair… | Element”). Note that whenyou do this, the “Fix ‘EOF Not Found’” option will automatically be turned on.This is because when you recover elements after an End-Of-Design marker, youmust also clean up all the Words-To-Follow errors that are generated in doing so.

• Press the START button.

FileFixer will read past a maximum of 1000 End-Of-Design markers looking foradditional valid elements. A new design file with a .fix extension will be createdcontaining all the valid elements encountered.

Note: because this command will also read past the “real” End-Of-Design marker, itmay recover more elements than you bargained for. If this happens, just use IGDS,MicroStation, or EdG to delete the elements you don’t want.

How to fix complex bit errors FileFixer now has the ability to repair complex bit errors automatically. To repair

complex bit errors, use the Automatic Design File Repair command of FileFixer.Turn on the CORRECT COMPLEX BIT ERRORS repair option. Click on OKand then click on the Start button. FileFixer will take care of the rest.

This option is found at “Options menu | Repair… | Complex”.

Note: FileFixer uses the information stored in the Words-In-Description of complexheader elements in the design file being repaired. If the design file being repaired also hasWords-In-Description errors, it is much better to repair these before repairing complexbits. Otherwise, you might create more complex bit errors than you eliminate.


How to fix element range errors FileFixer can detect and eliminate element range errors. By default, this type of repair isperformed. Below you will see that the REPAIR RANGE OF COMPLEX HEADERELEMENTS and REPAIR RANGE OF DISPLAYABLE ELEMENTS repair options areon.

These options are found at “Options menu | Repair… | Range”.

When repairing element ranges, FileFixer will:

• Determine if the X-Low, X-High, Y-Low, Y-High, Z-Low, or Z-High need to beadjusted. You tell FileFixer how accurate each of these range components mustbe when you specify the ELEMENT RANGE TOLERANCE on the SearchOptions dialog box (at “Options menu | Search… | Range”).

• If any of the above need to be adjusted, just that one component is adjusted; theothers are unchanged.

Example:

The element range tolerance is set to (-30, 90), the default. X-Low is 35% CLOSER to X-High than it should be. X-High is 50% FURTHER from X-Low than it should be. Y-Lowis 10% CLOSER to Y-High than it should be. Y-High is 110% FURTHER from Y-Lowthan it should be. (I realize this may be a bit confusing. Suffice it to say that X-Low andY-High are sufficiently inaccurate to alert FileFixer.) In this case, X-Low and Y-Highwould be adjusted, but not the other two components of the range. (We’re assuming thisis a 2D element).

Basically, this is another way of saying: FileFixer plays it safe. It changes only thoseparts of the element that really need changing. If you want FileFixer to set all the elementranges to their theoretical ideals, you can set the element range tolerance to (-0, 0). Butfor most practical purposes the default element range tolerance should prove adequateand effective.

See the section called DETECTING ELEMENT RANGE PROBLEMS in chapterDESIGN FILE DIAGNOSIS for more information about the element range tolerance.

Page 46 FileFixer

How to fix FIT problems There are a couple of reasons why the MicroStation FIT command doesn't work properly.They are:

• Range of an element is bad.

• You have one or more element that is a large distance away from the rest of theelements.

The first problem is solved by running FileFixer in Automatic Design File Repair mode.This will fit the ranges of all displayable elements.

The second problem is not easily solved. FileFixer has a RANGE OF GRAPHICELEMENT IS CAUSING A FIT PROBLEM search option. What FileFixer does iscompute a rectangle around 95% or more of the displayable elements, and then checks tosee if there are any elements some distance away from that rectangle. This distance awayis determined by the percentage you specify in the ACCEPTABLE ELEMENT RANGETOLERANCE field. The default is 300%. Normally you won't need to increase thispercentage, but you may need to lower it. By trial and error you can keep changing thispercentage until you get a couple of elements that show up in the report file with an errorcode of 107. You can use EdG or ProblemElementViewer to look at these elements anddetermine if they are valid or not. If they are not valid, then you should delete them. FITmay work fine now. If not, you may need to use this procedure a couple of times to findall the elements that are causing FIT to display incorrectly.

How to fix Words-In-Description errors All complex header elements have a Words-In-Description word. Just as Words-To-Follow describes how long an individual element is, Words-In-Description tells how longthe entire complex element (usually made up of many individual elements) is. When theWords-In-Description of a complex header element is wrong, you can get complex biterrors and elements can be left out of cell and complex shape manipulations. Worst of all,under certain circumstances, deleting an element with a Words-In-Description problemcan corrupt your entire design file! Words-In-Description problems are not good things toleave around in your design file.

Here’s how you fix Words-In-Description problems.

• If the file has Words-To-Follow errors, fix these first. Do this using the repairoptions ‘EOF NOT FOUND’ AND ‘DESIGN FILE I/O’ ERRORS and theAutomatic Design File Repair command.

• After you have fixed all Words-To-Follow errors, get back into the AutomaticDesign File Repair command.

• Name the previous output (.fix) file as the design file you want to repair.

• Turn off all repair options except CORRECT WORDS-IN-DESCRIPTIONerrors.

• Press the Start button.

FileFixer should fix about 97% of the Words-In-Description errors it encounters.Whether a particular Words-In-Description error is fixed depends upon the following:


A. Words-In-Description problems are the only things wrong with this file.

B. The complex header element to be fixed is not itself a component of another(bigger) complex element.

If A and B are both true, then the chances of FileFixer correctly fixing the Words-In-Description is nearly 100%. Even when A and B are not both true, FileFixer has anexcellent chance of correctly fixing the Words-In-Description. This is because FileFixeranalyzes up to six different characteristics of complex elements and determines which ofa number of possible Words-In-Description values yield the greatest likelihood ofproducing a correctly nested complex element which violates the fewest rules ofIGDS/MicroStation element construction.

Even in those few instances when FileFixer fails to recreate the original Words-In-Description value, the value it does generate should always (in theory, anyway) be atleast as good or better than the erroneous Words-In-Description it replaces. Even in theworst case, when FileFixer finishes its job, deleting the complex element with therepaired Words-In-Description will no longer cause the entire design file to get corrupted.

After repairing Words-In-Description errors, you may need to run the Automatic DesignFile Repair command again with only CORRECT COMPLEX BIT repair option turnedon to correct any complex bit errors that might have been created while fixing (the moreserious) Words-In-Description errors.

You can learn more about Words-In-Description problems by studying FileFixer errornumbers 505, 520, and 522 in Chapter 14— Error Messages.

The steps of manual file fixing

The steps of file fixing can be summarized as follows:

1. All types of repair that might remove elements or pieces of elements from thedesign file. This includes fixing Words-To-Follow errors and removing unwantedelements.

2. Words-In-Description repairs.

3. All other repairs.

Page 48 FileFixer

Each step requires its own run of the Manual Design File Repair command. Nevercombine a repair from one step with a repair from another. Unneeded steps can beskipped, but don’t do any steps out of sequence.

Note that the Automatic Design File Repair commands takes care of all of these problemsfor you automatically. The Manual Design File Repair command is more or lessobsolete. The Automatic Design File Repair command should be used in most cases.

Chapter 10 — Which Error Messages are Generated by Which Option Page 49

Chapter 10 — Which Error Messages areGenerated by Which Option

Sometimes you may not want FileFixer to report all the corruption it finds.

For example, you receive a design file from a contractor but he didn’t send the fontresource file he used. Well if you don’t have a font resource file with that font number,then FileFixer will report a lot of errors telling you that that font doesn’t exist. Since youknow about this problem and you will be receiving the font resource file soon, then youcould turn off the option which tells FileFixer to check for fonts that don’t exist. This willstop you from searching through a lot of errors, which really aren’t errors, and you cansee the errors that need to be addressed.

The following four tables show you which possible error messages occur for whichSearch or Repair options, sorted by category then sorted by error number.

Under the “Repair-type error messages sorted by category” section below you will findwhich step each repair option is repaired on. This includes all three steps, Step 1 (WTF-words to follow problems), Step 2 (WID-words in description problems and Step 3 allother problems.

Search-type error messages sorted by category

Category Search Opt ions DescriptionErrorMessages

ARC/Ellipse Arc or ellipse axis is too long 117

Arc or ellipse origin is off the design plane 118

Arc’s sweep angle is invalid (-360 <= angle <= 360) 318

B-spline B-spline has illegal number of one type of component 731

Elements in b-spline are in wrong sequence 784

Cell Cell is nested within itself 383, 783

Duplicate shared cell or library cell definition 766

H-bit (orphan flag) not set in orphan cell 572

Nesting level is too deep 565

Non-shared cell is not on level 0 741

Non-shared cell level or class map is incorrect 716, 717

Null name in cell library 570

Shared cell instance has no shared cell definition 768

Cell Shared cell level or class mask is incorrect 769, 770

Page 50 FileFixer


Shared cell definition with no shared cell instance 303

Shared instance level doesn’t match definition 171

Stray elements between type 1 cells in cell library 355

Type 2 in cell library is not part of a type 1 571

Complex Complex bit is on for a non-component element 702

Complex bit is on for an element with database linkage 138

Complex bit is off for a component element 703

Complex element contains disallowed element type 86, 121, 323,721

Component on different level than its header 336

Component graphic group doesn’t match header 341

Component symbology doesn’t match header 337, 338, 339

Curves and conics within complex shapes and curves 131

Curve or conic with consecutive identical vertices 190

Element must be nested in complex 719

Incorrect number-of-components in complex header 322, 334

Line string is missing from complex chain 555

Zero components in complex element 328

Design File Design file range doesn’t match the range of the graphicalelements

111

File size is not a multiple of 512 bytes 108

Dimension Dimension element with no data or associative points 722

EDF An EDF extends past the end of the text string 347

An EDF has a length of zero 350

An EDF has an unrecognized justification 346

An EDF is out of sequence 348

One EDF overlaps another 349

Text element has more EDFs than characters 191

Too many Enter-Data-Fields 335

Element 2d element found in 3d file 362, 762

3d element found in 2d file 362, 762, 776

Deleted phantom element detected 147

Element Element class is illegal 333



Element is locked 120

Element is too close to edge of design plane 119

GRAFIC is not equal to highest graphic group plus 1 134, 534

H-bit is set when it shouldn’t be 304

Reserved bit is set 103

Reserved nibble is non-zero 132

Text node number equals or exceeds CANODE 530

Headers Active angle is invalid (-360 <= angle <= 360) 153

Active level is out of range 155

CANODE not equal to highest text node number plus 1 135, 535

Cell library header must be 23 words 158

Deleted type 9, 8 or 10 detected 101

Design file header length must be 766 words 157

Error in type 9 header element 109, 126, 128,311, 526, 528,701, 329

Extra design file header (type 9 level 8) 170

GGBASE (graphic group base number) is greater thanGRAFIC

153

Graphic group number equals or exceeds GRAFIC 531

Missing vital element (like type 9, 8 or 10) 710, 713, 714,902

NNBASE (text node base number) is greater thanCANODE

154

Working units must be non-zero 156

Linkage A-bit is turned on, but there’s no attribute linkage 369

Index-To-Attributes error 301, 510, 512,513, 514, 515

Linkage area is suspiciously long 161, 761

Multiple instances of line style linkage 139

Null filled linkage 165

Siamese attributes linkage 364

User linkage is not a multiple of 4 words 365

Pattern Pattern scale is zero 375

Range Cell header’s diagonal is invalid 367

Page 52 FileFixer


Complex header range doesn’t match components’ range 320, 720

Low range greater than high range 704

Range Range of graphic element is wrong 305, 306, 307,309, 312, 324,325, 705, 706,707, 709, 712,724, 725, 912

Reference File Blank file name 387

Duplicate reference file attachment encountered 158

Duplicate reference file logical name encountered 342

File name, logical or description strings overflow theirfields

388

Missing reference files 343

Tag Element tagged with no tags 142

Tag element different than definition in tag set 143

Tag not associated with any element 140

Tag set missing 160, 360

Tag set not used 141

Text Rotation angle (2d only) is 360 degrees 175

Text element has zero characters 390

Text element has zero width or height multiplier 326

Text element uses non-existent character-font combination 145

Text element uses non-existent font 144

Text rotation does not match it’s text node 356

Text string overflows the element length 560

Text height or width is too large or too small 150

Text height to width or width to height ratio is bad 152

Type/Level Bad element type-level combination 115, 715

Element of this type should never have its a-bit set 316

Illegal element type (0, 20, 127, etc.) 302, 380, 382

Questionable (not recognized) element type 180

Vertices First and last vertex of type 6 shape don’t match 385

Vertices Too few vertices on line string, shape, curve, etc. 788, 789

Too many vertices on line string, shape, curve, etc. 787



WTF/WID Dangerous element (WTF may be unreliable) 700

Words-in-description error 505, 520, 522,550

Words-to-follow error 353, 354, 754,756, 758

Page 54 FileFixer

Search-type error messages sorted by error numberErrorMessages Category Search Opt ions Description86 Complex Complex element contains disallowed element type

101 Headers Deleted type 9, 8 or 10 detected

103 Element Reserved bit is set

108 Design File File size is not a multiple of 512 bytes

109 Headers Error in type 9 header element

111 Design File Design file range doesn’t match the range of the graphicalelements

115 Type/Level Bad element type-level combination

117 ARC/Ellipse Arc or ellipse axis is too long

118 ARC/Ellipse Arc or ellipse origin is off the design plane

119 Element Element is too close to edge of design plane

120 Element Element is locked

121 Complex Complex element contains disallowed element type



131 Complex Curves and conics within complex shapes and curves

132 Element Reserved nibble is non-zero

134 Element GRAFIC is not equal to highest graphic group plus 1

135 Headers CANODE not equal to highest text node number plus 1

138 Complex Complex bit is on for an element with database linkage

139 Linkage Multiple instances of line style linkage

140 Tag Tag not associated with any element

141 Tag Tag set not used

142 Tag Element tagged with no tags

143 Tag Tag element different than definition in tag set

144 Text Text element uses non-existent font

145 Text Text element uses non-existent character-font combination

147 Element Deleted phantom element detected

150 Text Text height or width is too large or too small

152 Text Text height to width or width to height is bad


ErrorMessages Category Search Opt ions Description153 Headers GGBASE (graphic group base number) is greater than

GRAFIC

154 Headers NNBASE (text node base number) is greater thanCANODE

155 Headers Active level is out of range

156 Headers Working units must be non-zero

157 Headers Design file header length must be 766 words

158 Reference Duplicate reference file attachment encountered

159 Headers Cell library header must be 23 words

160 Tag Tag set missing

161 Linkage Linkage area is suspiciously long

163 Headers Active angle is invalid (-360 <= angle <= 360)

165 Linkage Null filled linkage

170 Headers Extra design file header (type 9 level 8)

171 Cell Shared instance level doesn’t match definition

175 Text Rotation angle (2d only) is 360 degrees

180 Type/Level Questionable (not recognized) element type

190 Complex Curve or conic with consecutive identical vertices

191 EDF Text element has more EDFs than characters

301 Linkage Index-To-Attributes error

302 Type/Level Illegal element type (0, 20, 127, etc.)

303 Cell Shared cell definition with no shared cell instance

304 Element H-bit is set when it shouldn’t be

305 Range Range of graphic element is wrong






316 Type/Level Element of this type should never have its a-bit set

318 ARC/Ellips Arc’s sweep angle is invalid (-360 <= angle <= 360)

320 Range Complex header range doesn’t match components’ range

322 Complex Incorrect number-of-components in complex header

Page 56 FileFixer

ErrorMessages Category Search Opt ions Description323 Complex Complex element contains disallowed element type



326 Text Text element has zero width or height multiplier

328 Complex Zero components in complex element


333 Element Element class is illegal

334 Complex Incorrect number-of-components in complex header

335 EDF Too many Enter-Data-Fields

336 Complex Component on different level than its header

337 Complex Component symbology doesn’t match header



341 Complex Component graphic group doesn’t match header

342 Reference File Duplicate reference file logical name encountered

343 Reference File Missing reference files

346 EDF An EDF has an unrecognized justification

347 EDF An EDF extends past the end of the text string

348 EDF An EDF is out of sequence

349 EDF One EDF overlaps another

350 EDF An EDF has a length of zero

353 WTF/WID Words-to-follow error


355 Cell Stray elements between type 1 cells in cell library

356 Text Text rotation does not match it’s text node

360 Tag Tag set missing

362 Element 2d element found in 3d file


364 Linkage Siamese attributes linkage

365 Linkage User linkage is not a multiple of 4 words

367 Range Cell header’s diagonal is invalid

369 Linkage A-bit is turned on, but there’s no attribute linkage

375 Pattern Pattern scale is zero


ErrorMessages Category Search Opt ions Description380 Type/Level Illegal element type (0, 20, 127, etc.)

382 Type/Level Illegal element type (0, 20, 127, etc.)

383 Cell Cell is nested within itself

385 Vertices First and last vertex of type 6 shape don’t match

387 Reference File Blank file name

388 Reference File File name, logical or description strings overflow theirfields

390 Text Text element has zero characters

505 WTF/WID Words-in-description error










530 Element Text node number equals or exceeds CANODE

531 Headers Graphic group number equals or exceeds GRAFIC

534 Element GRAFIC is not equal to highest graphic group plus 1

535 Headers CANODE not equal to highest text node number plus 1


555 Complex Line string is missing from complex chain

560 Text Text string overflows the element length

565 Cell Nesting level is too deep

570 Cell Null name in cell library

571 Cell Type 2 in cell library is not part of a type 1

572 Cell H-bit (orphan flag) not set in orphan cell

700 WTF/WID Dangerous element (WTF may be unreliable)


702 Complex Complex bit is on for a non-component element

703 Complex Complex bit is off for a component element

Page 58 FileFixer

ErrorMessages Category Search Opt ions Description704 Range Low range greater than high range





710 Headers Missing vital element (like type 9, 8 or 10)




715 Type/Level Bad element type-level combination

716 Cell Non-shared cell level or class map is incorrect

717 Cell Non-shared cell level or class map is incorrect

719 Complex Element must be nested in complex

720 Range Complex header range doesn’t match components’ range

721 Complex Complex element contains disallowed element type

722 Dimension Dimension element with no data or associative points



731 B-spline B-spline has illegal number of one type of component

741 Cell Non-shared cell is not on level 0




761 Linkage Linkage area is suspiciously long



766 Cell Duplicate shared cell or library cell definition

768 Cell Shared cell instance has no shared cell definition

769 Cell Shared cell level or class mask is incorrect

770 Cell Shared cell level or class mask is incorrect


783 Cell Cell is nested within itself

784 B-spline Elements in b-spline are in wrong sequence


ErrorMessages Category Search Opt ions Description787 Vertices Too many vertices on line string, shape, curve, etc.

788 Vertices Too few vertices on line string, shape, curve, etc.

789 Vertices Too few vertices on line string, shape, curve, etc.



Page 60 FileFixer

Repair-type error messages sorted by category

Category Repair Option DescriptionErrorMessages

StepRepaired On

ARC/Ellipse Fix or delete arc/ellipse whose origin is off thedesign plane

118 3

B-spline B-splines with illegal component counts 731 3

Cell Adjust non-shared cell levels or class map 716, 717 3

Adjust shared cell levels or class masks 769, 770 3

Create dummy shared cell definition for missingdefinition

768 3

Correct null cell name (type 2’s only) 570 1

Delete duplicate nested cell 383, 783 1

Delete duplicate shared cell definitions 766 3

Delete shared cell definition with no shared cellinstance

303 3

Move non-shared cell headers back to level 0 741 1

Move shared instance to definition level 171 2, 3

Remove stray elements from between type 1 cells 355 3

Set H-bit (orphan flag) in orphan cell 572 1

Complex Add missing line string to complex chain 555 3

Correct complex bit errors 702, 703 3

Correct Number-Of-Component problems 322 3

Delete complex elements with no components 721 3

Move component to same level as complex header 336 3

Set graphic group of component to match its header 341 3

Set symbology of component to match its header 337, 338, 339 3

Design File Correct the design file range (DFRANG) 111 3

Dimension Remove dimension element with no data orassociative points

722 3

EDF Change zero-length EDF to length 1 350 1

Correct EDFs which overlap or are out of sequence 349 1

Correct Enter-Data-Field justification 346 3

Extend text element to contain largest EDF 347 1

Element Correct rotation angle (2d only) from 360 to 0 175 1



StepRepaired On

Fix reserved bit -- say no if using 127 levels? 103 3

Recover elements past the End-Of-Design marker 79 1

Remove elements with too few vertices 789 1

Remove illegal element types (0, 20 and 127) 302, 380, 382,776, 762

1

Resequence text node numbers 137 3

Resequence graphic group numbers 136 3

Set illegal class to ____ 333 3

Turn off illegal a-bits 369 3

Turn off illegal h-bits 304 3

Unlock Element 120 3

Headers Correct dimension bits in the file header 701 1

Delete duplicate design file header 170 3

Set active angle to ____ 163 3

Update GRAFIC 134, 534 3

Update CANODE 135, 535 3

Linkage Remove database linkages 37 3

Remove multiple instances of line style linkage 139 3

Remove null filled linkages 165 3

Pattern Set pattern scale to one when zero 375 1

Range Repair diagonal of cell header 367 3

Repair range of complex header element 320, 720 3

Repair range of displayable elements 305, 306, 307,309, 312, 324,325, 704, 705,706, 707, 709,712, 724, 725

1, 2, 3

ReferenceFile

Correct the file name, logical or description stringsfrom overflowing

388 3

Delete duplicate reference file attachment 158 3

Delete the reference file attachment with a blank filename

387 3

Tag Delete tag not associated with any element 140 3

Tag Delete unused tag sets 141 3

Remove tag from element with no tags 142 3

Page 62 FileFixer


StepRepaired On

Update tag element from tag set 143 3

Text Correct number of characters in text string 560 1

WTF/WID Correct Words-In-Description problems 505, 520, 522 2

Fix severe WTF errors (EOF not found) 101, 700, 750,752, 754, 758

1

Fix WTF warnings 364, 365 1, 3


Repair-type error messages sorted by error numberErrorMessages Category Repair Opt ion Description

StepRepaired On

37 Linkage Remove database linkages 3

79 Element Recover elements past the End-Of-Design marker 1

101 WTF/WID Fix severe WTF errors (EOF not found) 1

103 Element Fix reserved bit -- say no if using 127 levels? 3

111 Design File Correct the design file range (DFRANG) 3

118 ARC/Ellipse Fix or delete arc/ellipse whose origin is off thedesign plane

3

120 Element Unlock Element 3

134 Headers Update GRAFIC 3

135 Headers Update CANODE 3

136 Element Resequence graphic group numbers 3

137 Element Resequence text node numbers 3

139 Linkage Remove multiple instances of line style linkage 3

140 Tag Delete tag not associated with any element 3

141 Tag Delete unused tag sets 3

142 Tag Remove tag from element with no tags 3

142 Tag Update tag element from tag set 3

158 ReferenceFile

Delete duplicate reference file attachment 3

163 Headers Set active angle to ____ 3

165 Linkage Remove null filled linkages 3

170 Headers Delete duplicate design file header 3

171 Cell Move shared instance to definition level 2, 3

175 Element Correct rotation angle (2d only) from 360 to 0 1

302 Element Remove illegal element types (0, 20 and 127) 1

303 Cell Delete shared cell definition with no shared cellinstance

3

304 Element Turn off illegal h-bits 3

305 Range Repair range of displayable elements 1, 2, 3



Page 64 FileFixer

ErrorMessages Category Repair Opt ion Description

StepRepaired On




322 Complex Correct Number-Of-Component problems 3



555 Complex Add missing line string to complex chain 3

333 Element Set illegal class to ____ 3

336 Complex Move component to same level as complex header 3

337 Complex Set symbology of component to match its header 3



341 Complex Set graphic group of component to match its header 3

346 EDF Correct Enter-Data-Field justification 3

347 EDF Extend text element to contain largest EDF 1

349 EDF Correct EDFs which overlap or are out of sequence 1

350 EDF Change zero-length EDF to length 1 1

355 Cell Remove stray elements from between type 1 cells 3

364 WTF/WID Fix WTF warnings 1, 3

365 WTF/WID Fix WTF warnings 1, 3

367 Range Repair diagonal of cell header 3

369 Element Turn off illegal a-bits 3

375 Pattern Set pattern scale to one when zero 1



383 Cell Delete duplicate nested cell 1

387 ReferenceFile

Correct the file name, logical or description stringsfrom overflowing

3

388 ReferenceFile

Delete the reference file attachment with a blank filename

3

505 WTF/WID Correct Words-In-Description problems 2





StepRepaired On

534 Headers Update GRAFIC 3

535 Headers Update CANODE 3

560 Text Correct number of characters in text string 1

570 Cell Correct null cell name (type 2’s only) 1

572 Cell Set H-bit (orphan flag) in orphan cell 1


701 Headers Correct dimension bits in the file header 1

702 Complex Correct complex bit errors 3

703 Complex Correct complex bit errors 3







716 Cell Adjust non-shared cell levels or class map 3

717 Cell Adjust non-shared cell levels or class map 3


721 Complex Delete complex elements with no components 3

722 Dimension Remove dimension element with no data orassociative points

3



731 B-spline B-splines with illegal component counts 3

741 Cell Move non-shared cell headers back to level 0 1






766 Cell Delete duplicate shared cell definitions 3

768 Cell Create dummy shared cell definition for missingdefinition

3

Page 66 FileFixer


StepRepaired On

769 Cell Adjust shared cell levels or class masks 3

770 Cell Adjust shared cell levels or class masks 3


783 Cell Delete duplicate nested cell 1

789 Element Remove elements with too few vertices 1

Chapter 11 — Batch Mode Page 67

Chapter 11 — Batch Mode

What do we mean by Batch Mode ?In this chapter batch mode means starting FileFixer directly from the operating systemcommand line (instead of from within graphics). For example, if you were working on apersonal computer running MS-DOS you would enter the following DOS command:

msbatch.bat fixer -sb axiom.dgn

FileFixer would run in non-graphic, alphanumeric, batch mode. It would execute usingthe settings that were in effect the last time you executed FileFixer.

When you should use Batch ModeThe only time we recommend running FileFixer in batch mode is when you have all ofthe following:

1. You have a server which contains a large number of design files and it would beinconvenient to move them to a graphics workstation for processing.

2. Your server can’t run MicroStation normally because it has no graphics terminalhooked up to it.

3. Your server is not accessible via NFS.

4. Your server has MicroStation loaded on it despite having no graphics terminal.

How to run FileFixer in Batch ModeTo run FileFixer in batch mode follow these steps:

1. Run FileFixer in graphics mode on a workstation that has a graphics screen.

2. Set up the options (repair and search) the way you want FileFixer to work.

Note: You’ll be able to override the design filename wildcard and the mode on theoperating system command line when you start FileFixer in batch mode. If you set *.repas the report file on the FileFixer dialog box before running in batch mode then aseparate report file will be generated for each design file processed. The report(s) will beput into the same directory as the design file.

3. Copy your “fixer.ma” file to the server that lacks graphics capabilities. Copy theMicroStation file default.ucf (in the config/user directory under mstation) to theserver in the same directory. Put “fixer.ma” in the main mdlapps directory.Usually this is c:/ustation/mdlapps.

Page 68 FileFixer

4. Run MicroStation in batch mode. The syntax of the command you enter at theoperating system command line is:

msbatch fixer.ma options design_file_wildcard

The valid options are:-2 Assume files with unknown dimensions are 2D. Use

this option when the dimension of the design fileis unknown and you know it is a 2D file.

-3 Assume files with unknown dimensions are 3D. Usethis option when the dimension of the design fileis unknown and you know it is a 3D file.

-a Automatic design file repair. This option willuse the automatic repair options when repairingthe file.

-b Batch mode. This option is required when runningin batch mode.

-f The name of the report file you want to use. Usethis option when you don’t want to use the reportfile name you had last use when running FileFixerfrom within MicroStation.

-m Manual design file repair. This option will usethe manual repair options when repairing thefile.

-o Repaired design file directory. Use this optionwhen you want to specify the directory where therepaired files will be placed.

-r Resource file name. Which FileFixer resource filedo you want to use for the search and repairoptions.

-s Search mode. Analyze, but do not repair files.

Examples:msbatch fixer.ma -ab axiom.dgn

msbatch fixer.ma -s -b "*.dgn, *.cel"

msbatch fixer.ma –sb -f f:\axiom\fixer.rep *.dgn

msbatch fixer.ma –ab -r f:\axiom\fixer.rsc *.dgn

msbatch fixer.ma –ab -o f:\axiom\output -ff:\axiom\fixer.rep *.dgn

Note: DOS has a limit of 132 characters at the command prompt so if you put inlong switch options or if you specify to many options in one batch command in frontof your .dgns you may have a resource file or report name specified left off yourbatch process. This is why.

You can use the “–“ switch or the “/” switch interchangeably. You will need tospecify the full path to the design files and to fixer.ma.

Chapter 11 — Batch Mode Page 69

You need to specify the “-b” option as this tells FileFixer that it is being run in batchmode. Otherwise, FileFixer will try to start its dialog box which would causeMicroStation to abort.

Note: You can run FileFixer in Batch mode from a computer with graphiccapabilities and MicroStation loaded. Just skip step 3 (above). Run msbatch from theustation prompt at an operating system command line.

Currently, the only operating system you can’t run FileFixer in batch mode is CLIX.

Using the “AT” Command under Windows NT 4.0The “at” command allows you to run a task at a specified time. The format for the“at” command is:

at <time> /interactive cmd /c <program>

Where <time> can be specified as a 24-hour clock (military time) or a 12-hour clock.Examples: 18:20 or 6:20pm.

Where <program> is the fullpath of the program to be run.

To use the “at” command you need to build a batch file, which will run FileFixer.The following is an example of a batch file used to run FileFixer in MSBATCHmode:

c:cd \ustsemsbatch d:\axiom\fixer.ma /sb "e:\dgn\a*.dgn"

This batch file “c:\axiom\fixer.bat” will change the current working directory to theMicroStation root directory and then run MSBATCH. It will run FileFixer in searchmode on the design file starting with the letter “a” in the directory “e:\dgn”.

To run this batch file using the “at” command at 5:10pm do the following:

at 5:10pm /interactive cmd /c "c:\axiom\fixer.bat"

Page 70 FileFixer

Chapter 12 — SafetyCheck

Ensure your design files meet FileFixer’s standards!The “Good Housekeeping Seal-of-Approval” tells you that a consumer product has beentested, that it meets certain standards and that it can be trusted to perform as expected.

The “FileFixer Seal-of-Approval” tells you the same thing about a MicroStation designfile.

SafetyCheck is an MDL application from Axiom International. SafetyCheck tells youwhether or not any corruption was found the last time FileFixer was run on aMicroStation design file. If FileFixer didn’t find any corruption, that file is considered tohave the FileFixer Seal-of-Approval. If, on the other hand, FileFixer found corruptionthe last time it was run on that file, SafetyCheck reports the exact types of errors that werefound.

SafetyCheck is distributed by Axiom International at no charge to qualified MicroStationusers whether they own FileFixer or not.

The FileFixer Seal-of-ApprovalA wax seal is sometimes placed on an envelope containing legal documents. As long asthe seal remains unbroken, one knows that the envelope has not been opened and that itscontents have not been modified.

The FileFixer Seal-of-Approval works like a wax seal. When FileFixer is done testing adesign file, it writes a special code immediately following the file’s End-Of-Designmarker. As long as no new elements are added to the file, the seal remains undisturbed.But when new elements are added to the design file, the seal is overwritten.

SafetyCheck reports the presence or absence of the seal. If the seal is present and showszero errors, this design file merits the FileFixer’s Seal-of-Approval. That file is likely tobehave civilly, likely to translate to AutoCAD gracefully and unlikely to become corruptor have plotting problems.

If the seal is present, but indicates that FileFixer found errors when it was run on this file,SafetyCheck tells you about the errors that were found.

Chapter 12 — SafetyCheck Page 71

If SafetyCheck reports that the seal is absent, you know that the person who sent you thisfile either didn’t run FileFixer on it, or that the file was modified after they did. You canthen take your own measures to ensure that the file is properly validated.

The FileFixer’s Seal-of-Approval is displayed in the SafetyCheck’s dialog box when thecurrently loaded design file has been certified by FileFixer to have no errors greater than299. Once elements have been added to the certified design file then the Seal-of-Approval will disappear until the design file is once again certified.

How to test SafetyCheck1. Make sure the FileFixer option that writes the seal is not turned off. (Seal writing is

on by default.) This can be found at “Options menu | Search… | Report file”.

2. Run FileFixer in Search Mode on any design file.

3. Run SafetyCheck on the same design file. SafetyCheck will either verify thatFileFixer previously found no errors or it will report a summary of the errors thatFileFixer found.

4. Add a single element, say an ellipse, to the design file. Doing so overwritesFileFixer’s wax seal.

5. Now run SafetyCheck again. SafetyCheck will now report that no seal could be found.

Note: The seal-of-approval stamp is only placed at the end of the file when FileFixer isrun in “search” mode. It does not get placed when FileFixer is run is “repair” mode.

What SafetyCheck is used forMore and more organizations are insisting that outside contractors who create design filesfor them submit only design files that have been validated by FileFixer as being freefrom corruption. SafetyCheck makes it possible to quickly verify that the design filesbeing submitted have been properly validated without having to run FileFixer again onthe same set of design files.

SafetyCheck is also useful when archiving design files. Let’s say a design file is archivedto magnetic media with a zero-error Seal-of-Approval compliments of FileFixer. A yearlater the file is retrieved and is now found to have certain corruption’s in it. The presenceof the seal in the file indicates that the file was okay when it was archived and that anyflaw in the file was introduced later — the result of a flawed read head in the tape drive,perhaps. The person who originally did the archiving is thus vindicated from anyaccusation of having archived a corrupted file.

DisclaimerThe FileFixer Seal-of-Approval indicates that MicroStation design files comply in most,if not all, respects with IGDS standards published by Intergraph and subsequentlyextended by Bentley Systems, Incorporated to include additional element types.

Page 72 FileFixer

The exact design file corruptions which FileFixer attempts to detect and repair aredefined in the FileFixer document.

The FileFixer Seal-of-Approval does not guarantee a MicroStation design file will beappropriate for a particular purpose. The seal does not guarantee that your design file willbe trouble-free in all applications.

Chapter 13 — Miscellaneous Page 73

Chapter 13 — Miscellaneous

The following sections discuss a variety of things you should know about design filecorruption and FileFixer.

Everything you always wanted to know about corruptionFollowing is a list of some of the types of corruption FileFixer can detect and report:

• Words-To-Follow exceeds 65,533. This is a problem because adding 2 to a numberlarger than this (to get the total element length) will cause a 16 bit register overflow.(This is a problem for any software which stores the total length of a MicroStationelement in a sixteen-bit word.)

• Analysis of the number of database linkages, the dimension of the design file (2D or3D), and the number of vertices on a type 4, 6, 11 or 13 element indicates a Words-To-Follow error.

• Analysis of the number of poles, knots, rule lines, database linkages, and boundariesof 2D and 3D b-spline curves and surfaces indicates a Words-To-Follow error.

• Words-To-Follow is too small to indicate a valid element.

• Words-To-Follow of an active element exceeds 766. Most IGDS related programsreserves a buffer space of 768 words to store an element. Attempting to read in morewords than this can cause severe problems.

• Complex bits not set when they should be. (Uses Words-In-Description to track theelement nesting level.)

• Analysis of the vertices, points, or poles of a line, line string, curve, conic, pointstring, b-spline surface, or b-spline curve indicates an element range block error.

• Phantom elements. These are elements that are displayed, but cannot be selected ormanipulated in any way. This problem comes about when an element that is not partof complex element, such as a cell or a text node, has its complex bit incorrectly set.

• Analysis of the number of database linkages, characters, and Enter-Data-Fields in atext element indicates a Words-To-Follow error.

• Complex header element range doesn’t match components’ range. (Track the elementnesting level. The x and y min and max of each component element must be trackedsimultaneously, yet separately for each individual nesting level as each component isread in.) This error can cause serious problems because of the way current versions ofMicroStation handle cell placement.

• Analysis of the origin, number of characters, character size multiplier, rotation,and/or quaternions of a 2D or 3D text element indicates an element range error.

• 3D element found in 2D file. This involves two types of checks. 1) Some elementtypes (such as surfaces and circular truncated cones) exist in 3D files only. Detectingthese in a 2D file is easy. 2) When an element type can exist in either a 2D or a 3D

Page 74 FileFixer

file, we compare the number of characters, number of vertices, number of Enter-Data-Fields, number of poles, boundaries, ruler lines, knots, and Words-To-Followagainst each other to determine whether we have the 2D or the 3D form of theelement and report accordingly.

• 2D element found in 3D file. Same as above except that there are no element typesthat can exist in a 2D, but not in a 3D design file.

• Displayable element on invalid level. The first version of FileFixer could only detectdisplayable elements on level 0. The current version lets the user specify which levelsshould be considered invalid. Specifying which levels should be considered validgreatly improves the ability of the program to repair Words-To-Follow errors withoutlosing any elements and without including any bad elements.

• Analysis of the origin, major and minor axes, start angle, sweep angle, rotation, andquaternions of a 2D or 3D arc or ellipse indicates an element range block error.

• Incorrect Number-Of-Components in complex header. For dependability reasonsmany IGDS related programs have been modified so as not to rely on thisinformation. Nonetheless, an accurate Number-Of-Components word is part of thedefinition of an “ANSI standard” design file, so errors in this word are flagged.

• The first version of FileFixer flagged only type 0 elements as erroneous. The currentversion lets the user specify which element types should be considered invalid. Thisimprovement greatly improves the ability of the program to repair Words-To-Followerrors without losing any elements and without including any bad elements. Bydefault, type 0, 20, and 127 elements are considered invalid.

• Low range block value is greater than high range block value. The x, y, and (for a 3Dfile) z range block coordinates are examined in pairs.

• Displayable element has its reserved bit set. Technically this is not an error becausethere are no known programs that rely on this bit in any way. However, when tryingto pick up the trail of a valid element chain, the sophisticated algorithm FileFixeruses to automatically repair corrupted design files will make note of the fact that apotentially valid element has a set reserved bit and severely downgrade the likelihoodthat this portion of the design file is part of a valid element chain. (Note that as ofMicroStation version 4.0, the reserved bit may be used to store element levels from64 to 127. When the “127 LEVELS” option is turned on, FileFixer is aware of thisuse of the reserved bit and won’t flag reserved bit errors.)

• Too many vertices on a line string, shape, curve, etc. Different programs havedifferent tolerances for this problem. Some have problems if there is even one toomany vertex. Some don’t have problems until there are 20 or 30 or vertices more thanthere should be. Almost any program, however, given enough extra vertices, willbehave incorrectly.

• Analysis of the centers, radii, and quaternions of a right circular truncated coneindicate a range block error.

• A complex element (the whole element, not just the header — as indicated by theWords-In-Description stored in the complex element header), must end at thebeginning of a valid element. If this is not so, when this complex element is deletedusing IGDS, the entire design file will get corrupted. The way to detect this is to scanthrough the element using two different methods, 1) using Words-To-Follow and 2)


using Words-In-Description. If these two techniques don’t lead to the same designfile block/byte offset, something is wrong.

• A variation of the above error is if the Words-In-Description of an element points to alocation which is later discovered to be past the end of the design file.

• Even if a complex element ends at the start of a valid element you can still have aWords-In-Description problem. In a multiply nested complex element (nested morethan one level deep), it is possible for an “inner” complex element to end after an“outer” complex element. This is not as serious as the above mentioned types ofWords-In-Description errors because deletion of such an element will not corrupt theentire design file. Deleting an element with this kind of problem will, however, deletemore elements than the one intended. It can also cause the complex (nested element)status to be erroneously dropped for later elements and leave complex bit errors inthe design file.

• Missing End-Of-Design marker.

• File dimension bits not set to legal values (not 2D or 3D). The dimension of celllibraries and design files is indicated by bits in their type 5 and type 9 elements. If thebit values are illegal, some programs will treat the file as 2D, others as 3D. FileFixercan determine the actual file dimension by analysis of the elements themselves, sothis is easily remedied.

• Deleted type 8, 9, or 10 detected. Not necessarily an error, but something to besuspicious about.

• Type 1 element detected in design file. Type 1 elements should be found only in acell library. (Note that the list of element types FileFixer considers invalid isautomatically modified based on whether the file being analyzed is 2D or 3D or adesign file or cell library.)

• Type 9 element that is not on level 8 or 1 detected.

• The number of words of attribute data is not a multiple of 4.

• Index-To-Attributes is too small.

• Index-To-Attributes is too large. Index-To-Attributes errors can cause severedatabase problems.

• Cell levels mask is incorrect. This problem occurs when the list of occupied levels ina cell header element (type 1 or 2) does not match the actual levels used by the cell.When MicroStation displays a design file with cell level mask errors, the followingproblems can occur: 1) Cell components disappear, 2) Cell components are visibleafter multi-view updates, but not after single view updates, and 3) Cells cannot beselected or manipulated. Note that FileFixer has the ability to repair this type ofproblem automatically.

• Missing vital element (such as type 9, 8, or 10). FileFixer can be used to repair thiskind of problem.

Page 76 FileFixer

What FileFixer won’t do With all the things FileFixer does well, it’s easy to believe that it can do things it can’treally do. We feel it’s important for the user to understand the limitations of FileFixer.The list below describes some of the things that FileFixer can’t do:

• FileFixer works by analyzing each design file element it encounters. It can detectwhen an element violates certain basic rules of IGDS/MicroStation elementconstruction. Although FileFixer can tell when a rule is violated, it cannotcompletely predict what consequences that violation will have. Many violationswon’t cause any noticeable operational difficulties. So don’t be alarmed whenFileFixer finds errors in a design file you are not having problems with. Do be aware,however, that if you ever do start having problems with that file, that the error foundby FileFixer may be the culprit. Experience will teach you which errors are importantand which are unimportant.

• FileFixer repairs the types of errors that are listed on the Automatic Design FileRepair command. These are the only error types that FileFixer can repairautomatically. To repair other types of errors, follow the directions that go with eacherror number. What each error number means and how to correct that type of error islisted elsewhere in this document.

• FileFixer won’t find every possible error in every design file. There is only one waya design file can be constructed correctly. There are an infinite number of ways andcombinations of ways that one can be constructed incorrectly. FileFixer currentlydetects 50 to 100 of the problems we consider the most important or the mostcommon. We are in the process of implementing 50 to 100 more checks. By sendingus the design files you encounter that FileFixer doesn’t fully diagnose, you helpensure that FileFixer will eventually be able to detect the special kinds of problemsthat are common at your specific site.

We know that FileFixer isn’t perfect. We are working hard to make it better. Weappreciate your help in helping us do our job better.

Don’t kill the messenger When you first run FileFixer on a design file (or cell library), you may discover moreerrors than you bargained for! Design files that seem to work perfectly normally, maygenerate dozens (perhaps hundreds) of messages. Why is this?

FileFixer works by detecting elements and combinations of elements that violate a basicrule of IGDS/MicroStation design file construction. There are hundreds of these rules.The rules tend to fall into three certain categories:

1. Rules that affect only one element. Examples of such rules are:

• The element range must be set correctly.

• Words-To-Follow must be within a certain range.

• Planar elements must have their P-Bit (Planar Bit) set.

2. Rules that affect small groups of elements. Examples are:

• Complex bits must be turned on for the components of complex elements.


• The Words-In-Description of a complex element header must point to thefirst element after the complex group.

• Snap bits within complex groups must be set a certain way.

3. Rules that affect the design file as a whole. Examples:

• The first element of a design file must be a type 9.

• GRAFIC in the type 9 must be greater than any graphic group number usedin the design file.

• The last “element” of a design file must be an End-Of-Design marker.

When FileFixer reports something wrong with a design file, there is nearly alwayssomething wrong. The question is — how serious is it? The documentation that comeswith FileFixer goes a long way toward helping you determine how serious each error is.As you gain more experience with FileFixer, and MicroStation design files in general,you will become more and more skillful at determining how serious each type ofcorruption is and what to do about it.

If you’re tired of seeing mountains of error messages that indicate problems you aren’tworried about, just turn off the unwanted error messages. Use the search options to turnoff reporting of the types of errors you are not concerned about. The other errors, the onesthat you are concerned about, will stand out much more readily by doing so.

Does this documentation seem hard to read? If this documentation seems too advanced or is difficult to read, you may just need morebackground data. You will get the most out of this document if you have already read,recently reviewed, and thoroughly understand the following materials:

MicroStation 4 MDL Manual.

MicroStation 4 Customer Support Library Reference (MicroCSL) Manual, Appendix A.

The IGDS Application Software Interface Document, Appendix C.

Knowing these references well will make reading this document a great deal easier.You’ll also have a greater understanding and appreciation of just what FileFixer is doingwith the design files it processes.

How to test FileFixer FileFixer accomplishes things that until recently many experts considered impossible.Although FileFixer is inexpensive compared to the amount of time, money, andfrustration it will save, you have every right to ask, “Does this program really work?”The purpose of this section of the documentation is to help you answer this question toyour own satisfaction. Try the following:

• Create a new design file.

• Use IGDS or MicroStation to add up to 200 blocks (102,400 bytes) worth ofelements to the file.

Page 78 FileFixer

• Use EdG to change the Words-To-Follow of some elements to 0.

• Change the Words-In-Description of a cell.

• Mess up IGDS/MicroStation elements in any way you can think of. (Be creative.)

• Run the resultant mess through FileFixer and see what percentage of the errors itcan find. If you find any errors that FileFixer can’t detect, send us a copy of thefile and tell us how you would like future versions of FileFixer to work regardingthese errors.

• You can also run FileFixer on the test files that are shipped with all demos.These are small enough for the restricted demo to fix and demonstrate a greatmany of the types of errors FileFixer can find.

• If you have any questions that a thorough reading of this document doesn’tresolve, give us a call.

Problem Element Viewer Problem Element Viewer (formerly called Locate-Zinger) is a product that will help yourepair damaged design files.

The definition of “zinger” as used within the MicroStation community is as follows:

zinger; 1) An illegitimate, usually long, straight line that starts mid-screen or mid-plot and terminates at the extreme edge of the screen or plot. 2) Any erroneous orundesirable element.

FileFixer tells you which elements have problems. Problem Element Viewer shows youwhat those elements look like.

Example:

Let’s say FileFixer tells you that element #259 is a line string that has too manyvertices. This element looks okay on the screen, but when you plot it, you get“zingers”. You might be tempted to delete this element, but it might be an importantpart of your design file.

Here’s the solution: Bring up the design file in MicroStation, run Problem ElementViewer and enter 259. Problem Element Viewer will zoom in on element #259 so youcan see what it looks like. Now you can make an informed decision about whether toredraw the element or just delete it.

Deleting an element without knowing what it looks like is dangerous. ProblemElement Viewer gives you the information you need to make a safe, informeddecision.

Helpful hints If you are having trouble adding a type 9 element to a design file that doesn’t have one,the donor file you are specifying may be of a different dimension (2D or 3D) than therecipient file. If this is the case, try a donor file of the other dimension.


The EdG element numbers listed in the report file (fixer.rep by default) correspond toelements in the input file (the file being fixed or analyzed). When repairing Words-To-Follow errors some partially corrupted elements in the input file may be skipped. In thissituation the element numbers listed in the report file may not correspond with theelement numbers reported by EdG. When you are only analyzing files and when you arenot trying to repair Words-To-Follow problems, the element numbers given in the reportfile should correspond to EdG element numbers exactly.

When an element contains more than one error, FileFixer will report on the error itconsiders the most serious.

If you experience a power failure while using FileFixer, you may find a file with theextension “.A__”. This file lists the design files you were planning to process. Such filescan be deleted.

If you experience a power failure while you are repairing a design file, you may discovera file that starts with the letters “ff”. This is a temporary version of the design file youwere in the middle of repairing. Such files can be deleted.

If a design file is acting oddly (crashes randomly, elements appear and disappear as youzoom in and out on them, etc.), you should (1) use the FileFixer Replace Type 9command to replace the type 9s and the type 8 and type 10 of the file and (2) use theFileFixer Manual Design File Repair command to remove the type 66 elements from thedesign file. (This advice may take up but a few lines of this document, but it is one of themost important data in it.)

You may note that output (.fix) files are frequently smaller than the input (.dgn) files theycome from. Some users have expressed concern that this means FileFixer is notrecovering as many elements as it could, even though this is not usually the case. Most ofthe file size reduction stems from the fact that FileFixer leaves deleted elements out ofthe output (.fix) file, in essence doing a compress as it works, not because it is losingdesirable elements.

After fixing a cell library, you should recreate the cell library index file, if it had one. Usethe MicroStation index command to do so.

Although it is possible to use FileFixer to repair permanent files with an extension of .fix,this is highly frowned upon. FileFixer makes little effort to ensure the integrity of fileswith an extension of .fix. Files with a .fix extension may be destroyed by FileFixer. (Notethat this does not mean it is not okay to fix temporary .fix files produced by FileFixer. Ifsomething were to happen to one of these files, it is easily created by rerunning FileFixeron the original, permanent version.)

FileFixer has a mode called “emergency scanning”. FileFixer uses emergency scanningwhen the Words-To-Follow of an element does not point to the next element. FileFixeruses emergency scanning to find the next element without using Words-To-Follow.While in emergency scanning mode FileFixer writes a message to the bottom of thedialog box to let the user know what’s going on. Frequently FileFixer can figure outwhere the next element starts so quickly that this message flashes for only an instant,perhaps too quickly even to read. So if you were wondering what that bright flash acrossthe bottom of the screen was while fixing a file, that’s what it was.

A particular error may be obscured by an error FileFixer considers more serious.Therefore, if FileFixer fails to fix one of the kinds of corruption listed on the ManualDesign File Repair screen, try running FileFixer again on the output (.fix) file. An error

Page 80 FileFixer

that was obscured the first time through, may become fixable once the more seriousproblem is corrected.

If your design file uses filled elements, turn off the REMOVE TYPE 66 ELEMENTSoption.

This version provides a work around for customers who have installed NFS with filelocking turned off. To provide maximum file protection, previous versions of FileFixerrefused to open files it could not lock. Axiom recommends against installing NFS withfile locking not activated. We believe doing so, in spite of the fact that this is the default,is a possible source of network file corruption. Programs with less file protection thanours may run across the network with file locking turned off, but do so, we believe, byendangering your files. For those (daredevil) customers who want FileFixer to work onfiles across the network in spite of the fact that file locking is inactive we now provide amechanism for doing so. Simply set the environment variable NONFSLCK to YES(don’t forget to export NONFSLCK) and FileFixer will run on files across the networkeven with NFS file locking inactive. Again, we ordinarily recommend against the use ofthis option, but provide it for those customers who have a valid reason for leaving NFSfile locking off.

For those of you who are running this across an NFS network we recommend that youput your fixer.fix files on the system you are running from. This will greatly speed upFileFixer. Otherwise, there will be a lot of network traffic which can make FileFixer runat least 10 times slower depending upon the design file size.

For those of you who are using Modeler you will need to increase the size of the repairattribute linkage limits from 40 to 120. Modeler saves the rendering information inattribute linkage and FileFixer could remove them if this limit isn’t increased.

After upgrading from an older version of FileFixer it is best not to use the older FileFixeroptions resource file. After installation this file is named “fixer.rsc”. When FileFixer triesto use an older resource file it attempts to use as much of your settings as possible, buteach new version of FileFixer you have more and more options so it makes it moredifficult for FileFixer to extract this information. Sometimes when using an olderresource file you may get unpredictable results and FileFixer may even abort. Westrongly suggest you start with the new resource file, which will be in the directoryyou’ve installed FileFixer in, and then make any changes to it.

FileFixer makes as many repairs as possible during its three steps. FileFixer does manyfixes during step 3. However, once FileFixer has found something to correct during stepthree it will do it, but it will not continue looking for other corrupts will that element.This means that you may want to check for more errors in the fixed file before decidingthat the design file is corruption free.

Give Us Your Tired, Your Poor, Your Corrupted... You should never be satisfied with less than 100% perfect performance from this product.If you find any files that FileFixer cannot diagnose and/or repair or if FileFixer reportson something that doesn’t appear to be an error, send the file along with a description ofthe problem to us. We will do our best to find out what is wrong with your file and modifyFileFixer to handle that kind of corruption in the future.


If you find so much as a comma out of place with this product or its documentation, weare interested.

Contact Axiom International Support to obtain instructions for uploading problem files toour ftp site. Design files can be accepted on floppy disk only in MS-DOS format.

Be sure you have read the section of this documentation entitled “What FileFixer won’tdo” on page 76 before submitting problem files.

All files must be submitted with a report that explains exactly what operational difficultyyou are having with the file(s) in question and everything that needs to be done for us toreproduce the difficulty. We can analyze only those problems we can reproduce.

Page 82 FileFixer

Chapter 14 — Error Messages

Operational errors and messages

003 — Error creating output design file or cell library.

Cause — You don’t have the privilege to create files in the directory you specified.

Cause — The directory you specified does not exist.

Cause — You are out of disk space on the specified disk.

Cause — There is something wrong with the computer or its file system. For example,there may already be too many files open. Or the file system is corrupted.

Solution — Have your system manager find out why the file couldn’t be created andhandle.

004 — Process aborted by user.

Cause — You pressed the ABORT key while FileFixer was processing a file. UnderMS-DOS, this is the <ESCAPE> key.

005 — Too many errors have already been reported for this file.

Cause — The Search for Problems command screen lets you control the maximumnumber of errors that can reported for each file. This design file had more than thatnumber of errors.

Solution — Increase the maximum number of errors that can be reported.

006 — Deleted element detected.

Cause — This error is used internally and should never be reported to the user.

Solution — Call Axiom International.

007 — Could not rename temporary output design file to .fix file.

Cause — You don’t have the privilege to delete the old .fix file.

Cause — You don’t have privilege to make changes to the directory containing thedesign file being processed.

Cause — There is something wrong with the computer or its file system. For example,there may already be too many files open. Or the file system is corrupted.

Solution — Have your system manager find out why the file couldn’t be created andhandle.

Chapter 14 — Error Messages Page 83

010 — (Informational message)

Cause — This is an informational message only. It is not an error message. It does notmean that anything is wrong. FileFixer is simply giving you some extra data about whatit is doing.

017 — Unable to open file.

Cause — You do not have the necessary privilege to open this file.

Cause — Someone else or another process has the file open at the moment.

Cause — There is something wrong with the computer or file system. For example, theremay already be too many files open.

Effect — This file cannot be processed by FileFixer until the problem is corrected.

Solution — Have your system manager determine why the file cannot even be opened.

021 — This element is a type 9 the user asked to replace.

Cause — You have asked the Automatic Design File Repair command to replace theheader element (the first element in the file) with a type 9 from another design file. Thiselement is the one you asked to replace.

Effect — The type 9 from the donor file you specified using the REPAIR OPTIONSscreen will replace this element. Note that FileFixer is smart enough to make sure thatboth files (this file and the donor file) have the same number of dimensions and that theWTF of the type 9 we are replacing is 766 before attempting this action. Note also thatFile Fixer forces on the UPDATE GRAFIC and CANODE options to ensure that thedonor type 9 is fully compatible with the design file it is copied to.

029 — Backup file already exists.

Cause — You are in WORK ON ORIGINAL mode. You’ve told FileFixer to make abackup of your file and to make changes to the original file. A .bkp version of this filealready exists. To make sure that running FileFixer on the same design file more thanonce cannot delete the original version of the file (now stored in the .bkp file), FileFixerwill not overwrite a .bkp file that already exists.

Effect — You won’t be able to repair this file until the situation is remedied.

Solution — Rename the .bkp file to something else.

Solution — Use wildcards in the backup file extension.

Solution — Turn WORK ON ORIGINAL mode off. That way you’ll be creating a .fixfile instead of modifying the original file and creating a backup copy.

Solution — If you are absolutely positive that this backup file will never be needed, youcan delete it.

037 — Element has unwanted attribute linkage.

Cause — You have requested FileFixer to remove all the attribute linkages and thiselement has one.

Page 84 FileFixer

Effect — FileFixer will remove the attribute linkage as you requested.

Solution — FileFixer will remove the attribute linkage as you requested. Note thatFileFixer will not shrink an element to less than 22 words because some processes haveproblems with elements smaller than that.

050 — Error writing element to output (.fix) design file.

Cause — In most cases this error is caused by insufficient disk space on the disk towhich FileFixer is writing the output design file.

Cause — If the words-to-follow is greater than 780 you can also get this error.

Effect — The output design file will not be complete.

Solution — Copy the design file you want to repair to a disk with more disk space.

Solution — Free up some room on the disk in question by deleting unnecessary files.

079 — Unwanted End-Of-Design marker detected.

Cause — You have requested FileFixer to recover elements after the End-Of-Designmarker. This is the message that is generated when an End-Of-Design marker that will beignored is encountered.

Effect — FileFixer will search for elements after the End-Of-Design marker.

086 — Internal error in j_valnest involving complex header element. Cause — Used internally only.


088 — Fatal error detected with BackScanning in effect.

Cause — Used internally only.


Suspicious Conditions — Usually not Important

101 — Deleted type 9, 8, or 10 element detected.

Cause — Type 9, 8, and 10 elements are not usually deleted from a design file.

Effect — A deleted type 9, 8, or 10 element doesn’t violate any basic rule of design fileconstruction. It is noted because it is unusual and could be a sign of other problems.

103 — Reserved bit is set.

Cause — There is an unused bit in every IGDS/MicroStation element called the reservedbit. It was intended to allow future enhancement of the IGDS element format, but was


never used. This bit should be clear (set to 0). If it is not, this message is generated.Technically this is not an error because there are no known programs that rely on this bitin any way. However, when trying to pick up the trail of a valid element chain, thesophisticated algorithm FileFixer uses to automatically repair corrupted design files andcell libraries will make note of the fact that a potentially valid element has a set reservedbit and severely downgrade the likelihood that this element is part of a valid elementchain.

Cause — As of version 4.0 of MicroStation, it is possible for a design file to use up to127 levels. If this is such a design file, if this element is on a level above 63, and if the“127 LEVELS” option of FileFixer is not turned on, you may get this error. If this designfile uses more than 127 levels, turn on the “127 LEVELS” option of FileFixer and youwill no longer receive this message.

Effect — None at this time, but should Bentley Systems, Inc. decide to use this bit forsomething or if some application decides to use this bit for something (notrecommended), the fact that this bit is set could cause problems.

Effect — If you ever decide to start using 127 levels, this element will suddenly bemoved to the wrong level.

Solution — None required at this time.

105 — Type 21 range doesn’t match the min-max of its poles. Cause — The range of a type 21 is incorrect. The element’s range and the min-max of itspoles don’t fall within the user specified tolerance.

Cause — MicroStation sets the range of type 21 elements in a manner different from thewritten specifications for a type 21. The written specification calls for the range of a type21 to be set to the min-max of the poles for that particular type 21. MicroStation sets therange of a 21 to the min-max of all the poles in the b-spline element of which this type 21is part.

Effect — The scanning software of some processors may run infinitesimally slower dueto the range of these elements being somewhat larger than necessary.

Solution — Use the FileFixer’s Automatic Design File Repair command to fix this typeof problem automatically.

Solution — This error is so minor it can be ignored.

106 — EOD found too early in design file. Cause — A bad EOD (end-of-design) marker has been written to the middle of a designfile. This error will only be displayed if the design file is larger than 1KB and the EODmarker is found earlier than the middle of the design file. For example: the design filesize is 10,128 bytes, then this error will be displayed if the EOD marker is found beforebyte 5,064.

Effect — The elements after the EOD marker are now not being displayed.

Solution — Use the FileFixer’s Automatic Design File Repair command with theElements repair option “Recover elements beyond the End-Of-Design marker” turned onto recover elements beyond the EOD marker.

Page 86 FileFixer

107 — Element’s range may cause FIT problems

Cause — If all the displayable elements in a design file aren’t somewhat close togetherthen when you do a FIT most of the view is blank. The elements look like a dot in theview. FileFixer will check to see if several elements are some distance away from the restof the elements. This distance away is user definable. This is NOT a perfect test, it isFileFixer’s best guess for which elements are causing the problem. Since this is not aperfect test this search option is defaulted off.

Effect — When you do a FIT the elements look like a dot in the selected view.

Solution — Use EdG to delete the elements. Since this is not a perfect test for theelements that are causing the problem, we recommend that you make sure you want todelete these elements before doing so.

108 — File size is not a multiple of 512 bytes (1 block).

Cause — The number of bytes in the file (including the free space after the End-Of-Design marker) is not evenly divisible by 512 bytes.

Effect — The file may be difficult (or impossible) to transfer using FMU, KERMIT, orother file transfer utilities.

109 — Unusual type 9 element detected.

Cause — A type 9 element was found on a level other than level 1 or 8.

Effect — The element will most likely be ignored unless it is the first element in a designfile.

Solution — Use EdG to delete the element.

111 — Design file range is _________ should be _____________.

Cause — MicroStation not updating these TCB values.

Effect — This error will not cause MicroStation any trouble. At the current timeMicroStation doesn’t seem to use the design file high and low range values. If it does inthe future then key-in commands like FIT may not work properly.

Solution — Use the FileFixer Repair option “Correct the design file range (DFRANG)”,under Design File to correct the low and high range values.

115 — Type ___ element found on level ___.

Cause — An element was found on a level the user designated as unacceptable. (Thelevel indicated was not listed among the acceptable levels on the options screen.)

Effect — This error will not cause MicroStation or IGDS any trouble. This level isconsidered illegal only because the user has so designated it. Note that error 311 isidentical, except that the element is on level 0 which does violate IGDS/MicroStationelement construction rules and has more serious repercussions.

117 — Arc or ellipse axis may be too long.


Cause — An axis of an arc or ellipse is so long that it might cause MicroStation to fatallyabort. It is interesting that the condition for which FileFixer searches does not actuallyviolate any official IGDS or MicroStation element construction rules. We have added thisfeature to FileFixer only because some versions of MicroStation terminally abort uponencountering this condition.

Effect — MicroStation-PC sometimes fails with a “floating point” error when suchelements are manipulated.

118 — Arc or ellipse origin is off the design plane.

Cause — The origin of an arc or ellipse is off the design plane. The condition for whichFileFixer searches does not actually violate any official IGDS or MicroStation elementconstruction rules. We have added this feature only because some versions ofMicroStation terminally abort upon encountering this condition.

Effect — MicroStation-PC sometimes fails when such elements are manipulated.

Effect — MicroStation sometimes gives the error “System fault: floating point error.MDL abort in VIEWCTRL” when doing a FIT VIEW.

Solution — Use the FileFixer’s Automatic Design File Repair command with the “Fix ordelete arc/ellipse whose origin is off the design plane” option turned on. The only casewhere the origin can be corrected is when the high and low range values are equal andthat origin value is corrupted, otherwise the element will be deleted. For example: X high= 32689, X low = 32689 and X origin = -556890000000000.

119 — Element is too close to design file edge.

Cause — According to its range block, this element is located dangerously close to theedge of the design plane (or design cube).

Effect — Neither MicroStation nor IGDS should have any problems with such anelement. However, some auxiliary processes (InterPlot, for example) have been reportedto fail if an element is too close to the edge of the design file.

Solution — Use Problem Element Viewer to see what this element looks like and whereit is located. If this is a stray, unwanted element and is actually causing plotting (or other)problems, then use EdG or Problem Element Viewer to delete it.

Solution — If you are experiencing problems (particularly InterPlot problems) with thiselement, FENCE MOVE the entire design file towards the center of the design file.Change the global origin to readjust the coordinates of each element back to what theyoriginally were.

Solution — If you are not encountering any difficulties with this design file, turn off thedetection of this condition using the search options.

120 — This element is locked.

Cause — The L-Bit of this element is set.

Effect — IGDS and MicroStation will be unable to select this element. You will not beable to delete or modify this element. (The element behaves like a phantom element.)

Page 88 FileFixer

Solution — Use the FileFixer Repair option Unlock element, under Element to turn offthe L-Bit of the locked elements in a design file.

121 — Non-empty text node found in type 1 cell.

Cause — When IGDS creates a cell, it leaves non-empty text nodes (text nodes thatcontain at least one text element) out of the cell definition. The text elements (type 17s)within the text node are included in the cell definition, but the text node itself (the type 7)is not included in the cell definition. MicroStation works differently. It includes the type7 as part of the cell definition. When placing cells, IGDS cannot tolerate non-empty textnodes in cell definitions. They are placed incorrectly leaving complex bit and othererrors. Therefore cells created using MicroStation which contain non-empty text nodes, ifused under IGDS, will cause problems. Such cells can be placed by MicroStation withoutdifficulty.

Effect — The specified cell can be placed correctly by MicroStation, but not by IGDS.

Solution — If this cell must be used under IGDS, delete it from the cell library andrecreate it.

124 — Unwanted type 66 element encountered.

Cause — The user selected the REMOVE TYPE 66 ELEMENTS option on theAutomatic Design File Repair menu and this element is a type 66.

Effect — Type 66 elements can cause problems on IGDS. Users sometimes need toremoved them for this reason. Type 66 elements created under on one platform (such asCLIX) sometimes cause odd behavior on another platform (such as DOS).

Solution — This message is generated only when FileFixer is omitting type 66 elementsfrom the output design file. No further solution is necessary.

126 — CANODE is suspiciously high.

Cause — CANODE (in the type 9 of the design file) is greater than 65000. This does notviolate any IGDS or MicroStation rules, but it is somewhat unusual for CANODE to getthis high.

Effect — There is room for less than 600 new text node numbers. After that CANODEwill recycle back to 1 and you will be in danger of creating cross-linked text nodes (twodifferent text nodes sharing the same text node number). See error 530 for moreinformation about how an incorrect CANODE can affect a design file.

Solution — See error 530.

128 — GRAFIC is suspiciously high. Cause — GRAFIC (in the type 9 of the design file) is greater than 65000. This does notviolate any IGDS or MicroStation rules, but it is somewhat unusual for GRAFIC to getthis high.

Effect — There is room for less than 600 new graphic groups. After that GRAFIC willrecycle back to 1 and you will be in danger of creating cross-linked graphic groups (two


different graphic groups sharing the same graphic group number). See error 531 for moreinformation about how an incorrect GRAFIC can affect a design file.

Solution — This is not yet a serious problem; do nothing.

Solution — Use the FileFixer’s Automatic Design File Repair command with theUPDATE GRAFIC option turned on.

Solution — Use the FileFixer’s Automatic Design File Repair command with theRESEQUENCE GRAPHIC GROUP NUMBERS turned on.

131 — Curve or conic found in complex string or shape.

Cause — This is a legal construct, but causes MicroStation PC 3.00 and possibly otherversions of MicroStation to crash.

Effect — Zooming in on such an element may crash the system requiring a reboot.

Solution — Use a more recent version of MicroStation.

Solution — Drop status on the problem elements. Use the EdG command MODIFYSTATUS=DELETE on the offending complex headers. Then use the FileFixerCORRECT COMPLEX BIT ERRORS command to correct the resultant complex biterrors.

132 — Reserved nibble is non-zero.

Cause — The property word of every graphic element and complex header contains fourbits (a nibble) which are not used for anything and which should always be zero. Thereserved nibble is composed of bits 4:7 of the properties word.

Effect — Neither IGDS nor MicroStation use this information yet, so this error shouldnot cause any difficulties. However, the possibility exists that future enhancements toMicroStation could start using this information, in which case, the non-zero status of thisinformation could cause as yet indeterminable errors.

Solution — None needed at this time.

134 — GRAFIC is ___, but it should be ___. Cause — This error is essentially similar to error 534, except that GRAFIC is higher thanit should be instead of lower. This design file will run out of usable graphic groupnumbers earlier than it would if this error weren’t present. This is a very minor error.


135 — CANODE is ___, but it should be ___. Cause — This error is essentially similar to error 535, except that CANODE is higherthan it should be instead of lower. This design file will run out of usable text nodenumbers earlier than it would if this error weren’t present. This is a very minor condition.

Solution — Use the FileFixer’s Automatic Design File Repair command with theUPDATE CANODE option turned on.

Page 90 FileFixer

136 — Graphic group should be re-sequenced from ___ to ___.

Cause — User has requested that FileFixer re-sequence the graphic group numbers.

Solution — Use the FileFixer’s Automatic Design File Repair command with theRESEQUENCE GRAPHIC GROUP NUMBERS option turned on.

137 — Text node number should be re-sequenced from ___ to ___.

Cause — User has requested that FileFixer re-sequence the text node numbers.

Solution — Use the FileFixer’s Automatic Design File Repair command with theRESEQUENCE TEXT NODE NUMBERS option turned on.

138 — Element with database linkage has complex bit turned on.

Cause — The complex bit being turned on for an element means that the element is acomponent of a complex element. Component elements should never have databaselinkages. (They can have non-database linkages like the linkage that controls whether anelement is filled when it is displayed.) Only the header element of a complex elementshould ever have a database linkage. This element has a database linkage and its complexbit is turned on.

Effect — This problem by itself should cause no problems. As long as everything elseabout this element is correct, this problem should not be noticeable.

Solution — If the element is truly part of a complex element turn off the A-Bit usingEdG. Then let the Automatic Design File Repair command of FileFixer, strip off theunwanted database linkage.

Solution — If the element is not truly part of a complex element, the FileFixer’sAutomatic Design File Repair command will automatically turn the complex bit off foryou.

139 — Multiple instances of line style linkage.

Cause — Somehow the element had more than one occurrence of the line style linkage.This is a minor error.

Effect — This doesn’t seem to cause MicroStation any problem. It’s just taking up spacein the design file.

Solution — Use the FileFixer’s Automatic Design File Repair command with theREMOVE MULTIPLE INSTANCES OF LINE STYLE LINKAGE option turned on.This will remove all the line style linkages except for the first one.

140 — Tag ID ____ not associated with any element.


Cause — Somehow the element this tag element was associated with has been deleted orthe tag linkage on that element has been deleted. This is a minor error.

Effect — This doesn’t seem to cause MicroStation any problem. It’s just an unusedelement by MicroStation taking up space. These tags won’t be displayed.

Solution — Use the FileFixer’s Automatic Design File Repair command with theDELETE TAG NOT ASSOCIATED WITH ELEMENT option turned on.

141 — Tag set _____ is unused.

Cause — Tag set you created but never used. This is a very minor error, it is not causingany problem.

Solution — Use the FileFixer’s Automatic Design File Repair command with theDELETE UNUSED TAG SETS option turned on.

142 — Element is tagged but there are no tags.

Cause — The tag elements have been deleted but the displayable element still is flaggedas having tags.

Effect — MicroStation seems to handle this case just fine.

Solution — Use the FileFixer’s Automatic Design File Repair command with theREMOVE TAG FROM ELEMENT WITH NO TAGS option turned on. This option willdelete the tag linkage from the displayable element.

143 — Tag element string _____ is different than definition ____.Tag element integer ______ is different than definition ________.Tag element real _________is different than definition ________.Tag element type ________ is different than definition

Cause — You have changed the tag set definition since this tag was created. The tag type(string, integer or real) has been changed to a different type or the value has beenchanged.

Effect — When the tag is displayed it won’t be the same as you have currently defined inthe tag set.

Solution — Use the FileFixer’s Automatic Design File Repair command with theUPDATE TAG ELEMENT FROM TAG SET option turned on.

Page 92 FileFixer

144 — This font library does not contain font ____.

Cause — The font library you have specified to FileFixer does not contain the font usedby this text element. Either this element is corrupt or you are telling FileFixer to use adifferent font library than was used to create this element.

Effect — MicroStation will display this element using its default font.

Solution — Use the SEARCH OPTIONS screen to tell FileFixer to use the same fontlibrary that you usually use to display this file.

Solution — If you have specified the correct font library to FileFixer, then change thefont of this element to one that you do have in your font library.

145 — This font library has no character ____ in font ____.

Cause — The font library you have specified to FileFixer does not contain the specifiedcharacter in the font used by this text element. Either this element is corrupt or you aretelling FileFixer to use a different font library than was used to create this element. If thecharacter string shown in quotes is more than one character long and ends with a lowercase “x”, the bad character is an unprintable character. What is shown in quotes is thehexadecimal representation of the character.

Effect — MicroStation will display a blank for this character.

Solution — Change the font of this element to one that you do have in your font libraryor resource file.

147 — Deleted phantom element encountered.

Cause — This element is deleted, has its complex bit set and is not part of a complexelement.

Effect — This element does not violate any MicroStation design file construction rules,but is noted simply because it may be an indicator of other types of corruption in the area.

Solution — FileFixer’s Automatic Design File Repair command will delete this elementfor you automatically.

150 — Text height _________ size is larger than _____________.Text height ____________ size is smaller than ______________.Text width ____________ size is larger than ________________.Text width _____________size is smaller than ______________.

Cause — The text height or width is either larger or smaller than normal.

Effect — If the text height or width is too small than it might not be displayable inMicroStation.

Effect — If the text height or width is too large than it might cover up other elementswhen displayed.

Solution — Use MicroStation to adjust the text.


152 — Text height __________ to width ___________ is bad.Text width ________ to height _________ is bad.

Cause — The text height to width ratio is to large or the width to height ratio is large.

Effect — The text will not display correctly. The text will either be tall and narrow orwide and short.

Solution — Use MicroStation to adjust the text.

153 — GGBASE ___ is greater than GRAFIC ___.Cause — The GGBASE (graphic group base number) is greater than GRAFIC (nextgraphic group number). This means that the next graphic group number you use will beless than the graphic group base number.

Solution — Use EdG to change the GGBASE (graphic group base number) or GRAFIC(next graphic group number).

154 — NNBASE ___ is greater than CANODE ___.Cause — The NNBASE (text node base number) is greater than CANODE (next textnode number). This means that the next text node number you use will be less than thetext node base number.

Solution — Use EdG to change the NNBASE (text node base number) or CANODE(next text node number).

155 — Active level ___ is out of range (not between 1 and 63).

Cause — Any new elements will not be placed on the correct level.

Effect — MicroStation will not have any problems displaying this element.

Solution — Use MicroStation to correct the active level.

156 — Working units must be non-zero.

Cause — Any new elements will not be placed on the correct level.

Effect — Dimension elements created for any elements when the working units are zerowill have bad dimension values.

Solution — Use MicroStation to fix the working units.

157 — Design file header length must be 766 words.

Cause — The length of the design file header is not correct.

Effect — MicroStation will not consider this file a design file, and will not load it.

Solution — Use FileFixer to replace the type 9 element.

158 — Duplicate reference file attachment encountered.

Page 94 FileFixer

Cause — Only the first occurrence of a reference file attached is displayed inMicroStation.

Effect — The other occurrences of a reference file will not be displayed.

Solution — Use the FileFixer’s Automatic Design File Repair command with theDELETE DUPLICATE REFERENCE FILE ATTACHMENT option turned on.

159 — Cell library header length must be 23 words.

Cause — The length of the cell library header is not correct.

Effect — MicroStation will not consider this file a cell library, and will not attach it.

Solution — Use FileFixer to replace the cell library header.

160 — Tag set ID ______ is missing. Cause — The tag set has been deleted since this element was tagged using it. This erroronly occurs in a design file.

Effect — Can’t use that tag set again.

Solution — Use MicroStation to recreate the tag set.

161 — Linkage area {____ words} is suspiciously long.

Cause — The difference between the expected WTF of this element and its actual sizeindicates that either WTF is wrong or that the element has an attribute linkage area that issuspiciously long (more than 128 words).

Effect — This might be a rather long (but legitimate) user data linkage. Or it could be aregular data base linkage with 11 informational linkages. It might also be somecombination of both of these. These possibilities are legal, though unlikely. What’s mostlikely is that some part of the element such as number of vertices, text characters, Edit-Data-Fields, etc. is incorrect.

Solution — Use Problem Element Viewer to determine what this element looks like (ifpossible) so that you can redraw it. Use EdG or Problem Element Viewer to delete thiselement.

163 — The active angle _____ is out of range.Cause — The active angle saved in the design file header (type 9 level 8) is out of range(-360 <= angle <= 360).

Effect — Elements you place using the active angle won’t be placed correctly.

Solution — Use the MicroStation “active angle” keyin command to correct the activeangle.

165 — Null filled linkage found.

Cause —Null filled linkage, which are not required in make the element the minimumlength, increase the size of the design file.


Effect — MicroStation seems to work fine with this problem. It does however make thedesign file larger.

Solution — Use the FileFixer’s Automatic Design File Repair command with theREMOVE NULL FILLED LINKAGES option turned on.

170 — Duplicate type 9, level 8 (design file header) found. Cause — Multiple design file headers.

Effect — May not be able to display all the elements.

Effect — May not be able to display any elements.

Solution — Use FileFixer to delete the duplicate header.

171 — Shared instance level should be {___} not {___}. Cause — The level of a shared cell instance should be the same as the shared celldefinition.

Solution — Use the FileFixer to set the level to the same as the shared cell definition.

175 — Text element rotation angle is set to 360 degrees.

Cause — When text elements are rotated from one angle to an angle of 0 degrees, itassigns an angle of 360 degrees. This only occurs in a 2D design file.

Effect — Unknown.

Solution — Use FileFixer to set the angle to 0 degrees.

180 — Questionable element type detected.

Cause — This element’s type is not defined by IGDS or MicroStation. It is either anapplication element whose type the user failed to add (options screen) to the list of validapplication elements, or it is a corrupt element (garbage).

Effect — The element will either be ignored or treated as an application element.

Solution — If the element is not a valid application element, it should be deleted.(FileFixer does not do detailed validation testing on application elements at this time, soit is up to the user to determine whether this is an application element.)

190 — Type 11 (curve) or type 13 (conic) with two visible vertices has arepeating vertex.

Cause — A curve or a conic that has two visible vertices (six vertices counting the twoinvisible vertices at the beginning and the end of the curve) has two vertices in a row thatare exactly the same.

Effect — DXF translation will sometimes crash on such elements.

Effect — Other processors may crash.

Page 96 FileFixer

Effect — The element may display or plot intermittently (sometimes there, sometimesnot).

Solution — FileFixer’s Automatic Design File Repair command will delete this elementautomatically by default.

191 — Text element has more EDFs than characters.

Cause — A text element with more EDFs (Enter-Data-Fields) than characters has beenencountered.

Effect — Unknown.

Solution — Use Problem Element Viewer to find out what this element looks like. Deleteit. Redraw it.

Solution — Use FileFixer’s Automatic Design File Repair command with the EXTENDTEXT ELEMENT TO CONTAIN LARGEST EDF repair option turned on to repair theelement.

Minor Errors — Usually Won’t Cause Problems

301 — The number of words of attribute data is not a multiple of 4. Cause — Per the rules, database linkages should always be created in multiples of 4words. The number of words in the linkage area of this element is not a multiple of 4.

Effect — Since a DMRS database linkage utilizes all 4 words of a linkage, access to theproper database occurrence will probably be prevented.

Effect — For a user linkage, whether this situation will cause problems depends on thetype of user linkage involved.

Solution — Use EdG’s repair mode to repair this element.

302 — Type 1 elements are not allowed in design files.

Cause — Type 1 elements are library cell headers that should only be found in celllibraries.

Effect — IGDS and MicroStation ignore type 1 elements in design files.

Solution — Use the FileFixer’s Automatic Design File Repair command with theREMOVE ILLEGAL ELEMENT TYPES option turned on. Be alert for other types ofcorruption in the vicinity of this element. If FileFixer fails to delete this element becauseit detected a higher priority corruption first, then turn off all search options except 2DELEMENT FOUND IN 3D FILE, 3D ELEMENT FOUND IN 2D FILE and ILLEGALELEMENT TYPE DETECTED, and try again.

303 — Shared cell definition with no shared cell instance.


Cause — A shared cell definition has been found but there is no shared cell instancewhich uses that definition. This happens quite often when converting AutoCAD drawingfiles to MicroStation.

Effect —MicroStation will ignore this shared cell definition.

Solution — Use the FileFixer’s Automatic Design File Repair command with theDELETE SHARED CELL DEFINITION WITH NO SHARED CELL INSTANCESoption turned on.

304 — H-Bit should not be set for this element.

Cause — (Note: The H-Bit is called the H-Bit because for several element types itindicates a hole element. It means different things for different element types.) Accordingto the strictest rules of IGDS/MicroStation element construction, the only elements whoseH-Bit should ever be set are cells (type 2), lines (type 3), shapes (type 6), complex shapes(type 14), ellipses (type 15), and element types 21 through 28. This element was not oneof these types, yet its H-Bit was set. Since current versions of IGDS and MicroStationignore the H-Bit for element types that generate this message, this error will not causeany problems with current versions of IGDS and MicroStation. It might, however, causeproblems with future versions of MicroStation related software. This error is verycommon.

Effect — The situation causes no known problems with current versions of MicroStationrelated software.

Solution — This is an unimportant error. It is okay to ignore this error.

Solution — Use FileFixer’s Automatic Design File Repair command with the TURNOFF ILLEGAL H-BITS option turned on to repair this element.

305 — Element range doesn’t match the min-max of its vertices. Cause — This error is essentially similar to error 705, but is less severe in nature. Thiserror is generated when the range is off by more than the user specified tolerance, butwithin the tolerance -70% and 900%.

Solution — Use FileFixer’s Automatic Design File Repair to repair this element.

306 — Type 28 range doesn’t match range of its associated type 21.

Cause — This error is essentially similar to error 706, but is less severe in nature. Thiserror is generated when the range is off by more than the user specified tolerance, butwithin the tolerance -70% and 900%.


307 — B-spline pole element doesn’t match the min-max of its polesnor its b-spline surface header. Cause — This error is essentially similar to error 707, but is less severe in nature. Thiserror is generated when the range is off by more than the user specified tolerance, butwithin the tolerance -70% and 900%. See error 707 for more information.

Page 98 FileFixer


309 — Range of b-spline component does not match parent’s range. Cause — This error is essentially similar to error 709, but is less severe in nature. Thiserror is generated when the range is off by more than the user specified tolerance, butwithin the tolerance -70% and 900%.


311 — Design file header is not on level 8.

Cause — The level of the type 9 header element tells which version of IGDS created thefile. If the level is less than 8, this might be a very old design file (from before IGDSversion 8.0).

Cause — This is not and never was a design file.

Cause — This is a design file that has been damaged.

Effect — If this is not a design file then, of course, no IGDS/MicroStation programs willbe able to do anything with it.

Effect — If this is a damaged design file, most IGDS/MicroStation programs shouldhandle it without a problem because this information is usually ignored.

Solution — If this is, indeed, an IGDS 8.0 or later design file, you should use EdG tomove this element to the appropriate level, in almost all cases, level 8.

312 — Range of right circular truncated cone is incorrect.



316 — An element type that should never have its A-Bit set has its A-Bit set.

Cause — This type of element can only be a component of a complex element. There itshould never have its A-Bit (attribute bit) set. This element does anyway.

Effect — This situation violates the rules of standard MicroStation file create, but causesno known problems.

Solution — If the element doesn’t really have an attribute linkage, the FileFixer’sAutomatic Design File Repair command will turn off the A-Bit.

Solution — Since it doesn’t cause any known problem, you may want to ignore thiserror. You can turn off searching for this error using one of FileFixer’s options screens.

318 — Arc’s sweep angle ______ is invalid.

Cause — The arc’s sweep angle should always be between –360 and 360 degrees.


Effect — The arc may not display correctly.

Solution — The following procedure to modify the sweep angle of an arc is from theMicroStation 95 help system:

1. With AccuDraw active, select the Modify Element tool.

2. Identify the arc.

3. From the Method option menu in the Tool Settings window, choose Angle.

The drawing plane origin moves to the center of the arc, and the coordinate system alignsits x-axis with the start of the arc's sweep.

4. (Optional) Rotate the drawing plane axes.

5. (Optional) Preview the modifications by keying in desired changes in the AccuDrawwindow.

6. Enter a data point to complete the modification.

Note: You can adjust the arc sweep by either complement of the angle (180° either way).

320 — Complex header range is off by ___%.



322 — Number-Of-Components in complex header element isincorrect. Cause — Some complex header elements, such as type 7s and type 12s, specify thenumber of component elements that are embedded within it. For dependability reasonsmany IGDS related programs have been modified so as not to rely on this information.Nonetheless, an accurate Number-Of-Components word is part of the definition of an“ANSI standard” design file, so errors in this word are flagged.

Effect — Most, but probably not all, IGDS/MicroStation related programs ignore thisinformation. It should have little effect on most programs.

Solution — Use FileFixer’s Automatic Design File Repair command to correct theNumber-Of-Components.

323 — A deleted element was found within a complex element. Cause — Complex elements should not contain deleted elements.

Cause — The complex header element mentioned contains a Words-In-Description errorwhich causes it to think it contains elements that really should be after its end.

Effect — Some combinations of elements can cause MicroStation and IGDS to crash.

Solution — Run the FileFixer’s Automatic Design File Repair command with theHANDLE ILLEGAL COMPONENT IN COMPLEX ELEMENT option turned on. With

Page 100 FileFixer

this option turned on you have the choose of dropping status on the complex header orsqueezing out the deleted elements.

Solution — Run the FileFixer Manual Design File Repair command with all optionsturned off. This will remove all deleted elements from the file. Then run the ManualDesign File Repair command with CORRECT WORDS-IN-DESCRIPTION turned on.This will readjust the Words-In-Description of the complex element’s header.

Solution — If FileFixer sets Words-In-Description for the element incorrectly or if theabove solution fails for any other reason, delete and redraw the complex elementsinvolved. Axiom product, Problem Element Viewer, will help you find and display theelement you want to redraw.

324 — Range of arc or ellipse is incorrect. Cause — This error is essentially similar to error 724, but is less severe in nature. Thiserror is generated when the range is off by more than the user specified tolerance, butwithin the tolerance -70% and 900%.


325 — Range of text element is incorrect.

Cause — This error is essentially similar to error 725, but is less severe in nature. Thiserror is generated when the range is off by more than the user specified tolerance, butwithin the tolerance -70% and 900%. See error 725 for important information about thiserror.

Solution — Use FileFixer’s Automatic Design File Repair to repair this element. Be sureyou have the correct font library specified in MicroStation.

326 — Text element has zero width or height multiplier. Cause — Text elements should not have a zero width or height multiplier.

Effect — If both of the multipliers are zero then MicroStation will display this textelement as a tiny dot.

Effect — If only one of the multipliers is zero then MicroStation will display this textelement as a line, either vertical or horizontal depending upon which multiplier is zero.

Solution — Use MicroStation to delete and recreate the text element.

328 — Complex element has zero components.

Cause — The main purpose of a complex header element is to group together other typesof elements. The complex header element whose EdG element number is listed inparentheses has no component elements and therefore serves no purpose. (There aresituations where a complex header element has meaning even when it has nocomponents. FileFixer knows about these situations and does not report them as anerror.)

Effect — This element may be the source of Words-In-Description errors and nestingerrors.


Solution — Use FileFixer’s Automatic Design File Repair command with the repairoption DELETE COMPLEX ELEMENT WITH NO COMPONENTS turned on to deletethe complex element.

329 — GRAFIC should never be 0.

Cause — The type 9 of a design file contains a word called GRAFIC. The next graphicgroup placed in the design file should get GRAFIC as its graphic group number.GRAFIC is incremented after each graphic group is placed. GRAFIC in this design file is0.

Effect — The next graphic group you attempt to place in this design file will not betreated as a graphic group.

Effect — The ADD GROUP command will fail if you try to create a new graphic group.


333 — Class of element is illegal.

Cause — The class of this element is undefined (greater than 6).

Effect — This element may fail to display, may fail to plot, or may be left out of somefence operations.

Solution — Use the FileFixer’s Automatic Design File Repair command to set the classto a legal value.

334 — Number-of-Components exceeds legal maximum.

Cause — The maximum legal Number-Of-Components for elements that store thisinformation is 3641. This element has a Number-Of-Components word that is greaterthan 3641.

Effect — Most, but probably not all, IGDS/MicroStation related programs ignore thisinformation. It should have little effect on most programs.

Solution — Use EdG to count the number of components in the element. Use theMODIFY ELEMENT(20) command to set the correct Number-Of-Components.

335 — Text element has too many Enter-Data-Fields. Cause — Text elements can have up to, but no more than, 20 Enter-Data-Fields. Thistext element has more than 20 Enter-Data-Fields.

Effect — This element may display incorrectly.

Effect — This element may not display at all.

Effect — MicroStation or other processes may crash upon encountering this element.

Solution — Use Problem Element Viewer to locate and delete the element. Redraw theelement.

Page 102 FileFixer

336 — A component element is on a different level than its complexheader.

Cause — The indicated element is part of a complex element and is on a different levelthan its parent element.

Effect — Depending on what levels are being displayed, part of the element may bevisible while other parts are invisible.

Effect — Some processes may ignore the fact that parts of the element are on differentlevels and treat the entire element as though it were on the level indicated by the header.

Solution — Use FileFixer’s Automatic Design File Repair command with the repairoption MOVE COMPONENT TO SAME LEVEL AS COMPLEX HEADER turned onto move the component to the same level as its parent.

337 — A component element of one color is part of a complex header ofanother color.

Cause — The indicated element is part of a complex element and is a different color thanits parent element.

Effect — Some processes will treat this element as though it were the color indicatedwithin the element itself and some processes will treat this element as though it were thecolor indicated by the header element.

Solution — Use FileFixer’s Automatic Design File Repair command with the SETSYMBOLOGY OF COMPONENT TO MATCH ITS HEADER repair option turned onto repair this element.

338 — A component element of one line weight is part of a complexheader of another line weight.

Cause — The indicated element is part of a complex element and has a different lineweight than its parent element.

Effect — Some processes will treat this element as though it were the line weightindicated within the element itself and some processes will treat this element as though itwere the line weight indicated by the header element.

Solution — Use the FileFixer’s Automatic Design File Repair command with the SETSYMBOLOGY OF COMPONENT TO MATCH ITS HEADER repair option turned onto repair this element.

339 — A component element of one line style is part of a complexheader of another line style.

Cause — The indicated element is part of a complex element and is a different line stylethan its parent element.

Effect — Some processes will treat this element as though it were the line style indicatedwithin the element itself and some processes will treat this element as though it were theline style indicated by the header element.


Solution — Use FileFixer’s Automatic Design File Repair command with the SETSYMBOLOGY OF COMPONENT TO MATCH ITS HEADER repair option turned onto repair this element.

341 — A component is a different graphic group than its header.

Cause — All component elements must have the same graphic group number as thecomplex header.

Effect — Unknown.

Solution — FileFixer changes the graphic group number of the component element tomatch the header.

342 — Duplicate reference file logical name encountered.

Cause — This element is a reference file attachment whose logical name matches aprevious reference file attachment in this design file.

Effect — One or the other of the reference file attachments may not display.

Effect — One or the other of the reference file attachments may not plot.

Solution — Delete the unwanted attachment using MicroStation’s File-Referencecommand or using EdG.

343 — Reference file <________> is missing. Cause — The reference file may have been deleted.

Cause — The reference file may have been moved.

Effect — The missing reference file will not be displayed.

Effect — The missing reference file attachment will not plot.

Solution — Delete the unwanted attachment using MicroStation’s File-Referencecommand or using EdG.

Solution — Correct the path of the reference file attachment using Axiom’s RefManager.

346 — An Enter-Data-Field has an unrecognized justification. Cause — The Enter-Data-Field justification can only be left (-1), center (0) or right (1).


Solution — FileFixer changes the Enter-Data-Field justification to match the textjustification of the text element.

347 — An Enter-Data-Field completes outside the text string.

Cause — The Enter-Data-Field completes outside the text string. The Enter-Data-Fieldexpects the text string to be larger.


Page 104 FileFixer


Solution — Use the FileFixer’s Automatic Design File Repair command with theEXTEND TEXT ELEMENT TO CONAIN LARGEST EDF repair option turned on torepair this element.

348 — An Enter-Data-Field are not in order.

Cause — Enter-data-fields are not sorted.



Solution — Use the FileFixer’s Automatic Design File Repair command with theCORRECT EDF’s WICH OVERLAP OR ARE OUT OF SEQUENCE repair optionturned on to sort the Enter-Data-Fields.

349 — An Enter-Data-Field overlaps another Enter-Data-Field.

Cause — The Enter-Data-Field position or length is wrong so that it overlaps the nextEnter-Data-Field.


Solution — Use the FileFixer’s Automatic Design File Repair command with theCORRECT EDF’s WHICH OVERLAP OR ARE OUT OF SEQUENCE repair optionturned on to adjust the position and/or length.

350 — An Enter-Data-Field has a length of zero.

Cause — An Enter-Data-Field must have a length greater than zero.


Solution — Use the FileFixer’s Automatic Design File Repair command with theCHANGE ZERO-LENGTH EDF TO LENGTH TO 1 repair option turned on to repairthis element.

353 — A-Bit is incorrectly turned off or WTF should be ____.

Cause — The Words-To-Follow of this element is larger than expected. The nextelement in the file shows a reasonable possibility of being a valid element. If not for thefact that the A-Bit is turned off, the element’s Index-To-Attribute word would point tothe expected location of the linkage. The difference between the expected and the actualWTF is a multiple of 4, and the difference between the expected and actual sizesindicates that the cause of this anomaly could be the A-Bit of the element being turnedoff when there are indeed attribute linkages.

Effect — One of the parts of the element that affects Words-To-Follow is incorrect. Theeffect of this error is dependent on what part of the element is actually incorrect.

Solution — Try turning on the A-Bit, but be prepared to turn it off again if you aregetting data base or linkage errors.

Solution — Use the FileFixer’s Automatic Design File Repair command to fix this error.


Solution — See error 354 for additional solutions.

354 — Words-To-Follow warning. Cause — The Words-To-Follow of this element is larger than expected. Nonetheless, thenext element in the file shows a reasonable possibility of being a valid element. Oneexplanation for this is that the Words-To-Follow of the element is correct, but some otherpart of the element that affects Words-To-Follow (such as number of vertices, number ofcharacters, number of Enter-Data-Fields, the A-Bit, etc.) is incorrect.

Effect — One of the parts of the element that affects Words-To-Follow is incorrect. Theeffect of this error is dependent on what part of the element is actually incorrect.

Solution — Use Problem Element Viewer to see what this element looks like. If theelement displays properly, it may be okay to leave it in the file.

Solution — If Problem Element Viewer displays the element incorrectly, delete theelement and redraw it.

Solution — If you’re very (very) wise, you may be able to use EdG to determine whatpart of the element is wrong and correct it manually.


Solution — Turn off checking of Words-To-Follow errors (repair options) and run theFileFixer’s Search for Problems command on this file again. With Words-To-Followanalysis turned off, another error within this element may be discovered. This may helpyou to repair the file manually using EdG.

355 — Stray element found outside of any type 1 cell in a cell library.

Cause — A cell library should consist of only a cell library header and library cells.There should not be any elements between library (type 1) cells, before the first librarycell or after the last library cell.

Effect — MicroStation may be unable to find and place cells after this cell in the library.

Solution — Use FileFixer’s Automatic Design File Repair command to automaticallyremove this element.

356 — Rotation of text element does not match the rotation of the textnode it is in.

Cause — All the text inside a text node should be parallel. This text element has adifferent rotation than its parent text node.

Effect — Some of the text elements belonging to the text node may be omitted from thedisplay or from plots.

Effect — Some of the text elements belonging to the text node may be displayed at adifferent rotation angle than the other text elements in the node.

Effect — The text may plot at a different angle than the angle at which it is displayed onthe screen.

Solution — Drop status on the text node.

Page 106 FileFixer

360 — Tag set ID ______ is missing.

Cause — The tag set has been deleted since this element was tagged using it. This erroronly occurs in a cell library. Currently FileFixer doesn’t check for this error.

Effect — Can’t use that tag set again.

Solution — Use MicroStation to recreate the tag set.

362 — Possible 2D element in 3D file or vice versa.

Cause — Analysis of the number of vertices, database linkages, points, characters, Enter-Data-Fields, poles, boundaries, knots, etc. indicates that what might be a 2D element is ina 3D file or vice versa. Words-To-Follow in this element points to a design file locationwhich appears to be the start of a valid element. Using EdG to copy an element into adesign file of the wrong dimension is one possible way the error can be generated.

Cause — If you have an enormous number of these elements, you may have a 2D type 9at the top of a 3D design file or vice versa. Use the Replace Type 9 command to replacethe type 9 of this design file with one of the proper dimension.

Effect — File corruption is unlikely, IGDS and MicroStation may display very strangeresults for these elements. Other programs are likely to have problems also.

Solution — If you’re sure the type 9 (or type 5 for a cell library) of this file is of thecorrect dimension, then use EdG to delete this element.

Solution — If you’re not sure of the dimension of the header, replace the header with oneof the correct dimension.

364 — Siamese attribute linkage detected.

Cause — The attribute linkage extends beyond the end of the element it is attached. Thatmeans this linkage and the element following are sharing file space.

Effect — Since the shared file space can’t correctly contain both the attribute linkage andthe start of the next element, one of them must be corrupt. Chances are it is the attributelinkage. If it is the attribute linkage, then accessing the database using this linkage will, atbest, yield erroneous results and, at worse, cause MicroStation to crash.

Solution — FileFixer’s Automatic Design File Repair command can automaticallyremove the attribute linkage area of this element and adjust the graphic part of theelement so that no visual information is lost.

365 — Size of linkage is not a multiple of four.

Cause — The user linkage mentioned is not a multiple of four words in length. Note thatthis error is different from error 301 in that this error refers to the size of a particularattribute linkage as determined by analyzing Words-To-Follow of the user linkage itself(not Words-To-Follow of the element). Error 301 refers to the size of the linkage area.The linkage area is that part of the element after the graphic part of the element. Theattribute area of an element may contain several individual attribute linkages.


Effect — The same effects that can be cause by error 301 can be caused by error 765.

Solution — FileFixer’s Automatic Design File Repair command can automaticallyremove the attribute linkage area of this element and adjust the graphic part of theelement so that no visual information is lost.

367 — Cell header’s diagonal is invalid.

Cause — The cell header’s diagonal valids are invalid. One of the low ranges (X, Y, orZ) is higher than its corresponding high range.

Effect — The cell may not rotate.

Solution — Use the FileFixer’s Automatic Design File Repair command “Repair cellheader’s diagonal” to fix the diagonal.

369 — A-Bit is turned on even though there appears to be no attributelinkage.

Cause — The attribute bit of this element is turned on, but the Index-To-Attribute pointerof the elements points to a location beyond the end of the element.

Effect — Some database related processes may think part of the next element is theattribute linkage to this element. The result will be erroneous data base access at best orpossibly even a crashed design file.


375 — Active pattern scale set to zero in Extended TCB element.

Cause — In MicroStation 4.0 certain seed files were delivered with the active patternscale set to 0.

Solution — Use the FileFixer’s Automatic Design File Repair command “Set patternscale to one when zero” to fix this error.

380 — Illegal element type detected.

Cause — An element type, which should never exist (type 0, 20, and 127), was detected.

Effect — The element will probably be ignored. It is illegal for such elements to existand is probably an indicator of some other type of corruption. There is an excellentchance that there is an earlier Words-To-Follow error in the design file, which couldmake the design file undisplayable.

Solution — Use the FileFixer’s Automatic Design File Repair command with the“Remove illegal element types” option turned on. Be alert for other types of corruption inthe vicinity of this element. If FileFixer fails to delete this element because it detected ahigher priority corruption first, then turn off all search options except “2D element foundin 3D file”, “3D element found in 2D file” and “Illegal element type detected”, and tryagain.

382 — Type 8, 9 or 10 found in cell library.

Page 108 FileFixer

Cause — Type 8, 9 and 10 elements should be found only in design files. One of thesewas found in a cell library.

Effect — The element will probably be ignored. It is illegal for such elements to existand is probably an indicator of some other type of corruption.

Solution — Use the FileFixer "Remove illegal element types" repair option to deletethese elements.Be alert for other types of corruption in the vicinity of this element. IfFileFixer fails to delete this element because it detected a higher priority corruption first,then turn off all search options except “2D element found in 3D file”, “3D element foundin 2D file” and “Illegal element type detected”, and try again.

383 — Cell in a design file is nested within itself. Cause — This element is a cell that is nested within a cell of the same name.

Effect — The element will probably display and plot okay. But if you try to create a new(type 1) cell using this (type 2) cell, the elements in the redundantly named (innermost)cell will be missing from the (type 1) cell. That is because MicroStation will leave out thesecond (innermost) instance of the cell in order to prevent cell level nesting problems inthe cell library.

Solution — Use the FileFixer "Delete duplicate nested cell" repair option to deleteoccurrences of a cell that is nested within a cell of the same name. This option is off bydefault.

385 — First and last vertex of type 6 shape don’t match. Cause — The first and last vertex of a shape must always have the same location;otherwise the shape is not closed.

Cause — If you have many of these, you should suspect that the header of this file is ofthe wrong dimension.

Effect — Polygon, patterning, shading and hidden line processing software may produceerroneous results due to the element not being closed as expected.

Solution — Delete the element and redraw. To see which element needs to be redrawnbefore deleting element use Axiom product Problem Element Viewer.

Solution — If the header of this file is of the wrong dimension, replace the header withFileFixer’s Replace Type 9 command.

387 — Reference file attachment field name is blank.

Cause — A reference file attachment has been found with the number of characters inthe file name equal to zero.

Effect — MicroStation will not be able to display the reference file.

Effect — You will not be able modify this reference file attachment in MicroStation.

Solution — Use the FileFixer "Delete the reference file attachment with a blank filename" repair option to delete this reference file attachment.


388 — Reference file file name overflows its field.Reference file logical name overflows its field.Reference file description overflows its field.

Cause — The number of characters in the file name, logical name or description string islarger than its field.

Effect — MicroStation may abort when loading this design file.

Effect — EdG may exit when opening this design file.

Solution — Use the FileFixer "Correct the file name, logical or description strings fromoverflowing" repair option to fix the string from overflowing.

390 — Text element has zero characters.

Cause — A text element with zero characters has been encountered.

Effect — MicroStation will ignore this element.

Solution — Delete this element.

Future Problems — File is in Danger

505 — WID error. Complex component exceeds length of parent.

Cause — In a multiply nested complex element (nested more than one level deep), an“inner” complex element ends after an “outer” complex element.

Effect — This is not as serious as other types of Words-In-Description errors becausedeleting this element will not corrupt the entire design file. Deleting an element with thiskind of problem will, however, delete more elements than the one intended. It can alsocause an erroneous drop ping of complex status of a later element and leave complex biterrors in the design file.


510 — Element with A-Bit off, WTF minus ITA is not equal to 14.

Cause — The Index-To-Attribute word of an element should point to where in theelement the database linkage starts (if it has a linkage) or where in the element it wouldstart (if it doesn’t have a linkage). When there are no database linkages the differencebetween Words-To-Follow and Index-To-Attributes should be 14.

Effect — If a database linkage is added to this element, the entire design file my becomecorrupted.

Solution — Use EdG to change the Index-To-Attribute word of this element to 14 lessthan the element’s Words-to-Follow. The EdG command is MODIFY ELEMENT (16) =wtf-14. Of course, you don’t type in wtf-14; you enter the number that is fourteen lessthan the Words-To-Follow of the element.

Page 110 FileFixer

512 — Index-To-Attributes exceeds 752.

Cause — The Index-To-Attributes word of the element was such that the total length ofthe element would exceed 768 if a database linkage were present.

Effect — If the element already has a database linkage, it will be inaccessible due to thiserror. Trying to add a database linkage to this element is likely to cause file corruption.

Solution — If the element has no database linkages, set the Index-To-Attribute word ofthe element to 14 less than Words-To-Follow. If the element does have linkages, subtract14 from the Words-To-Follow and then subtract the total length of all database linkages.Set the Index-To-Attribute word to the resultant value. If this sounds too hard or if allelse fails, simply delete the element. Before deleting the element, it may be possible tosee what the element looks like (so you can redraw it) using Problem Element Viewer.

513 — Index-To-Attributes is too small.

Cause — The Index-To-Attributes word of the element was such that the basic part ofthe element (without any database linkages) is too short.

Effect — If the element already has a database linkage, it may be inaccessible due to thiserror. Trying to add a database linkage to this element will likely cause file corruption.

Solution — If the element has no database linkages, set the Index-To-Attribute word ofthe element to 14 less than Words-To-Follow. If the element does have linkages, subtract14 from the Words-To-Follow and then subtract the total length of all database linkages.Set the Index-To-Attributes word to the resultant value. If this sounds too hard or if allelse fails, simply delete the element. If Words-To-Follow of the element is less than 16,delete this element. Before deleting the element, it may be possible to see what theelement looks like (so you can redraw it) using Problem Element Viewer.

514 — Index-To-Attributes should be ___.

Cause — Except with deleted complex header elements, the Index-To-Attributes (ITA)word of an element tells us the element’s size (not counting attribute linkages). FileFixerwas able to calculate this element’s size exactly, but the Index-To-Attribute word was notwhat FileFixer expected.

Effect — If the element already has a database linkage, it will be inaccessible due to thiserror. Trying to add a database linkage to this element is likely to cause file corruption.

Solution — Use EdG to set the Index-To-Attributes word to the value reported byFileFixer. The command would be: MODIFY ELEMENT (16) = (whatever FileFixersaid ITA should be).

515 — Element with linkages, WTF minus ITA is less than 18.

Cause — The Index-To-Attribute word of an element should point to where in theelement the database linkage starts (if it has a linkage) or where in the element it wouldstart (if it doesn’t have a linkage). When there are no database linkages, the differencebetween Words-To-Follow and Index-To-Attributes should be 14. When there is adatabase linkage the difference must be at least 18 (14 plus at least 4 words for thelinkage).


Effect — If a database linkage is added to this element, the entire design file maybecome corrupted.

Solution — Delete the element and redraw it.

520 — Complex element doesn’t end on element boundary.

Cause — The Words-In-Description word of a complex header element (like a cell, aconnected string, or a text node) points to a location that is not the start of a new IGDSelement. This is detected by scanning through the element using two different methods,1) using Words-To-Follow and 2) using Words-In-Description. If these two techniquesdon’t lead to the same design file block/byte offset, something is wrong.

Effect — If this complex element is deleted with IGDS the entire design file will getcorrupted. Some versions of MicroStation will crash trying to place a type 1 cell with thisproblem.

Solution — Use the FileFixer "Correct words-in-description" repair option toautomatically correct the Words-In-Description of this element.

Solution — Use the EdG MODIFY STATUS=DELETED command to delete thecomplex header element without deleting its components. DO NOT USE THE EdGDELETE COMMAND! DO NOT USE IGDS OR ANY IGDS LAYERED PRODUCTTO DELETE THIS ELEMENT! If this is a design file, use the EdG MODIFYSTATUS=SIMPLE to turn off the complex bits of each of the component elements. Ifthis is a cell library, use the EdG MODIFY STATUS=DELETED command to deleteeach of the component elements. Before deleting the element, it may be possible to seewhat the element looks like (so you can redraw it) using Problem Element Viewer.

522 — Complex element doesn’t end before End-Of-File.

Cause — The Words-In-Description word of a complex header element indicates that thenext element after the entire complex element (not just the header element) starts after theEnd-Of-Design marker. Another way of saying this is that we encountered the End-Of-Design marker before we encountered the end of this complex element.

Effect — Deleting this complex element with IGDS will corrupt the entire design file.


526 — Running out of text node numbers. Cause — CANODE (in the type 9 of the design file) is greater than 65525. This does notviolate any IGDS or MicroStation rules, but it is somewhat unusual for CANODE to getthis high.

Effect — There is room for less than 10 new text node numbers. After that CANODEwill recycle back to 1 and you will be in danger of creating cross-linked text nodes (twodifferent text nodes sharing the same text node number). See error 530 for moreinformation about how an incorrect CANODE can affect a design file.


528 — Running out of graphic group numbers.

Page 112 FileFixer

Cause — GRAFIC (in the type 9 of the design file) is greater than 65525. This does notviolate any IGDS or MicroStation rules, but it is somewhat unusual for GRAFIC to getthis high.

Effect — There is room for less than 10 new graphic groups. After that GRAFIC willrecycle back to 1 and you will be in danger of creating cross-linked graphic groups (twodifferent graphic groups sharing the same graphic group number). See error 531 for moreinformation about how an incorrect GRAFIC can affect a design file.


530 — Text node number equals or exceeds CANODE.

Cause — The type 9 of a design file contains a word called CANODE. The next textnode placed in the design file will have CANODE as its text node number. CANODE isincremented after each text node is placed. The text node number of this text node isgreater than or equal to CANODE. Following the instructions given by VAX-EdG forreplacing the type 9 of a design file instead of using the FileFixer Replace Type 9command is one way that CANODE can get messed up. The MERGE command, undercertain circumstances, can also leave CANODE errors in a design file.

Effect — Sooner or later this design file will develop “cross-linked text nodes”. Thismeans two or more text nodes sharing the same text node number. This should cause noserious problems for IGDS or MicroStation proper. There are, however, processors thatrely on text node numbers to identify specific text nodes (BITS is one such processor).These could have problems if more than one text node shared the same text node number.

Solution — Use the FileFixer’s Automatic Design File Repair command with theUPDATE CANODE option turned on.

531 — Graphic group number equals or exceeds GRAFIC. Cause — The type 9 of a design file contains a word called GRAFIC. The next graphicgroup placed in the design file will have GRAFIC as its graphic group number. GRAFICis incremented after each graphic group is placed. The graphic group number of thiselement is greater than or equal to GRAFIC. This means that sooner or later anothergraphic group with this same graphic group number will be placed. Following theinstructions given by VAX-EdG for replacing the type 9 of a design file instead of usingthe FileFixer Replace Type 9 command is one way that GRAFIC can get messed up. TheMERGE command, under certain circumstances, can also leave GRAFIC errors in adesign file. If, in the history of this design file it ever had an enormous number of graphicgroups or if, for any other reason, GRAFIC was allowed to recycle past 65535 back to 1,this situation (graphic group numbers exceeding GRAFIC) can occur.

Effect — Sooner or later this design file will develop “cross-linked graphic groups”. Thismeans two or more graphic groups share the same graphic group number. Since the two(ill-fated) graphic groups will be manipulated simultaneously whenever the graphic grouplock is on, and since they may be widely separated in the design file, it then becomesquite easy to unintentionally delete or otherwise mess up one group (which is off thescreen) while manipulating the other (which is on the screen).



534 — GRAFIC is ___, but it should be ___.

Cause — The type 9 of a design file contains a word called GRAFIC. The next graphicgroup placed in the design file will have GRAFIC as its graphic group number. GRAFICis incremented after each graphic group is placed. FileFixer scanned this entire designfile looking for the highest graphic group number. It found that GRAFIC is not set to thehighest graphic group number plus one (as it should be).

Effect — GRAFIC is too small. The design file will eventually develop cross linkedgraphic groups (see error 531).

Solution — Use the FileFixer’s Automatic Design File Repair command with theUPDATE GRAFIC option turned on. To find out exactly which elements have graphicgroup numbers that exceed (or are equal to) GRAFIC, run the Search for Problemscommand on this file with the GRAPHIC GROUP NUMBER EQUALS OR EXCEEDSGRAFIC option turned on.

535 — CANODE is ___, but it should be ___.

Cause — The type 9 of a design file contains a word called CANODE. The next textnode placed in the design file will have CANODE as its text node number. CANODE isincremented after each text node is placed. FileFixer scanned this entire design filelooking for the highest text node number. It found that CANODE is not set to the highesttext node number plus one (as it should be).

Effect — CANODE is too small. The design file will eventually develop cross linkedtext nodes (see error 530).

Solution — Use the FileFixer’s Automatic Design File Repair command with theUPDATE CANODE option turned on. To find out exactly which elements have text nodenumbers that exceed (or are equal to) CANODE, run the Search for Problems commandon this file with the TEXT NODE NUMBER EQUALS OR EXCEEDS CANODE optionturned on.

550 — Words-In-Description exceeds 65516.

Cause — This is an complex header with a one word Words-In-Description. The Words-In-Description of this element exceeds 65516.

Effect — When this element is deleted the entire design file will probably get corrupted.

Effect — Any effort to manipulate this element is likely to produce unpredictable results.For example, it is likely that an operation on this element will result in the same operationbeing performed on the other elements, even if those other elements are not visible on thescreen when the operation takes place.

Solution — Use FileFixer’s Automatic Design File Repair command to repair this errorautomatically nearly all the time.

555 — A complex chain is missing a line string.

Cause — When creating a complex chain from several line strings that are not connectedMicroStation will not create a line string component element for connecting the line

Page 114 FileFixer

strings. MicroStation will automatically display a line string between the original linestrings, but no element was actually created.

Effect — When you drop status of the complex chain the line string MicroStationautomatically displays between the line strings will be erased.

Solution — Use the FileFixer’s Automatic Design File Repair command with the ADDMISSING LINE STRING TO COM0PLEX CHAIN option turned on. FileFixer will onlycreate a line string to fill in the gap between two line strings (type 3 or 4), not between aline string and any other type of element (like arc, conics, b-spline).

560 — Text string overflows element length. Cause — The number of characters is incorrect. It says there are more characters thanactually exist.

Effect — Eventually the design file will become corrupted. A phantom element may getcreated.

Solution — Use FileFixer to correct the number of characters.

565 — Nesting level cannot be deeper than 12. Cause — The nesting level of cells is greater than 12. Most likely the words indescription is bad.

Effect — Elements may not be displayed.

Effect — All elements may not be plotted.

Effect — May not be able to snap to an element.

Solution — Use EdG to correct the Words-In-Description.

Solution — Use Problem Element Viewer to delete the cell.

570 — Null cell name in cell library or design file. Cause — The cell name is null in a cell (type 2).

Solution — Use FileFixer to set this cell to an orphan cell.

571 — Cell (type 2) must be nested in cell library. Cause — A cell (type 2) must always be nested when in a cell library. The library cellheader’s words in description is most likely bad.

Solution — Use EdG to correct the problem.

Solution — Use Problem Element Viewer to delete the cell.

572 — Orphan cell definition without orphan flag. Cause — A cell (type 2) is nested within a library cell (type 1) contains its own elements,but doesn’t have the orphan property set.


Solution — Use FileFixer to set the orphan flag.

Serious Errors — Problems are Very Possible

700 — WTF suspected for unspecified reasons. Cause — FileFixer uses a new algorithm which analyzes more than 20 elementcharacteristics in various combinations to determine the “trustworthiness” of an element’sWTF. Error number 700 means there are numerous element, design file, and programvariables in combination which tell FileFixer the WTF is untrustworthy. The fullexplanation of how FileFixer identifies an “untrustworthy” WTF is considered eitherproprietary and/or beyond the intended scope of this documentation.

Effect — There is a fairly good chance that a fatal Words-To-Follow error is lurkingwithin this element or an element very nearby (in either direction).

Solution — Let the FileFixer’s Automatic Design File Repair command handle this errorfor you.

701 — Can’t tell if file is 2D or 3D. Assuming 2D.

Cause — The dimension of cell libraries and design files is represented by two bits intheir type 5 and type 9 elements (respectively). These bits have illegal values which donot correctly represent “2D” or “3D”.

Cause — This file has neither a valid design file header (type 9) nor cell library header(type 5). For type 5 errors FileFixer currently will not replace the header.

Effect — If the file has a (mostly) valid design file or cell library header, some programswill try to treat the file as 2D and others as 3D. Those that “guess” right will have nodiscernible trouble. The others will fail miserably.

Solution — If you specified the “-3” option on the FileFixer command line, FileFixerassumes this file is 3D. Otherwise FileFixer assumes the file is 2D. If FileFixer hasassumed the wrong dimension for the file, you will get a lot of error messages indicating2D element in 3D file or vice versa. If you don’t get a lot of error messages of that type,FileFixer assumed the correct dimension. Use the FileFixer Replace Type 9 command toreplace the current type 9 element with a good type 9 of the appropriate dimension.

702 — Phantom element. Complex bit is set for a non-componentelement. Cause — An element which is not a component of a complex element has its complex bitset.

Effect — The element will not be selected nor manipulated.

Solution — Use the FileFixer’s Automatic Design File Repair command to fix this typeof corruption automatically.

703 — Complex bit is not set for a component element.

Page 116 FileFixer

Cause — An element which is a component of a complex element does not have itscomplex bit set.

Effect — Unlike IGDS, MicroStation does not rely on Words-In-Description whendeleting most complex elements (such as cells, complex shapes, and text nodes). Insteadit scans for the first element whose complex bit is not set and resets the Words-To-Followof the deleted complex header to point there. Therefore, when component elementcomplex bits are not properly set, file corruption can occur when a complex element isdeleted.

Solution — Use the FileFixer’s Automatic Design File Repair command to fix this typeof corruption automatically.

704 — Low range is greater than high range.

Cause — The x-low value is greater than the x-high value, the y-low value is greater thanthe y-high value, or the z-low value is greater than the z-high value. The z-range ischecked for 3D files only.

Effect — Such elements may be ignored by plotting software and fence contentscommands. They usually will not be displayed by IGDS or MicroStation.

Solution — Use the FileFixer’s Automatic Design File Repair command to fix this typeof problem automatically. Note that if this element is a complex element header with nocomponents, it is not possible for FileFixer (or any other program) to fix this error.Delete such elements.

705 — Element range doesn’t match the min-max of its vertices.

Cause — The range of an element with vertices, points, poles, etc. is incorrect. Theelement range and the min-max of the vertices, points, poles, etc. that make up theelement don’t fall within the user specified tolerance.

Effect — This element may be improperly ignored by fence contents manipulationcommands.

Effect — It may be impossible to snap to or select this element for manipulation.

Effect — If the element range is not wildly off, this error will probably cause little or noproblem.


706 — Type 28 range doesn’t match range of its associated type 21.

Cause — Type 21 and 28 elements always come in pairs. The range of each part of thepair should be identical. This element and the element preceding it didn’t match.

Effect — Possible element snapping, selection, and fence manipulation problems.



707 — B-spline pole element range doesn’t match the min-max of itspoles nor the range of its b-spline surface header.

Cause — The range of a b-spline pole element is incorrect. IGDS sets the range of thiselement type to the range of its poles. MicroStation sets the range of this element type tothe range of its type 24 b-spline surface header. The range of this element matchesneither.

Effect — This element may be improperly ignored by fence contents manipulationcommands.

Effect — It may be impossible to snap to or select this element for manipulation.

Effect — If the element range is not wildly off, this error will probably cause little or noproblem.


709 — Range of b-spline component does not match parent’s range.

Cause — All type 25 and 26 elements and type 21 and 28 elements that are componentsof b-spline curves should have the exact same range as their parent header element. Therange of this element didn’t match its parent.

Effect — Possible element select, snapping, and fence manipulation problems.


710 — Cell library header is not on level 8.

Cause — The first element of what appears to be a cell library was a type 5, but it wasn’ton level 8.

Effect — Some IGDS/MicroStation related programs may not recognize this file as a celllibrary.

Solution — If, indeed, this is a cell library, use EdG to change the level of the firstelement (the type 5) to level 8.

712 — Range of right circular truncated cone is incorrect.

Cause — FileFixer calculates the range of right circular truncated cones based on thelocations of their centers, radii, and quaternions. The range calculated by FileFixer forthis element doesn’t match the range stored in its element header.



713 — Second element of design file is not an active type 8.

Cause — The second element might be a deleted type 8.

Page 118 FileFixer

Cause — The second element of the design file is not a type 8 at all.

Effect — A few programs may process this file without problems. Many won’t. Even theones that succeed to some degree will fail if any attempt is made to do digitizing underIGDS. Many user commands expect the first word of the fifth block of the design file(usually the first word after the type 9, 8, and 10 elements) to be a valid element. If this isnot the case, this design file could become totally corrupted (if it isn’t already).

Solution — Use the Replace Type 9 command of FileFixer to transplant a type 8 elementfrom another design file.

714 — Third element of design file is not an active type 10.

Cause — The third element might be a deleted type 10.

Cause — The third element of the design file is not a type 10 at all.

Effect — A few programs may process this file without problems. Even with theprograms that succeed to some degree, if level symbology is turned on, you are likely tosee some very strange results. Many user commands expect the first word of the fifthblock of the design file (usually the first word after the type 9, 8, and 10 elements) to be avalid element. If this is not the case, this design file could become totally corrupted (if itisn’t already).

Solution — Use the Replace Type 9 command of FileFixer to transplant a type 10element from another design file.

715 — Type ___ element found on level 0. Cause — An element was found on level “0”. Level 0 is not considered a validIGDS/MicroStation level.

Effect — This element may be left out of fence manipulation commands and plots. Itmay display improperly. It may be unselectable. It may be impossible to turn off thedisplay of this element regardless of which levels are turned off. This element may beimproperly included or improperly omitted from plots.

Solution — Move this element to a valid level (1-63).

716 — Cell level mask is incorrect.

Cause — This problem occurs when the list of occupied levels in the cell header element(type 1 or 2) does not match the actual levels used by the cell.

Effect — Displaying a design file with cell level mask errors using MicroStation cancause the following problems: 1) Cell components disappearing, 2) Cell components arevisible after multi-view updates, but not after single view updates, and 3) Cell cannot beselected or manipulated.

Solution — Use the FileFixer’s Automatic Design File Repair command to correct thisproblem automatically.

717 — Cell class map is incorrect.


Cause — This problem occurs when the list of classes used by elements in the cell(which is stored in the cell header element) does not match the actual classes used byelements in the cell.

Effect — Cells with this problem may be unselectable (phantom elements).

Effect — Cells with this problem may be ignored by the FIT command. These problemsare much more likely to occur if a bit in the class map is incorrectly turned off. Bits thatare incorrectly turned on may cause no problem.

Solution — Use the FileFixer’s Automatic Design File Repair command to correct thisproblem automatically.

719 — Element type ___ must be nested in a complex. Cause — B-spline components are allowed only as part of a complex b-spline element.This b-spline component was found all by itself.

Cause — Raster data elements (type 88) are allowed only as part of a complex rasterelement. This raster data component was found all by itself.

Effect — Some versions of MicroStation crash when such elements are encountered.

Solution — By default the FileFixer’s Automatic Design File Repair command willdelete elements such as these automatically.

720 — Complex header range is off by ___%. Cause — The union of the range blocks of the components of the complex elementheader does not match the range block of the complex header element itself. Thepercentage is determined by dividing the deviation from perfection as calculated byFileFixer (in UORs) by the size of the element (in UORs). This test is performed on thex, y, and (for 3D files) z axes. The worst (largest) of the error percentages is the onereported. Note that if the size of the element (along the z-axis as an example) is verysmall (lets say 1 UOR as an example), then a relatively small deviation from the ideal Z-High or Z-Low (lets say 50 UORs) would result in a large sounding percentage deviation(in this example 5000%). If all this sounds confusing just remember this — to make surethat no range errors are missed, FileFixer calculates the error using a method thatsometimes generates large sounding percentages. Don’t worry about it. Just use theAutomatic Design File Repair command to adjust the problem elements.

Effect — This can be a serious problem in a cell library because some versions ofMicroStation rely on the cell range when placing cells. Also, the complex element maybe improperly excluded from fence manipulation and plotting commands.


721 — An element of this type cannot be a component of a complexheader of the specified type. Cause — Each type of complex element (like cells and text nodes) can only containcertain types of elements. For example, a text node (type 7) can contain only textelements (type 17’s). A connected string (type 12) can contain only linear elements such

Page 120 FileFixer

as lines (type 3’s), line strings (type 4’s), arcs (type 16’s), etc. The element just read incannot legally be contained in the complex element header mentioned near the end of themessage.

Cause — The complex header element mentioned contains a Words-In-Description errorwhich causes it to think it contains elements that really should be after its end.

Effect — Some combinations of elements can cause MicroStation and IGDS to crash.

Solution — Use Problem Element Viewer to view both the complex element as a wholeand the unwanted component so you know what is going on. Best bet is to delete andredraw the complex element(s) involved.

722 — Dimension element with no data or associative points. Cause — A dimension element must have at least one data or associative point.

Effect — Sometimes you will get an MDL abort in MicroStation when you select a cellthat has a dimension element, which has no data or associative point.

Effect — When you place a cell that has a dimension element, which has no data orassociative point, the dimension will always be placed at the same location in the designfile. It will be placed with the origin of the dimension element at x=0, y=0, z=0.

Solution — Use FileFixer's "Remove dimension element with no data or associativepoints" repair option to delete the bad dimension element. You will then need to recreatethe dimension element.

724 — Range of arc or ellipse is incorrect. Cause — FileFixer calculates the range of arcs and ellipses based on the length of theiraxes, angle of rotation, origin, start angle and sweep angle. The range calculated byFileFixer for this element doesn’t match the range stored in its element header.



725 — Range of text element is incorrect.

Cause — The range of this text element is incorrect.

Cause — FileFixer calculates the range of 2D and 3D text elements based on theirorigin, number of characters, rotation or quaternions, length multiplier, and heightmultiplier. As of version 4.0 of FileFixer, the font and the size of EACH INDIVIDUALCHARACTER is taken into account in determining the size of the text element. Thisrequires FileFixer to open and thoroughly analyze your font library. The size of eachcharacter for each font is different. Therefore, You must tell FileFixer to use the samefont library that was used to create the text elements. IF YOU TELL FileFixer TO USETHE WRONG FONT LIBRARY, YOU MAY GET MANY TEXT RANGE ERRORS.

Cause — Some MicroStation versions before 4.0 appear to handle some fonts with wordsize vectors (“Word size vectors” means that the width of each character is store in aword rather than a byte.) incorrectly. FileFixer correctly calculates the position and rangeof text with such fonts, as do all versions of MicroStation after 4.0. To determine the


vector size of a particular font, run the flib program that comes with MicroStation on thefont library. Example:

FLIB SPECIAL.FLB -LIST -FULL

Cause — The view independent bit of the property word may be set incorrectly. If thetext range appears to be correct, but FileFixer reports the text range as being widely off,this is something you should suspect.

Cause — Version 4.02 (and probably other versions of MicroStation) set the range boxof view independent text non-optimally. FileFixer will set the range of view independenttext so that the range box encompasses the element no matter what orientation a viewcontaining the element is rotated to. The range box surrounding view independent textshould appear roughly twice as big as the text itself. The anomaly in MicroStation isapparent mainly on very short (one or two character) text strings.

Cause — A few customers have asked why EdG sometimes reports an error on anelement where FileFixer doesn’t and vice versa. There are two reasons for this: 1)FileFixer opens your font library and looks up the width of each individual character indetermining the correct range of a text element. EdG does not; it uses an approximationof the text width. Therefore, FileFixer’s text range calculations are more accurate thanEdG’s. 2) By default FileFixer’s range tolerance is (-10,30). We have determined byextensive study that if the range of an element is no more than 10% too small or 30% toolarge, no problems will be encountered in the use of that element. EdG reports rangeerrors which (in our opinion) are not significant. If, however, you want to clean up everysingle range error, no matter how small, just set FileFixer’s range tolerance to (-.001,.001) and run the Automatic Design File Repair command.

If you wish to verify that FileFixer’s text range calculations are correct, do the followingtest. 1) Find a text element in which you suspect FileFixer has set the range incorrectly.2) Use EdG to copy that element to its own file (after a type 9, 8, and 10). 3) SetFileFixer’s range tolerance to (-.001,.001). 4) Run FileFixer’s Automatic Design FileRepair command on the new (tiny) file. 5) Bring up MicroStation with the output (.fix)file created by FileFixer. 6) Do a FIT command. 7) Key-in SET RANGE. 8) Update theview. 9) You should see a box surrounding the element. This is the range of the element.If the text in question is View Independent, the box should be about twice as large as thetext and the text will not be centered in the box. If the text in question is not ViewIndependent, the box should fit (more or less) neatly around the element.

We don’t claim that FileFixer’s range calculations are perfect. We, however, are notaware of any product or program (including MicroStation itself) that can calculationranges more accurately than FileFixer. If, after performing the test described in the aboveparagraph, you find any instance where FileFixer worsens the range of an element or,based on the test described above, any program appears to adjust the range of an elementbetter than FileFixer, please contact us immediately.

Effect — Possible element snapping, selection, and fence manipulation problems. If therange is too small the element may be improperly omitted from certain operations. If therange is too large, the MicroStation scanning software will not run as efficiently.


Page 122 FileFixer

731 — B-spline curve or surface has an illegal number of a certain typeof component.

Cause — A b-spline element is made up of many different kinds of components. The b-spline header indicated in parentheses had an illegal number of a certain type ofcomponent. One of the following illegal conditions was found:

Cause — A b-spline curve (type 27 header) had more than one b-spline knot element(type 26).

Cause — A b-spline curve (type 27 header) had more than one weight factor element(type 28).

Cause — A b-spline curve (type 27 header) did not have exactly one pole element (type21).

Cause — A b-spline surface (type 24 header) had no pole elements type 21).

Cause — A b-spline surface (type 24 header) had neither zero weight factor elements northe same number of weight factor elements (type 28) as pole elements (type 21).

Cause — A b-spline surface (type 24 header) had more than one b-spline knot element(type 26).

Effect — A design file with this problem will frequently crash MicroStation.

Solution — Use FileFixer’s Automatic Design File Repair command to delete thiselement automatically.

741 — Non-shared cell must be on level 0.

Cause — Type 1 and type 2 cells must be on level 0. This one is on some other level.

Effect — If this is a type 2 cell, you may have plotting problems with this cell. Forexample, this cell may be omitted from plots.

Effect — If this is a type 1, placing this cell will propagate the error described above toevery design file in which it is placed.

Solution — Use FileFixer’s Automatic Design File Repair command to correct thisproblem automatically.

750 — Words-To-Follow exceeds 65533.

Effect — This is a problem because adding 2 to a number larger than this (to get the totalelement length) will cause a 16 bit register overflow. This will crash mostIGDS/MicroStation related processors including the VAX file processor hardware.

Solution — The FileFixer’s Automatic Design File Repair command will delete thiselement and recover as many elements after it as possible.

754 — Words-To-Follow error.

Cause — The Words-To-Follow of this element appears to be incorrect. Furthermore,Words-To-Follow points to a location in the design file that does not appear to be a validelement.


Effect — There is a good chance that this design file is undisplayable due to an “EOF notfound” or a “Design file I/O Error”. It is also possible that this design file will display,but that large pieces of it will be missing.

Solution — The FileFixer’s Automatic Design File Repair command will delete thiselement and recover as many elements after it as possible. Before repairing the file, if it ispossible to bring it up in graphics (unlikely), use Problem Element Viewer to see whatthis element looks like so that it can be redrawn.

756 — Words-To-Follow of active element exceeds 766.

Cause — Most IGDS related programs reserve a buffer space of 768 words to store anelement. Attempting to read in more words than this can cause severe problems.

Effect — Some programs may allocate an element buffer larger than 766 (or 780 whenalignment requirements are taken into consideration). Most don’t. File corruption and/orother problems due to overwritten memory are likely.

Solution — The FileFixer’s Automatic Design File Repair command will delete thiselement and recover as many elements after it as possible. If it is possible to bring up thisdesign file in graphics before repairing it (unlikely), use Problem Element Viewer to seewhat this element looks like so that it can be redrawn.

758— Siamese element. Words-To-Follow is too small.

Cause — This element and the one following it share disk space. The end of this elementand the beginning of the next are using the same disk space. Words-To-Follow of thiselement is too small.

Effect — Some processes (MicroStation-32 in particular) are prone to crashing whenthey encounter Siamese elements. Severe file corruption is possible.

Solution — The FileFixer’s Automatic Design File Repair command will delete thiselement and recover as many elements after it as possible. If it is possible to bring up thisdesign file in graphics before repairing it (unlikely), use Problem Element Viewer to seewhat this element looks like so that it can be redrawn.

761 — Linkage area suspiciously long. Probably WTF error.

Cause — The difference between the expected WTF of this element and its actual sizeindicates that either WTF is wrong or that the element has an attribute linkage area that issuspiciously long (more than 60 words). Words-To-Follow of this element points to alocation in the design file that does not appear to be a valid element.

Effect — There’s a good chance that this design file is totally corrupted.

Solution — If you can bring up this design file in graphics, use Problem Element Viewerto see what the element looks like so that you can redraw it. Use EdG or ProblemElement Viewer to delete this element.

762 — Possible 2D element in 3D file or vice versa. Cause — Analysis of the number of vertices, database linkages, points, characters, Enter-Data-Fields, poles, boundaries, knots, etc. indicates that what might be a 2D element is in

Page 124 FileFixer

a 3D file or vice versa. Words-To-Follow in this element points to a design file locationthat is unlikely to be the start of a valid element.

Effect — File corruption is likely. IGDS and MicroStation may display very strangeresults for these elements. Other programs are likely to have problems also.

Solution — The FileFixer’s Automatic Design File Repair command should delete thiselement and recover as many elements after it as possible.

766 — Duplicate shared cell definition matches element ___.Duplicate library cell definition matches element ___.

Cause — This shared cell definition has the exact same cell name as the specified sharedcell definition, or this library cell definition has the exact same cell name as the specifiedlibrary cell definition. The match is sensitive to trailing blanks and is case sensitive. Forexample, if one cell name is “X” and the other is “X” this message will not be generated.

Effect — If the two shared cell definition elements with the same name are exactly thesame, you’re simply wasting a bit of space in your design file.

Effect — If the two shared cell definitions with the same name are different, then youmay be displaying all the instances of this shared cell incorrectly.

Effect — If there are two library cells with the same name then only the first one will befound when that cell library is attached.

Solution — Delete the unwanted definition so that MicroStation will draw the shared cellusing the desired definition.

Solution — Use EdG to delete the library cell that you don’t want to keep.

768 — Shared cell instance has no matching shared cell definition. Cause — Whenever there is a shared cell instance (type 35) in a design file, there mustalso be a shared cell definition element (type 34) with the same name in the design file.The type 34 contains the instructions on how to draw the type 35. This design file has atype 35 with no corresponding type 34. The shared cell definition element must have theEXACT same name. The match is sensitive to trailing blanks and is case sensitive. Forexample, if the type 35 name is “X”, then a type 34 name of “X” will not match as a type34 name of “x” will not match.

Effect — This cell will not be displayable (invisible).

Solution — Find (or create) a cell library that contains a cell of the specified name.Attach that cell library. Place that cell as a shared cell. Delete the instance you justplaced. Do a FIT. The original cell (and all other shared cell instances with the samename) should now be visible. Use Axiom product Problem Element Viewer to zoom in onthe repaired cell if you don’t know where it is located.

Solution — The FileFixer’s Automatic Design File Repair command with the "Createdummy shared cell definition for missing definition". This option will create a dummyshared cell definition. What this option does is create a shared cell definition elementwith a text element as its only component. The text element is created with the name ofthe shared cell as the text string.


Solution — If the above solutions do not cause the specified cell to become visible, or ifthe cell displays incorrectly, you should use EdG to delete the type 34 and type 35 andreplace the cell from the cell library. Even if the cell is displaying incorrectly, Axiom’sProblem Element Viewer product may be able to at least show where in the design file,the problem cell is located.

769 — Level mask {_____} contradicts its def {______}. Cause — The level mask of an absolute shared cell must match the level mask of itsdefinition element. The level mask of this absolute shared cell doesn’t match itsdefinition element.

Effect — This cell may not be displayable (invisible).

Effect — Some levels of the cell may not be displayable.

Effect — Elements on some levels of the cell may plot intermittently.

Effect — The cell may not be able to be snapped to and/or deleted.

Solution — Use the FileFixer’s Automatic Design File Repair command to repair thisproblem automatically.

Solution — Delete and redraw the cell. Even if the cell is displaying incorrectly,Axiom’s Problem Element Viewer product may be able to at least show where in thedesign file, the problem cell is located, so you can see which cell needs to be redone.

770 — Shared class mask {____} contradicts its def {____}. Cause — The class mask of an absolute shared cell must match the class mask of itsdefinition element. The class mask of this absolute shared cell does not match itsdefinition element.

Effect — This cell may not be displayable (invisible).

Effect — Some classes of the cell may not be displayable.

Effect — The cell may not be able to be snapped to and/or able to be deleted.

Solution — Find (or create) a cell library that contains a cell of the specified name.Attach that cell library. Place that cell as a shared cell. Delete the instance you justplaced. Do a FIT. The original cell (and all other shared cell instances with the samename) should now be visible. Use Axiom product Problem Element Viewer to zoom in onthe repaired cell if you don’t know where it is located.

Solution — Use FileFixer to correct the class mask to correct the shared cell instanceclass mask.

776 — 3D only element (type ___) in 2D file.

Cause — An element type that is only found in 3D files was found in a 2D file.

Effect — Some programs will ignore the element. Some will get very confused.

Solution — Use the FileFixer’s Automatic Design File Repair command with theREMOVE ILLEGAL ELEMENT TYPES option turned on. Be alert for other types ofcorruption in the vicinity of this element. If FileFixer fails to delete this element because

Page 126 FileFixer

it detected a higher priority corruption first, then turn off all search options except 2DELEMENT FOUND IN 3D FILE, 3D ELEMENT FOUND IN 2D FILE and ILLEGALELEMENT TYPE DETECTED, and try again.

783 — Cell in a cell library is nested within itself.

Cause — The current element is a cell that is nested within a cell of the same name.

Effect — If you try to place this cell in a design file, MicroStation won’t crash, but it willplace the cell incorrectly.

Solution — Delete cell and recreate.

784 — A type ___ cannot follow a type ___ in a b-spline curve.

Cause — There are many rules concerning the sequence of elements in a b-spline header.The components of a b-spline must in a very exact sequence. This element violates one ofthese rules.

Effect — Depending on the exact sequence MicroStation and/or other processors such asplotting may crash.

Effect — The element may display incorrectly.

Effect — The element may not display at all.

Solution — Use EdG to delete the b-spline this element is a part of. The first type 27preceding this element is the one to delete.

787 — Element has too many vertices, points, poles, boundaries, etc.

Cause — Element types with vertices, points, etc. can have only so many of these.

Effect — Different programs have different tolerances to this problem. Some haveproblems if there is even one too many vertices. Some don’t have problems until there are20 or 30 or more vertices more than there should be. Any program, however, givenenough extra vertices, will behave incorrectly. Note that the number of visible vertices ona curve (type 11) and a conic (type 13) is actually 4 less than that reported by EdG. Thefirst and last two “vertices” are not displayed, but are used only for determining the shapeof the element near the endpoints. Therefore, a curve which EdG reports as having 102vertices, actually has 98 visible vertices. Such an element would be flagged by FileFixer.That is why the number of vertices reported by EdG, and FileFixer do not agree for theseelement types. FileFixer reports the correct number of visible vertices. EdG intentionallyreports the total number vertices the way EdG does for the sake of consistency.

Solution — Use EdG to delete the affected element or, if everything else about theelement seems okay, reduce the number of points, vertices, etc. to the legal maximum. Ifit is possible to bring up this design file in graphics, use Problem Element Viewer (beforedeleting the element) to see what this element looks like so that it can be redrawn.

788 — B-spline pole element (__) has too few poles.

Cause — This type 21 element has less than two poles.


Effect — MicroStation and other software may display an infinite length line for thiselement.

Effect — Displaying this file may cause MicroStation to crash.

Solution — Delete the parent complex header of this element. The element number ofthe parent is shown in parentheses.

789 — Element has too few vertices, points, boundaries, etc. Cause — Elements with vertices, points, etc. must have a minimum number of these.This element did not have enough.

Note that the number of visible vertices on a curve (type 11) and a conic (type 13) isactually 4 less than that reported by EdG. The first and last two “vertices” are notdisplayed, but are used only for determining the shape of the element near the end-points.FileFixer reports the correct number of visible vertices. EdG intentionally reports thetotal number of vertices the way EdG does for consistency. Therefore, a curve whichEdG reports as having 5 vertices, actually has only 1 real (visible) vertex. Such anelement would be flagged by FileFixer. The minimum number of (visible) vertices for ashape (type 6), is 4. Shapes with less than 4 vertices will be flagged with this error.

Effect — Some plotting software has been reported to fail if a line string, curve, orsimilar element has fewer than 2 vertices.

Effect — The file may be displayable under MicroStation and under IGDS withoutACTEM, but may crash under ACTEM.

Solution — Select the REMOVE ELEMENTS WITH TOO FEW VERTICES option onFileFixer’s Automatic Design File Repair menu to automatically remove these elementsfrom the design file. Optionally, you can use Axiom’s Problem Element Viewer programto determine if the erroneous element is displayable. If the element is displayable,Problem Element Viewer will show you what the element looks like. You may want toredraw the element before deleting it.

Fatal Errors — File is Probably Unusable

902 — First element of file is not an active type 9 or type 5. Cause — This is not a design file or cell library and never was.

Cause — This is a design file or cell library whose first element has been deleted orbadly damaged.

Effect — Most IGDS/MicroStation related programs will fail trying to process this file.

Solution — Problems of this kind can be easily fixed using FileFixer’s Replace Type 9command. Currently File Fixer will not replace cell library headers.

912 — Illegal floating point value encountered.

Page 128 FileFixer

Cause — Part of an element stored in VAX D floating point format contains an illegalvalue. Under MS-DOS and CLIX, this error indicates that the value stored in the elementcould not be converted to a valid IEEE format floating point value.

Effect — Most programs will abort trying to display or plot this element.

Solution — Use EdG to delete the affected element.

995 — Fatal error attempting to read past physical End-Of-File. Cause — Words-To-Follow of the previous element points to a block/byte locationbeyond the physical End-Of-File.

Effect — It is very unlikely that any IGDS/MicroStation software will be able to readthis file in its entirety.

Solution — Use the Automatic Design File Repair command of FileFixer. This willrecover as many elements from the file as possible.

996 — Fatal error. End-Of-Design marker was not found.

Cause — The physical End-Of-File was reached without encountering an End-Of-Designmarker.

Effect — There are some IGDS/MicroStation related programs that will be able toprocess this file without error. Most, however, won’t.

Solution — Use the Automatic Design File Repair command of FileFixer. It will add anEnd-Of-Design marker after the last valid element.

997 — Fatal error. File ended before element did.

Cause — Words-To-Follow of the specified element was larger than the number ofwords remaining in the physical file.


Solution — Use the Automatic Design File Repair command of FileFixer. This willrecover as many elements from file as possible.

999 — Fatal error attempting to read element. Cause — An unspecified error occurred attempting to read in an element.


Solution — Use the Automatic Design File Repair command of FileFixer. This willrecover as many elements from file as possible.

Free analysis of problem design files is a limited time offer. Magnetic media cannot bereturned. Confidential or proprietary design files and cell libraries must be noted inwriting.

Chapter 15 — The File List Editor Page 129

Chapter 15 — The File List Editor

The File List Editor Dialog BoxUse the File List Editor dialog box to create a list of files to be processed.

The List menu

Page 130 FileFixer

The List menu lets you create, save, and re-use different lists of files. There are severalapplications that can make use of these lists of files. So lists can be imported andexported between applications.

Tip: Although there are some similarities between this menu and a standard “File” menu,the differences are significant. When you Import or Export from this menu, the files donot remain “open”, you are not “editing a file”, and no files are “updated”. Effectively,these are “one shot copy” operations where an entire set of data is copied from the dialogbox to a file, or from a file to the dialog box.

There are two possible file formats, each having different advantages and disadvantages.

File list only (text)This format is a simple text file, with each line in the file containing a fully qualified,unambiguous file specification. No other data is saved.

Definition: “fully qualified, unambiguous file specification” means “including a driveletter, a complete path starting from the root, a filename, and optionally an extension, allwith no wildcard characters.” An example of this would be “c:\temp\tempfile.tmp”.

Files of this format can be edited using any text editor. Notepad is an example of a simpletext editor.

This format is handy for using as a basis for an “@listfile” (see below). Or even forgenerating a list of files for any application that uses a list of files for input.

The default extension for this format is .lst, which stands for “list”.

All data (binary)In this format, all the data displayed in the dialog box is saved. This includes not only the“Selected files:” list, but the drive, path, “Files:” field, and earliest and latest date fields.

The data is saved in a specific format which cannot be safely modified by any programother than the File List Editor dialog box.

The default extension for this format is .efl, which stands for “Edited File List”.

List | Import

Use this option to restore a list of files from a file.

All data (binary) — Select this option to restore the complete state of the dialog boxfrom a file. If the file selected is not of the proper format, no changes will be made to thestate of the dialog box.


File list only (text) — Select this option if you want only the list of files to be restored.When this option is used, nothing in the dialog box changes except the “Selected files:”list.

Note: This option will attempt to import any file. Everything from the beginning of thefile up to the point where the file no longer contains text, will be imported and displayedin the “Selected files:” list.

List | Export

Use this option to save a list of files to a file.

All data (binary) — Select this option to save the complete state of the dialog box.

File list only (text) — Select this option to save just the list of files.

Files

This field may be thought of as having two modes: standard and extended. The modedepends on what is entered here, and effectively, changes on-the-fly based on your entryso there is no “checkbox” or “setting” that needs to be changed.

Standard modeThis mode might best be called “simple directory listing” mode. In this mode, there isalways a one-to-one correspondence between what is displayed here, and the rest of thegraphical interface in this dialog box – changes you make in the “Drives:” option button,and the “Directories:” listbox are reflected here, and vice versa. It is very similar to acombination of the “Files:” field and the “List files of type:” option button in a standardMicrostation “Open File” dialog box.

If you are familiar with the DOS “dir” command, you can easily understand this modesimply by treating it as if you were typing “dir”, followed by the contents of this field, atthe DOS prompt. The main difference between the DOS “dir” command and this field isthat the filename and extension are always saved, along with the path, for each drive.This saved “default” is “filled in” whenever something is entered which does notspecifically include a filename and/or extension.

Page 132 FileFixer

Extended modeThis mode might best be called “extended file specification” mode. In this mode,specialized parameters may be used to extend the list of specified files beyond that whichis possible with a simple graphical interface.

Note: When an entry of this “extended” type is detected by the program, the “Availablefiles:” and “Directories:” listboxes, and the “Path:” field, are cleared.

/s – include sub directories

“/s” includes all matching files in all subdirectories of the one specified in the precedingfile specification.

/fedate – earliest date

“/fe1-1-1992” includes files with dates that fall in a range beginning on January1st, 1998

/fldate – latest date

“/fl12-31-1998” includes files with dates that fall in a range ending on December 31st,1998

/fodate – on date

“/fo1-1-98" includes only files modified on January1st, 1998.

/ft – today

“/ft” includes only files with dates matching the current system date.

Note: Neither the forward slash nor backslash are available for separating month, dayand year. Use either periods (12.31.92) or dashes (12-31-92).

Tip: “/fl date” and “/fedate” may be combined to restrict file dates to a specific range, asin “c:\dgnfiles\*.dgn /fe7-1-97 /fl8-1-97 /s”

semicolon (;)

Multiple extended file specifications may be strung together by separating them withsemicolons (;). For example:

c:\dgnfiles\*.dgn /s ; d:\dgnfiles\*.dgn /s


@‘@’ prefixed to a file specification indicates a list file. A “list file” is a flat text filecontaining lines composed of file specifications as defined above. That is, each line canbe a simple file specification, a wildcard file specification, a list file specification, asingle extended file specification, or multiple file specifications of any of theses types,separated by semicolons.

<Add>

Note: This is the button above the “Files:” field. Do not confuse this button (underlined‘d’) with the <Add> (underlined ’A’) button beneath the “Available files:” listbox.

Use this pushbutton to add all the files specified by the “Files:” field to the “Selectedfiles:” listbox.

Tip: In standard mode, this is equivalent to selecting all the files in the “Available files:”listbox, and then pressing the <Add> button.

<Remove>

Note: This is the button above the “Files:” field. Do not confuse this button (underlined‘m’) with the <Remove> (underlined ’R’) button beneath the “Available files:” listbox.

Use this pushbutton to remove all the files specified by the “Files:” field, from the“Selected files:” listbox.

<Replace>

Use this pushbutton to rebuild the “Selected files:” from scratch, using only those filescurrently specified by the “Files:” field. This is equivalent to deleting all the files from

the “Selected files:” list and then clicking the <Add> button.

Drive

Page 134 FileFixer

Use this option button to change the drive containing the files you wish to see listed inthe “Available files:” listbox. If the drive is changed, the “Path:” and “Files:” fields willbe updated accordingly.

Note: Unlike drive letters, which will always default to “\*.*”, if “UNC” is selected andno UNC path has been entered previously, all pertinent fields will be blanked out, sincethere is no way for the program to determine a default UNC path.

Path

This displays the drive and directory (or the UNC path) to the files and directories beingdisplayed in the “Available files:” listbox and the “Directories:” listbox.

Available files

This displays the filenames specified in the “Files:” field. There are two ways you canadd files from this list to the “Selected files:” listbox.

1. Double click on a filename.

2. Select one or more files and click the <Add> or <Add by dates> pushbutton.

This listbox supports the standard Windows file selection conventions such as <shift> leftclick to select a range of file names or <control> left click to select an additional file.

If a file in this listbox also exists in the “Selected files:” listbox, it is grayed out andcannot be selected.


Directories

This listbox displays the sub directories of the directory displayed in the “Path:” field.Double clicking on any directory name will change to that directory and update the“Path:” and “Files:” fields accordingly.

<Add>

Note: This is the button beneath the “Available files:” listbox. Do not confuse thisbutton (underlined ‘A’) with the <Add> (underlined ’d’) button above the “Files:” field.

Use this pushbutton to add all highlighted files in the “Available files:” listbox, to theSelected Files list.

<Remove>

Note: This is the button beneath the “Available files:” listbox. Do not confuse thisbutton (underlined ‘R’) with the <Remove> (underlined ’m’) button above the “Files:”field.

Use this pushbutton to remove all highlighted files in the “Available files:” listbox, fromthe Selected Files list.

<OK>

Use this pushbutton to save the list in the “Selected files:” listbox and exit the dialog box.

Page 136 FileFixer

<Cancel>

Use this pushbutton to cancel any changes made to the list in the “Selected files:” listboxand exit the dialog box.

Select files by date

Earliest date

Use this field to enter a beginning “cutoff” date for a range of files to be added to the“Selected files:” listbox. Files whose last modification date is before this date will not beadded to the “Selected files:” listbox when the <Add by dates> pushbutton is clicked orremoved from the “Selected files:” listbox when the <Remove by dates> pushbutton isclicked.

Latest date

Use this field to enter an ending “cutoff” date for a range of files to be added to the“Selected files:” listbox. Files whose last modification date is after this date will not beadded to the “Selected files:” listbox when the <Add by dates> pushbutton is clicked orremoved from the “Selected files:” listbox when the <Remove by dates> pushbutton isclicked.

<Add by dates>

Click this button to add all files from the “Available Files:” listbox whose dates fallwithin the range specified by the “Earliest date:” and “Latest date:” fields, to the“Selected files:” listbox.


<Remove by dates>

Click this button to remove all files from the “Selected files:” listbox whose dates fallwitting the range specified by the “Earliest date:” and “Latest date:” fields.

Selected files

This listbox shows the files that have been selected for processing. Double-click a singlefilename to delete it from the list. Select multiple filenames and use the <Remove> or<Remove by dates> pushbuttons to delete multiple filenames from the list.

Number of files selected

This simply shows the number of filenames currently in the “Selected files:” listbox.

Special note about UNC pathnamesUnder the old DOS “drive lettering” system, there were only 26 possible disk drives (A-Z) that could be specified. UNC (Universal Naming Convention) pathnames havechanged that. The number of possible drives (now called “resources”) that can bespecified is theoretically unlimited with UNC. For this reason, there is only a single“slot” for saving the last UNC entered.

Messages

“xxx” is not currently accessible.

This message indicates one of two things:

1. A file specification was entered into the “Files:” field, but it does not correspond toany resource accessible to the system. This usually just ends up being a mis-typedor mis-remembered directory name or UNC path.

Page 138 FileFixer

2. A resource is truly not accessible to your system. Some likely reasons for this are: a)you do not have, or no longer have, access permissions for the resource, b) theresource’s name has changed, c) a resource is down, offline, or inaccessible for someother “mechanical” reason, d) drive letter mappings have been changed on yourcomputer, e) a directory has been deleted or moved.

If you get this message and have checked your entry, contact your systems administratorto determine why the resource is not accessible.

Note: The term “resource” is borrowed from the UNC definition“ \\<server-name>\<resource-name>”. In our context we mean “a specifieddevice/directory combination in either DOS or UNC format”. This specifically excludesthe filename and extension. Examples of this might be “c:\dgn_files\” and“\\server\drive_c\dgn_files\”.

Chapter 16 — Glossary Page 139

Chapter 16 — Glossary

A-bit Indicates whether attribute data is present:

0 = not present, 1 = present

ANSI American National Standards Institute. An organization thatacts as a national coordinator for voluntary standards in theUnited States.

Attribute Linkage Any element may optionally contain attribute data orattribute linkage data. This data may consist of a link to anassociated database or any other information that pertains tothe element.

Attribute data that is not associated with DMRS or aMicroStation supported database is referred to as a user datalinkage. A user linkage may coexist with a database linkageor other user linkages. MicroStation makes no attempt tointerpret user linkages; these linkages are maintained whenMicroStation modifies an element.

Bit A binary digit (0 or 1). Eight bits make up a byte.

CAD Computer-Aided Design. A process in which a designer ordrafter uses a computer to create and update design files.

CANODE Next text node number.

Cell Level Mask Every cell has, as part of its definition, a list of the levels onwhich the cell has displayable elements.

Class Number identifying the class of the element.

0 - Primary

1 - Pattern component

2 - Construction element

3 - Dimensioning element

4 - Primary rule element

5 - Linear patterned element

6 - Construction rule element

Complex Bit When clear, indicates that the element is a simple (non-complex) element. When set the element is considered acomponent of a complex element. The only exception to thisis the file header element (the first type-9 element in adesign file or type-5 element in a cell library); the complexbit for the file header element indicates that the file is a 3Dfile.

EdG A utility which comes with MicroStation to edit graphical

Page 140 FileFixer

elements.

Element Chain All the elements in a design file or cell library are linkedtogether, in other words, an element chain. They are linkedtogether by the WTF (words-to-follow) values. The WTF isa pointer to where the next element starts.

End-of-Design The marker in the design file which marks the end of all theelements.

End-of-File The physical end of the file.

Enter-Data-Fields (EDF) These fields allow a MicroStation user to break up a textstring into smaller pieces which are then easily modified.

Extended TCB Elements A type 66 element on level 9 is used to store certain TCB(Terminal Control Block) variables that are specific toMicroStation (not supported on Vax-based IGDS systems).

GRAFIC Next graphic group number.

H-bit For closed element types (shape (6), complex shape (14),ellipse (15), cone (23), b-spline surface header (24), andclosed b-spline curve header (27)) the Hole-bit indicateswhether the element is a solid or a hole.

0 = solid, 1 = hole.

For a cell header (type 2) the Hole-bit indicates:

0 = regular cell

1 = orphan cell (created by “group selection” or

application)

For a line (type 3), the Hole-bit indicates:

0 = regular line segment

1 = infinite-length line

For a point string (type 22), the Hole-bit indicates:

0 = continuous

1 = disjointed

IGDS Stands for Interactive Graphics Design Software. Thissoftware runs on VAX-based CAD systems and works onfiles with the same format that is used by MicroStation.

Index-To-Attributes Word 16 defines the number of words existing between (andexcluding) itself and the first word of the attribute linkagedata. The attribute linkage is optional and may or may notbe present, but the index must point to the location for thefirst word of the data whether or not it exists. This word

Chapter 16 — Glossary Page 141

essentially describes the numbers of words of element-typedata following word 16.

L-bit When set, indicates the element is locked.

M-bit When set, indicates the element has been modified.

N-bit When set, indicates the element is new.

Nesting Level A component element which is part of a complex element isconsidered to be nested in that complex element. Complexelements can be nested within other complex element. Eachtime a component element is nested within a complexheader its nesting level would increase by 1.

For example, cell ‘GASKET’ is part of cell ‘FITTING’,which is part of cell ‘FAUCET’. The component elementswhich make up the cell ‘GASKET’ are also nested in othercells, so therefore its nesting level is 3.

NFS (Network File System) NFS was originally designed by Sun MicroSystems whichallows you access to disks on other computer systems as ifthey were your local disk drive.

Nibble Four binary digits.

P-bit Indicates whether or not element is planar:

0 = planar, 1 = non-planar

Phantom Element These are elements that are displayed, but cannot be selectedor manipulated in any way. This problem comes about whenan element that is not part of complex element, such as a cellor a text node, has its complex bit incorrectly set.

Property Bits Describes various properties of an element. See A bit , H bit ,L bit , M bit , N bit, P bit, R bit and S bit.

Quaternions In 3D design files, the orientation of an element isrepresented by the transformation matrix to design filecoordinates.

Range Block Words 3 through 14 of an element define the absolute UORrange of the elements.

R-bit Indicates whether element is oriented relative to the screenor relative to the data base:

0 = relative to data base (view dependent)

1 = relative to screen (view independent)

RLID These are a special type of attribute linkage used by the oldVAX product IGDS.

S-bit Indicates whether or not the element is snappable.

0 = snappable

1 = non-snappable

Page 142 FileFixer

Siamese Attributes Linkage The attribute linkage extends beyond the end of the elementit is attached to. That means the linkage and the elementfollowing are sharing file space.

TCB Terminal Control Block (TCB). A global data area ofmemory in which MicroStation stores settings, such asworking units, view information, global origin, etc.

Text Node This element is a complex header for groups of textelements.

Text Height & WidthMultipliers

These multipliers are used to scale a text element against thenormal character size to determine the true size of the textelement.

Words-In-Description All complex header elements have a Words-In-Descriptionword. Words-In-Description tells how long the entirecomplex element (usually made up of many individualelements) is.

Words-To-Follow All active (non-deleted) elements must have a words tofollow of at least 16, which will encompass the standardelement header, and not greater than 766. In reality no activeelement should ever have a words-to-follow of less than 22.That is why complex-shapes and connected-strings alwayshave a dummy attribute linkage appended. The pointer tothe beginning of the next element in a design file or celllibrary.

Chapter 17 — New Features and Fixes Page 143

Chapter 17 — New Features and Fixes

7.2a — 16 March 1999Corrected the problem where the “Set illegal class to” option was getting unselected afterpressing the <OK> button on the Select Class dialog box Options|Repair|Element|<SelectClass>”.

Corrected the spelling of "Construction" in the Select Class dialog box.

Fixed a problem with the text range not being repaired correctly where it was leaving alarge range block around the text string.

FileFixer no longer gives you an MDL abort in prescan.mc at line 1215 when itencounters attributes flagged but no attributes as non-graphic elements.

Added the “Recover deleted vital elements (like type 9, 8 or 10)” repair option toundelete vital elements, such as a design file header where the file is not viewable andreporting it’s not a design file.

FileFixer will now turn off the complex bit on a type 66 element when it is set (turned onunnecessarily) and not part of a complex header. It is controlled under Options|Repair|Complex|Correct complex bit errors and Search|Complex|Complex bit is on for a non-component element. This is one of the things that handle range block problems manifestwhen you attempt a fit view.

Under Repair|Design File| reworded the “Work on original file (backup original file)” to“Create backup file (work on original file)”.

Any specific resource file used and saved as “Save Resource File” or “Save ResourceFile As”will now remember and use this same resource file the next time FileFixer isloaded. Additionally a new version of FileFixer that is being installed will not overwritean existing “fixer.rsc” that contains the users settings.

Modified FileFixer to not report a problem with reference file attachments if the numberof vertices is less than 102 because all vertices based elements are limited to 101 vertices.

Added the ability to find and delete nested cells in a cell library when you have a type 1element (Cell Library Header) nested within a type 1 element.

Added the ability to find and delete reference file attachments that have a blank filename. This is under Options|Repair|Reference File.

Added the ability to find and repair reference file attachments that have a file name,logical name or description string which overflow their field, also under Options|Repair|Reference File.

Fixed an MDL abort problem which would happen when you pressed the <Remove>button on the "Options|Repair|Type 66" and there were no type 66 items selected. TheMDL aborts were in fixer.mc at line numbers 5557, 5385 and 7872.

Page 144 FileFixer

Added the ability to find and delete dimension elements that have no data or associativepoints in them. These are located under Options|Search|Dimension andOptions|Repair|Dimension.

Added the ability to restore view rotations when replacing type 9 elements to allow userto keep their view rotations and not have to do a “Fit View” on each view afterreplacing.the type 9.

Modified FileFixer to check and repair arc range errors when the arc has an attributelinkage. Previously FileFixer would only find arc range errors when there were noattribute linkage.

Modified FileFixer to also check the reference file logical name before determine thatthis is a duplicate reference file attachment. So, before it is determined that a referencefile attachment is a duplicate both the file name and the logical name must match.

7.1a — 8 February 1999Corrected a problem where locked elements weren’t being found in design files, whichdidn’t have TriForma data in them.

Corrected a problem where FileFixer was reporting and deleting shared cell definitionsthat had no shared cell instances, these being used as pattern data for associativelypatterned shapes. FileFixer now reports no errors for these shared cell definitions.

FileFixer is now able to repair a reference file that is currently referenced by a design fileloaded in MicroStation at another workstation on the network.

FileFixer now allows type 38 (IGDS reserved) elements to be part of a cell or shared cell.TriForma creates this element as part of a cell or shared cell. Previously, FileFixer wouldconsider this element to be illegal, as it isn’t a displayed element type, and would dropstatus on the cell in order to delete this illegal element. By doing this TriForma linkagedata would be lost.

Previously FileFixer reported a cell range diagonal problem as one that needed to berepaired. This was never fixed even though it was reported as being fixed because therewas no problem here in the first place. This anomaly has now been corrected

In the manual a column was added to the “Repair-type error messages sorted bycategory” table which reports the step each repair option is done on. This includes allthree steps, Step 1 (WTF-words to follow problems), Step 2 (WID-words in descriptionproblems) and Step 3 (all other problems).

The ability to save the level symbology information was added to the “Replace Type 9Elements” dialog box.

Added the following search options:

• Report arc’s sweep angles that are not between –360 and 360 degrees. The errornumber is 318.

• Report classes that are illegal (greater than 6). The error number is 333.

• Expanded the search option that reports multiple shared cell definitions in a designfile to also report multiple library cell definitions in a cell library. The error numberis 766.


• The design file header active angle should be between –360 and 360 degrees. Theerror number is 163.

• The design file header GGBASE (graphic group base number) is greater thanGRAFIC (next graphic group number). The error number is 153.

• The design file header active level is out of range. The active level should be between1 and 63. The error number is 155.

• The design file header NNBASE (text node base number) is greater than CANODE(next text node number). The error number is 154.

• The design file header working units are bad. All the working units must be non-zero.The error number is 156.

• The design file header words-to-follow value is incorrect, must be 766. The errornumber is 157.

• The cell library header words-to-follow is incorrect, must be 23. The error number is159.

Added the following repair options:

• You can set illegal class (greater than 6) to a valid class. The class is user definable.

7.0a — 31 December 1998Added the following options when using MSBATCH mode:

• -f Specify the report file name you want to use.

• -r Specify the FileFixer resource file you want to use for the search and repairoptions.

• -o Output file directory. The fixed or backup file will be placed in this directory.

Corrected a problem with MSBATCH mode not being able to fixed design files with aWTF error.

Corrected a problem where occasionally FileFixer wouldn't find a cell within a cell of thesame name.

Changed the message “WARNING: FileFixer has finished processing. However, at leastone file could not be updated. See your report file for more information. Successfullyrepaired files have a ‘.bkp extension.” to “WARNING: FileFixer has finished processing.However, at least one file could not be updated. See your report file for moreinformation. Backup files have a .bkp extension.”.

Fixed an anomaly where FileFixer sometimes would hang up when run on a small fileand the license dialog box was still displayed.

Added the option button character to the main option button on the main FileFixer dialog box.

Added the ability to add a null filled linkage on a surface (type 18) element to make it theminimum length of an IGDS element.

Added the ability to delete duplicate reference file attachments.

Page 146 FileFixer

Added the ability to find elements that are some distance away from the rest of theelements in a design file. This can help solve some FIT problems.

Added the ability to select which database linkages you want to delete. The databaselinkages you can delete are: DMRS, Oracle, INFORMIX, Ingres, ODBC, RIS, Sybaseand XBASE/DB3.

FileFixer will now automatically remember what you last had in the “Report File” and“Which Files?” fields when you start the program again. You don’t have to save theresource file for this to happen. Whatever you had in those fields when you exited theprogram will be restored when you re-start the program. The only except to this is if youhave the general option “Use current design file as default” turned on then the “WhichFiles?” field won’t be restored, but the “Report File” will be.

Added an error message to the report file when FileFixer wasn’t able to delete it’stemporary files. The format of the names of the temporary files are: FFxxxxxx where thex’s are numbers. This could happen when a user has the ability to write a file to adirectory but not change a file in that directory. This will help you isolate why FileFixercouldn’t delete it’s temporary files.

Modified the way the correction was done for error 346 (An Enter-Data-Field has anunrecognized justification). The old method was to set the EDF justification to rightjustification. It now sets it to match the text justification of the text element (type 17).

All the search and repair options are now listed in the report file. There were severalmissing.

Added the ability to skip the elements locked check when processing a design file withTriForma information in it, as TriForma locks elements that it built.

Added a close button to the main FileFixer dialog box.

FileFixer will now look at the configuration variable AXI_RSC_DIR to find the resourcefile which holds the default settings for the search and repair options. FileFixer will usethis variable if the fixer.rsc file doesn’t exist in the current working directory. This isvaluable for network users who want their own resource file but share FileFixer.

You can now replace the type 9 elements of the active file. Previously you would get a007 error.

6.8c — 26 November 1998Corrected a problem where FileFixer would exit when run in batch mode and a words-to-follow error was encountered.

6.8b — 1 October 1998This is the first version ready for year 2000.

Modified to run under MicroStation J.


Corrected a problem with version 6.8a not correctly handling "<EDITED FILE LIST>".When <EDITED FILE LIST> was in the files text field. FileFixer wasn’t finding anyfiles to process.

6.8a — 22 September 1998Added the TCB (terminal control block) definition into the glossary.

Added a “select directory” dialog box to specify the directory you want to put the reportfiles in.

Added the capability to be able to specify full file names using UNCs (universal namingconvention), such as “\\server\server-p\dev\fixer\axiom.dgn”.

Added the “Uninstalling” chapter to this document.

Before creating a new cell library header FileFixer scans through the cell library todetermine what the dimension is. If FileFixer determines that the dimension of the celllibrary is different than what is defined in the cell library header, then it will prompt theuser to select the correct dimension.

6.7a — 19 August 1998Made changes to handle spaces in a directory name when specifying the pathname of thedesign files in the text field “Which files:”.

Added the section “Using the ‘AT’ Command under Windows NT 4.0” to explain how torun FileFixer at a specified time each day under Windows NT 4.0.

Modified the report summary text line for error code 110 from “Design file range(DFRANG) is off” to “Design file range (DFRANG) is incorrect”.

Modified FileFixer to not increment the “number of files analyzed are in danger” counterwhen the only error encountered is error code 079 (Unwanted End-of-Design markerdetected).

Added a search and repair option to find and delete null filled linkages. This will notdelete those null filled linkages that are needed to make an element the minimum IGDSelement size.

FileFixer will no longer delete a text element which has no characters but does haveattribute linkage. Text elements in Modeler files can be created will no characters buthave attribute linkages.

Modified FileFixer to correctly check the WID for raster header elements (type 90).

The “Report file extension” field will now be defaulted to “rep”.

6.6d — 10 August 1998Added error code 037 (Element has unwanted attribute linkage) into Chapter 7 — WhichError Messages are Generated from Which Option tables. This error code is controlled by

Page 148 FileFixer

the Repair Options “Remove all database linkages” and “Remove database linkage ofcomponent elements”.

Made a change so that MicroStation wouldn’t exit sometimes when repairing a designfile with a NOC (number-of-components) corruption error.

Corrected a problem with the b-spline knots getting corrupted when the b-spline knotelement is larger than 300 words.

Changed the message from “Put reports in directory with MicroStation files” to “Putreports in directory with fixed files” on the Report File Selection dialog box.

Added the ability to correct an ITA error in a pattern element (type 5 level 0).

Changed the message from “Highest graphic group number” to “Highest graphic groupnumber”.

Changed the category label from “Tags” to “Tag” on the Search option dialog box.

6.6c — 6 July 1998Modified FileFixer to not delete a nested cell if the nested cell has a dimension element(type 33) associated with it.

Added a search and repair option to verify the cell header diagonals. The cell headerdiagonals are defined as the deltas from the cell origin to the lowest and highest points ofthe cell. When the cell header diagonals are corrupted it can prevent you from being ableto rotate the cell.

Changed the message “Press ESC to abort ” to the standard convention “Press<Esc> to abort ” .

Modified several messages to state the complete program name “FileFixer ” insteadof “Fixer ”.

6.6b — 27 June 1998Added a search and repair option to find and repair missing strings (type 3 or type 4) in acomplex chain (type 12 header). When you create a complex chain from two line stringsthat are not connected, then MicroStation will not create a line string element for thespace between the line strings. MicroStation will automatically display a line stringbetween the two line strings, but no element is created. This means that at some point youdrop status on the complex chain then the line string between the two original line stringswill disappear. FileFixer can now create a line string and add it to the complex chain sowhen the status is dropped on the complex chain the line string will not disappearbetween the two original line strings.

Corrected an abnormality when extracting a text string from a corrupted text element.

Corrected an abnormality in which FileFixer would exit when it found a corrupteddimension element (type 33).


6.6a — 11 June 1998Modified the Replace Type 9 feature to not ask which working units to use if they are thesame.

Added the ability to delete type 19 elements, which are too small.

Modified the way a shared cell instance level mask is checked against the shared celldefinition. FileFixer can now check and repair shared cell instance level mask when theshared cell instance is placed relative to the shared cell definition, or if the level mask hasbeen overridden. When the level mask is overridden then the only level being used is thelevel the shared cell instance is on. The following example shows how the shared cellinstance level mask is defined when the shared cell instance is relatively placed:

Shared cell definition level mask: 20,21,34,37

Shared cell instance level: 41

Shared cell instance level mask: 41,42,55,58

Moved the check for a locked element to after the check for a suspiciously long linkagearea. Otherwise, occasionally you might see the 120 error (locked element) and below itin the report file, the linkage area being corrected.

Added the ability for FileFixer to warn you if there may be elements beyond the end-of-design marker. FileFixer checks to see if the location of the end-of-design marker ismuch earlier than the actual end-of-file, if so it will display the warning message “EODfound too early in design file. [106] ”.

Under “Help” added the “About” dialog box to display the version of FileFixer andlicense type, copyright notice and the date and time this version was built.

The copyright year, displayed in the about box and in the report file, is now displayedwith all four digits, instead of only the last two. This is a handling for the year 2000.

Added the message “___ elements were recovered past End-Of-Design marker ” to tell you how many elements were recovered.

FileFixer has been modified to require at least one radio button to be selected when youchoose “One report file per MicroStation file ” after pressing the<Select> button next to the Report File field on the main dialog box.

FileFixer can now automatically delete the Modeler BRP file.

Added an option to search and repair elements, which have multiple line style data in thelinkage area of the element. Line style data is saved in the linkage area of the element.For all elements, except for the multi-line element, there can only be a maximum of onecustom line style linkage for that element. FileFixer will now search for and remove anycustom line style linkage, incorrectly added, after the first one.

Page 150 FileFixer

Added the message “This file now has x elements (after beingfixed) ” after the message “This file originally had x elements ” in thereport file.

Added a search option, which allows you to search for errors in and repair reference fileattachments. This search option is “____ layers of reference filesshould be processed .” For example, let's say you set FileFixer to process twolayers of reference files. Then if design file abc.dgn has a reference file of xyz.dgn andxyz.dgn, itself, has a reference file of ghi.dgn, all three files will be processed when youselect design file abc.dgn to be processed.

Added a <Quit> button to the pop-up working units dialog box. This dialog box isdisplayed when you are replacing the type 9 elements and the working units are differentin the donor file than in the destination file. This dialog box allows you to select whichworking units you want to use.

Changed the factory default setting for the search option “Linkage area is suspiciouslylong” to be off, so that it will not automatically search for suspiciously long linkages.

Changed the factory default setting for allowable linkages from 40 to 128.

Changed the wording of the repair option from “Add on the repair file extension insteadon replacing it” to “Add on the repair file extension instead of replacing it”.

6.5f — 22 May 1998Modified the design file range repair feature to not change the global origin of the designfile. It now only updates the design file range.

6.5e — 2 April 1998 Added ability to fix or delete an arc or ellipse element whose origin is off the designplane.

Added the ability to detect the differences between tag linkages. Tag linkages can pointto a dimension element or a tag element.

Correctly save the current FileFixer's resource file address, so that when FileFixer isrestarted it loads the correct option settings.

6.5c — 15 March 1998 Added -o option to batch mode. This option allows you to specify the directory for therepaired files.

Added ability to specify where the report files will reside if you are creating one reportfile per design file. The options are to put them in the directory where the design filesbeing repaired exist, in the directory where the repaired files are being placed, orspecifying the directory you want them to be placed in.


Created a work around for the MDL function, which was causing dimensions to bestretched.

6.5b — 31 October 1997 Changed the message to be more informative when a 007 error is encountered. When theoriginal file is read only and you are updating the original file this new message will bedisplayed.

Changed the message when replacing type 9s and updating the original file. The previousmessage was misleading. It made you think the repaired file was the backup file, which isnot the case.

When replacing type 9s the fixed file will now use the extension specified on the designfile repair option screen. Previously it always defaulted to “.fix”.

The factory defaults dialog box now has “Factory Defaults” as a title.

Added the design file “edg-cant.dgn” to the design files shipped. EdG can’t repair thisfile. You must use the byte search feature in FileFixer.

Whenever you turn on the options in FileFixer, which will remove database linkages, youwill get a warning dialog box telling you that this is risky. One of the uses of attributelinkage is to extract information from a database. This shouldn’t be done without beingaware of all the ramifications.

FileFixer now allows a type 14 (complex shape) component element within a type 18(surface) header.

The following text search options were added:

• Text height or width too large or too small . This option checksthe text height or width multipliers to see if they are larger or smaller than values youspecify. You can specify the multiplier values in master units or sub units orpositional units.

• Bad text height to width or width to height ratio . Thisoption will check to see if the height to width or width to height ratios are within aratio you specify. The default is 10.

Created a graphic interface for specifying which type 66 levels that you want deleted.

Updated SafetyCheck 1.2c to handle the new FileFixer error numbers.

6.5a — 28 August 1997 Changed Locate-Zinger to Problem Element Viewer in this document.

Added the ability to allow more than one user on a network to be able to run FileFixer atthe same time.

Created FileFixer Light based on how it is licensed. This product only has the ability tosearch a design file and only reports the number of 100, 300, 500, 700 and 900 errors.

Page 152 FileFixer

Added a general option, which allows the user to have FileFixer default to the currentdesign file or the last file searched or repaired.

Fixed an anomaly in which the Siamese attribute linkage (error #364) wasn’t beingrepaired, even though it was being reported as having been repaired.

The directory specified on the Design File repair option screen is not verified when theOK button is pressed.

Added the following Tag search options:

• Element tagged with no tag . This option reports an error when it finds anelement with tag linkage but there is no tag element (type 37) associated with it.

• Tag element different that definition in tag set . This optionreports an error when the information in any tag element (type 37) is different that thedefinition in its tag set element (type 66 level 24).

• Tag not associated with any element . This option reports an errorwhen there is a tag element (type 37) but it’s not associated with any displayableelement.

• Tag set missing . This option reports an error when there are tag elements (type37) but no tag set element (type 66 level 24) for these tags.

• Tag set not used . This option reports an error when there is a tag set element(type 66 level 24) but no tags are used which make up that tag set.

Added the following Tag repair options:

• Delete tag not associated with any element . This option willdelete any tag elements (type 37) which aren’t associated with any displayableelement.

• Delete unused tag sets . This option will delete any unused tag sets (type 66level 24).

• Remove tag from element with no tags . This option removes theelement’s tag linkage information when there are no tag elements (type 37) for thiselement.

• Update tag element from tag set . This option will update the tagelement (type 37) with the definition for this tag from the tag set (type 66 level 24).

The fixed design file now has the same time date as the design file being repaired. Thereis a Design File search option which allows you to set the fixed design file date to thecurrent system time. This is how the old command line version of FileFixer worked.

Added the ability to have wildcards (‘*’ and ‘?’) in the list file.

The format for including files found in sub-directories into the Files to Process list waschanged from using –s to using /s . For example:c:\axiom\fixer\*.dgn /s

The “Which files?” field on the FileFixer dialog box no longer accepts comma delimitedfile names. The updated File List Edit Dialog handles multiple file names and directories.

Fixed an anomaly were sometimes the component elements were getting deleted when acells status was dropped.


FileFixer will now not attempt to correct more errors in an element when that elementhas been deleted by FileFixer.

Added the ability to find and correct DFRANG (TCB values for the high and low rangesof the displayable elements in the design file) errors.

FileFixer brought up to internal code standardization.

6.4b — 12 June 1997 Added the capability to optionally prevent anyone but the System Administrator frommodifying FileFixer’s search and repair options.

Added the File pull-down menu. This menu allows you to quickly select any of the lastnine files you searched or repaired. You can also use this menu to save FileFixer resourcefiles or to open a different FileFixer resource file. FileFixer resource files storeFileFixer’s search and repair option settings.

Improved the wording of a number of error messages to clarify the exact nature of theproblem and the needed solution.

When replacing the type 9 in a design file, you now have the option of creating a .fix fileor making the fixes directly to the original design file (and creating a .bkp file).

FileFixer now verifies that the report file and the fixed file won’t have the same name.Previously this would cause the fixed file to get overwritten by the report file.

FileFixer now defaults to repairing the design file currently loaded in MicroStation.

Changed the name of the temporary design file that FileFixer uses when repairing acorrupted design file from axiomtmp.dgn to fixerdgn.sys. This file is now put in the samedirectory as fixer.ma.

The “current step” progress bar now works during the initial scan.

Added the ability to repair corrupt or missing cell library headers. FileFixer can now adda brand new cell library header to a very badly damaged cell library just as it has alwayshad the ability to add a type 9, 8 and 10 to very badly damaged design files.

Added the following search and repair options:

• Search option to detect shared cell definitions with no shared cell instance.

• Repair option to delete shared cell definitions with no shared cell instance.

• Repair option to delete recursive nested cells (a cell nested within itself). This optionwill delete the unwanted cell headers while retaining all the displayable elementswithin the cell.

• Search option to detect duplicate shared cell definitions.

• Repair option to delete duplicate shared cell definitions. Only the first definition willbe retained.

Cleaned up the right edge of the Safety seal which was being cut off.

Page 154 FileFixer

6.3e — 21 March 1997Ported to MicroStation 5 for CLIX, DOS, NT and MicroStation 95 for DOS.

Adjusted the handling of Non-shared cell level or class map problems for DOS.

Updated License2 code for the handling of foreign operating systems.

6.3d — 14 February 1997Ported to MicroStation 95 for Windows platforms.

Ported to MicroStation 5 for the Sun workstation.

Added a list box for specifying which elements to remove for certain FileFixer errormessages.

Updated License2 code for the handling of foreign operating systems.

6.2a — 28 August 1996Ported to MicroStation 95 and MicroStation 5 under Windows 3.11.

Fixed an anomaly in which complex bits were not getting reset on non-componentelement (error 702).

Added repair option to unlock elements, re-sequence text node numbers and to re-sequence graphic group numbers.

Upgraded to new license software.

Changed name of temporary Axiom design file from axiom.axi to axiomtmp.dgn.

Moved report options to the end of the report file.

Added glossary to User’s Guide.

Added the FileFixer’s Seal-of-Approval to SafetyCheck when the currently loaded designfile is certified by FileFixer with no errors greater than 299.

6.1a — 12 July 1996Ported to MicroStation 95.

Changed error level 771 “Shared instance level doesn’t match definition.” to level 171.

Added current file and all files completion indicators.

Added variable backup extensions.

Fixed an anomaly where FileFixer was checking for the .bkp file even though FileFixerwasn’t creating the .bkp file.

Handled an anomaly where the .rep file wasn’t being created correctly for the rightdesign file when a .rep file was being created for each design file during that run.


SafetyCheck now tells you to run FileFixer if no certification stamp is found.

6.0c — 2 April 1996First port to CLIX as an MDL application. The SafetyCheck MDL application is madeavailable for all FileFixer platforms.

6.0b — 21 March 1996First port to NT as an MDL application.

5.1o — 15 March 1996License2 version for JAM was released.

6.0a — 16 January 1996Rewritten as an MDL application.

5.1l — 8 June 1995Fixed an anomaly in which you are back scanning and a WTF error is discovered andsometimes that element would be discarded by FileFixer.

5.1k — 1 May 1995Modify a couple German messages (German version only). Made a couple of minorimprovements.

5.1j — 11 January 1995Improved the copy file routine to use less memory. You only need 350k to run from thecommand line. You only need 380k to run within the graphic screens if you don’t use theF5 key.

Made improvement in saving the original file as a .bkp file and updating the originaldesign file.

Page 156 FileFixer

5.1h — 8 November 1994Modified to create a Demo with Everlock.

5.1g — 25 September 1994Modified to work with an old beta version of the font.rsc file.

5.1f — 17 August 1994Modified to work with Everlock.

5.1e — 21 July 1994Made the following changes:

• Added the function of working across the NFS network with no difficulties.

• Now reports element type 37 correctly as a bad element type.

• Handles font resources from different platforms.

5.1c — 9 July 1994Made the following enhancements and fixes:

The type 9 was getting corrupted when there was a range error on an element at thebeginning of the design file, and the type 9 was ambiguous regarding the design filedimension.

To delete the EDFs when the number of EDF’s are unusually large.

Initialize the total error count so that a negative error count wouldn’t be displayed.

5.1b — 1 June 1994Fixed a lock up problem.

5.1a — 30 March 1994Modified to work with either the old font libraries or the new font resource files.


5.0h — 25 March 1994Handled the following anomalies:

• not allowing 151 vertices in a type 25.

• not verifying a type 5 is on level 1 before checking if A-Bit is set.

• not allowing type 25’s under type 24’s.

• not allowing type 25’s to follow 25’s.

• not calculating WTF on type 25’s correctly.

5.0g — 25 February 1994Added new license capabilities.

Fixed an anomaly where a “J” would be displayed in the “Correct Complex Bit Errors”field.

Fixed a problem when a delete element is greater than 766 characters. It would createphantom elements.

5.0e — 10 December 1993Added the ability for the user to specify which levels the type 66 elements can reside on.

Corrected problems with creating phantom elements in cell libraries.

5.0a — 6 September 1993Added the ability to report and fix orphan cell definition without orphan flag.

Can now detect and fix shared instance class or level mask which differ from the sharedcell definition. Also detects and fixes when the shared instance is on a different level thanthe shared definition.

Added the ability to report and fix Enter-Data-Fields which overlap, which are not inorder and which have a length of zero.

Corrects and reports when the text string overflows the element length.

Reports when a cell (type 2) is not nested in a cell library and when there’s a null name ina cell library. Also reports when the maximum complex nest level has been exceeded.

Will now detect and fix when there is a duplicate design file header (type 9 level 8).

Will now turn off the attribute flag in a color table (type 5 level 1) when attributes are notpresent.

Will set the active pattern scale to 1 when it is zero.

Will set the rotation angle to 0 degrees when it is 360 degrees.

Page 158 FileFixer

4.8i — 27 July 1993Fixed to work across an NFS network with locking turned off.

Added byte search capabilities if the next element doesn’t begin on a word boundary.

Added option to not compress deleted elements (FRAMME uses these elements).

Now works on directories with extensions.

Now puts the .fix file in the same directory as the .dgn file.

Now properly handles fonts that are too large for a text element.

Added a number of Enter-Data-Field validations.

4.8c — 26 March 1993Shared cell definition checking is no longer incorrectly skipped when only one design fileis being diagnosed.

FileFixer now detects duplicate shared cell definitions (more than one type 35 with theexact same cell name in a design file).

4.8b — 24 March 1993Very long elements with unreliable Words-To-Follow are now handled correctly by theAUTOMATIC FILE REPAIR command.

Type 11s and type 13s with only two visible vertices are now flagged only if the twovisible vertices are identical.

A “This font has no such character. [145]” message is now generated for text elementscontaining a character above 128 only when the font is truly missing the indicatedcharacter.

The level of an empty text node in a cell is now added to the cell level mask of cells in acell library.

4.8a — 23 February 1993The Replace Type 9 command now gives lets the user decide which set of working unitsto use — the set from the design file being repaired or the set from the seed design file.

FileFixer now has the ability to replace the type 9 of hundreds of design files with asingle command. This is because the ability to replace a type 9 has now been added to theAutomatic Design File Repair command.

FileFixer now has two ways of replacing type 9 header elements. 1) Using the AutomaticDesign File Repair command. This method has the advantage of being able to replace thetype 9 of hundreds of design files with a single command. 2) Using the Replace Type 9command. This method has the following advantages: it can add a type 9 to a design file


that has lost its type 9; it can replace a type 9 element that has an illegal Words-To-Follow.

The REMOVE TYPE 66 ELEMENTS option no longer removes named level elements.

4.7c — 16 January 1993FileFixer is now able, in almost all cases, to automatically determine the dimension (2Dor 3D) and file type (design file or cell library) of a file even if it has no type 9 or type 5header element.

FileFixer can now repair a file with more than 31,999 errors in it.

4.7b — 5 January 1993Added the ability to detect a text element whose rotation does not match the text node itis part of.

The user is now able to tell FileFixer to create its .fix files on a different disk anddirectory than the one containing the original design file.

4.7a — 18 December 1992Added the ability to detect and (at your option) automatically remove stray elementsfound outside of type 1 cells in a cell library.

Added the ability to detect deleted phantom elements — that is, deleted elements thathave their complex bits set, but which are not part of a complex element. This option isturned off by default.

FileFixer now lets you set one range tolerances for text elements and another rangetolerance for other element types.

FileFixer now detects complex elements whose Words-In-Description exceeds 65516.(Deleting such elements can corrupt a design file).

4.6c — 22 November 1992Added the ability to detect and repair an absolute shared cell instance (type 35) whoselevel mask does not match the level mask of its type 34 shared cell definition.

Added the ability to detect duplicate reference file logical names.

Added the ability to detect text elements that use a font that is not contained in the currentfont library.

Added the ability to detect a character in a text string that is not represented in the fontlibrary specified by the user.

Page 160 FileFixer

Added the ability to ignore the font library when doing text range testing. When thisoption is in use, each text character is considered to have the same standard size. Sincethis option is much less precise than using the font library, the element range toleranceused for text elements is 20 times what is given in the SEARCH OPTIONS screen.

Added the ability to skip text range validation while still performing range validation onthe other element types.

FileFixer now produces a summary indicating how many of each type of error wasencountered while generating a report.

FileFixer-DOS’s memory requirements have been reduced by another 40K.

FileFixer now includes pattern (type 5, level 1) elements in its graphic group andGRAFIC validations and repairs.

For the purpose of range block calculations, FileFixer now treats arcs with a sweep angle(positive or negative) of 360 degrees or greater like ellipses.

If a deleted element is found inside a type 1 cell in a cell library, FileFixer nowautomatically squeezes out (removes) the deleted element and adjusts Words-In-Description, Number-Of-Components and other parts of the type 1 automatically.

4.6b — 20 November 1992No longer searches for missing type 34 definitions in cell libraries.

4.6a — 17 October 1992FileFixer-DOS memory requirements have been shrunk by about 40K.

The user now has the option of either 1) having FileFixer write the repaired file to a .fixfile (like it has always done) or 2) have FileFixer make a backup of the original file (withan extension of .BKP) and makes its changes to the original file.

The parameter (.PAR) file is where all user preferences are stored. When the useranswers “Yes” to the question, “Do you want to save all current settings as yourdefaults?”, the parameter file is created or updated. By default the parameter file has thename FIXER.PAR and is located in the same directory as the FileFixer executable file.The user can now specify an alternate parameter file on the FileFixer command line.Each alternate parameter file can contain a different set of defaults. You could, therefore,have a different set of defaults for each user, each project, or each directory. To specifyan alternate parameter file simply enter “fixer -p parameter_filename”.

Previously, if the user wanted a separate report file for each design file processed, thereport file would have the same file name as the design file, but have the last two lettersof the extension set to “ff”. Now, all reports files have the same name as the design file,but an extension of .rep.

Previously, if the first linkage on an element was a non-database linkage, the element wasineligible for having its linkage area removed. Now, if ANY linkage on an element is anon-database linkage, the element is ineligible for having its linkage area removed. This


protects non-database linkages (such as area fill linkages) from being inadvertentlyremoved.

FileFixer now gives the fixed version of the design file the same file ownership, dates,archive bit and protection as the original design file.

4.5e — 15 November 1992Nested type 1 cells no longer have their cell level mask adjusted.

4.5d — 6 October 1992FileFixer is now even better at differentiating garbage elements from desirable elements.(Special thanks to Dan Denton for providing the test file that made this possible.)

Previously if an element had a linkage area greater than 60 words the element was alwayssuspected of being a damaged element. This test has now been changed so that anelement is considered suspicious only if its linkage area is greater than 60 words andgreater than the MAXIMUM LINKAGE AREA SIZE IF EVERYTHING ELSE ISPERFECT value specified by the user on the REPAIR OPTIONS screen.

4.5c — 10 August 1992Only database (DMRS, Oracle, Informix, DBase III and RIS) linkages (instead of anylinkage) on a component element can cause error 340 now.

The REMOVE ALL ATTRIBUTE LINKAGE option now removes only databaselinkages, not other types of linkages (like fill linkages, the linkage type that controlswhether a closed element is filled when it is displayed).

Previously, the range of type 34 elements was sometimes calculated incorrectly. This isnow fixed.

Earlier releases of version 4.5 were unable to use a font library across the network if thatfont library was already in use by MicroStation. This is now fixed.

FileFixer no longer analyzes the level mask of type 1 elements containing nested (type 2)cells.

4.5b — 12 July 1992FileFixer has, for several versions now, had the ability to automatically repair Words-To-Follow warnings. FileFixer has numerous methods of repairing Words-To-Followwarnings depending on the exact situation encountered. Some of the techniques includeturning off the A-Bit (Attribute Bit) of the element, turning on the A-Bit of the element,rounding up the size of the attribute linkage area to the nearest multiple of 4 words andremoving the linkage area of the element altogether. The user now has explicit control

Page 162 FileFixer

over which techniques FileFixer is allowed to use and which it isn’t allowed to use.Further, the user now has explicit control over the maximum linkage area size allowed inhis design file files.

A change was made to the algorithm which FileFixer uses to repair fatal Words-To-Follow errors. FileFixer is now much less likely to include worthless elements (like type96s) when repairing fatal Words-To-Follow errors.

4.5a — 11 July 1992Previously one report file was created for each run of FileFixer regardless of the numberof design files processed in that run. The user now has the option of creating a differentreport file for each design file processed. The report file has the same name as the designfile except that the last two letters of the design file’s extension are changed to “f”. Forexample, the report for design file xyz.dgn would be in file xyz.dff. The report for fileabcdef.cel would be in file abcdef.cff. This option is turned on by enter “*.*” as the nameof the report file.

RLIDs are a special type of attribute linkage used by the old VAX product DGS. Thisversion of FileFixer supports DGS users by providing an option that treats deletedelements with RLIDs as though they were active (non-deleted) elements.

Earlier versions of FileFixer made no mention in the report file of design files containingno errors. The new version of FileFixer has an option that tells FileFixer to list perfectdesign files in the report file with a message indicating that they have no errors.

4.4f — 8 July 1992H-Bit errors are no longer reported for types 8, 9 and 10.

Added the ability to automatically repair Reserved Bit errors.

Added the ability to detect and correct cell level mask, cell class map and other errors inshared cells.

4.4e — 11 June 1992Added the ability to detect and automatically delete a b-spline element with an illegalnumber of a specific type of b-spline components. Design files with type of problem willcrash MicroStation.

The range of an arc with a sweep angle of exactly 360 degrees is now calculated correctlyunder CLIX.

The user can now change the default report file name by answering “yes” to the “Do youwant to save all current settings as your defaults?” question.

The file fixer.par (the parameter file which holds the user’s preferences) is now optional.


4.4d — 28 May 1992Added the ability to detect and automatically remove b-spline components that are notpart of a b-spline complex element. Such elements will frequently crash MicroStation.

FileFixer now has an interrupt handler so that if it is abort with <CONTROL C>,<CONTROL BREAK> or <CONTROL Y>, it no longer leaves behind scratch files thatbegin with “ff” or files that have “.a__” as an extension.

4.4c — 9 May 1992FileFixer now has the ability to detect and automatically correct non-shared cells (type 1sand type 2s) that are not on level 0. Until repaired by FileFixer, type 2 cells with such aproblem do not plot correctly. Placing a type 1 cell with this problem propagates theproblem into every design file into which it is placed. FileFixer can also repair thisproblem in cell libraries to prevent such propagation from occurring.

The REMOVE ALL ATTRIBUTE LINKAGES option now has no effect on associativedimensioning “TAG” linkages.

FileFixer no longer checks the range of text elements on level 63 of non-graphic type 1cells (such as menu cells and tutorial cells) because these have non-standard ranges bydesign.

4.4b — 18 April 1992FileFixer now looks at attribute linkages in greater detail than ever before. Instead of justlooking at the linkage area of an element as a whole, we look at the individual linkagesthat compose the linkage area. (The linkage area may contain several attribute linkages.)

Added the ability to detect Siamese attribute linkages. A Siamese attribute linkage is alinkage that, accord to its Words-To-Follow (the Words-To-Follow of the linkage, NOTthe Words-To-Follow of element it is attached to), shares design file space with the nextelement. In addition to detecting this condition, FileFixer can automatically delete thelinkage area of elements containing such linkages (without harming the graphic part ofthe element).

Added the ability to detect attribute linkages with sizes that are not a multiple of 4.FileFixer now has the ability to automatically delete the linkage area of elementscontaining such linkages (without harming the graphic part of the element).

Added the ability to detect shared cell instances with missing shared cell definitions.

4.4a — 5 March 1992Fixed an anomaly that made it difficult to enter the maximum number of errors to searchfor under CLIX.

Added extensive error checking of font libraries so FileFixer won’t crash when readingin a corrupt font library.

Page 164 FileFixer

Added the ability to detect type 6 shapes whose first and last vertex don’t match.

Previously, if the user improperly installed FileFixer he could accidentally attempt to runFileFixer with the wrong version of FIXER.INI. This sometimes caused considerableconfusion. FileFixer now detects when it is being run with the wrong version ofFIXER.INI.

We also now make sure that the version of FIXER.PAR matches the current FileFixerexecutable.

Added the ability to detect a cell nested within a cell of the same name.

Negative element numbers used to occasionally flash in the “Element number” fieldwhile FileFixer was running. This no longer occurs.

In previous versions of FileFixer there were always a few types of errors whose messagescouldn’t be turned off. Now the only errors that cannot be turned off are fatal errors.

The REMOVE TYPE 66 option will no longer remove type 66, level 5 reference fileattachment elements.

The REMOVE ILLEGAL ELEMENT TYPES option will now automatically delete type1 cell headers found in design files and type 9s, 8s and 10s found in cell libraries.

FileFixer’s ability to correct the range of complex element headers that contain othercomplex element headers has been improved.

GRAFIC and CANODE are now corrected when GRAFIC is 0.

The size of unwanted elements are reported when they are deleted from a file.

When an element that is a component of a complex element is deleted, either the Words-In-Description and Number-Of-Components of its parent or parents is adjusted so that nonew Words-In-Description or Number-Of-Component errors are created; or status isdropped on the complex element.

Manual repair options weren’t being saved by the save options command. This is nowfixed.

If we are not sure whether the file is 2D or 3D and the user doesn’t tell us, no fixes aremade to the file. This prevents creating a damaged file when the dimension of the file issuspect.

In Automatic Design File Repair mode, step 3 is skipped if no errors were detected on theprevious step.

Added the ability to detect and repair cell class map errors.

We now drop status on complex elements that contain element types they should not. Anexample of such would be a line (type 3) in a text node (type 7).

When a deleted element is found inside of a complex element the user now has a choice:he can have FileFixer drop status on the complex element or he can have FileFixer“squeeze out” the deleted element by removing it from the file and adjusting the Words-In-Description and Number-Of-Components of the parent complex header elements.

Added the ability to detect a graphic element whose complex bit and A-Bit (Attribute Bit)are both turned on.

Added the ability to automatically remove type 1 cell headers from design files.

Added the ability to automatically remove type 9, 8 and 10 elements from cell libraries.


Added the ability to automatically remove text elements with 0 characters.

Added the ability to automatically remove elements with Words-To-Follow greater than65533.

Added the ability to automatically remove Siamese elements from a design file. (ASiamese element is an element that shares words in a design file with another element.

Added the ability to automatically remove 3D only elements (like surfaces, solids andcones) from a design file.

Added the ability to automatically remove elements with too many vertices (like linestrings and shapes with more than 101 vertices.

Added the ability to automatically remove elements that contain illegal floating pointvalues.

Added the ability to automatically remove any element for which FileFixer reports aproblem.

Added the ability to detect and delete complex element headers with zero components.

The user can now display the report file without exiting FileFixer with a singlekeystroke.

Added the ability to repair errors in the Number-Of-Components word of the complexheader elements that have such words.

Added the ability to automatically move elements off unacceptable levels (level 0 andother levels selected by the user) onto the level of the user’s choice.

We now make sure that the components of b-spline curves and b-spline surfaces are inthe right sequence.

IGDS sets the range of a type 21 to the union of the range of its poles. MicroStation setsthe range of a type 21 to the range of its b-spline curve or surface header. FileFixer nowprints an error message for the range of a type 21 only if it matches neither its poles norits header.

Added the ability to automatically repair elements whose H-Bits are improperly turnedon.

Added the ability to automatically move component elements to the level of their parentcomplex header elements.

Added the ability to automatically change the color, weight and style of a componentelement to the color, weight and style of the its parent complex header element.

Added the ability to automatically remove the attribute linkage of component elements.(Component elements should never have attribute linkages).

Added the ability to remove all attribute linkages from a design file or cell library.

4.3a — 10 August 1991Added the ability to detect component elements that are on a different level than theirparent complex header.

Page 166 FileFixer

Added the ability to detect component elements that have a different color, weight, orstyle than their parent complex header.

Replaced the -b option (for forcing FileFixer to run in monochrome mode) to -t mono.This was done so that -b could be used to indicate batch mode. Implemented batch mode.

Made it possible for the user to specify what files he wants to analyze (Search forProblems) on the FIXER operating system command line.

The “Special Information” screen, which was omitted in the previous version, has beenrestored.

Added the ability to run FileFixer in batch (background) mode.

Added the ability to specify the design files to be processed on the FIXER command line.

Added the -2 and the -3 options to tell FileFixer to assume that files whose number ofdimensions can’t be figured out should be assumed to be 2D or 3D. This makes itunnecessary for FileFixer to stop in the middle of a long repair job to ask the number ofdimensions of a problem file.

Dramatically improved FileFixer’s ability to recover valid elements after a 997 (Fatalerror. “File ended before element did.” error.

FileFixer now handles fonts with a vector size of WORD correctly — the same wayMicroStation 4.0 does.

FileFixer now has an option to handle design files with elements on levels above level63.

Gave FileFixer the ability to run through all three repairs steps AUTOMATICALLYwithout user intervention!

When we analyze the font library, we now use the character code table instead of thecharacter dimension table to determine which characters are represented in eachparticular font.

Improved the message printed for text range errors to indicate the font of the bad element,whether it is a view independent element, and the first few characters of the text string.

We now handle the range of symbol text fonts correctly.

Various and sundry improvements to text range calculation.

Maximum number of errors in search mode is now be saved with the other usercustomizations.

The REMOVE TYPE 66 option now leaves user elements (type 66, level 20) elementsintact (not deleted).

FileFixer for UNIX platform no longer leaves VT100 compatible keyboards inapplication mode when it exits.

The code on several operating systems was adjusted so as to handle elements that endvery near the End-Of-File (not the End-Of-Design marker) much better.

4.2o — 22 June 1991Shared cells (type 34s) were generating error number 86 errors. Fixed.


4.2n — 26 May 1991Some errors causing ranges to be calculated incorrectly once in a while have been fixed.

702 errors (phantom elements) were occasionally reported for non-graphic elements. Thisno longer occurs.

Some improvements to the algorithm for repairing Words-In-Description.

FileFixer appears to no longer crashes when executed after MicroStation 4.0.

4.2m — 21 April 1991A problem in one of the third party libraries we use caused FileFixer to crash sometimeswhen run after Windows or MicroStation. A work-around for this has been found andimplemented.

4.2l — 29 March 1991Added the ability to automatically update GRAFIC and CANODE.

Miscellaneous code clean-ups found needed during the port to UNIX.

Graphic group number of a deleted complex header element exceeding GRAFIC (beingfound to be quite common) is now treated as a POSSIBLE Words-To-Follow dangerrather than a DEFINITE Words-To-Follow danger.

An anomaly (found by Dick Simkins of Washington DOT) that caused FileFixer toattempt to adjust the range of elements with Words-To-Follow problems has beencorrected.

In some cases an element with an incorrectly turned off A-Bit was reported as a 3Delement found in a 2D file. This has been corrected.

Added a number of minor “tweaks” and improvements.

Fixed error number 101 (deleted by 9, 8, or 10 detected) was not being reported.

A reference file attachment with too many vertices is now reported as a “too manyvertices” error rather than a Words-To-Follow error.

Illegal and deleted components of complex elements are now detected as documented.

4.2k — 26 March 1991Added the ability to detect the A-Bit being turned on when there is no attribute linkage.

The Replace Type 9 command of FileFixer4 has been graced with the ability to replacethe type 9 of design files containing elements with severely damaged Words-To-Follows.Unfortunately the algorithm which enables such robustness would sometimes omitpartially corrupt elements from the output design file. Some user have requested theability to retain such elements in the output design file. This ability has now been added

Page 168 FileFixer

to FileFixer. By default, emergency scanning mode (the mode that enables FileFixer torepair design files with Words-To-Follow errors) is turned off in the Replace Type 9command; all elements in the design file (including partially corrupt elements) are copiedto the output file, but the replacement of type 9 elements in files with “EOF not found”errors is not possible. The user can enable emergency mode scanning in the Replace Type9 command using an option on the Replace Type 9 screen. When this option is enabled,FileFixer can replace the type 9 of design files with severe Words-To-Follow errors(albeit with the possibility of leaving semi-corrupt elements out of the repaired designfile).

4.2j — 21 March 1991Replaced QuickC compiler with MicroSoft C5 compiler. Remaining user interfaceproblems now appear handled.

<CONTROL X> now works as advertised, exiting the program in most situations

The error “Could not rename file” was being generated when the user attempted to repaira design file that was not stored on his current default disk. This has now been fixed sothat the user can repair files that are not on his current default disk.

An error that sometimes caused the error number 89 (indicating a programming error) hasbeen corrected.

4.2i — 7 March 1991Fixed bug that caused the interactive selection of design files to be process to be less userfriendly than in previous version.

4.2h — 5 February 1991Fixed a problem in the Replace Type 9 command.

4.2g — 28 January 1991Due to a MicroSoft compiler error, the Replace Type 9 command sometimes left desiredelements out of the fixed file. Parts of FileFixer have been recompiled with reducedoptimization to handle this problem.

The range of elements containing disconnects (special “pen-up” commands) is nowhandled correctly.


4.2f — 15 January 1991The report files generated by previous versions sometimes reported “Error writing tooutput file” when, in fact, no such error had occurred. This is now corrected.

4.2e — 1 January 1991Graphic group and text node number tests are now automatically turned off whilechecking cell libraries.

4.2d — 15 December 1990Some Words-To-Follow warnings were being reported as Words-To-Follow errors. Thiscaused “emergency scanning mode” to be invoked in cases when it was not trulynecessary. This is now fixed.

4.2c — 13 December 1990Spurious “Index-To-Attributes is too small” errors were being generated for type 12s andtype 14s in 3D design files. This is now fixed.

4.2b — 24 November 1990Several errors related to the RECOVER ELEMENTS AFTER EOD option have beenfixed.

The repair menu now lists the step number of each type of repair.

It is now possible to repair files with the an extension of .fix.

The demo now reports ALL errors for design files smaller than 200 blocks. Previously,only about half of such errors were reported. The demo still reports only half of the errorsin design files larger than 200 blocks.

4.2a — 20 October 1990The report generated by FileFixer when fixing the Words-In-Description of b-splineheader elements was incorrect even though the element was properly fixed. This has beencorrected.

Added the ability to detect a graphically grouped element which is in danger of becomingcross-linked with another graphic group.

The user has been given greater control over which element types should be consideredvalid or invalid.

Page 170 FileFixer

The shared cell definition element (type 34) was added to the list of complex headerelements. Complex bit errors and Words-In-Description errors involving this elementtype can now be corrected.

Added the ability to detect GRAFIC (next graphic group number) being set to 0.

Added the ability to detect a text node which is in danger of becoming cross-linked with atext node having the same text node number.

Added the ability to detect complex header elements whose Number-Of-Componentword exceeds 3641.

Added the ability to detect locked elements.

Added the ability to detect the imminent exhaustion of graphic group numbers.

Improved FileFixer’s ability to differentiate between an element whose Words-To-Follow is different than expected and an element whose Words-To-Follow is truly likelyto cause an “End-of-File Not Found” or “Design File I/O” error. FileFixer’s Words-To-Follow repair algorithm has been enhanced so as to make it much less likely for slightlycorrupt elements to be omitted from the repaired design file. The algorithm now makesheavy use of recursion. That is, the odds of a particular design file offset being the start ofa valid element chain is tempered by the odds of the starting point of next potentialelement being a valid element which is tempered by the odds of the potential elementafter that being a valid element chain, and so on.

Previously, the same algorithm was used for determining when an error message shouldbe reported for an element and for determining when to go into “emergency scanningmode”, looking for the start of the next valid element without using the Words-To-Followof the previous element. Now, two completely different algorithms are used for each ofthese tasks. In other words, in past versions of FileFixer the term “corrupt element” wasused ambiguously. We now differentiate between two different types of “corruption”.One type of corruption indicates that there is something wrong with the element that weshould tell the user about. The other type of corruption indicates that the Words-To-Follow of the element should not be trusted. It is possible for an element to have one typeof corruption, but not the other. By having two totally different algorithms to detect eachof these types of corruption, we have been able to make FileFixer’s concept of what“elements” should be left out of repaired design files align more closely with the ideas ofan expert system manager. The result is that FileFixer is much less likely, whenautomatically repairing Words-To-Follow error, to remove elements that the average useror system manager would want to keep, while still managing to omit nearly all elementssuch an individual would want to get rid of.

Added the ability to detect elements with illegal classes.

Added the ability to detect elements with illegal reserved nibbles. The reserved nibble ofan element is composed of bits 4:7 of the properties word.

The fact that an error message refers to a deleted element is now indicated in the reportfile.

Added the ability to detect the imminent exhaustion of text node numbers.

Added the ability to detect Siamese elements. Siamese elements are two elements sharingthe same space in a design file.

Added the ability to detect elements with a suspiciously large quantity of attribute linkagespace.


Changed the way Words-To-Follow errors are repaired such that most of the advantagesof the BackScanning option and almost none of the disadvantages are built into thestandard Words-To-Follow repair algorithm. The BackScanning option is retainedbecause there are still some (rare) situations where it can recover more lost elements thanotherwise possible.

Added the ability to detect the presence of attribute linkages even when the A-Bit is off.

Deleted elements (even deleted complex headers) are now scrutinized much morecarefully for indicators that their Words-To-Follow may be unreliable.

The FileFixer scanning software has been made even more robust. The scanner can nowefficiently read in the entire element even if the Words-To-Follow of the element iswrong.

User interface improvement. The scrolling fields used on the Automatic Design FileRepair menu and the EXPERT ONLY menu now work more smoothly when the userchanges the last visible entry.

4.1a — 4 October 1990Added the ability to spot curves (type 11s) and conics (type 13s) in connected strings andcomplex shapes. This can crash at least one (old) version of MicroStation.

On the Automatic Design File Repair menu selecting RECOVER ELEMENTS AFTEREOD should always force on the repair option that fixes Words-To-Follow errors. Thiswas not working properly, but is now fixed.

The range of view independent type 1 cells was being calculated incorrectly. This is nowfixed.

When a change is made to Words-In-Description, if the complex header being modifiedalso contains a Number-Of-Components word, Number-Of-Components is automaticallyverified and, if necessary, updated.

The user now has the option of omitting type 66 elements from repaired design files. Thiswas possible previously, but is much easier, now.

The user now has the option of removing elements with too few vertices (such as linestrings with only one vertex) from repaired design files.

Previously, any range error was classified as a 700 level error. Now only severe errors areso classified. Lesser range errors are classified as 300 level errors.

Added the ability to detect text elements with zero characters.

Added the ability to detect text elements with more Enter-Data-Fields than characters.

4.0c — 29 September 1990Added the ability to automatically repair Words-In-Description errors.

Page 172 FileFixer

If Words-In-Description for an element was enormous (greater than 65,516) and thatelement also had a Words-In-Description error, that error was not reported. This is nowfixed.

The ability to save user preferences between uses of FileFixer now works correctly.

The presence of associative dimensioning elements (type 33), multi-line elements (type36), and shared cell elements (types 34 and 35) no longer trigger a warning message.

4.0b — 17 August 1990The ideal range of point cells and view independent text elements is now calculatedcorrectly.

Nesting errors and other errors are no longer reported for deleted complex headerelements.

Complex bit errors are no longer reported for components of deleted complex headerelements.

4.0a — 1 June 1990Added the ability to detect elements such as line strings and curves with too few vertices.The current version of MicroStation permits the creation of such elements when itshouldn’t.

Reorganized the options menus.

Range verification of text elements is now performed precisely taking into account thefont library and the size of each individual character in the text element.

FileFixer now has the ability to automatically repair element incorrect element ranges!

Trivial element range errors (less than 1 UOR) are not reported unless the user explicitlysets the element range tolerance to less than 1%.

Added the ability to detect text nodes containing non-text elements.

Added the ability to detect connected strings and complex shapes containing non-linearelements.

Added the ability to detect cells containing element types not legal for a cell.

Added the ability to detect surfaces and capped surfaces (solids) containing elements notallowed in such elements.

Added the ability to detect b-spline curves and surfaces containing elements other thanpoles, knots, weight elements, and boundaries.

Demo will now repair files up to 200 blocks (102,400 bytes) in size.

Under DOS and UNIX repaired design files (.fix files) are now always rounded up to thenearest block (512 byte) boundary. This facilitates their transmission with FMU,KERMIT, and possibly other file transmission methods.


Added the ability to detect files that are not a multiple of 512 bytes (1 block) in size.Such files may be difficult or impossible to transmit using FMU, KERMIT, and other filetransfer utilities.

Added the ability to detect Words-To-Follow errors in reference file attachments.

Added the ability to detect too few clipping vertices in a reference file attachment.

Added the ability to detect too many clipping vertices in a reference file attachment.

The Replace Type 9 command now protects the donor file by ensuring that the name ofthe donor file and the name of the output .fix file are not the same.

An error that caused some types of Index-To-Attribute errors not to be reported has beenfixed.

Previously, the Adjust Element Range option would not adjust elements which had a highrange lower than a low range. This has now been corrected.

The properties bit for type 1 cells was being retrieved from the wrong location in theelement yielding many spurious H-Bit errors. This has now been corrected.

Made the handling of insufficient disk space errors more graceful.

3.4n — 10 December 1990Recompiled to work with newer version of CLIX.

3.4m — 27 May 1990UNIX version now works on C300 Clipper based Intergraph workstations.

3.4l — 21 April 1990Repaired files under UNIX now have an extension of .fix instead of .fix. This change wasmade because some versions of MicroStation cannot display a file with upper casecharacters in its name.

An error that caused many 3D type 11s and 13s to be reported as having an invalid rangehas been corrected.

The degree (represented as a percentage) by which an element range is incorrect is nowincluded with each range error.

Elements that are very near the edge of the design file can cause plotting problems. Theseare now detected.

3.4j — 29 March 1990Added detection of illegal arc and ellipse origins and axes.

Page 174 FileFixer

3.4i — 18 March 1990An error that caused deleted type 127 elements to generate an “Unwanted End-Of-Designmarker detected” message has been fixed.

3.4h — 3 March 1990Modified the VMS scanning software so that a corrupt element will not return a nextelement pointer that is beyond the last block of the design file. Although this was not acritical problem under MS-DOS and UNIX, these versions were also modified so that allversions of FileFixer produce consistent results.

Increased the text element range tolerance differential from 40% to 80%.

Default element range tolerance increased to 20%.

Made it possible to use the RECOVER ELEMENTS PAST END-OF-DESIGNMARKER option at the same time as the BackScanning option. This will help FileFixerrecover elements from severely damaged design files.

3.4g — 20 January 1990Ported to VMS.

3.4f — 18 January 1990Licensing code added to UNIX version.

3.4e — 4 January 1990The Search for Problems command has been speeded up by about 30%.

Ported to UNIX.

3.4d — 23 December 1989Modified FileFixer so that the RECOVER ELEMENTS AFTER END-OF-DESIGNMARKER command can recover elements after more than one End-Of-Design marker.Now, up to 1000 End-Of-Design markers can be skipped.

3.4c — 14 December 1989Added code to enable customers to lease FileFixer.


3.4b — 13 December 1989Fixed a problem that caused by differences between the 80287 and 80387 mathcoprocessors. The program will now run correctly on machines equipped with anycoprocessor chip.

Added call to interrupt hex 10, function hex 10, subfunction 3 to fix a cosmetic problemcaused by the failure of XTreePro Gold to properly reset the video mode.

3.4a — 5 December 1989Added type 28 (b-spline weight factor) element range verification.

Added type 25 (b-spline surface boundary) and type 26 (b-spline knot) element rangeverification.

Added type 3 (line), 4 (line string), 6 (shape), 11 (curve), 13 (conic), 21 (b-spline pole),and 22 (point string) element range verification.

The user can now control how much the range of an element must be off by before anelement range error is generated.

Reorganized the user interface so that features requiring an understanding ofIGDS/MicroStation file structure are hidden from the user on “Expert” screens.

Information about the parent header element is now reported when complex bits areincorrectly turned off.

Added element type 15 (ellipse) and type 16 (arc) element range verification.

Added the ability to detect certain kinds (NANs and VAX reserved floating point) ofillegal (crash causing) floating point values in right circular truncated cones, arcs, andellipses.

Added element type 23 (right circular truncated cone) element range verification.

Added element type 17 (text) element range verification. Range verification is nowperformed on all IGDS element types.

This version was released to Intergraph Certification and Support only.

3.3a — 5 November 1989Extensive internal reorganization to permit new enhancements to be added rapidly andeasily.

Pressing the abort key stops processing immediately now, instead of after the currentdesign file is finished.

Added extensive documentation on every possible error condition that can be detected byFileFixer.

Each error has been assigned a severity code. The user can now select which errors willbe reported on by severity.

Added the ability to detect illegally set H-Bits.

Page 176 FileFixer

Added the ability to add a type 9 element to a design file whose type 9 has been deletedor destroyed.

The user is now warned if he attempts to replace a 2D type 9 header with a 3D type 9header or vice versa.

3.2a — 30 October 1989The cursor is always moved to the first position of each field when moving about on thedata entry screens.

The user can now control which element types should be considered valid.

The user can now control which levels should be considered valid.

When an error involves a cell, the cell name is now reported.

Added the ability to recover elements after the End-Of-Design marker.

Demo licensing software improved.

Description of individual types of corruption added to documentation.

An error that caused complex bit and other errors to be reported for deleted complexelement headers have been eliminated.

Added the Filter Factor feature to enable the user to control how picky FileFixer is aboutaccepting a design file block/byte location as the start of a valid element chain whentrying to recover from a Words-To-Follow error.

Added the BackScanning option to recover elements, which appear, due to certain kindsof undetectable Words-To-Follow errors, to be part of an earlier element.

3.1a — 14 October 1989Added the ability to detect, report, and automatically repair cell level mask errors.

Added the ability to detect missing vital elements (like types 8, 9, and 10).

When replacing type 9 and other elements we now guarantee that the first three elementsof a design file are types 9, 8, and 10 even if this was not so when we started. An errormessage is generated if this is not possible. We can also now copy in type 8 and 10elements even when the original design file did not have such elements.

3.0a — 5 October 1989Initial release re-written by David Greenbaum.

Micro Station File Fixer

Documents

fence manipulation

current resource

fully automatic

recipient

cell library

style dialog

weird design

cell level