Applejack: Getting New Features

Applejack, the command line troubleshooting utility for Mac OS X, is undergoing prerelease testing now for version 1.4.3rc3, which adds a new experimental expert mode. From the read me:

+ Experimental expert mode exists, but is currently hidden until it can be tested further. (see Appendix B). The only well-tested options at this point are the memory test using the included Memtest utility, and the option to disable auto login.

This is great, because among other neat features, it adds the memtest utility as well, which will save you the $1 download charge from its developer.

Memtest and Applejack are must-have utilities, IMHO. Memtest saved my butt on bad memory (via the GUI version in the form of rembr), whereas Tech Tool Pro told me my memory was fine. Wrong! Changed it out and my numerous problems went bye-bye!

Yojimbo 1.2 Quick Input Panel Crap (and .Mac syncing)

MacUpdate: Yojimbo Reviews: I like the app, but the Quick Input F-key keeps saying:

'Yojimbo could not communicate with the Quick Input Helper.'

Nothing I've tried seems to fix the error. (9/30/2006, Version: 1.2)

1 Reply To Review:

I finally fixed this problem. Solution: Close Yojimbo, move ~/Library/Application Support/Yojimbo to Desktop, reopen Yojimbo, close it again, return the above folder to its original position.

Now Quick Input Panel works again...go figure.

However, .Mac syncing hasn't worked. I'm hoping this will fix it too.

(10/10/2006, Version: 1.2)

Memory = the source of many problems!

For the last several months, I had numerous problems with my old G4 AGP dual 1.2, which has been as upgraded just about as far as it can go. The problems included recurrent program crashes (especially Safari) and random kernel panics.

I used a little utility called Rember and discovered that a few memory sticks I had were bad. Tech Tool Pro (grumble, grumble) did not catch these errors, so if you think you're having memory issues, please run another utility (apparently, the hardware test disc Apple ships with newer Macs can catch these problems too). You can also run Memtest (which is really the command-line basis of Rember); the author charges $1 to download it (very reasonable given that you can boot in single-user to test MOST of your RAM).

In my case, Memtest wasn't necessary. Rember caught the defective RAM right away, and I narrowed it down to 2 sticks by pulling them one at a time, restarting, and testing with Rember until the errors were gone.

I had 2 bad DIMMs--one at 128 MB and another at 512 MB. So I ordered 2 new 512 MB sticks from OWC (with lifetime warranty). The new memory checked out fine with Rember, and I've had no kernel panics or other major issues since installing it. The old Mac is rock-solid!

Now, how did this happen? I think a Tiger update somewhere down the line didn't agree with those two older RAM sticks. The lesson is to suspect bad RAM (or other hardware) if you're having weird crashes and random panics suddenly.

ATPM 11.08 - How To: Is Your Memory Failing?

ATPM 11.08 - How To: Is Your Memory Failing?:

Great information on testing your Mac's memory in single-user mode. Memory failure is a common kernel panic problem.

Here's another great link on the same subject at Macworld:

http://www.macworld.com/2006/02/features/speedmemory/index.php

inessential.com: Flash Crash? WebKit Crash? Both?

inessential.com: Flash Crash? WebKit Crash? Both?:

"2   ...romedia.Flash Player.plugin  

0x06b14140 Flash_EnforceLocalSecurity + 47880"

I've had recurring Safari crashes that are quite annoying. Most of them appear related to the Flash Player plug (both version 8 and 9 for OS X); they all appear similar to the crash report line above.

Apparently, it's a bug in Webkit, FLash, or some synergistic malfunction. Safari crashes about 5 or more times a day. And it's weird, because though it says it has crashed I still have to force quit Safari.

Crashing Finder on Find

If you discover the Finder crashing when you type in the little search box in the upper right corner of any Finder dialog box, it likely means you need to rebuild your Launch Services database, which is separate for each user. In most cases, Spotlight still functions, but Finder finding doesn't.

Notice lines 2-5 in the crash report: Exception: EXC_BAD_ACCESS (0x0001) Codes: KERN_INVALID_ADDRESS (0x0001) at 0x70586e60 Thread 0 Crashed: 0 ...ple.CoreServices.CarbonCore 0x90b99530 CSStoreGetUnit + 56 1 com.apple.LaunchServices 0x91936754 _LSBindingListGetEntryWithClass + 44 2 com.apple.LaunchServices 0x9193667c _UTTypeSearchConformsToTypesCore + 92 3 com.apple.LaunchServices 0x919365ec _UTTypeSearchConformsToTypes + 64 4 com.apple.LaunchServices 0x91936588 _UTTypeConformsTo + 56 5 com.apple.LaunchServices 0x9193ee80 UTTypeConformsTo + 228 6 com.apple.finder 0x002734fc dyld_stub_OpenADefaultComponent + 504460 7 com.apple.finder 0x001c9398 0x1000 + 1868696 8 com.apple.finder 0x001cab64 0x1000 + 1874788