User’s Guide – FileFixer for V8
Chapter 7 — General Settings
The General Settings Dialog Box
“General Settings” dialog box.
Alternate temporary files directory
FileFixer creates a number of temporary files while it is repairing a design file or cell library.
FileFixer determines the location for these temporary files in the following manner:
Use the directory specified in the “Alternate temporary files directory” on the General Settings dialog box.
If no directory is specified in the “Alternate temporary files directory” field then use the directory specified by the Windows “TEMP” environment variable.
If the “TEMP” environment variable isn’t specified then use the directory specified by the Windows “TMP” environment variable.
If the “TMP” environment variable isn’t specified then put them in the directory containing the design file or cell library being processed.
Skip checking the file if the first element is not a valid element.
If the first element in a design file is not a design file header then skip processing this file. This option can be used to skip files that are not V8 design files or cell libraries.
Initialize “Which Files” field on startup with:
Use these settings to specify how the “Which Files” field is initialized when FileFixer is started.
Use the “Currently loaded design file” setting when you want FileFixer to be initialized with the design file currently loaded in MicroStation.
Use the “File name that was in the field when last terminated” setting when you want FileFixer to remember the name of the file you were working with when you last quit FileFixer.
Note: When you have a demonstration license, FileFixer always initializes the “Which files” field with the sample files in ...\Axiom\Fixer\v8\sample\.
You can process any V8 design file or cell library with a demonstration license.
When repairing a design file or cell library
“When repairing a design file or cell library:” settings.
Backup/repaired file name
FileFixer offers the option to work on the original design file (after first backing up the design file) or to work on a copy of the original design file (leaving the original unchanged). With either option you have the ability to specify the final extension and directory where the backup file or repaired file will be placed.
Demo Users Note: We do not recommend selecting “Work on original” when you have a demonstration license. If your file is greater than 100KB, a backup will be created, but a repaired file will not be created to replace the original file.
The backup file extension is limited to three characters on all platforms.
The “?” character provides some flexibility when naming backup file names. In this context it is not a traditional wildcard character.
One or more question marks “?” can be used to create a numerical extension which automatically increments.
You can use up to three question marks in the extension “???”, which supports up to 999 backup files. If you attempt to make the 1000th backup, FileFixer will notify you that no more backup file extensions are available (until you select a different extension, different output directory or delete the previous backups).
The question marks must be at the end of the extension. This means that the extension “b?k” is not recognized.
Examples:
Original file name | Backup or repaired | Backup or repaired |
filename expression | filename created | |
Axiom.ff1 | bk? | Axiom.bk1 |
Axiom.ff2 | Axiom.bk2 | |
... | ... | |
Axiom.ff9 | Axiom.bk9 | |
Axiom.f01 | b?? | Axiom.b01 |
Axiom.f02 | Axiom.b02 | |
... | ... | |
Axiom.f99 | Axiom.b99 | |
Axiom.dgn | ??? | Repeated FileFixer |
processing of the same | ||
file creates: | ||
Axiom.001 | ||
Axiom.002 | ||
Axiom.003 | ||
Use the original file’s extension for the repaired file.
Select this option if you want your repaired file to retain the extension of the original file. Of course, FileFixer requires you to specify a different output directory for the repaired file (so your original is always retained).
Add on the repair file extension instead of replacing it.
Using this repair setting the repair file extension will be added onto the end of the design file or cell library file name instead of replacing the extension. For example, when creating a fix file, the repaired file extension “.fix” will be added onto the end of the design file “axiom.dgn” making the fixed file name “axiom.dgn.fix”.
Set modification date and time of fixed file to that of the original file.
Use this setting when you want the date and time stamp of the fixed file to be the same as the design file or cell library being repaired. Normally, the date and time of the fixed file will be the date and time the file was repaired.
When you are working on the original design file and creating a backup file the backup file will always maintain the date and time stamp of the original file. Only the original file’s date and time stamp will be optionally kept or set to the current date and time.
Search for Problems Mode
“Search for Problems Mode” settings.
Skip checking the file if there is a seal-of-approval.
If the seal-of-approval is found and there are no error numbers greater than 199 in it then FileFixer will not process this design file.
Write seal-of-approval information to the design file.
FileFixer has the ability to add the seal-of-approval information to your design file when running in “Search for Problems” mode. The seal-of-approval information contains the error numbers found, date and time when FileFixer analyzed the file and the level of error reporting that was done (e.g. “Fatal error only”, “Errors and fatal errors”, etc.).
If you elect to de-select this setting, you can also direct FileFixer to retain or delete any pre-existing seal-of-approval:
Don’t delete the seal-of-approval if it exists.
Note: If the design file’s date is newer than the date saved in the seal-of-approval then the message "WARNING: File modification date exceeds certification date" is output to the report file.
Note: The seal-of-approval is stored in a type 66 element saved in the non-model section of a V8 design file or cell library.