Software Interaction
Is it hazardous to your productivity?

by John Boline
Service Manager, MCSE, CNE, USE

These days we have all seen the commercials for new drugs and pharmaceuticals and the list of disclaimers, displayed or read, of the possible side effects and the interaction with other drugs and conditions. Come on, show of hands, who has seen the ads? Ok, hands down now. Did you know the same is true of software, but many people do not know it? Show of hands again; I do not see any hands, well then, allow me to provide you with some information that is vital to your productivity!

Definition of Software Interaction
In order to understand what we are talking about, we need to establish a definition of software interaction. In many cases, software is supposed to work together. This is not the interaction of which I speak. I am talking about the hidden interactions that occur without warning. Yes, the definition of Software Interaction that I an speaking of is one where the behavior of one or more software is adversely affected by another piece of software - sometimes merely changing one program's behavior by the mere existence of the other; in other cases, the software is not able to even run; and all the levels in between. It does happen, and more often than you think. It can be an application, a utilities, firewall, anti-virus, anti-malware, even an operating system patch that will render an application that worked before impaired or dead!

Remember Windows XP SP2
A perfect example of an operating system patch breaking things was Windows XP SP2. Now while this was the grand-daddy of patches with its sheer size (it was larger than many operating systems alone), this baby locked down all kinds of communications, threads and processes used by existing applications. As I outlined in the article last year on Windows XP SP2 in our newsletter (http://newsletters.hagerman.com/newsletters/ebul23-WP.htm), at the time we knew that programs including Microsoft SQL Server, Outlook, Network Shares and CAD software from Autodesk are known to either have issues or not to work at all after the installation of this patch. The new versions of software have rectified this problem, in part, but other vendors still have not updated their software.

The Case of Anti-Virus Software
Ok, so we all know you should be on the current version of software. What happens though when you upgrade your software and something else breaks? Case in point, you have a CAM package and you get the new version. Then you upgrade your anti-virus to the new version. Now, suddenly the dialog boxes in the CAM software no longer work. Yes, this is a true, real world scenario. The key to upgrades is that everything must work together. Having the latest anti-virus software is important so your systems are protected against infection. But when that software breaks something else, you have to make a call. You contact the support people for both products and make them aware of the problem. They may have a fix or they may have to work on one, but the point is they need to be made aware.

Rules for Compatibility
It is funny, but by modifying the rules we set forth for Windows XP SP2, you really have a best practice list for use with all applications. To make sure everything works together you should:

Check with all your software vendors to see if their product will work with your other applications. Vendors often have interaction information posted on their web sites.
If there are problems, you may need to upgrade your hardware, software or both so that all of the products you are using are compatible with each other.
If a fix is not available for a known problem, find out if the problem is being addressed or if your will need to wait for the next version of the software. That way the problem does not have to be a show stopper.

How can I get more information about Interactions?
You can get more information about this subject? Well if you have support with us, ask us. Often times we will have logged a problem already and you can learn from the problems others have encountered and gain knowledge or patches, workarounds or fixes that way. The software vendors’ web sites and knowledge bases can be a wealth of knowledge as well. If you have questions or comments about this article, contact me (JohnBoline@hagerman.com).

All product names / logos, company names / logos are copyrights of their respective holders. John Boline is an MCSE, CNE, USE and a member of the Network Professional Association. The content herein is often based on late-breaking events. Much of the material is based on information from sources that are believed to be reliable. Hagerman & Company, Inc. disclaims all warranties as to the ultimate accuracy or completeness of the information. Hagerman & Company, Inc. and its employees shall have no liability for errors, omissions or inadequacies in the information contained within this article or for any interpretations thereof. The recommendations, positions and best practice policies outlined herein represent Hagerman & Company, Inc. initial analysis and therefore are subject to change as further information which may have bearing on these positions is made available. The reader assumes sole responsibility for the selection of these materials to achieve its intended results. The opinions expressed herein are subject to change without notice. Entire contents © 2004 Hagerman & Company, Inc. All rights reserved. Reproduction of this publication in any form without prior written permission is forbidden.

Check with all your software vendors to see if their product will work with your other applications. Vendors often have interaction information posted on their web sites.

If there are problems, you may need to upgrade your hardware, software or both so that all of the products you are using are compatible with each other.

If a fix is not available for a known problem, find out if the problem is being addressed or if your will need to wait for the next version of the software. That way the problem does not have to be a show stopper.