ali@rocky.STANFORD.EDU (Ali Ozer) (12/10/87)
--- A friend just got his rev 4.2 2000 yesterday and first tests indicate something's wrong with the machine. In the Workbench, attempting to drag icons (or sometimes even just activating them) fails in the following fashion: Within 20 pixels of motion, the icon drops back to the Workbench (without text) and further attempts to move it or activate any other icon fail. The pointer continues to function until one attempts to activate an intuition gadget (drag bar, right mouse button anywhere on the screen, etc). Here the pointer hangs (but you can still A-M/A-N) until a disk is inserted in any drive. Input events are stored while the pointer is hung and processed properly following the disk insertion. It's a vanilla 2000 with an external drive. And *any* workbench disk will do. Seems like someone (Intuition?) is leaving the layers locked; hence the pointer position is updated until an event requiring drawing on the locked layer occurs. It seems to miss a BLITTER_FINISHED signal during the drag, so it never thinks the drag is done so it never thinks to unlocklayer(). Please send any comments to me (ali@rocky.stanford.edu), or, better yet, if you can get it to work, to my friend Art (r.racer@lear.stanford.edu). Ali Ozer, ali@rocky.stanford.edu
bryce@hoser.berkeley.edu (Bryce Nesbitt) (12/10/87)
In article <818@rocky.STANFORD.EDU> ali@rocky.stanford.edu (Ali Ozer) writes: >--- >A friend just got his rev 4.2 2000 yesterday... >...attempting >to drag icons (or sometimes even just activating them) fails in the >following fashion: > >Within 20 pixels of motion, the icon drops back to the Workbench (without >text) and further attempts to move it or activate any other icon fail. The >pointer continues to function until one attempts to activate an intuition >gadget (drag bar, right mouse button anywhere on the screen, etc). Here >the pointer hangs (but you can still A-M/A-N) until a disk is inserted >in any drive. Input events are stored while the pointer is hung and >processed properly following the disk insertion. This is a problem with one of the 8520 I/O chips. The Amiga's power-on self-test does not check if all the timers operate. Commodore's final production line test might not either. Swap these chips, and if your problem changes to, say , the keyboard locking up, then you have your problem. Replace the bad chip. If this is *not* the problem, then there are two separate sets of problems that produce the exact same results. <my friend Art (r.racer@lear.stanford.edu). <Ali Ozer, ali@rocky.stanford.edu |\ /| . Ack! (NAK, SOH, EOT) {o O} . bryce@hoser.berkeley.EDU -or- ucbvax!hoser!bryce (") U WARNING: hoser's spool directory eats a *lot* of mail. :-(