Linux FUD Pattern #8: Linux will void your warranty
Will the use of Linux void the manufacturer’s warranty of your computer hardware? This is one fear that prevents some people from making the leap to Linux, which is why it is on my Top 10 List of Linux FUD Patterns. The short answer is, it depends; however, there are steps that you can take to increase your probability of receiving service under a warranty.
What Is A Warranty?
A warranty is a seller’s obligation to provide a remedy when a product fails to meet the conditions of the warranty. The conditions and the remedies are specific to the warranty for a product, though some warranties are legally implied and need not be explicitly expressed. The Federal Trade Commisison provides a very informative page describing warranties.
Conditions under which a buyer may exercise the right to receive a remedy usually concern attributes of product quality. Express warranties are an incentive to the buyer, because it shows that the seller is willing to stand behind its products and protect the consumer from unintended defects that arise during manufacturing or during normal use. The definition of normal (or “intended”) use may be specified in the conditions.
In the United States, Article 2 of the Uniform Commercial Code governs warranties, both express and implied. Sellers are legally limited in the extent to which they can disclaim warranties. Specific statutes are established at the state level. Moreover, the Magnuson-Moss Act of 1975 was enacted to make warranties more readily understood, but its application is limited to consumer (read: household) products.
Why Not Honor Warranty Claims?
Why would a company not want to honor a claim made against its product warranty? In a word: cost.
Warranties are considered to be contingent liabilities for financial accounting purposes. At the time of sale, a reasonable estimate of warranty costs can often be made. This also means that until the costs either are realized (e.g. warranty work is performed) or expire (e.g. at the end of the warranty period), the obligation to replace or repair the product in question impacts the financial health of the seller or manufacturer. Depending on the product, such obligations can be significant. Financially, expiration is much better than realization because it does not impact cash.
Moreover, the cost of troubleshooting and repairing a system with a nonstandard OS installed is higher than that for a standard configuration because time must be spent either learning to work within the unfamiliar operating environment or time is spent working around that environment. It’s also much easier to determine when a problem is not a result of manufacturing or normal use when the technician is working within a known environment as it has been (pre)installed by the seller. If you replaced the software used by your automobile’s internal computer with a variety of your own, do you really think a dealership or even an independent mechanic is prepared (much less willing) to assist?
What’s worse, if a component of a product that provides some sort of control over the use of the product for the purpose of maintaining or extending its useful life, then the replacement or modification of that component may cause hard to the product as a whole. This is obviously not a manufacturing defect and is unlikely to be considered “normal use”. The extent to which an OS fits this description depends on what functions the OS provides (e.g. teperature control).
Read Your Warranty!
Ultimately, the answer to the question lies in the language of the warranty itself. A statement of warranty is a legal document and the one shipped with your new PC was probably written with or by a lawyer. The specific conditions and remedies are contained therein. READ YOUR WARRANTY! This will be the primary source of coverage information should you decide to take a dishonored claim to the courts. If it is that important to you, read the warranty before you buy the computer and only buy a computer with a favorable warranty.
Rest assured, the company will probably steer clear of violations of implied warranty, which means that they will probably not refuse to replace items that pose grave safety hazards, such as exploding laptop batteries. Dealing with your non-standard OS is much less costly than a court settlement with your home insurance company or your estate. A motherboard or power supply that stops working altogether is not a grave safety issue and claims regarding these issues are subject to more scrutiny.
HP Case Study
An exegesis of each and every warranty provided by every PC manufacturer over time is far beyond what I can do here. But, since a Web search for ‘Linux’ and ‘warranty’ readily retrieves stories about Hewlett-Packard, and since my family has two HP laptops in the household currently, I decided to do a little research on their warranty specifically. Here’s what I found, followed by an account of my own experience with HP support.
The HP warranty is published online, so rather than quote what is on my warranty card, I thought it might be more useful for the reader to have access to the warranty disclosed publically. In the first paragraph of the “Limited Warranty” section, the application of the warranty conditions is expressly limited to hardware products and specifically excludes software and non-branded peripherals. The section continues to explain the HP guarantee, the customer’s entitlement to receive hardware warranty service, and the conditions for repair or replacement.
The “Software Limited Warranty” section near the bottom of the warranty page explains that HP’s obligations are limited to defects in the removable media (i.e. floppies, CDs, DVDs, etc.) shipped with the product, and then, for only a period of 90 days. Of course, the chance that an average PC customer is actually going to use the recovery or installation CDs for a preloaded PC within 90 days, especially for the express purpose of testing the media for defects, is pretty remote – good thing the expectations weren’t set too high for software.
That section also explicitly disclaims support for “freeware operating systems and applications.” Yes, Linux is Open Source and not freeware, but then, the actual verbiage of the paragraph refers to “software provided under public license by third parties” and that would include an aftermarket installation of any GPL software.
So far, so good. Hardware is supported and software isn’t. Uh oh…
There is a possible out for HP in the “Customer Responsibilities” section. For “best possible support”, the customer must be able to “run HP diagnostics and utilities” and even allow HP to monitor using “system and network diagnosis and maintenance tools”. No doubt, these are compiled for Windows only. “I’m sorry, we cannot fix a problem that we cannot diagnose. Good bye.”
This doesn’t mean that HP will not support you, but it does provide them with a logical and reasonable excuse not to do so. Indeed, HP reportedly clarified in early 2007 that the installation of Linux does not affect the warranty of the hardware so long as the software is not the cause of the problem being fixed.
Here is a case in point. In recent months, HP issued a recall of specific models of the Pavilion laptop due to a BIOS problem. As I understand it, the problem had something to do with the computer’s ability to regulate temperature, so units would overheat. Battery problems and other component failures were extreme symptoms. My wife’s laptop was one of the models listed, so I called tech support to schedule a repair. During the course of the conversation, I told the representative that I would remove the hard drive prior to shipment, primarily because it contained sensitive data (which was true). I also mentioned that Linux was installed and that the hard drive would be of little value in the repair process. The rep said that removal of the hard drive was acceptable. The unit was fixed and returned without incident.
How To Protect Your Warranty
Based on my experience and research, here are a few things that you can do to help ensure warranty service:
Troubleshoot the problem. If you are tech-savvy enough to run Linux, you probably know a thing or two about computers. Troubleshooting problems is a science, not an art, and the more you isolate the problem to a specific component, the more leverage you have with the warranty organization.
Buy a second hard drive. The only evidence of a Linux install is on the hard disk (unless you’ve replaced the Windows case badge with a Linux one, of course). When you buy a new PC, set up the preinstalled system, register it, remove the hard drive and store it in a safe place should you need to run vendor-supplied diagnostics. Buy and install a second hard drive for your Linux install and go to town!
Retain possession of your hard drive. Do what I did and tell them that you will be sending the unit in for repair sans hard drive. Data security is a big deal, even more so if the data in question is your employer’s data! Besides, the worthy repair facilities have their own diagnosis disks to use in lieu of a customer’s drive. You need not mention Linux at all. Of course, you cannot expect them the repair or replace a hard drive if you do not furnish the broken one.
Play it safe. Do not use software or perform other system tweeks that have the potential to harm hardware if you want the warranty honored. It is very unlikely that a standard Linux distro will cause such harm, but Linux does provide much more software access to hardware components than do other consumer operating systems. You may be surprised how easy it can be for the experts to determine how a component burnt out and the probable reasons as to why.
|<< Go To Part 7||Part 9 Coming Soon >>|
This article contains information on warranties, but does not contain legal advice. Opinions expressed herein belong solely to the author. If you have a warranty issue that may necessitate legal action, please contact a lawyer.
Hello All! As you may have noticed, there’s been a bit of a lull in the postings on our humble little ‘blog. For various reasons, I’ve not been able to dedicate as much time to this site as I wanted (my lame excuses listed below). Thankfully, that is starting to change now!
First and foremost, I plan to finish out the Top Ten Linux FUD Patterns. Seven down and three to go!
Second, I am planning a new series. I often write about market forces since most of the intentional FUD is generated by the supporters of the competition. In this series, I will cover some basic economic concepts and how they relate to the OS market.
Finally, I’d like to hear from you, our readers, about what you want to know with respect to Linux. If you are on the fence, what information will help you decide if Linux is right for you? I’d also love to hear some success stories on the FUD front and how you helped combat it. Please feel free to post a comment to this article or write to us directly via the Contact page.
Oh yeah. As promised, here are my lame excuses for not posting more often:
- Becoming a Dad. This is my second and whoever said the woman does all the work should be shot. Finding the perfect shade of pink wall paint is not easy!
- Finishing College. This is also my second time around, presently with a postgraduate business degree. Burnout is not a pretty place.
- Earning a Living. The busy season in our office spans from August to October. Unfortunately, many lunch hours had to be sacrificed this year, which is when I do most of my writing.
- Writing a Book. I started writing a technical management book six years ago and all but shelved the project to go to school. That was a good move, but now I am excited to get back to it.
- Running the Country. Well, indirectly. Researching candidates is time consuming, but well worth the effort.
Yesterday, David Williams posted on ITWire’s Linux Distillery an article about how Linux is keeping Microsoft honest. The real meat begins with a discussion about Windows PowerShell, Microsoft’s newest scripting language. ‘New’ is a relative term, as Williams points out that the scripting concept is not only a very old one, but that the punch cards of computer lore could be considered the first form of scripting. Williams points out that the Windows trend of ‘dumbing it down’, creating GUI tools to replace thousands of keystrokes, may be reversing. The focus of PowerShell, a CLI, is to replace thousands of mouse clicks with scripts. Williams continues with the revelation that PowerShell is becoming ‘entrenched’ in Microsoft’s server offerings, including a headless, GUI-less mode for Windows Server 2008. He attributes this shift in design philosophy to Linux.
I think this is great news for Windows, because as systems grow, especially online offerings, effective system management depends on efficiency. Ultimately, this means automating as many maintenance functions as possible. With Linux and other *nix platforms, this has never been a problem, but the Windows CLI has been fading into obscurity for many years now. The DOS shell sat right on top of the kernel, but beginning with NT, the ‘command prompt’ became just another application that had to operate through various other layers, such as the oppressive NT HAL, diminishing its power. Moreover, the range of CLI utilities remained unimpressive. Thankfully, products such as MKS Toolkit, Cygwin and Sourceforge’s UnxUtils have helped to fill that gap.
Let’s not forget that the CLI is useful for far more than executing OS-related functions. In my experience, all the best software applications offer a CLI interface. I implement systems that help IT managers manage the activities of their staffs, including helpdesk and other customer issue management suites, source code control and software media distribution centers, and project/programme management repositories. I always look for software that provides a Unix release, even if the target platform is Windows. Why? Unix-based applications almost always include a CLI which is almost always ported to the Windows release if one exists. Not only is the CLI of great use to me from a user’s and administrator’s perspective, but I know that the existence of a CLI usually indicates that the software has tested more thoroughly. If an application has been designed well, then the CLI functions call the same underlying subroutines as their GUI counterparts – this allows the vendor to easily write (and more importantly, to execute) scripts for regression and load testing. Nightly smoke tests of new builds are possible without the maintenance of complex GUI-based test harnesses. Don’t misread me – the GUI must be tested, just not to the same extent as when the GUI is the only interface available.
Where’s the FUD? For years, Windows zealots have denounced Linux for being arcane, hard-to-use, and backward. Heavy reliance on the CLI for administration was cited as a failure to progress (through obstinacy, ignorance or both). Now, it appears that Microsoft is admitting that a powerful shell is indeed useful, forcing its fanboys to dine on crow tartare.
The return of a powerful shell is a step in the right direction for Windows! Is this really due to Linux? I wouldn’t be surprised.
I’m soooooo glad that the PC Weenies have taken the time to explain the Microsoft commercial! The Shoe Circus is a Mac Store slam and Microsoft’s future is a fried snack.
P.S. You probably know by now that I believe in supporting artists, and revelations like this don’t come along everyday, so please commemorate this occasion by ordering a copy of this cartoon on card stock today!
The new Microsoft commercial featuring Jerry Seinfeld and Bill Gates aired for the first time late last week. I caught it yesterday morning, but was on a treadmill at the gym and couldn’t hear what they were saying, so I had to catch up on YouTube.
I usually try to link some good references for you, but there are just too many articles and ‘blog posts to cite on this one! Most claim that the ad was too expensive for so little content. I agree and would like to add that it was too long…a minute and a half! Throw in some commercial breaks and some yada-yada-yada and you have a full-legnth Seinfeld episode!
I actually got more out of the ad without sound. It appeared that Jerry was going the extra mile to provide good, personal customer service to Bill in the shoe store, explaining in great detail how a particular brand of shoe, the “Conquistador”, is quality-tested for ruggedness. I could see the gears in Bill’s head turning as he absorbed Jerry’s message and pondered how he could reap the benefits of quality-testing at Microsoft. Once I heard the commercial, however, I felt the urge to buy a pair of Conquistidor shoes and was suddenly hungry for a churro. Upgrading my OS or office productivity software was the last thing on my mind.
If subsequent commercials don’t send a clearer message, I may have to start a FUD ‘blog to warn consumers about the fear, uncertainty and doubt campaign Microsoft is waging against itself. You know, just to be fair, right?
As Microsoft is chided by the media and in the blogosphere about its decision to hire comedian Jerry Seinfeld as the new Vista spokesperson, I ponder just who the Linux community would hire as their representative. Assume for a moment that the community (a) actually had an interest in hiring a celebrity to “sell” the OS in the mass market and (b) could raise the money to pay the bill, who who it be?
Smart alec as I tend to be, the first comedian that comes to mind is Rodney Dangerfield, whose “No Respect” humor may speak to the feelings of current Linux users. There’s one small logistical problem to overcome – Dangerfield died in 2004.
I think I’ve decided that comedians were not the way to go afterall. A more serious actor may work out better.
Ah, Jack Nicholson! Now there’s a prospect! Just think of the taglines. “You can’t handle the truth!” “Where does he get those wonderful toys?” “You make me want to be a better man.” (Ok, not so sure about that last one.)
Well, enough pondering…time to get back to reality. If you have any suggestions, we’d love to hear them.