Troubleshooters.Com Presents

Troubleshooting Professional Magazine

Volume 5 Issue 9, September 2001
More Corporationally Incorrect Software
Copyright (C) 2001 by Steve Litt. All rights reserved. Materials from guest authors copyrighted by them and licensed for perpetual use to Troubleshooting Professional Magazine. All rights reserved to the copyright holder, except for items specifically marked otherwise (certain free software source code, GNU/GPL, etc.). All material herein provided "As-Is". User assumes all risk and responsibility for any outcome.

[ Troubleshooters.Com | Back Issues ]

We are continually faced by great opportunities brilliantly disguised as insoluble problems -- Lee Iacocca


Editor's Desk

By Steve Litt
For years we Troubleshooters have been alarmed at the intermittence and quirkiness of modern corporationally correct software. In fact, the State of Troubleshooting Addresses from the 1998, 2000 and 2001 Troubleshooting Professional Magazines mentioned this as a problem.

Now Microsoft is giving us allies in our endeavor for more reliable software. Microsoft's new licensing policies are making enemies out of their customers, increasing numbers of whom are now looking for alternatives to corporationally correct software.

In the mid 1980's corporationally incorrect PC's and MS-DOS overthrew the corporationally correct but problematic mainframe technologies of the day. We could be on the verge of another such revolution.

And if it happens, we Troubleshooters will be the beneficiaries as intermittent systems are replaced with solid systems. Things will still break, but the breakage will be less frequent, and we'll be able to use real Troubleshooting Process instead of today's reboot/reapply/reinstall process.

Most of today's corporationally incorrect software is guaranteed source-available software commonly referred to as free software, Open Source software, and GPL software. This issue of Troubleshooting Professional explains how to use these technologies to your benefit, and to the benefit of your organization.

This issue of Troubleshooting Professional Magazine discusses free software and Open Source alternatives to the current crop of corporationally correct software, starting with Microsoft and Open Source/free software licensing policies, software alternatives for your business needs, an exploration of Microsoft's vitriolic public attacks on free software and then two case studies (the Life After Windows and Linux Log columns). These two columns should give you an idea of the process of adopting business methods compatible with an Open Source alternative.

So kick back, relax, and read this magazine. And remember, if you're a Troubleshooter or Technologist, this is your magazine. Enjoy!

Steve Litt is the main author of Samba Unleashed. He can be reached at Steve Litt's email address.

Some Definitions

By Steve Litt
The terms "Open Source" and "free software" have gotten fairly synonomous over the years. They both refer to software that preserves the user's right to use the software, sell or give away the software, obtain the source code as part of receiving the software, and modify the software. In turn for all those rights, the user must agree to bestow those same rights on anyone he gives or sells the software to. Whether or not software is Open Source or free software depends on the software license. There are several licenses that have been declared "Open Source" and "free software".

The best source of free software compatible licenses is the Free Software Foundations license list at The best source for Open Source compatible licenses is their Approved Licenses page at

"Copyleft" is, to quote the FSF license list page: "Copyleft is a general method for making a program free software and requiring all modified and extended versions of the program to be free software as well.".

Copyleft generally implemented by requiring that any modifications to the copylefted program be issued with the same license as the original copylefted free software. By guaranteeing that a program is free software now and in the future, the license tells a would be contributor to the project that he's not just an unpaid worker for a proprietary outfit, and that his modifications will ALWAYS be available.

Copyleft REALLY bothers Microsoft, because it competes with them but they cannot legally use copylefted code in their proprietary Windows product without making Windows itself copylefted free software.

The extent of copyleft is not always clear because the definition of "modifications" must be made. Generally speaking, if a copylefted program or parts thereof are embedded in a larger program, the larger program is a modification that must be copylefted free software. If the copylefted program is statically linked into a larger program the larger program is considered a modification that must be copylefted free software. However, dynamic linking does not constitute a modification, nor does running on the same machine. So it's perfectly legal to run a proprietary program on Linux, which is licensed as copylefted free software.

