Windows XP

The 7 QC steps process is structured as follows:

Step 1: Select a Theme.

In this step, the weakness in the process or the problem to be solved is clarified in a theme statement. A Flowchart, a Theme Selection Matrix, or a Cause & Effect Diagram is used as a tool in this step.

Step 2: Collect and Analyze Data.

This step focuses facts about the problem and discovers what types of problems occur frequently. When collecting data, you must think of all possible causes. Checksheets and Pareto Diagrams are the tools most often used.

Step 3: Analyze Causes

.With sufficient data from step 2, the root cause, or fundamental cause, is found by constructing a Cause & Effect Diagram.

Step 4: Plan and Implement Solution.

In this step, you brainstorm for ideas that are causing the problem and develop a solution that prevents the root cause from recurring. Then, you implement an adjustment to the process. The 4W's and 1H Matrix (What, When, Where, Who, and How Matrix) is used to develop a plan.

Step 5: Evaluate Effects.

You evaluate the effects of implemented solution to make sure the solution worked and does not have unacceptable results from the comparison of data, before and after the implementation of the solution. In this step, comparative Pareto Charts and Graphs are frequently used to identify the results.

Step 6: Standardize Solution.

A standardized solution is confirms that the old process is replaced with an improved process and indicates that the solution is workable. A flowchart is most often used.

Step 7: Reflect on Process and the Next Problem.

In this step, you consider what the team's accomplishment was in the first 6 steps and recommend a weakness to work on next.

== == == == The easiest way to explain solution is: Open the C:\windows\repair folder Highlight and copy autoexec.nt and config.nt (Ctrl+C) Open the C:\windows\system32 folder Paste (Ctrl+V) files and click Yes if box prompts to replace existing file If it does it again, it is because it gets deleted on Restart You just do it again or mark the files for Read-Only I just paste and copy and worry about tomorrow tomorrow If you try to start or install an MS-DOS-based or a 16-bit Windows-based program on your Windows XP-based computer, you may receive an error message that is similar to one of the following:

KB324767 - 16-bit MS-DOS Subsystem

path to the program that you are trying to start or install

C:\Windows\System32\Autoexec.nt The system file is not suitable for running MS-DOS and Microsoft Windows applications. Choose 'Close' to terminate the application. Although you may be prompted to quit the program or ignore the error message, either selection makes the program quit.

This issue may occur if one or more of the following files are missing or damaged: * Config.nt * Autoexec.nt* Command.com

In order to stay abreast of the new trends in Client-Server, we must start by looking at what is happening in the software trends as a whole. In the 1960s and 1970s was the era of centralized computing, with IBM mainframe occupied over 70% of the world's computer business. Throughout the 1980s, many functions once performed by the omnipresent IBM behemoths were systematically taken over by PCs. The result of this gravitational shift toward personal computers makes two significant remarks on the computer industry:

The PC shift made corporations to reset their IT organizations in a number of ways. We are currently in the Client-Server phase of the software development and will eventually move towards the truly distributed computing environment. In IT manager's point of view: distributed computing can be used as a tool for business process reengineering, corporate right-sizing, and customer responsiveness. The new software developments can be characterized as follows:

- Distributed: The main operating force in the software industry is the drive toward distributed computing, currently in its Client-Server phase.

- Multiphased transition: Client-Server is merely an intermediate step toward distribution. The ultimate goal is collaborative computing based on peer-to-peer networks.

- Enabling technologies: Prominent supporting technologies are object-oriented components, document-centric software architectures, data warehouse technology, standards, and the end-user programming trend.

On the other hand all the above software developments cannot afford to become set in its ways and without taking considerations or meeting the business needs as follows:

- Isolated desktop software solutions are no longer sufficient. The software industry must respond to consumer demand for portable, interoperable, distributed software solutions or else becomes extinct like their mainframe-only predecessors.

- Open Systems for Computing: the pressure on software vendors to establish interoperable, distributed, easy-for-end-user-programmers-to-use tools and standards upon which enterprise-wide architectures can be built.

-Business process reengineering increased consumer expectation, and networked distributed hardware, as well as numerous second-order complications are driving software complexity through the roof.

The software industry will, out of necessity, respond to the above pressures by forming forums, consortia, and back-room alliances in order to establish market-leading architectural infrastructure standards, interfaces, and middleware for the express purpose of shifting the balance of power in favour.