Why Eurosoft Diagnostics are Strategic

Testing hardware is not only tactical, it's strategic:

- Why use self-boot testing when you need Windows-based testing?

Simple example: Using self-boot testing i.e. non-Windows operating system allows you to test core hardware, such as memory modules without Windows consuming the memory space. This ensures that the entire memory module is independently tested for 100% accuracy. Using Windows driven testing, however, allows you to test PCI or device driven hardware, such as win-modems and integrated graphics.

Testing core or device driven hardware is specific, necessary and tactical. Without using both varieties of diagnostic tests, a system running Windows driven hardware will not get the full diagnostic attention it requires. For further testing emphasis, consider the hardware environment.

- What is your hardware environment?

Tactical testing is an important part of service and RMA work. However, there is a further strategic basis for testing systems in the environment where it is or may actually end up being installed.

At the first point of manufacturing or integration, where component assembly, software imaging and staff capabilities unite, a system may be exposed to a mismatch or faulty set of conditions. For example:

• When installing the graphic card and audio, the matching device drivers did not get loaded on to the system;
• After the 512Kb of memory was carefully installed, the system would not meet the performance criteria because a slower CPU was installed;
• Once the main board was installed, the updated BIOS version was not flashed and loaded on to the system.
• Wrong software image loaded--again.
• Failing hardware components is common occurrence: memory module corruption, crossed USB and audio connections, media player laser head failure, hard drive sectors failing, etc.

The list goes on. These production and integration problems can be reduced or even eliminated. The dual approach of core self-boot and Windows based testing stresses the entire system by running installed software images and device drivers with its associated hardware.

Stress testing the entire system in its final environment, ensures that the test can say with certainty that the appropriate diagnostic were run, the drivers are installed, and the system works. When you test a system in its intended final environment, you are becoming much more strategic in your test plan.

Take your test plan one giant step further. Warranty and recycling compliances will dictate the condition of systems; how they will be serviced or disposed of. By distributing end-user versions of the same test scripts used during manufacturing-"womb-to-tomb" diagnostics-these compliances can be effectively managed. This is a very strategic solution as opposed to a very tactical one that just gets the job done of testing.

Summary

Simply explained, find problems before the system gets shipped or installed and reduce your service burden and cost. Find problems during service and reduce your compliance burden and cost. Using diagnostic tests on each system built, upgraded or recycled ensures the system is successfully used throughout its lifecycle. That is strategic.