a499@mindlink.UUCP (Robert Salesas) (08/27/90)
Well, it also has been happening to me for a LONG LONG LONG time. It is a documented (at least I've talked to people who knew about it) bug. Just wait a while when you swap screens before you double-click or DC a little slower. Robert
vincelee@earthquake.Berkeley.EDU (Vincent H. Lee) (08/27/90)
Please help: My amiga crashes once in a while and I haven't found out why. It happens sometimes just when I double-click an icon on the Workbench and no other time. It has occurred with disk icons, drawer icons, .. all sorts. Anyway, just after I click the icon, the overscan area ABOVE the screen gets turns white, and the machine gurus. (usually 00000003 or 00000000b guru #'s). The overscan color changing seems weird to me. Has anybody else seen this? By the way, my system is very nonstandard--an A500 with 1Meg Chip, Lucas and Frances boards with 4Megs of 32-bit ram, and Kickstart in 32-bit RAM. I am also running a number of programs in the background. I haven't been able to isolate a cause as the repeatability of the crashes is intermittent. Can anyone help? Thanks in advance -Vince
ridder@elvira.enet.dec.com (Hans Ridder) (09/14/90)
In article <2948@mindlink.UUCP> a499@mindlink.UUCP (Robert Salesas) writes: >Well, it [system crashing when icon double-clicked - hgr] also has been >happening to me for a LONG LONG LONG time. It is a documented (at least >I've talked to people who knew about it) bug. Just wait a while when >you swap screens before you double-click or DC a little slower. Documented, eh? I had an A500 doing this once. It turned out to be a bad CIA (8520?). Try swapping the two CIA's and see if the problem goes away/changes. When it happened to me, I asked the 'NET, and someone said that the workbench uses some "beam sync'ed blits" which use a timer in one of the CIA's. Sorta made sense. Give it a try. >Robert -hans ------------------------------------------------------------------------ Hans-Gabriel Ridder Digital Equipment Corporation ridder@elvira.enet.dec.com Customer Support Center ...decwrl!elvira.enet!ridder Colorado Springs, CO
jms@tardis.Tymnet.COM (Joe Smith) (09/19/90)
In article <2948@mindlink.UUCP> a499@mindlink.UUCP (Robert Salesas) writes: >Well, it [system crashing when icon double-clicked - hgr] also has been >happening to me for a LONG LONG LONG time. One way to crash an Amiga in a colorful way is to modify a "tool" or "project" icon and change one byte to make it look like a "disk" or "drawer" icon. If you double-click on that icon, WorkBench will attempt to read the nonexistent window parameters from that icon file, stomp on low memory, and cause the blitter to make pretty garbage on the screen. If you're lucky, the lights on all the floppies and the modem will flash in a syncopated rhythm and the audio ports go "gurk gurk gurk" before it crashes. Like most "corrupted copper-list" crashes, it is quite spectacular. -- Joe Smith (408)922-6220 | SMTP: jms@tardis.tymnet.com or jms@gemini.tymnet.com BT Tymnet Tech Services | UUCP: ...!{ames,pyramid}!oliveb!tymix!tardis!jms PO Box 49019, MS-C41 | BIX: smithjoe | 12 PDP-10s still running! "POPJ P," San Jose, CA 95161-9019 | humorous dislaimer: "My Amiga speaks for me."
vincelee@tornado.Berkeley.EDU (Vincent H. Lee) (09/22/90)
In article <1228@tardis.Tymnet.COM> jms@tardis.Tymnet.COM (Joe Smith) writes: >In article <2948@mindlink.UUCP> a499@mindlink.UUCP (Robert Salesas) writes: >>Well, it [system crashing when icon double-clicked - hgr] also has been >>happening to me for a LONG LONG LONG time. > >One way to crash an Amiga in a colorful way is to modify a "tool" or It seems that an early reply to my particular problem seems to be correct. (the one that described how workbench used an 8520 timer to sync its blits). Anyway, I swapped my 8520's (with each other) and the problem seemed to go away. Weird. -Vince
ken@cbmvax.commodore.com (Ken Farinsky - CATS) (09/24/90)
In article <1990Sep21.231202.20501@agate.berkeley.edu> vincelee@tornado.Berkeley.EDU (Vincent H. Lee) writes: > >It seems that an early reply to my particular problem seems to be correct. >(the one that described how workbench used an 8520 timer to sync its >blits). Anyway, I swapped my 8520's (with each other) and the problem >seemed to go away. Weird. Note that if swapping your 8520s fixed a problem, then one of them is probably bad. You should figure out which has the problem and replace it (or replace both if unsure.) Continuing to run in your present configuration could lead to intermittent bugs. -- -- Ken Farinsky - CATS - (215) 431-9421 - Commodore Business Machines uucp: ...{uunet,rutgers}!cbmvax!ken bix: kfarinsky
ridder@elvira.enet.dec.com (Hans Ridder) (09/27/90)
In article <1990Sep21.231202.20501@agate.berkeley.edu> vincelee@tornado.Berkeley.EDU (Vincent H. Lee) writes: >It seems that an early reply to my particular problem seems to be correct. >(the one that described how workbench used an 8520 timer to sync its >blits). Anyway, I swapped my 8520's (with each other) and the problem >seemed to go away. Weird. That was my reply, glad it helped. As has already been mentioned, you probably want to replace the bad 8520, since it is probably breaking something else now that you moved it. My guess is that the bad chip is now CIA A, which I believe is marked "even" on the PC board. The symptoms might be that the time-of-day clock isn't working, or the timer.device isn't working. Although I imagine it's possible that the chip isn't being used in the same way as it was in the other position, so it might not be causing any harm. >-Vince -hans ------------------------------------------------------------------------ Hans-Gabriel Ridder Digital Equipment Corporation ridder@elvira.enet.dec.com Customer Support Center ...decwrl!elvira.enet!ridder Colorado Springs, CO