Xref: utzoo comp.sys.amiga:24515 comp.sys.amiga.tech:2259 Path: utzoo!yunexus!geac!syntron!jtsv16!uunet!husc6!rutgers!mcnc!ecsvax!paleo From: paleo@ecsvax.uncecs.edu (Constantine A. LaPasha) Newsgroups: comp.sys.amiga,comp.sys.amiga.tech Subject: Sick Amiga 1000 - HELP - Keywords: gurus, gurus, gurus ... hardware problem? Message-ID: <5654@ecsvax.uncecs.edu> Date: 25 Oct 88 00:57:59 GMT Article-I.D.: ecsvax.5654 Organization: UNC Educational Computing Service Lines: 90 :{ HELP... I've just started having guru visitation problems on my Amiga 1000 system. After several hours, I get lots of gurus fairly regularly, seemingly independent of what software I am running, and independent of what I am doing, or not doing - it will sometimes guru just sitting there in the CLI. I'm requesting suggestions, and opinions as to the source/cause of these problems. (PAL grounding? chips with thermal problems? chips not seated properly? ...) system hardware configuration: Amiga 1000 - 512K internal (circa Nov. 1985) (rev 6 motherboard, rev 3 small board) Amiga 3.5" external floppy drive Microbotics StarBoard - 2M Amiga 1300 genlock DigiView - (sometimes) Sony Trinitron 12" monitor basic system software config: KS 1.3 AmigaDos 1.3 qMouse 1.3 csh 2.07M... or ... KS 1.3 AmigaDos 1.3 Mach csh 2.07M... or ... KS 1.2 AmigaDos 1.3 Mach csh 2.07M... or ... KS 1.2 AmigaDos 1.2 (+ARP) Mach csh 2.07M conman ... Symptoms: Turn on the system and boot. After a while, generally a few hours... guru# 00000003. or # 00000004. or # 00000005. the 03. guru seems to predominate. the 03 and 04 gurus often alternate -- last few gurus (within the last 20 minutes) were: #00000003.0020F890 #00000004.002038F0 #00000003.00200E8A #00000003.0025E858 #00000003.002038F0 #00000004.002038F0 #00000004.0020F8B0 It doesn't seem to matter what I'm running. When the problems start, the guru visitations seem to come fairly regularly, even after rebooting or power down and cold starting. The problems started soon after I started using 1.3, but does not seem to be connected to 1.3 since I can cold start with the same 1.2 configuration I had been using for months, and still get frequent guru visits. The problems got much worse when I moved the system to do some demos for some visiting researchers. (don't gurus make great impressions when you're trying to show off a system :-( After some tinkering, I got the system to stabilize after reseating the 2M board. The next day, doing demos of DigiView, DigiPaint, Dpaint ... for our local users group at a local computer show - the system started acting up again after running fine for about 3-4 hours. Again, it seemed to be a problem with the 2M board coming off line. Since then I've carefully cleaned the whole machine, and I've gotten the 2M board secured properly. Now, I have no problems with the memory going off line, but I still get lots of gurus after the machine has been running for a few hours. I ran the mem test that came with the starboard (after tracking down a copy of KS 1.1 :) and the 2M board tested ok according to their test program. So far, I haven't done any internal modifications on the 1000. ???? Anybody have any suggestions on what might be the trouble, or what I should try next? The most annoying thing, is that the trouble persists using the same software that I've been using for months without previous problems. Could it be something other than hardware? If hardware, what's the most probable problem? Should I try tracking it down further, or haul it to the techs at my dealer? (these guys are real good, and very helpful). Any assistance would be greatly appreciated. Thanks in advance. (Ahh...got the ol' CP/M machine out to use online till I get Amy fixed up - what nostalgia! Just like working with my fossils :) -- === If at first you don't succeed, hire a grad student... === Kostya LaPasha paleo@uncecs.edu or paleo@ecsvax.uncecs.edu === NCSU takes no responsibility for anything above ===