Hi lothar56,
There are some available third-party resources for Mac OS errors, including websites (e.g., Rustle Laidman's
Apple Error Codes, which even offers a new discussion board) and shareware programs (e.g., Bleu Rose's
Black and Bleu utility, which tries to give detailed user-friendly explanations that go beyond Apple's notoriously terse descriptions).
Speaking of info straight from the horse's mouth, Apple's old TIL article
Mac OS System Error Codes: 0 to -261 (and the 'MacErrors.h' header-file from Apple's Universal Interfaces 3.3.x SDK) says that error number -110 is a "memory address error (address was odd or out of range)". (!) I believe that this error can also show up as a 'Type 2' error. AFAIK, it usually means that something has accidentally overwritten some executable memory-location. [How's that for a vague description? ;-)]
If your script applet uses a third-party scripting addition (OSAX), it could be that there's a bug in that OSAX. On the other hand, if you're just using "vanilla" AppleScript and the scriptable Finder, then perhaps there's a bug in AppleScript itself, or you might be the victim of an extensions-conflict of some kind. Which version of AppleScript (or the Mac OS) are you using? [Actually, an AppleScript bug isn't entirely out of the question. According to the
AppleScript SourceBook's subsection on AppleScript 1.5.5's fixed bugs, Mac OS 9.1 has fixed a known issue in AppleScript 1.4.x (Mac OS 9.0.x) and possibly earlier which might cause an applet to randomly crash if it had launched another applet at some point. I suppose a similar kind of bug could affect an applet when it quits...]
In any event, if you're already using Mac OS 9.1, and you still get the error after starting up with only the 'Base' extensions set, then I guess you could try bumping up the applet's preferred memory size, or running it from within Script Editor to see if you get the same error.
Regards,
--Paul
[This message has been edited by Paul Crawford (edited 03-08-2001).]
Top
