Like KesslerB, I got an error "incompatible cpu-subtype" from the dynamic loader (dyld) when trying to run memtest on a G3 (an iMac G3 in my case) with Tiger 10.4.2. Also like KesslerB, I did not get this error on the same machine under Panther 10.3.9. Many thanks for the work-around, B!

I wasn't able to figure out where this error is coming from. The project is built for the PowerPC, and with libraries statically linked. "otool -L" shows that the only dynmically linked libraries are /usr/lib/libmx.A.dylib (v. 92.0.0) and /usr/lib/libSystem.B.dylib (v. 88.0.0), so the problem must be in there somewhere. But where?

BTW, memtest did corroborate my suspicions about my RAM. A very, very useful program! As the documentation says, it's best to use memtest in single-user mode. That means typing one simple command instead of pointing and clicking. Most computer users should be able to survive it, if they just read the instructions (for a change).

A major benefit of the single-user mode approach is that your file system can remain read-only, and will not risk getting trashed by memory problems. This is no idle theorizing, but painful experience: I first started suspecting my RAM when my file system got badly corrupted and my only recourse was to erase and reinstall.