2fmlcalls@kuhub.cc.ukans.edu (03/14/91)
Sorry if this has been beaten to death or if it's obvious. An app I'm working on runs fine under the Finder. Well, I thought I'd write my first WNE program for MultiFinder. It doesn't run under MultiFinder now. App unexpectedly Quit (1) - error. What does the 1 signify? Is that a standard code (i.e. Bus Error) or Multi's own? And what would cause it to unexpectedly quit? I've bumped my SIZE up to 1.5 meg to no avail. As well, under LSP 3.0 with a 1 meg Zone size for my App under Multi - no crashes or errors! Just the compiled code drops out. Under the Finder though it STILL works - just not Multi. I'm on a new si, 5 meg, 6.07 and the current v. of MultiFinder. INITs? PseudoFPU, and a couple others. Thanks in advance... john calhoun
bskendig@phoenix.Princeton.EDU (Brian Kendig) (03/14/91)
In article <29053.27dedb76@kuhub.cc.ukans.edu> 2fmlcalls@kuhub.cc.ukans.edu writes: >An app I'm working on runs fine under the Finder. Well, I thought I'd write >my first WNE program for MultiFinder. It doesn't run under MultiFinder now. >App unexpectedly Quit (1) - error. >What does the 1 signify? Is that a standard code (i.e. Bus Error) or Multi's >own? And what would cause it to unexpectedly quit? I've bumped my SIZE up to >1.5 meg to no avail. As well, under LSP 3.0 with a 1 meg Zone size for my App >under Multi - no crashes or errors! Just the compiled code drops out. Under >the Finder though it STILL works - just not Multi. I'm not sure what the (1) means (any other netters out there care to elucidate?), but the "Application unexpectedly quit" message means, simply, that your program had an error and crashed. The Macintosh was fortunately able to regain control, but the errant program might still have had a chance to romp merrily through memory and play with other other running programs, so the safest thing to do when you see this error is to reboot at the first chance. Your program is probably crashing into the limits set for it by Multifinder; either it got away with buggily writing to random memory addresses under the Finder because it had the run of the machine anyway, or you're just implementing Multifinder-awareness incorrectly. For a good introduction on how to do Multifinder-awareness (and lots of other Mac programming things), I'd suggest _The Macintosh Pascal Programming Primer_, or whatever it's called (by David Mark and Cartwright Reed?). The original Primer was written for C, but was so popular that a second C volume and this Pascal edition were written. Good luck! << Brian >> | Brian S. Kendig \ Macintosh | Engineering, | bskendig | | Computer Engineering |\ Thought | USS Enterprise | @phoenix.Princeton.EDU | Princeton University |_\ Police | -= NCC-1701-D =- | @PUCC.BITNET | "It's not that I don't HAVE the work to *do* -- I don't DO the work I *have*."
tagreen@bronze.ucs.indiana.edu (Todd A. Green) (03/15/91)
In article <7162@idunno.Princeton.EDU> bskendig@phoenix.Princeton.EDU (Brian Kendig) writes: >In article <29053.27dedb76@kuhub.cc.ukans.edu> 2fmlcalls@kuhub.cc.ukans.edu writes: >>the Finder though it STILL works - just not Multi. > >I'm not sure what the (1) means (any other netters out there care to >elucidate?), but the "Application unexpectedly quit" message means, According to memory, System Errors Table 3.0, and the numerous times my programs have bombed :), an error of (1) is a dsBusError. Todd ============================================================================== Todd A. Green "<_CyberWolf_>" ---> Pascal <- tagreen@ucs.indiana.edu Unix Systems Administration ---> Unix <--- tagreen@silver.ucs.indiana.edu Macintosh Systems Administration ---> VMS <---- tagreen@bronze.ucs.indiana.edu WCC Office:136.04 phone:855-0949 ---> C <------ tagreen@lothario.ucs.indiana "Friends don't let friends ---> Mac <---- tagreen@iubacs.BITNET Use DOS" - Scott Ostrander ---> SunOS <-- tagreen@lykos (FTP only) ==============================================================================