I wish I didn't have so much experience in this area, because these situations
are never happy times, and it is almost always true that a little bit of
planning and foresight could have prevented it. I would much rather you
hired me before disaster strikes so that we can put in place the things that
will prevent or at least minimize the down-time.
But if it's too late for that, I can help to get you back up and running.
My years of experience can minimize losses and contribute toward
a speedy recovery.
Experience can make the difference. Having done this sort of work
since 1978, I've encountered just about every situation that you
could imagine, and have learned a lot about avoiding and/or compensating
for problems that arise.
This is particularly true with regard to the older versions (Xenix,
pre-R5 Unix). Having programmed and maintained these systems when
they were state of the art, I am intimately familiar with issues
that affect upgrades or re-installations.
But any upgrade can present challenges that are best
handled by experienced people. When your entire computer system
is at stake, you don't want neophytes working on it. You want
experience and knowledge.
Small jobs are difficult to get the large firms to even look
at. They usually want weeks or even months worth of work. I
can do the small jobs, whether it's a small change to an
existing program, a filter, a little utility you need but can't
find, or whatever.
Administrative scripting to eliminate repetitive tasks
I think there is little question that Filepro was the most
popular database on Sco Xenix and Unix systems for many years.
I got involved with a beta version of it on Tandy Xenix in
1983, and wrote a number of custom packages using it over
the years. So did just about everyone else who was programming
on Xenix or Unix. It surprises me how many of those early efforts
are still being used.
The Filepro database itself has improved over the years, and
still exists (though it is no longer owned by the Small Computer
Company). Of particular interest to those who have older
databases is the fact that Filepro has made provisions to
handle Year 2000 problems. This means that existing Filepro code can be
brought into the next century. Accomplishing this does involve
some analysis and possible reworking of code, but it is
far less expensive and traumatic than starting over from scratch.