It was reported what was thought to be a conflict between RAMDoubler and ClarisWorks 3.x and 2.x. Neither application would launch while RAMDoubler was active. When the Kensington Turbo Mouse software was updated to version 4.02 or later, both versions of ClarisWorks launched with RAMDoubler enabled.