profile for composer++ (_highly_ recommended), let's say forComposerPlusPlus. Then launch composer with
c:\composer\mozill -editor -p forComposerPlusPlus
and it should work fine.
I think my problem was having another mozilla.exe process. Thus, mozilla not liking to have more than one profile open at one time would launch the browser suites version of composer.
I think it would be worth noting on the composer++ page to 'dont have mozilla.exe running of the browser suite (seamonkey is more correct?) running when attempting to launch composer++'
-sime