The GPL stands for "GNU Public License", and is the most stringently copylefted free software. Linux is licensed as GPL, which is probably why it gained so many contributors and grew to challenge Microsoft.

For the remainder of this document I will use "Open Source" and "free software" as synonyms. While that's not completely true, it's close enough for the discussion at hand.

Steve Litt is the author of Troubleshooting Techniques of the Successful Technologist. He can be reached at Steve Litt's email address.

Microsoft's New Licensing Policies

By Steve Litt
Formerly satisfied Microsoft users are starting to look for alternatives. What happened?

I'm no authority on Microsoft licensing, but from what I hear and read, Microsoft is trying to drag their customers kicking and screaming into the equivalent of software rental. Every few years (I hear the number three bandied about) they stop supporting the current thing. Nor will they sell it to you. You must buy the modern version.

Buying the modern version is a good thing if you're a gung ho user of that software, but many of us use the software only to handle one specific task. For instance, here at Troubleshooters.Com I use Windows 98 (first edition) and MS Office 97 to access my older, pre-Linux documents. As such I have no need for Windows ME, 2K, or XP. But if my dog chewed up my Windows installation CD, I could not get another Windows 98. I'd have to buy a modern version.

The modern version would "upgrade" my data, possibly in a way preventing import into StarOffice and other Open Source software. In my situation, older is better. I'm not alone.

Then there's the licensing on the newer software. I've heard that MS Windows XP will have enforced registration via the net, and that you will be granted only a minimal number of installs. So if you upgrade computers, you could be toast.

Let's talk about software rental.

Renting an apartment works quite well. When you decide your rent's too high or your apartment is too dilapidated, you simply pick up your possessions and place them and yourself in a new apartment. You immediately have full use of your possessions.

Contrast that with software rental. You can certainly move all your data files to another operating system with other software, but you  probably can't use your data files. Most proprietary software stores data in formats that cannot be read by other software. Sometimes the proprietary software offers useful data export mechanisms, but many times it doesn't. And with various laws threatening to put teeth in the "no reverse engineering" clauses of licenses, other vendors might be stopped from creating import mechanisms for your data. The bottom line is that if you "move" to other software, either you could lose the use of your data, or be forced to expend significant time and money to regain it.

It's very much like signing an apartment lease stating that you can move out, but you need to leave all your possessions behind. With such a lease, what would be your landlord's motivation to maintain the apartment in a livable condition or keep the rents par with market value?

Luckily there are alternatives. Read on...

Steve Litt is the creator of the Universal Troubleshooting Process Course. He can be reached at Steve Litt's email address.

Open Source and Free Software's Licensing Policies

By Steve Litt
There are many different Open Source and free software licenses, but they all basically say if anyone selling or giving away the program must also throw in the source code to the program free of charge. They must grant the receiving party the same rights they have. The source code can be modified. Some licenses (the copylefted ones) require that any modifications of the software be issued with the same license, thus preventing modifications being taken proprietary.

Without going into a huge theoretical discussion, that means the price of Open Source or free software (yes, they can be sold for money) cannot rise higher than the convenience factor of receiving it on CD. In fact, it usually costs you nothing to download it.

But it's not about price, it's about freedom. Because you have the source code, you can modify the program to deal with any eventualities that come your way. If you decide to stop using the program and want an export mechanism to a new program, you can modify the program to export your data. Of course you might not  have the ability to  do the program modification yourself, but because you legally have possession of the source code, you can hire someone to do it for you if absolutely necessary.

But that's not usually necessary because there are many other users of the program, and if there's a beneficial modification or a needed export mechanism to be made, each of whom have have possession of the source code. So somebody's probably already done it. And because it's Open Source or free software, the source code is available, and most likely a binary version is available too. Get on the 'net, download the software, and use it. Life is easy.

For some reason most Open Source and free software programs tend to place their data in human readable text formats that are easy to write programs to modify. Such data formats eliminate the chance that your data will become locked into a specific format. A license that prommotes free giving of the software has nothing to gain from obfuscated data format.

