> Is there anyone that uses Axiom's File Fixer on a regular basis? If so,
> what version do you use? Would you recommend it to other companies? What
> do you like and dislike about the software?
>
> All comments are appreciated.
>
> --------------------------------------------------------------------------
> Daryl Cammack
> 409 E. Monument Ave.
> Dayton, OH 45402
>
> 513-461-5660
>
> daryl....@woolpert.com
Daryl:
We have used FileFixer regularly since 1993 and it has saved us many,
many times. We originally bought it because we had over 200 mapping
files that had to be run through Projection Manager to convert from
one coordinate system to another. Projection Manager would process
until it met a corrupt element in a file, then stop. I fixed a few
using EDG but there were so many Words-to-Follow and
Word-in-Description errors that it would have taken me weeks to fix
them all. We decided to try FileFixer for DOS (single-user license)
and it worked as advertised. It located file corruptions and corrected
them.
Since we are networked, having a single-user license hasn't been a
problem. Other users can wander over to the PC that FF is installed on
and run their files through, though it runs much slower on a network
drive than on a local drive. We have used versions 4.x (a DOS
executable program) through the current MDL-based version 6.0. All
versions have run well, though I'm not sure I like the MDL version. It
seems to run slower and you have to start MicroStation first. But it
cleans up files like the older versions and it's still much better
than trying to use EDG.
Dislikes: not cheap, no on-line help, tech support is so-so (don't
expect a call back the same day).
--
"I'm trying to think but nothing happens!" - Curly
<snip>
>Dislikes: not cheap, no on-line help, tech support is so-so (don't
>expect a call back the same day).
>--
>"I'm trying to think but nothing happens!" - Curly
>
I'd agree with everything what "Curly"... er, Kurtis says here. I did
not appreciate the move to to an MDL as we now have to tie up a
MicroStation license in order to use the product - but it works. We've
used it since the 80s and have saved countless $$$$. Ditto on the
dislikes as well. BTW, there are versions for CLIX, NT and DOS - maybe
more.
One thing to be aware of is the affect that Filefixer has on files
containing db stuff: our PDS files get exceptionally "cleaned" of all
that annoying information... although there may be some deep deep cfg'g
I missed to turn that off.
.. rew
Sounds like interesting product.
How much does it cost?
Who sells it?
Has they got WWW address?
--
Juhani Inkilainen
Projekti-insinoorit Oy tel. 358 0 5309 789
Myyrmaenraitti 2 fax 358 0 563 2003
PL 31
01600 VANTAA FINLAND
EMAIL juhani.i...@pop.pipic.fi
>> >> Is there anyone that uses Axiom's File Fixer on a regular basis?
>
>
>Sounds like interesting product.
>
>How much does it cost?
>Who sells it?
>Has they got WWW address?
>
>--
> Juhani Inkilainen
>
There is a war going on between Axiom International in Florida who says Axiom
Software in San Francisco is no longer allowed to sell their product. This is not
made any easier by the MicroStation Manager continuing to carry both ads.
A/International says A/Software is only selling older versions that they still have
access to and there's no upgrade path. Who knows...
I am asking Axiom Software to address this in the newsgroup now.
Axiom Int. has a free demo: call (USA) 813-442-7774, ext 6306 - according to the
last MM magazine I have.
Axiom Software - (USA) 415-753-8591 and email axi...@crl.com
.. rew
I got my copy of FileFixer from Florida after having been referred to Florida
by San Francisco. I'm not quite sure what the cost was, but it is a usefull
product well worth the investment.
Michael Boadway
H.G. Engineering
File Fixer is a good program. We use it often...
There is a new version, give them a call in Florida
NT version is out, have not tried it yet... Getting ready to
order it soon..
--
+ Daniel Sirk - Architectural Designer +
+ Gilberti Spittler International +
+ http://www.gsiarch.com +
Joe Raymundo
Raymundo Engineering
Joe: You can customize a color table and attach it to designs by using
the ATTACH COLORTABLE <table> or CT=<table> key-ins. The on-line
documentation has more information on this. You can even create a
script file that automatically does the attachment when you get into
a design (either using -s<startupFile> on the MicroStation command
line or a simple user command that is pointed to by MS_INIT.) HTH
============== One of "The People Behind MicroStation" ==============
Phil Chouinard - ITO Phone: (610) 458-5000
Bentley Systems Fax: (610) 458-1060
690 Pennsylvania Drive CompuServe: 75300,3376
Exton, PA USA 19341-1136 mailto:Phil.Ch...@Bentley.com
== MicroStation FORUM & Exhibition @ http://www.bentley.com/forum/ ==
>> I'm trying to change older drawings to use a different color table.
>> Is there a way to speed this up? Right now i have to open the DGN
>> and select color table change the background color manually and then
>> attach it. Can i capture this using MBE? How do i get around the
>> dialog box?
>Joe: You can customize a color table and attach it to designs by using
>the ATTACH COLORTABLE <table> or CT=<table> key-ins. The on-line
>documentation has more information on this. You can even create a
>script file that automatically does the attachment when you get into
>a design (either using -s<startupFile> on the MicroStation command
>line or a simple user command that is pointed to by MS_INIT.) HTH
This brings up an interesting point. UCMs are supposed to be dead meat. Yet
the MS_INIT won't let me point to a comparable Basic program, just a user
command. Hmmmmm........ :-)
Mark
[snip]
> This brings up an interesting point. UCMs are supposed to be dead
> meat. Yet the MS_INIT won't let me point to a comparable Basic
> program, just a user command. Hmmmmm........ :-)
Mark: Actually, there were reasons why we decided not to implement
macro initialization via the MS_INIT means. In order to make
certain things consistent with MDL apps, we developed something called
RUNMACRO and deliver the source code to it with MicroStation 95 (it's
an example MDL application.) Here's the README to it...
RUNMACRO
========
This example runs a list of macros at MicroStation startup and/or
at design file open time.
Steps to utilize this example program:
======================================
1) Build RUNMACRO using BMAKE or BMAKEWIN (see the MDL Programmer's
Guide for instructions about BMAKE setup & execution)
2) Set the following in a configuration file or in MicroStation's
configuration variables dialog box.
a) if you want BASIC macros run at MicroStation startup then set:
MS_INITAPPS > runmacro # Load RUNMACRO as a MS_INITAPPS
MS_INITMACROS = macro1.ba # Macros to be run after MicroStation is
# started and before a design file is
# opened
b) if you want BASIC macros run after a DGN is opened then set:
MS_DGNAPPS > runmacro # Load RUNMACRO as a MS_DGNAPPS
MS_DGNMACROS = macro1.ba # Macros to be run after a design file is
MS_DGNMACROS > macro2.bas # opened
Notes:
======
a) MS_MACRO would be used to find the macros.
b) RUNMACRO as a MS_INITAPPS will ignore any command line parameters
sent to MicroStation and open the MicroStation Manager dialog box
after all macros have been completed.
c) RUNMACRO can be run as both a MS_INITAPPS and a MS_DGNAPPS
d) Any number of macros may be included in either the MS_INITMACROS or
MS_DGNMACROS configuration variables. Simply separate the macro names
with a semi-colon when using MicroStation's Configuration Variables
dialog box, or use the ">" sign as shown above in 2b). BASIC macro
names may have no extension, ".BA" extension, or ".BAS" extension.
e) MS_INITMACROS are run before a design file is opened. Therefore
the macro must not access any design file objects or attempt to do
anything which requires an open design file.
f) This example starts the graphics environment using
mdlSystem_enterGraphics, however, this MDL application may be modified
to not start the graphics environment. In this case, the application
must not perform any BASIC function which requires graphics. Opening
a dialog box is an example of a function which requires the graphics
environment.
In article <31ECF0...@Bentley.com> "Phil Chouinard [Bentley]"
>Mark Neuhaus wrote:
>[snip]
>> This brings up an interesting point. UCMs are supposed to be dead
>> meat. Yet the MS_INIT won't let me point to a comparable Basic
>> program, just a user command. Hmmmmm........ :-)
>Mark: Actually, there were reasons why we decided not to implement
>macro initialization via the MS_INIT means. In order to make
>certain things consistent with MDL apps, we developed something called
>RUNMACRO and deliver the source code to it with MicroStation 95 (it's
>an example MDL application.) Here's the README to it...
> RUNMACRO
> ========
>This example runs a list of macros at MicroStation startup and/or
>at design file open time.
Thanks Phil, that looks like the ticket. I've got nothing against user
commands for some jobs, but I always wondered why MS_INIT didn't like BASIC.
I will look into this more.
Mark