Difference between revisions of "Prebuild"
| Line 1: | Line 1: | ||
| − | The first step in Free Geek's Build Program is called Prebuild. | + | The first step in Free Geek's Build Program is called '''Prebuild'''. |
| − | Prebuild is divided into two main branches, Hardware Identification and System Evaluation. | + | Prebuild is divided into two main branches, '''Hardware Identification''' and '''System Evaluation'''. |
Most people begin in '''Hardware Identification''' by signing up for a shift at the front desk. In Hardware Identification volunteers work through a series of lesson boxes -- each one teaching a basic skill that will later be needed in the build program. The boxes are generally arranged from most basic to more advanced. Each is available to the builder throughout the program, so any volunteer can refresh their memory as needed. People with enough hardware knowledge can test out of Hardware Identification, or they can skip whichever steps are unnecessary for them. Most people work through all of Hardware Identification in one or two shifts, but it is designed to be a "work at your own speed" experience. | Most people begin in '''Hardware Identification''' by signing up for a shift at the front desk. In Hardware Identification volunteers work through a series of lesson boxes -- each one teaching a basic skill that will later be needed in the build program. The boxes are generally arranged from most basic to more advanced. Each is available to the builder throughout the program, so any volunteer can refresh their memory as needed. People with enough hardware knowledge can test out of Hardware Identification, or they can skip whichever steps are unnecessary for them. Most people work through all of Hardware Identification in one or two shifts, but it is designed to be a "work at your own speed" experience. | ||
| − | Once a volunteer has completed or tested out of Hardware Identification they move on to '''System Evaluation'''. In System Evaluation the student sees how the computers fits together, sharpens up their hardware ID skills, learns some basic troubleshooting, and helps prep systems for build, culling out systems we do not want to keep. | + | Once a volunteer has completed or tested out of Hardware Identification they move on to '''System Evaluation'''. In System Evaluation the student sees how the computers fits together, sharpens up their hardware ID skills, learns some basic troubleshooting, and helps prep systems for build, culling out systems we do not want to keep. The student follows several flow charts that walk them through the triage and troubleshooting necessary to evaluate each system. |
| − | |||
== Hardware Identification Documentations == | == Hardware Identification Documentations == | ||
| + | Each lesson box builds on previous ones and contains a few lessons. Some are basic background information. Others are hands on exercises. | ||
; Box A | ; Box A | ||
| Line 42: | Line 42: | ||
== System Evaluation Documentations == | == System Evaluation Documentations == | ||
| + | Starting with the main overview flow chart, the volunteer works their way through. When they hit colored boxes they are directed to | ||
| + | |||
* [[System Evaluation Overview]] | * [[System Evaluation Overview]] | ||
* [[System Evaluation Visual Triage]] | * [[System Evaluation Visual Triage]] | ||
Revision as of 16:46, 12 June 2009
The first step in Free Geek's Build Program is called Prebuild.
Prebuild is divided into two main branches, Hardware Identification and System Evaluation.
Most people begin in Hardware Identification by signing up for a shift at the front desk. In Hardware Identification volunteers work through a series of lesson boxes -- each one teaching a basic skill that will later be needed in the build program. The boxes are generally arranged from most basic to more advanced. Each is available to the builder throughout the program, so any volunteer can refresh their memory as needed. People with enough hardware knowledge can test out of Hardware Identification, or they can skip whichever steps are unnecessary for them. Most people work through all of Hardware Identification in one or two shifts, but it is designed to be a "work at your own speed" experience.
Once a volunteer has completed or tested out of Hardware Identification they move on to System Evaluation. In System Evaluation the student sees how the computers fits together, sharpens up their hardware ID skills, learns some basic troubleshooting, and helps prep systems for build, culling out systems we do not want to keep. The student follows several flow charts that walk them through the triage and troubleshooting necessary to evaluate each system.
Hardware Identification Documentations
Each lesson box builds on previous ones and contains a few lessons. Some are basic background information. Others are hands on exercises.
- Box A
- All About Cards
- All about memory
- Card Sorting
- Cards
- Cards vs Memory
- Heat sinks
- Memory Sizing
- RAM Sorting
- What kind of memory is this?
- Box B
- Box C
- Box D
- Box E
- Box F
System Evaluation Documentations
Starting with the main overview flow chart, the volunteer works their way through. When they hit colored boxes they are directed to