>Well, that's a pretty good definition of finding the problem ;-)
>
>I had a similar situation some time ago. A client ordered a bunch of new Dell W98 workstations all with Logitech mice. They found that DOS boxes running their DOS accounting program were always suspended if not the foreground application; a real pain when wanting to run long accounting batch jobs and do other work in the meantime.
>
>Eventually traced the problem to the Logitech 8.03 mouse driver; replaced with the 9.0, problem solved.
>
>I still find it difficult to believe that the mouse driver could have such a major and fundamental effect on the system, but I can't argue with success.

Al;

Some people cannot be convinced of reality and I have had my share of "interesting solutions" to solve problems. One nasty one was a company bought 50 new computers from a well known vendor (nameless) and they were installed with a 100t network. Everything worked fine except for one client machine and my newly installed application. After determining it had a different BIOS release date/number, a call to the manufacturer was made.
Replacing the BIOS with the latest version was all that was needed.

Keep an open mind when troubleshooting. My background as a Electronics Engineer taught me to expect anything and everything. Be logical and eliminate the major causes of possible problems first. Simple things like a client who said: "Your new app does not work on my machine". Turned out there was no AC power to his computer. Help! I have worked with guys who would recode the app rather than check the specific problem first!

Tom