Difference between revisions of "Computer Lab Problems"
Line 29: | Line 29: | ||
For example, if there is a hardware problem, failure to report the problem just delays the problem being fixed, and becomes someone else's problem... | For example, if there is a hardware problem, failure to report the problem just delays the problem being fixed, and becomes someone else's problem... | ||
− | |||
− | |||
== Procedure == | == Procedure == | ||
− | |||
− |
Revision as of 12:56, 17 May 2011
Types of Computer Lab Problems
Here are some examples that would represent a computer lab problem:
- Discovering a hardware problem upon entry to lab
- Discovering a messy lab upon entry to lab
- Encountering a problem during lab session including:
- Keyboard / Mouse not operating
- Data Display bulb warning (or not operating)
- Workstation not booting up
- Workstation monitor not working
- Workstation CPU not working
- User not able to log into workstation
- Application crashes during session
- Cannot connect to the Internet
- Computer system running VERY slow
There are other reasons to contact AVIT regarding the Computer Lab:
- Provide Feedback regarding effectiveness of Computer Lab
- Inquire regarding additional software (note: open-source software only allowed in Computer Lab)
- Provide suggestions to improve the Computer Lab
Reason for Reporting Computer Lab Problems
It is important to contact the AVIT department whenever there is a problem encountered in the Westminster Computer Lab.
For example, if there is a hardware problem, failure to report the problem just delays the problem being fixed, and becomes someone else's problem...