TroubleshootingUpdated Fri Sep 16 11:56:10 CDT 2016
I have now retired but will do occasional adjunct work for the Computer Systems and Networking Technology program at Arkansas State University-Beebe
I am still interested in the field and celebrate the addition of "Programming" back into the program.>
They have added Python, C, and the Java languages to the program.
Since I used to teach programming here (Assembly, Quick BASIC, and Visual BASIC) I look at this as a very positive thing. I will add some thoughts and links as I update this site.
Since from time to time there can be some problems with software (BUGS....) this site will speak to these issues too.
Last update Phil Hart Thu Sep 8 17:47:11 CDT 2016
This site is concerned with problems and answers to those problems. I taught Computer Troubleshooting at Arkansas State University - Beebe (ASUB). I also taught Intro to Hardware and Software, Intro to Microcomputer Programming, and Operating Systems (Linux). I also have taught Networking or as Cisco likes to call it Internetworking, Lan 1 (Microsoft Server: Active Directory), and Lan 2 (Microsoft Server: Infrastructure).
Prior to this I taught Electronics which evolved into Computer Electronics and then into non-existence. Electronics closed because we could no longer find students who were interested in it. Computers on the other hand have had an allure that attracted and still attract students.
But back to the reasons for this site. I will post links, downloads, and commentaries that I think useful to students and anyone else that is interested. Troubleshooting or problem solving is a wide and interesting area: and since we are unlikely to run out of problems a useful field of study
- Where it all begins to make sense!
- The Lab is where you can make your mistakes, learn the most from
those mistakes and gain the most confidence. "An expert in their field
is one who has made all the mistakes in a narrow area!"
One of the basic troubleshooting procedures is to replace a suspected bad module with a known good module. That is, if you suspect a hard drive as being bad replace it with on that you know is good (it works on another machine. If it works you've found the problem. If it doesn't keep searching. This technique works also with code. If a suspected bad module of code works when replaced by a known good module then you've found the problem. Unfortunately, it is sometimes hard to find a module of code that can be tested to simulate all of the variables in a live program.
I hope you find something useful in this site!