FileFixer conquers the expanding universe of MicroStation design file corruption.

By on

  • Keep your projects on schedule. (Time travel not necessary.)

    Clearwater, Florida, USA — Any long-time MicroStation veteran has encountered their share of corrupted V7 design files. As you migrate to MicroStation V8, get ready to teleport into the expanding universe of V8 file corruption — complete with previously unseen alien categories of V8 file corruption.

    Ah, the simple life – V7 elements are stored nose-to-tail in each V7 design file. Not so under V8 – FileFixer has its work cut out!

    Why is it V8 elements fall off the edge of the design plane? How is it possible a V8 element’s level could disappear? Why can’t we make that model active? Why can’t MicroStation open that V8 file?

    No one encountered these extraterrestrial manifestations of design file corruption prior to MicroStation V8. But sure enough, when MicroStation users move to V8, they routinely report to Axiom entirely new species of V8 file corruption never witnessed in V7 files.

    Welcome to the expanding universe of V8 design file corruption.

    There are two distinct versions of FileFixer. FileFixer for V7 specializes in analysis and repair of V7 design files. FileFixer for V8 specializes in analysis and repair of V8 design files.

    It wouldn’t be accurate to say that FileFixer for V8 is “FileFixer for V7 adapted for V8″. FileFixer for V8 was re-created from the ground up to specialize in the entirely new V8 file format. FileFixer for V8’s user interface is similar to the V7 version to ease user transition to V8. But under the hood, the two applications are quite different.

    FileFixer for V8’s capabilities have evolved to handle the expanding universe of V8 file corruption — greatly exceeding the scope of FileFixer for V7.

    Internally, V7 design files contain a series of lines, circles, shapes, text and other graphical and non-graphical data — all arranged nose to tail. Like a stack of pancakes.

    V8 files are entirely different. Internally, each V8 file consists of numerous subfolders and subfiles.

    And on top of that, all V8 elements are subjected to additional alien technology. The lines, circles, text (and other graphical and non-graphical elements) in V8 design files are compressed (much like ZIP files).
    Because V8 elements are nestled in subfolders and subfiles and are compressed, the scope of potential V8 file corruption is three times more extensive than V7.
    Here’s why:

    • V8 subfolders and subfiles can be corrupted. MicroStation can’t access your graphical elements if the file’s subfolders or subfiles are damaged. This is an entirely new category of corruption found only in MicroStation V8 files.
    • Compressed portions of a V8 file can be corrupted. MicroStation can’t access your elements if they can’t be decompressed. This is an entirely new category of corruption found only in MicroStation V8 files.
    • The original V7 “universe” of file corruption remains at the core of V8 file corruption. The entirety of the V7 corruption universe is now only one-third of the V8 corruption universe.

    V8 design files contain a tree of subfolders and subfiles (increasing the complexity of the internal storage and the number of ways things can go wrong).

    Fortunately, Axiom’s been busy and FileFixer for V8 has conquered the universe of corruption.

    FileFixer for V7 enhancements continue concurrently as well. The FileFixer developers work like genius hummingbirds to keep up with the influx of customer-submitted corrupt V7 and V8 design files.

    MicroStation/J and V7 design files are alive and well.
    Brace yourself for some “tough love”. What you don’t know about V7 design file corruption can hurt you (and delay projects and reduce profits).

    Remember the familiar MicroStation/J error dialog “End of file missing, attempt repair?”

    You’ll never see MicroStation V8 display that error dialog for a V7 file (even if the end of file is missing). If you attempt to upgrade a V7 file with that type of corruption to V8, MicroStation V8 will truncate the file without warning and without your permission. No error is reported. The V7 to V8 upgrade appears successful (no error messages), but the majority of your file might be missing! This is arguably the most treacherous step in transitions to V8 — one or many design file assets might be truncated without warning. MicroStation users need to be aware of this!

    Have you seen this legendary error message lately? If not, keep reading!

    Fortunately, Axiom provides the optimum solution. Analyze your V7 files with FileFixer for V7 before migrating them to V8. Let FileFixer for V7 identify which files must be repaired before attempting to upgrade them to V8. This is the best guarantee your V7 files will reach V8 healthy and whole.

    After successfully upgrading your V7 project files to V8 (thanks to FileFixer for V7), FileFixer for V8 takes over — keeping the expanding universe of file corruption under your control.

    See for Yourself...
    Get FREE Trial Versions
    * Select one or more of the following:

    Enter "AutoCAD" before submitting.