mweasner@trwrb.UUCP (Michael L. Weasner) (12/06/86)
Question for you Mac hardware gurus. I had my 512K Mac upgraded first to the 512KE and then a month later to the full MacPlus configuration. Shortly thereafterward, it started rebooting on its own. No, it wasn't a too long programmer's switch -- in fact, the dealer never did figure out what was wrong and just replaced the analog board, the logic board, and the 800K drive. No rebooting problems since but now something new has started. About every fourth or fifth time I insert a disk into the internal 800K drive, the system bombs. Usually I get an ID=02 but occasionally an ID=28. The inserted disk IS NOT ACCESSED before the bomb. In fact, the bomb seems to occur right after the disk is grabbed and seated. It almost seems like a mechanical problem and not software. I am running System 3.2 and the bombs have occurred in the Finder and just about any other program. And it doesn't matter whether I have booted from a floppy or from the hard disk. This really makes backing up the hard disk onto floppies a frustrating experience. Does anyone know what the problem is? I am reluctant to take the Mac back to the dealer until I have a better idea of what is wrong. Any help appreciated. Mike Weasner
suhler@im4u.UUCP (Paul A. Suhler) (12/09/86)
In article <1454@trwrb.UUCP> mweasner@trwrb.UUCP (Michael L. Weasner) writes: >Question for you Mac hardware gurus. I had my 512K Mac upgraded first to the >512KE and then a month later to the full MacPlus configuration. Shortly >thereafterward, it started rebooting on its own...... I've been in the habit of letting my Mac run all day while I'm gone to save wear and tear due to power cycling; I always leave the Idle DA running to save the screen. Since having my 512k Mac upgraded to a Mac+, though I found that maybe once a week I'd come home to find the bomb notice on the screen, usually a 02, I believe. Sometimes it happens after I stop Idle and try open an application, but always after it's been idling for a while. Any causes or cures? Flakey memory chips? (There are more of them now.) Problems with Idle or New Idle?
planting@rsch.WISC.EDU (W. Harry Plantinga) (12/09/86)
> Question for you Mac hardware gurus. I had my 512K Mac upgraded first to the > 512KE and then a month later to the full MacPlus configuration. > About every fourth or fifth time I insert a disk into the internal 800K drive, > the system bombs. In fact, the bombs occur right after the disk is > grabbed and seated. I had the same problem, and it got worse. Eventually, *every* disk insertion caused a crash. I started getting other crashes, too. On a hunch I took the cover off the mac, and I haven't had any crashes since. It seems to have been a heat-related problem. (I wonder if the culprit is the disk controller chip? I have a scsi port adapter (Supermac's) that covers some chips back there.) Harry Plantinga planting%colby.wisc.edu {allegra,seismo,ihnp4,heurikon}!uwvax!planting
werner@ut-ngp.UUCP (12/11/86)
In article <1454@trwrb.UUCP> mweasner@trwrb.UUCP (Michael L. Weasner) writes: >Question for you Mac hardware gurus. I had my 512K Mac upgraded first to the >512KE and then a month later to the full MacPlus configuration. Shortly >thereafterward, it started rebooting on its own...... if I remember right, there were problems with new Mac+ case where the RESET switch would get stuck and ....
howard@amdahl.UUCP (Howard C. Simonson) (12/13/86)
On the subject of "kinetic bombs"; I used to drag the Mac back and forth
between home and work a lot. I think all the travelling started to take
its toll on the machine because one day I banged on the desk (in frustration
that had nothing to do with the mac :-) and managed an "02" bomb. I found
tapping the case had a similiar effect. Being somewhat hardware oriented,
I took it home, opened it up, and did the first line of defense: I reseated
all the chips in sockets between the motherboard and the Monstermac board.
Of course this meant reseating the Monstermac board as well (its a pre-clipon
upgrade). Problem solved. I haven't bombed for this reason since.
P.S. When I had the Levco SCSI port added on, the guy put a new set of
socketing pins in that are supposed to be better; at no request of
mine. They may be adding to the stability of the machine since it
still has occasion to travel and problems have not arisen.
P.P.S. I too have been running the Mac 24x7 for sometime to avoid wear-n-tear
via power cycling and for availability reasons. I am pleased to
say that the Mac has been running this way for nearly a month.
I have never yet come home to a bomb on the screen. I use the
Blackout FKEY to save the screen (can't waste those valuable DA slots).
The only strange thing that has happened was some sort of static type
buildup once that seemed to ocurr on the screen. It was a sort of
flash/snap/bomb, but it only happened once so I attribute it to
balled lightning :-).
P.P.P.S. I only recommend running 24x7 if you have a Dataframe or similiarly
quiet disk, or a soundproof room in your house.
P.P.P.P.S. I absolutely abhore people who extend Post Scripts (except Abobe:-)
--
"What it boils down to is that when Howard C. Simonson
you have a problem you want a solution." ...{hplabs,ihnp4,nsc}!amdahl!howard
<MacMemory ad/Nov. Macworld> (very profound guys, now mug for the camera...)
[ A disclaimer for this messages is on file in my elevator and may be viewed
Monday thru Friday between the hours of 9-5 and between floors 3 thru 11 ]wmartin@ut-ngp.UUCP (Wiley Sanders) (12/14/86)
In article <4599@amdahl.UUCP> howard@amdahl.UUCP (Howard C. Simonson) writes: >one day I banged on the desk (in frustration >that had nothing to do with the mac :-) and managed an "02" bomb. Same thing happened with me - what you'd expect with my 128-512K memory upgrade with cheapo chip sockets. I've returned to my office to find the Mac crashed, too. My problem is MacKermit-related. Kermit doesn't do a very good job of closing the serial port. My modem is connected and on all the time (with S0=0). Once the phone rang, the modem sent "RING" to the RS422, and the Mac crashed! -w