gt0t+@andrew.cmu.edu (Gregory Ross Thompson) (11/29/89)
I've got a few questions: 1) Why is the event manager called when the GS is powered up? 2) If it's not, then why do I get Fatal System Error $0682 (emBadQHndlErr) when I power up on certain occasions? Here's what happens: If I power up my CMC hard drive, and then power up the GS, everything is peechy. If I then turn off the GS, and turn it back on without powering the drive down, then I get the fatal system error before the computer even does anything. Can anyone out there help? -Greg T.
4156an@GMUVAX.GMU.EDU (12/01/89)
gt0t+@andrew.cmu.edu (Gregory Ross Thompson) writes: [stuff omitted] > 2) If it's not, then why do I get Fatal System Error $0682 > (emBadQHndlErr) when I power up on certain occasions? > > Here's what happens: If I power up my CMC hard drive, and then > power up the GS, everything is peechy. If I then turn off the GS, and > turn it back on without powering the drive down, then I get the fatal > system error before the computer even does anything. Funny... same thing happens to me, although I never went and isolated it to being a problem of whether or not the hard disk(s) were turned on (I have three; two SCSI and one CMS). The error is either an $0681 or $0682. Only way to get the system unlocked is to initiate a self-test (OA/Option/Ctrl/RESET), and then immediately abort it (Ctrl/RESET) -- works fine after that. Furthermore, the error isn't consistant -- it strikes on about 50% of power-ups. The only GOOD news about your report, Greg, is that now I know it's NOT my motherboard giving me troubles. ;( Anyone else having this problem? Joseph F. Schober, Sysop, StarPort BBS [703/931-0947 - 3/12/2400] UUCP: crash!gnh-starport!jschober ====================== ARPA: crash!gnh-starport!jschober@nosc.mil Amer-Online: JSchober INET: jschober@gnh-starport.cts.com infrequently->CompuServe: 72727,2765 4156an@gmuvax.gmu.edu ======================
gt0t+@andrew.cmu.edu (Gregory Ross Thompson) (12/01/89)
4156an@GMUVAX.GMU.EDU writes: > gt0t+@andrew.cmu.edu (Gregory Ross Thompson) writes: > [stuff omitted] [ more stuff omitted ] > Funny... same thing happens to me, although I never went and isolated > it to being a problem of whether or not the hard disk(s) were turned on > (I have three; two SCSI and one CMS). The error is either an $0681 > or $0682. Only way to get the system unlocked is to initiate a > self-test (OA/Option/Ctrl/RESET), and then immediately abort it > (Ctrl/RESET) -- works fine after that. Furthermore, the error isn't > consistant -- it strikes on about 50% of power-ups. Yeah, I have (at times) had it power up fine, but it usually (more than 50% for me) gives me the error, and it's always $0682. Can any of you Apple guru's out there explain what the computer is doing with the event manager when you power up, and why it crashes with that error? [stuff omitted] > Joseph F. Schober, Sysop, StarPort BBS [703/931-0947 - 3/12/2400] > > UUCP: crash!gnh-starport!jschober ====================== > ARPA: crash!gnh-starport!jschober@nosc.mil Amer-Online: JSchober > INET: jschober@gnh-starport.cts.com infrequently->CompuServe: 72727,2765 > 4156an@gmuvax.gmu.edu ====================== -Greg T.
paul@pro-europa.cts.com (System Administrator) (12/04/89)
In-Reply-To: message from gt0t+@andrew.cmu.edu > Here's what happens: If I power up my CMC hard drive, and then > power up the GS, everything is peechy. If I then turn off the GS, and > turn it back on without powering the drive down, then I get the fatal > system error before the computer even does anything. I get the same thing. I always thought it was because my IIgs shares my CMS SCSI drive with my //e and that might be causing the problems but I disconnected the //e and it still does the same thing. What's the deal? | UUCP: [ucsd, nosc] !crash!pro-europa!paul | "All that is necessary for the | | INET: paul@pro-europa.cts.com | triumph of evil, is for good | | ARPA: crash!pro-europa!paul@nosc.mil | men to do nothing." |
SELLSWORTH@HMCVAX.CLAREMONT.EDU ("Scott, part time fuzzy") (12/04/89)
>gt0t+@andrew.cmu.edu (Gregory Ross Thompson) writes: >[stuff omitted] >> 2) If it's not, then why do I get Fatal System Error $0682 >> (emBadQHndlErr) when I power up on certain occasions? >> >> Here's what happens: If I power up my CMC hard drive, and then >> power up the GS, everything is peechy. If I then turn off the GS, and >> turn it back on without powering the drive down, then I get the fatal >> system error before the computer even does anything. >Funny... same thing happens to me, although I never went and isolated >it to being a problem of whether or not the hard disk(s) were turned on >Anyone else having this problem? > Joseph F. Schober, Sysop, StarPort BBS [703/931-0947 - 3/12/2400] Yep. Happens to me too, but I have one CMS HD and the CMS SCSI card. Explanation I heard was that the running drive leaks enough power to the card when the computer is off to prevent the memory from being cleared properly. I have not had the motivation to get out the VOM and track this down, but it seems plausible. Perhaps someone (like maybe me?) should try keeping the computer off for varying lengths of time to see if there is a correlation. For about a month, I was contantly reseating my SCSI card, as I thought that was the problem. Since I turned everything off when I did that, of course it worked fine. Sigh. Scott SELLSWORTH@HMCVAX sellswor@jarthur.claremont.edu
gt0t+@andrew.cmu.edu (Gregory Ross Thompson) (12/07/89)
paulh@nuchat.UUCP (Paul Hutmacher) writes: >In article <14A4BCA8BA5FC00B85@HMCVAX.BITNET> SELLSWORTH@HMCVAX.CLAREMONT.EDU\ >("Scott, part time fuzzy") writes: >>>gt0t+@andrew.cmu.edu (Gregory Ross Thompson) writes: >> >>>[stuff omitted] [even more stuff omitted] > It won't work. You can keep your computer off for a month and as long as you > leave the drive on you'll get the same error. The leaking current sounds > like a good excuse but we need a cure. I hate to think of the wear and > tear on my drive by shutting it down all the time to turn on my IIgs after > having it off for awhile. > > Until a fix is found I use the tried and true Control-Option-Open Apple- > Reset to put it in self test and then a quick Control-Open Apple-Reset. Would putting a toggle switch, or a simple button, in the cable leading from the drive to the computer fix the problem? Lemme re-state that. What I mean, is put a small button that is usually in the on position in the power wire leading from the drive to the card, and when you power down, all you gotta do is his the button momentarily to kill power, then release and reboot. Would it work? If not, what would keep it from working? -Greg T.