For some reason proprietary programs tend to store their data in undocumented binary format that's difficult to modify programmatically. For some reason those same vendors add to that difficulty with "no reverse engineering" clauses in their software licenses. And inexplicably, some software vendors go so far as to patent the format of their data files so it's illegal to make an import or export facility.

I think most of us agree it's a vendor's right to protect their programs from unauthorized duplication. But we know it's our data in those locked up formats. Most of us believe our data belongs to us, and we have a right to read it regardless of whether we continue to work with a specific vendor.

That's why so many formerly satisfied Microsoft users are searching for alternatives.

Steve Litt is the author of Rapid Learning: Secret Weapon of the Successful Technologist. He can be reached at Steve Litt's email address.

Open Source and Free Software Alternatives

By Steve Litt
Everyone agrees that Photoshop is top of the line graphics software, worth every penny of its $609.00 cost (price taken from Adobe website). But did you know that there's a program called Gimp with many similar features and it won't cost you a cent? It comes with source code, meaning that if somehow Gimp's authors abandoned it and operating system changes stopped it from working, you could change the source code to restore functionality. But you wouldn't need to, because in practice somebody would fix it before it became a problem for you.

Did you know that a great deal of the web runs on free software and Open Source? That includes the entire domain naming system. The majority of websites run the Open Source Apache web server. Many of those sites run Apache on the free software GNU/Linux operating system. Many of the web's email servers are free software or Open Source.

In the "Enterprise", long considered a bastion of proprietary software, many IT departments deploy a free software file and print server called Samba, saving thousands on Windows server licenses.

Look what else is available:
Task Proprietary or Windows software Free Software/Open Source alternative
High quality graphics Photoshop Gimp
Diagramming Visio Dia
Spreadsheet Excel StarCalc*, Gnumeric, kspread
Word Processor Word, WordPerfect StarOffice*
Presentation software MS StarOffice*
Email client Outlook,Eudora Kmail, mutt, pine, elm, many others
Web design Frontpage, Netscape Composer Bluefish, Screem, Quanta, Netscape Composer**
Fax Winfax Hylafax, Sendfax
Digital cameras Various drivers from camera manufacturers Gphoto
High quality text editor Multiedit, etc VI, Emacs
Webserver IIS Apache, Zope, others
Web programming ASP,Java, Perl, Python Java, Perl, Python, PHP, Zope
Database MS SQL Server MySQL, PostgreSQL
File & Print Server with authentication NT/2K/XP Samba
* StarOffice is not Open Source or free software at the moment, but the next version is slated to be.

**Netscape is not Open Source or free software, but it's freely available in binary format at no cost, and furthermore there's a fork of the Netscape software called Mozilla that IS Open Source, and Mozilla has a Composer feature almost identical to that of Netscape.

Whatever you can't find in actual free software/Open Source programs, you can usually put together by combining Linux commands and existing programs. And many of your favorite proprietary products run on free software GNU/Linux. There's little that cannot be done with Linux and free software.

So if you're worried about Microsoft's new licensing, know that you have an alternative.

Steve Litt is the documenter of the Universal Troubleshooting Process.  He can be reached at Steve Litt's email address.

Transition is a Journey, not an Event

By Steve Litt
Success demands the transition from corporationally correct proprietary software to corporationally incorrect free software be viewed as a journey. You don't need to throw your Windows machine in the dumpster and switch to a Linux machine equipped with only free software. A journey of 1000 miles begins with a single step.

If you're like me your introduction to free software will be a Windows port of an Open Source or free software program. For me that introduction was Perl for Windows. There's lots of Open Source and free software on Windows. The following have Windows ports: Gimp, Dia, StarOffice, VI (Vim), Perl, Python, and many, many more. There's no law against using free software or Open Source on Windows.

There's no law against using Linux for some things and Windows for others. Make your transition a journey, plan the journey, travel the journey carefully, and you will succeed.

For more information on making the journey, see the April 2001 Troubleshooting Professional Magazine.

