On my old XP daw, I tried stopping code meter in the start up group,
not just setting it to manual.
I also stopped it in services.
The result was that when I boot up and look in task manager,
processes, code meter is not running.
So, I open reason and it plays normally, all features I've discovered
so far working as usual.
I exit reason and the task manager shows code meter is running in
processes, but it's only consuming about 2400k.
Before I stopped both code meter service and stopped it in the start
up group, I often saw both Code meter.exe and code meter cc.exe
running after exiting Reason, and each was drawing over 4,000k, so
stopping them definitely makes a difference in my old ram starved
computer, and stopping them seems to have no drawbacks for running
Reason.
I'll bet, without knowing for sure, that if one found a way to
entirely prevent code meter from running when opening Reason, Reason
wouldn't run at all.
Stopping code meter in the start up group and in services does not
affect either running Reason as a demo, or running it with the license
dongle.
Everything works normally.
2400k of CPU drain is not much of a price to pay to get those Reason
sounds, I feel.
I have no proof at all that it harms anything else on the same hard
drive, but I'll still wait to get a separate drive just for Reason and
Reaper, maybe a few other little things, because I'd rather be
superstitious than sorry.
For roy, I find that I need to switch my PCR-300 on each time I boot
up, to get midi sent back to the PCR when it's hooked up with USB.
If I leave it switched to USB position; shut down and boot up, the PCR
sends midi out the USB cable, but it doesn't return to the PCR unless
I switch it on while the computer is running, so the PCR is recognized.
That's for Reason, anyway, don't know if it's the same behaveor for
Reaper and sonar yet.
Not much of an inconvenience to switch it to USB position, to get midi
to go both directions; just a little peculiarity.
Indigo L
