MaBaSoft | Support


Home	News	Products	Downloads	Support	Registration	Contact us

Questions?

Find answers in our list of Frequently Asked Questions or, if you need more help, email us. We will be glad to help you.

	I can't use Stopwatch CSM because it is x-ed off in the Control Strip. What's wrong?
	I can't use Stopwatch CSM because it is x-ed off in Extensions Strip. What's wrong?
	I can't use Stopwatch CSM because it is dimmed. What's wrong?
	If I try to start the stopwatch I get the error message: "Sorry, the stopwatch couldn't be started because Stopwatch Engine is already in use by another module.". What's wrong?

	I use Extensions Strip as module host. Stopwatches display incorrect times at startup. What's wrong?
	I use Extensions Strip as module host. I checked the Reset stopwatch option, but stopwatches aren't reset at startup. What's wrong?

	I use ACTION GoMac as module host. Stopwatches display incorrect times at startup. What's wrong?
	I use ACTION GoMac as module host. I checked the Reset stopwatch option, but stopwatches aren't reset at startup. What's wrong?

I can't use Stopwatch CSM because it is x-ed off in the Control Strip. What's wrong?

A bug causes Stopwatch CSM 2.0 to be always inactive in the Control Strip if Extensions Strip is also installed. To solve the problem, download and install Stopwatch CSM 2.1.

I can't use Stopwatch CSM because it is x-ed off in Extensions Strip. What's wrong?

Stopwatch CSM 2.0 or later requires Extensions Strip 2.0bx. Upgrade Extensions Strip.

I can't use Stopwatch CSM because it is dimmed. What's wrong?

It isn't possible to run more Stopwatch CSM 2.0.x modules at one time. Therefore, if you have more Stopwatch CSM 2.0.x copies in your Control Strip Modules folder, one copy will effectively run and all other copies will be dimmed.

Similarly, if you have more module hosts installed, Stopwatch CSM 2.0.x will effectively run from one module host and be dimmed in all other module hosts. If you have more module hosts installed and wish to use Stopwatch CSM from a particular module host, please refer to the Installation chapter in the Stopwatch CSM Documentation file for installation guidelines.

If I try to start the stopwatch I get the error message: "Sorry, the stopwatch couldn't be started because Stopwatch Engine is already in use by another module.". What's wrong?

Stopwatch CSM 2.0 fixes this problem arising when Multiple Users is on and the owner of the computer selects the Start stopwatch at restart option. Download and install Stopwatch CSM 2.1 to solve the problem.

I use Extensions Strip as module host. Stopwatches display incorrect times at startup. What's wrong?

I use Extensions Strip as module host. I checked the Reset stopwatch option, but stopwatches aren't reset at startup. What's wrong?

Both problems are due to the fact that Extensions Strip 1.x.x does not "close" control strip modules at shutdown or restart. Upgrade to Extensions Strip 2.0bx.

I use ACTION GoMac as module host. Stopwatches display incorrect times at startup. What's wrong?

I use ACTION GoMac as module host. I checked the Reset stopwatch option, but stopwatches aren't reset at startup. What's wrong?

Both problems are due to the fact that ACTION GoMac doesn't "close" control strip modules at shutdown or restart. Stopwatch CSM 2.0 gets round this problem: download and install Stopwatch CSM 2.1.