Meta Triage of Systems

From FreekiWiki
Revision as of 16:56, 3 November 2006 by Rfs (talk | contribs)
Jump to navigation Jump to search

<graphvizr>

 digraph BUILDPATH {
  size = "6, 8"
  start         [label="START HERE", fontsize="11", shape="box"]
  missingmobo [label="Missing the\nMotherboard?", fontsize="11"]
  highend     [label="Marked as HIGH END?\n(Celeron, P-III, P4, Athlon, Duron)", fontsize="11"]
  lowend      [label="Marked as LOW END?\n(Pentium, Pentium Pro,\n486, 386, 286, 80/86\nMade for Windows 95)", fontsize="11"]
  damaged     [label="Missing sides?\nor Other major damage?", fontsize="11"]
  fast        [label="Speed marked\nABOVE 500 MHz?", fontsize="11"]
  waiting       [label="Put on\nWAITING FOR EVAL 2\npile", fontsize="11", shape="box", style="bold"]
  incoming      [label="Put on \nINCOMING\npile", fontsize="11", shape="box", style="bold"]
  start       -> missingmobo
  missingmobo -> incoming [taillabel="YES", fontsize="11"]
  missingmobo -> highend [taillabel="NO", fontsize="11"]
  highend     -> waiting [taillabel="YES", fontsize="11"]
  highend     -> lowend [taillabel="NO", fontsize="11"]
  lowend      -> incoming [taillabel="YES", fontsize="11"]
  lowend      -> damaged [taillabel="NO", fontsize="11"]
  damaged     -> incoming [taillabel="YES", fontsize="11"]
  damaged     -> fast [taillabel="NO", fontsize="11"]
  fast        -> waiting [taillabel="YES", fontsize="11"]
  fast        -> incoming [taillabel="NO", fontsize="11"]
  
 }

</graphvizr> The idea of this chart is to safely bypass the ever-bottlenecked INCOMING pile in system evaluation. If you don't know how to identify the terms on this page, please learn to before attempting this job. In general this job should be done by trained system evaluation instructors and staff.