Understand Bad F line error
The System Error Handler (sometimes referred to as "dire straits" manager and other more colorful names) has complained. Normally, when you execute a ROM routine it would be an $Axxx trap and that is how Apple implemented it. $Fxxx (thus F-line) are reserved for Motorola. Bottom line: you can't execute an $F trap. I would be surprised if you or the student intended to try to execute an $F trap. Most likely there is a bad branch (possibly based on an old pointer/handle) that points at a word of storage that just happens to start with $Fxxx. Many times the code is making assumptions about the availability of specific managers. Does the code do a Gestalt call and check that all necessary managers/features. Depending on the OS release, many ROM calls may not be available and making assumptions could cause errors much further down the road ( in execution terms). Also check any inline assembler. Hope this helps some.