Everything is backed up via CCC (Carbon Copy Cloner).
Do you think a hard drive going bad would cause the mouse (actually the cursor) to hang up?
Only if it is silently corrupting data on the paging path and part of WindowServer or the kernel got swapped out.
I'm assuming this is Mac OS X. If you are still running Mac OS 9, all bets are off.
Freezes of the cursor are generally caused by one of the following
- Extreme paging pressure.
Diagnosing: Is the hard drive thrashing? If so, wait a few minutes and see if the machine comes back to life. If so, some application probably pigged out on RAM and subsequently crashed.
Fixing: Figure out what app did so and stop using that application. Either that or buy more RAM.
- Dirty mouse ball or other mouse failure.
Diagnosing: Does the computer freeze, or just the mouse? Try using keyboard navigation, e.g. command-tab to switch applications.
Fixing: Replace the top case (laptop) or mouse (desktop).
- Bad OS installation.
Diagnosing/Fixing: Do an archive and install of the OS. Sounds like the store tried that, hence your missing printer drivers.
- Bad RAM.
Diagnosing: Remove half the RAM. See if problem goes away. If problem persists, put in the other half. If problem persists, find more RAM from another machine just to be sure. This is the cause of 99% of all freezes and crashes in my experience.
Fixing: Replace bad RAM
- Bad CPU or improper CPU to heat sink contact.
Diagnosing/Fixing: Swap the CPU. (The heat sink comes with the CPU as a module, so don't try separating them unless it is out of warranty.)
- Bad motherboard.
Diagnosing/Fixing: If none of the above cured the problem, swap the motherboard.
My guess would be either bad RAM or a thermal problem with the CPU. If it is the hard drive, you can find out easily. In Terminal, type:
ioreg -l -w 0
That's a zero, BTW. Then, do a command-f (find) and search for disk0. you should see something like this:
| | | +-o ST9160821AS Media <class IOMedia, registered, matched, active, busy 0, retain count 10>
| | | | {
| | | | "Leaf" = No
| | | | "Writable" = Yes
| | | | "BSD Minor" = 0
| | | | "IOBusyInterest" = "IOCommand is not serializable"
| | | | "Preferred Block Size" = 512
| | | | "BSD Major" = 14
| | | | "BSD Name" = "disk0"
| | | | "Size" = 160041885696
| | | | "Content Hint" = ""
| | | | "Removable" = No
| | | | "IOMediaIcon" = {"IOBundleResourceFile"="Internal.icns","CFBundleIdentifier"="com.apple.iokit.IOStorageFamily"}
| | | | "BSD Unit" = 0
| | | | "Ejectable" = No
| | | | "Content" = "GUID_partition_scheme"
| | | | "Whole" = Yes
| | | | }
| | | |
Look at the node right above it. It should look like this:
| | | +-o IOBlockStorageDriver <class IOBlockStorageDriver, registered, matched, active, busy 0, retain count 7>
| | | | {
| | | | "IOMatchCategory" = "IODefaultMatchCategory"
| | | | "IOGeneralInterest" = "IOCommand is not serializable"
| | | | "IOClass" = "IOBlockStorageDriver"
| | | | "Statistics" = {"Errors (Read)"=0,"Total Time (Write)"=103178178485,"Latency Time (Read)"=0,"Bytes (Read)"=201591296,"Latency Time (Write)"=0,"Retries (Read)"=0,"Bytes (Write)"=373583872,"Errors (Write)"=0,"Operations (Read)"=10362,"Retries (Write)"=0,"Operations (Write)"=13888,"Total Time (Read)"=106339091965}
| | | | "IOProviderClass" = "IOBlockStorageDevice"
| | | | "CFBundleIdentifier" = "com.apple.iokit.IOStorageFamily"
| | | | "IOPropertyMatch" = {"device-type"="Generic"}
| | | | "IOProbeScore" = 0
| | | | }
| | | |
If the error count is nonzero, you have a failing drive. Note, however, that this is only the error count since the last reboot, so checking it once may not be enough to notice a problem.