|
|
|
|
|
|
|
|
|
 Posted: Thu Oct 12, 2006 5:34 pm
THIS THREAD LOCKED UNTIL FURTHER NOTICE
I apologize, but due to events in my life (most recently- my mother being hospitalized) I've had no time to work on any flowcharts. Due to other events (the loss and possible theft of my flashdrive) I've lost all work that I had done on flowcharts, meaning that this whole project will be delayed until an undefined future date. Much apologies.
Hello, and welcome to what will be an on-going project of mine for the next little while (along with a way for me to pass the time and hopefully distract myself during depressive days where nothing seems to go right) ^_^ I hope you enjoy this little addition to the guild.
So- let us begin. What is a flowchart? A flowchart is an image. It's more than that, though. It's an image with a beginning and one or multiple ends along with a trail which can be followed through simple yes or no questions to lead to the ultimate answer. It's usually used to determine exactly what something is based on gettig more and more specific. An example would be common charts in biology, asking questions like "Does it live on land" -> no -> "Does it have fins" -> yes -> "Does it have a dorsal fin?" -> yes -> "It's a shark"
So what's a Troubleshooting Flowchart? A Troubleshooting Flowchart is just a flowchart with ideas and suggestions for fixing common computing problems. It's NOT AT ALL a strict guideline. You don't have to follow its pattern step by step and, should situations deem it necessary, you may go against one of its steps. It's merely a guide. I'll be producing and posting these flowcharts (hopefully about one every other week) from now on. If you come to this thread, you can find the many Troubleshooting Flowcharts. These flowcharts of mine are copyrighted (2006 by Steven Barnett) however use and reproduction are explicitly allowed so long as due credit is given to the producer (i.e- me) of said material. In other words- feel free to copy these, put them on your own website, print them out and carry a folder of them, show them to your friends, or base a religion off of them. Just make sure that everyone knows I spent too many hours working on them mrgreen
If you wish to submit your own flowchart, you can PM or post one here in any format or style you desire and I'll re-create it in the common format that I'll be using on all of mine, then post it giving full credit to whomever sent me the flowchart. Know, however, that by allowing me to modify it to fit the common format and posting it you give me the rights to re-produce it under my own set standards and EULA, which shall be limitted only to the similar clause of free use with due permission given to the creator (in this case- whomever donates a flowchart).
Why all this legal stuff? Because this is a brilliant idea and I don't want anyone getting pissed if a company starts using these 3nodding
The first Troubleshooting Flowchart will be posted over the weekend. I had this plan last week and intended to get to work on it and post it, but a whole lot came up and I haven't been online (or even very productive) for the past week. I'm finally getting into a steady habit of work, though, so things should begin to bounce back for me soon. Expect Troubleshooting Flowchart 1 (Monitor Troubleshooting) by Monday ^_^
EDIT- Much delay in getting the flowchart >.< 3 large projects I gotta do over the weekend and lots of stress = bad working conditions. I got the flowchart half done and I'll totally get it finished and uploaded before the week is over, promise.
|
 |
|
|
|
|
|
|
|
|
|
|
|
|
|
Posted: Fri Dec 22, 2006 1:48 pm
ambrose_sallia THIS THREAD LOCKED UNTIL FURTHER NOTICEI apologize, but due to events in my life (most recently- my mother being hospitalized) I've had no time to work on any flowcharts. Due to other events (the loss and possible theft of my flashdrive) I've lost all work that I had done on flowcharts, meaning that this whole project will be delayed until an undefined future date. Much apologies.
Hello, and welcome to what will be an on-going project of mine for the next little while (along with a way for me to pass the time and hopefully distract myself during depressive days where nothing seems to go right) ^_^ I hope you enjoy this little addition to the guild.
So- let us begin. What is a flowchart? A flowchart is an image. It's more than that, though. It's an image with a beginning and one or multiple ends along with a trail which can be followed through simple yes or no questions to lead to the ultimate answer. It's usually used to determine exactly what something is based on gettig more and more specific. An example would be common charts in biology, asking questions like "Does it live on land" -> no -> "Does it have fins" -> yes -> "Does it have a dorsal fin?" -> yes -> "It's a shark"
So what's a Troubleshooting Flowchart? A Troubleshooting Flowchart is just a flowchart with ideas and suggestions for fixing common computing problems. It's NOT AT ALL a strict guideline. You don't have to follow its pattern step by step and, should situations deem it necessary, you may go against one of its steps. It's merely a guide. I'll be producing and posting these flowcharts (hopefully about one every other week) from now on. If you come to this thread, you can find the many Troubleshooting Flowcharts. These flowcharts of mine are copyrighted (2006 by Steven Barnett) however use and reproduction are explicitly allowed so long as due credit is given to the producer (i.e- me) of said material. In other words- feel free to copy these, put them on your own website, print them out and carry a folder of them, show them to your friends, or base a religion off of them. Just make sure that everyone knows I spent too many hours working on them mrgreen
If you wish to submit your own flowchart, you can PM or post one here in any format or style you desire and I'll re-create it in the common format that I'll be using on all of mine, then post it giving full credit to whomever sent me the flowchart. Know, however, that by allowing me to modify it to fit the common format and posting it you give me the rights to re-produce it under my own set standards and EULA, which shall be limitted only to the similar clause of free use with due permission given to the creator (in this case- whomever donates a flowchart).
Why all this legal stuff? Because this is a brilliant idea and I don't want anyone getting pissed if a company starts using these 3nodding
The first Troubleshooting Flowchart will be posted over the weekend. I had this plan last week and intended to get to work on it and post it, but a whole lot came up and I haven't been online (or even very productive) for the past week. I'm finally getting into a steady habit of work, though, so things should begin to bounce back for me soon. Expect Troubleshooting Flowchart 1 (Monitor Troubleshooting) by Monday ^_^
EDIT- Much delay in getting the flowchart >.< 3 large projects I gotta do over the weekend and lots of stress = bad working conditions. I got the flowchart half done and I'll totally get it finished and uploaded before the week is over, promise.
|
|
|
|
|
|
MoterMouth19 Vice Captain
|
|
|
|
|
|
|
|
|
|
|
|
|
Reply
