|
New version of FileFixer for V8
handles newfound, V8-specific design file problems.
« Back
CLEARWATER, FLORIDA, USA —
As robust MicroStation V8 becomes the standard for more and
more MicroStation shops each day, users are encountering different
problems that they did not encounter in previous versions.
 |
| Why are your V8 design files behaving oddly? Why can't
you select certain models? FileFixer for V8 is
the solution to problematic files in MicroStation V8. |
Each MicroStation V8 file consists of multiple internal directories
and sub-files. This data organization scheme, also used by
Microsoft Word and Excel, is called "structured storage".
Structured storage errors are one of the most serious, recurring
V8-specific corruption problems occurring in production. This
is a new phenomenon with MicroStation V8 files; hence, drafters
and designers using V8 in production might have encountered
structured storage errors without realizing it.
Structured storage damage manifests itself in different ways.
The most obvious symptom is MicroStation V8's inability to
open a file. If you've ever encountered an "Unable to
open design file" message, corruption in the structured
storage system is one likely culprit. The latest release of
FileFixer for V8 automatically detects and repairs
structured storage damage.
Additional FileFixer for V8
enhancements
In response to customer demand, FileFixer for V8 now
detects and handles the most serious structured storage problems.
"We have been working with customer V8 files since 2001,
and along the way we discovered various V8-file troublemaking
trends," stated Steve Palmer, FileFixer's Executive
Product Manager. "This latest FileFixer release
addresses additional problems we've been finding in customer
V8 files."
Some additional enhancements in the latest release of FileFixer
for V8 are:
-
A more solid and comprehensive
repair algorithm for elements on undefined levels (for
example, an element indicates it resides on a level for
which no level definition exists). FileFixer's improved
algorithm resulted from analysis of many customer files
with damaged level tables. Symptoms of bad level definitions
include elements that are excluded from level manipulations
and elements that remain displayed when levels are turned
off.
-
Increased capacity for error
tracking from 65,535 to 4,294,967,296 for each type of
error. Capacity was increased to accommodate the quantity
of errors being found analyzing large batches of customer
V8 files.
Don't let these problems impact
your projects.
If you are encountering these or any problems with V7 or V8
design file, contact an Axiom MicroStation Consultant today!
Ask about FileFixer
for J and FileFixer
for V8. Don't let damaged design files halt your production.
Call 727-442-7774 extension 9033, e-mail 9033@axiomint.com
or click here for more info.
« Back
|
