Problem: 1. Slot-loading iMac running MacOX 10.2.4. One night AppleWorks 6.2 running perfectly. The next day hardly running at all: spinning black & white beachballs, MacOS 10 beachballs, Nothing much else happening, Eventually the icons appear in the Starting Points window, but nothing is active. Documents, when double-clicked, eventually load, but are unusable because of all the beachballs. Process Viewer and Top both show that AppleWorks is using up to 94% of the CPU during all of this. 2. The same copy of AppleWorks runs perfectly in MacOS 9.2.1.
Solutions tried: 1. Run a different version version of AppleWorks (6.2.7) from an external drive 2. Upgrade user's version to 6.2.4 3. Uninstall AppleWorks completely, including all preference files. Reinstall AppleWorks 6.2 and upgrade to 6.2.4. 4. Upgrade MacOS X 10.2.4 to 10.2.6 5. reset PRAM None of these measures had any effect whatsoever. AppleWorks still insists on claiming huge amounts of CPU, and won't do anything sensible. The only thing left to do, as far as I can see, is a clean install of MacOS X 10.2 and start again. Anyone out there with any other ideas? -- Peter Hinchliffe Apwin Computer Services FileMaker Pro Solutions Developer Perth, :::::::::::::::::::::::: Western Australia Phone (618) 9332 6482 Fax (618) 9332 0913 -------------------------------------------------------------------- Mac because I prefer it -- Windows because I have to. [Non-text portions of this message have been removed]
