The second step in the troubleshooting process is to establish a theory of probable cause. First, create a list of the most common reasons for the error. Even if the customer thinks there is a major problem, start with the obvious issues before moving to more complex diagnoses, as outlined here:
You can determine an exact cause by testing your theories of probable causes one at a time, starting with the quickest and easiest. Some common steps to determine the cause of the problem are as follows:
PATCHED Windows 7 Loader 1.6 By Hazar With Step By Step Guide.
After the repairs to the computer have been completed, finish the troubleshooting process with the customer. Explain the problem and the solution to the customer verbally and in writing. The steps to take when you have finished a repair are as follows:
Journal: Include descriptions of the problem, possible solutions that have been tried to correct the problem, and the steps taken to repair the problem. Note any configuration changes made to the equipment and any replacement parts used in the repair. Your journal, along with your notes, can be valuable when you encounter similar situations in the future.
This step must be done only if you (or your retailer) have NOT previously installed a SimuCUBE bootloader. If you have a system with MMOS Drive Firmware installed start at step #1, If you have a NEW SimuCUBE purchased direct from Granite Devices or from a retailer that does not install firmware the device should be in DFU mode and you can start at step #3. If the SimuCUBE is not in DFU and MMOS is not installed you will need to manually enable DFU mode by using the #CASE C method described in the "Setting SimuCUBE into Device Firmware Mode (DFU)" section of the Installing MMos firmware into SimuCUBE page. 2ff7e9595c
Comments