Steve Litt is the author of Troubleshooting Techniques of the Successful Technologist. He can be reached at Steve Litt's email address.

Why Microsoft Doesn't Like free software

By Steve Litt
Steve Balmer says "Linux is a cancer that attaches itself in an intellectual property sense to everything it touches."

Craig Mundie says "This viral aspect of the GPL poses a threat to the intellectual property of any organization making use of it. It also fundamentally undermines the independent commercial software sector because it effectively makes it impossible to distribute software on a basis where recipients pay for the product rather than just the cost of distribution."

Jim Allchin was attributed by CNet as first comparing Open Source to Napster, and then saying Microsoft must do a better job of talking to policymakers.

I guess Microsoft doesn't like Open Source. It's a cancer, a virus, and congress must do something about it.

Why doesn't Microsoft like Open Source? Obvously Open Source and free software (especially the GPL) are competitors to Microsoft, but it goes deeper. Because Open Source and free software are developed collaboratively without need for revenue, they cannot be revenue starved out of existence. That makes them immune to the revenue starvation process that Microsoft has allegedly used to destroy some of its other competitors. For the first time in over a decade, Microsoft must compete.

And Microsoft knows what they don't what want you to know -- the competition is superior in almost every way. If you start writing books in LyX you're never coming back to MS Word. If you start serving web pages in Apache, you're never coming back to IIS.

