It’s a new school year. This year, you have laptops, Chromebooks, a pod of desktops, and a cart of iPads. Your IT folk will do their best to support you, but you know–without a doubt–it will fall on your shoulders when the lesson is about to start and the computers don’t work.
Before you say words students shouldn’t hear, try these six quick solutions. You can even teach them to students:
Is Power on?
When you’re talking to tech folk, their first question always centers around whether your computer system is getting power. Surprisingly, this is often why it doesn’t work–I know, who would guess? Clear this as a reason before moving on by making sure all the working pieces are getting the power they need. Here’s a checklist:
- Are all plugs in wall sockets
- Are all cables connected to the computer? An easy way to check both of these: Is the power light on the keyboard and the monitor?
- Is the internet working? That has plugs too, so check those.
- Are headphones plugged in?
Are you logging in under your name?
Everyone knows to confirm their password, but few people think to check the log-in name. School computers are often shared, from carts or classroom pods. That means students log in with different user names. They’re supposed to log out, but that doesn’t always happen. The student having the problem may have forgotten to check. Make it part of the log-in routine–to check the user name.
This can even be the problem on your personal computer used at school. Someone might have accessed their online or networked account through your computer and forgotten to return it to your settings. If you can’t log in, or your desktop doesn’t have files and folders it should, check the log-in name. Is it you?
Try a different browser
All browsers are not created equally. I have a lot more problems with IE than Firefox and more with Firefox than Chrome. Yes, you counted right. I have three browsers on my computer because they are all quirky at times in their delivery of websites. If I can’t load a site in one browser, I try another. I don’t care WHY it won’t work in one if it works in another. All I care is that I got to the website. It’s become the first trouble-shooting tool I use when a website doesn’t work.
It’s not just me, either. It’s the Universe. You’ll often see suggestions on websites–Works better with the *** browser. Coding and scripts and stuff are different in different browsers, which makes them act differently on websites. That’s as technical as I can get about the reasons.
In the geek world, which browser is best is a hot topic. The only point Chrome and Firefox users agree on is they’re better than IE. Here are a few articles on this debate:
One other filter you can use in identifying the cause of tech problem is to try a different computer. If it works there, it means the problem is your system.
If something doesn’t work the first time, do it again. Why is this so often effective? It’s called ‘user error’. You typed a password in wrong, or left a blank space without even knowing it. This is why forms always ask you to type an email address twice. It’s not likely you’d have the same typo twice. Even websites are starting to recommend this. Learn from the experts and adopt ‘repeat’ as a viable solution for tech problems.
This works more often than you’d think, in my experience, at least half the time. Here’s why: When you turn your computer on, it goes through lots of organizing and prioritizing steps to get your desktop looking just the way you want it. Over time, that arranging gets undone by your activities. Pieces get lopped off, forgotten, like DNA mutations. Not your fault, just the way it is. The computer still works, but not quite the same.
When you shut down and reboot, it closes everything, stores them away, and then brings them back out in the proper order. Be sure you ‘shut down’ from the Start button (for Windows folk), not by pushing the power button.
Jacqui Murray has been teaching K-18 technology for 30 years. She is the editor/author of over a hundred tech ed resources including a K-12 technology curriculum, K-8 keyboard curriculum, K-8 Digital Citizenship curriculum. She is an adjunct professor in tech ed, Master Teacher, webmaster for four blogs, an Amazon Vine Voice, CSTA presentation reviewer, freelance journalist on tech ed topics, contributor to NEA Today, and author of the tech thrillers, To Hunt a Sub and Twenty-four Days. You can find her resources at Structured Learning.