Computer Repair with Diagnostic Flowcharts - Troubleshooting Del. Eight of the troubleshooting flowcharts for PC hardware from my book "Computer Repair with Diagnostic Flowcharts Third Edition" are excerpted on this site and linked below. The non-active links are for charts that are included in the book but not available online. The Third Edition is 170 pages and includes seventeen flowcharts for troubleshooting PCs plus explanatory text for every decision symbol on every flowchart. The troubleshooting process is the same for an expensive Sony or IBM, or a cheaper eMachines or Acer. Dell and HP (who purchased Compaq) manufacture desktop PC's in a wide range of price points, but you have to go through the same troubleshooting steps for the cheap ones as the expensive ones if you want to correctly identify and repair the failure.
Boot Failure Troubleshooting Poster ( 30" x 30" printable PDF). Zoom to 100% after it opens or you'll barely be able to read it! Computer Repair with Diagnostic Flowcharts | Foner Books Home. How to Build a Hackintosh with Snow Leopard, Start to Finish - H. Cool guide haha. Pretty fast. Is there a reason why you don't install Chameleon directly on the hard drive? You don't need to keep your key in if you do so. Also RC2 is available as a installer so you can bypass the terminal work.
I've got the exact same Motherboard as you (just bought it to replace my old hackintosh), and I've gotten network and audio working with a DSDT patch. If anyone else has this or any of its sibling mobo's, check out this guy's installer package: [www.insanelymac.com] SL PACK v4 is rock solid. I just hope this Vanilla install will be just as stable as when it was with Leopard for future updates... Oh and as jeffk said... Process Explorer. Process Explorer can be used to track down problems. For example, it provides a means to list or search for named resources that are held by a process or all processes.
This can be used to track down what is holding a file open and preventing its use by another program. Or as another example, it can show the command lines used to start a program, allowing otherwise identical processes to be distinguished. Or like Task Manager, it can show a process that is maxing out the CPU, but unlike Task Manager it can show which thread (with the callstack) is using the CPU – information that is not even available under a debugger. History[edit] Process Explorer began in the early Sysinternals days as two separate utilities, HandleEx and DLLView, which were merged in 2001.[1] Until 2008, Process Explorer worked on Windows 9x, Windows NT 4.0 and Windows 2000. Features[edit] See also[edit] Process Lasso References[edit] External links[edit] Shuttle Europe - SN95G5.