rz@camcon.co.uk (Rob Zanconato) (10/10/89)
Can anyone help. A few months ago I purchased a second-hand MACII at what I thought was a good price (what a mug). Everything seemed to work OK except a few applications under multifider. This I put down to the applications not being Multifinder compatible, since they worked quite happily under the standard finder. However, I recently, installed THINK C 4.0 on the machine and tried to run the debugger (THINK C requires the multifinder). As the debugger started up the system immediately fell over with a system error ID=11. My first thought was that the system was corrupted, so I installed a new system. This didn't work. Next I reformated the disk and installed the system afresh. This again didn't work. After a long period of experimentation I found that the system only seemed to fall over when a BLEEP sound is made whilst running under multifinder. This could be invoked by changing the volume level in the control panel to a non-zero value. Also, if the sound volume was set many times in quick succession the system did not fall over until after the last BLEEP was heard. Resetting the PRAM before setting the sound volume allowed me to set the volume OK, but after re-booting the problem reappeared. I would like to take the machine in for repair, but here in England my local Apple dealer wants 90 pounds sterling (approx $150) just to test the machine. Has anyone any suggestions as to the cause (eg could it be the Lithium batteries going flat, or is it something worse). Does anyone know of any software that I can get hold of to do a hardware check myself. -- Roberto Zanconato | Phone: 0223 420024 Cambridge Consultants Ltd | International: +44 223 420024 Science Park, Milton Road | UUCP: ra@camcon.co.uk Cambridge CB4 4DW, England | or: rz@camcon.uucp
cp26+@andrew.cmu.edu (Christopher Thomas Parker) (10/11/89)
I left my System Errors DA on my Macintosh, (which I'm not using now) so I can't tell you what error ID=11 is, but it is possible that you don't have enough memory to run the THINK C debugger and the compiler at the same time (it occurs to me that the system should realize this and not let you run it, but I'm not sure how THINK C runs the debugger. Whether it tries to bypass the Finder/System or not would make a difference.) If anyone's got any ideas better than mine, then please post them. -CParker cp26+@andrew.cmu.edu "Yield to temptation - it may not pass your way again."
d88-jwa@nada.kth.se (Jon W{tte) (10/12/89)
In article <MZAXJo200Xo447d0co@andrew.cmu.edu> cp26+@andrew.cmu.edu (Christopher Thomas Parker) writes: >I left my System Errors DA on my Macintosh, (which I'm not using now) so >I can't tell you what error ID=11 is, but it is possible that you don't >have enough memory to run the THINK C debugger and the compiler at the The "Out of Memory" message is the all-known, all-feared System Error ID=25 (THAT one I know by heart from previously running with only 2 megs :-) 11 is "Miscallaneous Exception" (all other MC680x0 exceptions) and this is mostly jumps to undefined space and things... I guess there's something strange with your sound chip or sound driver. h+@nada.kth.se -- Have a nice day!