Sometimes my MultiFinder environment (and/or CommandShell) freezes up; how can I unfreeze it? Should I hit the Interrupt switch?
The “Cmd-Ctrl-e” (⌘-^-e) keypress will kill the current MultiFinder environment and “unfreeze” (and kill) your MultiFinder/CommandShell. Depending on whether your session-type is Console Mode or 32/24-bit, you will either get returned to the console or get returned to the Login screen. You should not press the Interrupt switch since this puts you into A/UX’s kernel debugger. If you have MacsBug installed (which is recommended) then you can press “Cmd-Ctrl-i” (⌘-^-i) to enter it. This may enable you to clean some things up before the MultiFinder environment is blasted (even just using ‘rs’ under MacsBug helps…). If MacsBug is not installed, the “⌘-^-i” behaves almost like a “⌘-^-e” except that it appears that A/UX doesn’t need to “rebuild” your icon/Desktop “environment” the next time Mac-mode is entered. To make sure that MacsBug installs correctly, it’s name must be ‘MacsBug’. A munged Debugger Prefs file can also prevent MacsBug from installing. This happened to me when upgrading t
Related Questions
- Can I use the PF2 in the environment C and D without applying the External NightShot Switch Method or Internal Microswitch Method?
- Can I use the PF1 in the environment A and B without applying the External NightShot Switch Method or Internal Microswitch Method?
- Sometimes my MultiFinder environment (and/or CommandShell) freezes up; how can I unfreeze it? Should I hit the Interrupt switch?
