Misbehaving iBook - ignores mouse and won't sleep

gulliver

Registered
Previously posted - no success so here again...

I've a misbehaving iBook (clamshell G3 running 10.3.7/whatever's current).

Apple mouse regularly stops working after a while - then fine again after restart.

Also refusing to sleep - immediately wakes when slept.

I routinely/regularly/all the damn time run a repair sequence... run Disk Warrior and/or use Onyx to repair permissions, repair preferences, manually run the regular maintenance scripts... etc. Also zapped PRAM.

Problem soon returns.

Used Activity Monitor to quit all possible processes... shows trying to 'write out' - rate from 512b to 25kb. Why?

Airport is switched off. So is File Sharing.

On restart it gets to desktop then has kernel panic.
Second restart is fine - and mouse behaves... for awhile... then it's not recognised (works fine on other machines) (and other mice also won't work on the iBook), and when put to sleep (after quitting all apps) it immediately wakes and spins drive.

Suggestions appreciated. Please and thanks. (Perhaps I should go back to my Centris/OS7?)
 
Thanks, Bob.

Oh happy day - another 97meg download. Luckily I have a copy I d/l-ed earlier this week. I shall follow your tip.
 
Also, you might wanna check the RAM -- if you have multiple modules, try removing one (and later the other) and seeing if the machine "behaves" any better than before. Faulty RAM (even the stuff pre-installed by Apple is sometimes, but rarely, bad) is a leading cause of kernel panics.

Other than that, what kind of external devices do you have? Anything USB besides the mouse? What kind of mouse?
 
The memory was recently upgraded - I'll revert and see if there's a difference.
There's no externals and the mouse is the standard Apple USB.

Thanks.

Mouse problem is now even stranger - when the mouse stops working, if I immediately plug it into an iMac it works fine, but then won't work when immediately re-plugged back into the iBook - but the original mouse from the iMac will. hhhmmm... doesn't seem to suggest faulty mouse or usb socket.
 
Back
Top