afry@troi.cc.rochester.edu (Alan R. Fry) (06/01/91)
In article <1991May31.163624.3293@informatik.uni-ulm.de> bauer@first_next (Bauer Christian) writes: >We have the problem, that on all Mac II SI under System 6.0.7 the >mouse-cursor suddenly stops to respond to our real mouse-movement. Apple >(inofficially) says that it is a known bug. So after a ADB-Bus reset the >mouse works again normaly. To do so we used a keyboard macro to reset the >ADB-Bus with ADB-Probe. > >Some people tell me to reset the ADB-Bus by reinserting the mouse cabel >into the keyboard causing a ADB-Bus-Reset (I think that is not (!) >recommended due to a very sensible ADB-Bus DMA-Chip which is about $300 to >repair). > >Has anyone a clean solution by patching the wrong routine in system 6.0.7 or in ROM of the Mac II si? >Is this problem solved is System 7.0? > >Christian Bauer I don't know the solution (unfortunately), but I can echo your statement that unplugging and replugging the mouse is a *very bad* idea. I have seen a lot of fried ADB ports because of this. I have a similar problem on my SE/30 running 6.0.5. From time to time the keyboard will not be recognized on startup. The mouse works fine, so I am able to recover using ADB Probe (which seems to tell me that the ADB thought my keyboard was also a mouse - weird). This problem used to be a lot worse (i.e. in one in 3 reboots the keyboard would die), until I remove the F1-F4 init (which sets the F1-F4 function keys to cut, copy, paste, and undo). Now I only have the problem in maybe 1 in 20 reboots. I'm curious as to whether this is hardware or software. Anyone else have ADB mystery stories to tell? Alan -- -------------------------------------------------------------- Alan R Fry | You know what I hate? afry@uhura.cc.rochester.edu | Rhetorical questions --------------------------------------------------------------