Line Trap (Type 9), Bad F-line Instruction (Type 10), and
Unimplemented Trap of Core Routine (Type 12) Errors
Probable Causes:
These three errors are closely related; all can involve the Macintosh's ROM (read only memory), where core operating system routines are stored. Any of these errors can occur when a request made for a routine that's in ROM could not be completed because the routine was unavailable. Typically, these errors are caused by older software that assumes an older version of ROM. The software in question could be an application or a system extension.
Bad F-line Instruction errors are also often related to a math co-processor (or FPU -- floating point unit). Some Macintosh models do not have an FPU, which is required by some applications.
These errors can also occur when the Macintosh model or the system software is too old for your application(s). While most software is written to be backward compatible (i.e., designed to work with older hardware models and system versions), it is not possible to be compatible with every Macintosh and system software version.
Possible Solutions:
Make sure your software is current and is compatible with your Macintosh model and system software.
Most software applications include system requirements in the documentation or on the outside of the box. If your configuration does not meet the minimum requirements, upgrade your configuration as necessary.
Similarly, if you are using an application that is more than one major version older than the current version (major versions being 2.0, 3.0, 4.0 and minor versions being 2.01, 2.2, 2.2.3, etc.), but your Macintosh model and system software are current, upgrade your application to the current version.
If your Macintosh model and system software meet or exceed the minimum requirements of your application, try troubleshooting the problem using the troubleshooting steps.