Microsoft desparately needs to prevent people from trying free software and Open Source. So Allchin whines to congress saying such software should be illegal. And they preach to the business community that if you use free software and Open Source all your intellectual property is forfeited (that's not true).

Microsoft's worst fear is a guy like me. I've gone to the dreaded "other side", found it better, and told all my friends. Now some of them will dabble in free software, find it better, and tell their friends. Microsoft has met its match.

Don't be the last to adopt free software and Open Source. Being the last will put you at a horrible competitive disadvantage.

Steve Litt is the documenter of the Universal Troubleshooting Process.  He can be reached at Steve Litt's email address.

Life After Windows: PDF Fever

Life After Windows is a regular Troubleshooting Professional column, by Steve Litt, bringing you observations and tips subsequent to Troubleshooters.Com's Windows to Linux conversion.
So there I was, with a PDF version of a government form needing completion. Back in the old Windows days I used a program called "Envoy" that came with Corel WordPerfect. I can't read my envoy files anymore. Ugh!

Later I used MS Word, placing text boxes all over the image of the PDF. Crude, but effective.

So here I was, with my new Linux box and this PDF needing completion. I tried a few things with StarOffice but no go. I tried several other things. Then I hit upon Gimp...

I opened the PDF in Gimp, setting it for 150dpi, heavy text antialiasing, light graphic antialiasing. Unbelievably each page of the PDF became a separate Gimp image, and I saved each as a Gimp native .xcf file. The next step was to create a new transparent layer on top of each image, save again, and then place text on the new layer. A mistake could be corrected by erasing the text from the top layer without erasing the underlying PDF image layer. When completed it can be saved as Gimp native .xcf for future mods, as .jpg for transmission, and printed it on my printer.

At the LEAP Installfest a few days later I noticed that Abiword and Gimp can save directly to PDF, but other apps can't. LEAPster Brian Ashe reminded me how the ps2pdf program can convert Postscript files to PDF format.

So there it is. Full circle! You can capture a PDF form in an image suitable for completing in Gimp, and then save it back to PDF. Without a single Adobe program in the mix. So if you're one of those people less than pleased with Adobe because of the  arrest of the Russian programmer, that's a good thing to know.

What's life like after Windows? A Linux computer is a field of dreams. Build it and the software will come.

Steve Litt is the creator of the Universal Troubleshooting Process Course. He can be reached at Steve Litt's email address.

Linux Log: Writing Books with Linux

By Steve Litt
After my Windows to Linux conversion in March 2001 two big concerns were software for outlining and software suitable for composing a 200+ page book. In Windows those two functions were neatly addressed by MS Word. Word doesn't run on Linux. Would my upcoming book on Troubleshooting force me to retreat back to Windows for book writing? In March of 2001 I assumed so.

The plot thickened a few weeks later when I created the VimOutliner program to use Vim version 6 as an outliner. And what an outliner. Lightning fast for the touch typist, able to hyperlink between outlines. More and more of the planning function of my professional and business life involved VimOutliner.

So when it came time to outline my new book, VimOutliner was a nobrainer. But a pesky little voice in the back of my mind kept asking "what will you use to compose the book?". Of course StarOffice would work, but lacking MS Word's outline view, it's a Word knockoff without Word's #1 bookwriting tool. There had to be a better answer.

DocBook would have been wonderful, but my research indicated the only reasonable front end to DocBook was Emacs, and I just didn't have time to learn Emacs. Some folks suggested simply coding markup in VI. Either they've never written a full length book, they've taken forever to write a full length book, or they know something I don't know (and probably can't learn).

But one technology appeared hopeful, if problematic. Several people suggested LyX, a front end to the LaTeX macro enhancement of the TeX typesetting language created by computer pioneer Donald E. Knuth. LyX has a quick and easy user interface, and it comes with most of the styles you need to write a book, so you can quit your job as a layout designer and work full time as a writer. But LyX seemed to have two problems:

  1. It has very limited export mechanisms, seeming to make migration to something like DocBook difficult.
  2. Methods of creating and changing styles are inobvious to say the least, and there's little if any documentation giving a step by step process to create or modify a style.
As a result, I hadn't taken LyX seriously. But two weeks ago, with an 800 line book outline and no way of writing the book, a crisis was looming.

The "no exports" problem turned out to be a paper tiger. After viewing a LyX document in VI it was obvious that it was simple, styles-based markup that could be easily manipulated, and yes, converted, with simple Perl scripts. One problem down, one to go.

So I set about using Rapid Learning techniques. Learning the terminology was easy, although at first discerning where LyX stopped and LaTeX started was confusing. Next, I needed a single proof of concept of style creation, and the rest would be a matter of simple incrimental learning.

But no matter how hard I looked, no matter how many questions I asked on the LyX mailing list, no complete proof of concept occurred. With an 800 line outline begging for the writing, frustration doesn't begin to describe the situation.

Finally someone emailed me a proof of concept way to change an environment by editing an existing .layout file. But if the environment changed a font, the font changed only within the LyX environment, not in the finished Postscript file. Worse yet, it seemed to depend on the specific filename. Renaming the file removed the environment. A grep command revealed absolutely nothing pointing to the filename. How had LyX decided to use this particular filename, and when I renamed the file it ceased to work?

A LyX mailing list member took pity and emailed the answer. .layout files need to refer to an existing document class. The answer is that .layout files default to a document class with the same name as their filename. Lacking that, the .layout file must internally specify the document class to which it refers. That's why renaming it blew off the style.

I specified the existing class inside my renamed .layout file, and once again the style could be pulled up in LyX, and indeed formatted correctly in LyX. But the finished Postscript file used the font from the base class, not my class coded in my .layout file.

But how could the changes be recognized in the finished output? Another nice LyX list member had mailed me his own .layout file. A careful and thorough examination of that file led to the observation that one needs to link the style to the preamble by linking the style's LatexName to the Preamble/EndPreamble section's \newenvironment's name. That did it. The font change was recognized in the finished output.

So I put it all in a tutorial (URL in the URL's section) to make this an hour's learning process instead of several days. So YOU can use LyX without the pain I endured.

Now I have a superior outlining program, which can be imported into a superior book composition program. My data is completely secure, and when the time comes to convert my book to something other than LyX I can write a script to do so.

Lessons Learned

Open Source and free software can do almost anything, but sometimes it's not obvious how to achive the goal. They often sacrifice "user friendliness" for utility and robustitude. The idea is that the user, or the user's organization, creates scripts or configurations to make the software "user friendly" in the context of the way the organization uses the software. So it's very easy to use, but learning how to initially set it up can be more difficult.

So you start by evaluating whether it will do what you want. Use mailing lists and the like. Then verify by learning how to use it. Start by learning the terminology, then develop the most trivial proof of concept (Hello World), and then repeatedly learn in increments. Finally document it so those following you won't have the steep learning curve.

The result is a vastly superior product that's infinitely configurable. Better yet, a product that doesn't try to lay claim to ownership of data you create with it.

Your Alternative

If you really like Microsoft software, and you feel OK about Microsoft's new licensing policies, by all means keep using Microsoft. But if your only reason for staying with Microsoft is that there's no alternative, rejoice. Writing books is just one example of how switching to Linux can not only offer an alternative, but can offer a superior alternative. Yes, it will take a little bit of learning, and there may appear to be some brick walls, but you can almost always either knock those walls down or go around them.

And when you get to the other side, your data is safe. It's truly yours, by license, and you can reverse engineer your software or even modify the software to do what you want. If you're anything like me, you'll breath a sigh of relief.

Steve Litt is a member of Linux Enthusiasts and Professionals of Central Florida (LEAP-CF). He can be reached at Steve Litt's email address.

Letters to the Editor

All letters become the property of the publisher (Steve Litt), and may be edited for clarity or brevity. We especially welcome additions, clarifications, corrections or flames from vendors whose products have been reviewed in this magazine. We reserve the right to not publish letters we deem in bad taste (bad language, obscenity, hate, lewd, violence, etc.).
Submit letters to the editor to Steve Litt's email address, and be sure the subject reads "Letter to the Editor". We regret that we cannot return your letter, so please make a copy of it for future reference.

How to Submit an Article

We anticipate two to five articles per issue, with issues coming out monthly. We look for articles that pertain to the Troubleshooting Process, or articles on tools, equipment or systems with a Troubleshooting slant. This can be done as an essay, with humor, with a case study, or some other literary device. A Troubleshooting poem would be nice. Submissions may mention a specific product, but must be useful without the purchase of that product. Content must greatly overpower advertising. Submissions should be between 250 and 2000 words long.

By submitting content, you give Troubleshooters.Com the non-exclusive, perpetual right to publish it on Troubleshooters.Com or any A3B3 website. Other than that, you retain the copyright and sole right to sell or give it away elsewhere. Troubleshooters.Com will acknowledge you as the author and, if you request, will display your copyright notice and/or a "reprinted by permission of author" notice. Obviously, you must be the copyright holder and must be legally able to grant us this perpetual right. We do not currently pay for articles.

Troubleshooters.Com reserves the right to edit any submission for clarity or brevity. Any published article will include a two sentence description of the author, a hypertext link to his or her email, and a phone number if desired. Upon request, we will include a hypertext link, at the end of the magazine issue, to the author's website, providing that website meets the Troubleshooters.Com criteria for links and that the author's website first links to Troubleshooters.Com. Authors: please understand we can't place hyperlinks inside articles. If we did, only the first article would be read, and we can't place every article first.

Submissions should be emailed to Steve Litt's email address, with subject line Article Submission. The first paragraph of your message should read as follows (unless other arrangements are previously made in writing):

I (your name), am submitting this article for possible publication in Troubleshooters.Com. I understand that by submitting this article I am giving the publisher, Steve Litt, perpetual license to publish this article on Troubleshooters.Com or any other A3B3 website. Other than the preceding sentence, I understand that I retain the copyright and full, complete and exclusive right to sell or give away this article. I acknowledge that Steve Litt reserves the right to edit my submission for clarity or brevity. I certify that I wrote this submission and no part of it is owned by, written by or copyrighted by others.
After that paragraph, write the title, text of the article, and a two sentence description of the author.


All trademarks are the property of their respective owners. Troubleshooters.Com(R) is a registered trademark of Steve Litt, Kepner-Tregoe(R) is a registered trademark of Kepner-Tregoe, Inc. Neither Steve Litt, Troubleshooters.Com, the A3B3 website network nor American Troublebusters are in any way affiliated with Kepner-Tregoe, Inc.

URLs Mentioned in this Issue