Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!zaphod.mps.ohio-state.edu!sdd.hp.com!spool.mu.edu!snorkelwacker.mit.edu!bloom-beacon!eru!hagbard!sunic!news.funet.fi!cc.tut.fi!cc.tut.fi!n67786 From: n67786@cc.tut.fi (Tero Nieminen) Newsgroups: comp.sys.mac.programmer Subject: Re: What's System Error 12, exactly? Message-ID: Date: 2 Apr 91 15:03:00 GMT References: <670554754.1@mmug.fidonet.org> Sender: n67786@cc.tut.fi (Tero Nieminen) Organization: Tampere Univ. of Technology, Finland. Lines: 32 In-Reply-To: Jim.Spencer@p510.f22.n282.z1.fidonet.org's message of 1 Apr 91 04:23:48 GMT In article <670554754.1@mmug.fidonet.org> Jim.Spencer@p510.f22.n282.z1.fidonet.org (Jim Spencer) writes: Eric Bowman writes in a message to All EB> Does anyone have any suggestions for what might cause a System EB> Error 12? IMII says it's an "Unimplemented Core Routine: An unimplemented EB> trap number was encounted." EB> It only happens inside a printing loop, on an app run over a EB> network, on a Mac Plus. Everything works fine on a Mac II, heap EB> scrambling or no. It's compiled for a 68000; written in MPW C++, EB> and compiled using C 3.2b1 (optimizer on -- might this be the EB> problem?) EB> Any suggestions would be greatly appreciated. I don't profess expertise but could you be calling a trap that is not provided on a Plus, like a Color QuickDraw routine? Compiling for a 68000 only means you won't use FPU instructions, etc., not that you won't call a ROM routine which doesn't exist on the target. You don't get a compile or link error because you have the correct interface files and libraries. More probably it's just some random data that the OS interprets as a nonexisting trap. It's gone haywire and riunning wild in the memory and this just happened to be the spot where OS begun doubting what's going on. -- Tero Nieminen Tampere University of Technology n67786@cc.tut.fi Tampere, Finland, Europe