Are all these InterVideo processes needed with MF6?

[Alan Mintaka]

Hi Everyone,
Now that I've finally gotten MF6 installed, I've been noticing a number of performance hits even when I'm not running the program. I looked around and found a number of processes that Intervideo was running in the background at all times.

There were also some startup items I'm not interested in running at all; when they're loaded into memory (assuming they're not there already). I was wondering if anyone knew what they are and why we need them with MF6. Here's the short list:

iviRegMgr - process always in memory, highest CPU usage when no foreground apps are running. I left this one alone for the time being.

DevSvc - ?? another process that's always in memory even when no MF6 or Intervideo apps are running. This one I also left alone for now.

InterVideo WinCinema Manager (WinCinemaMgr.exe) - doesn't appear in memory by that name but is run from my Startup group when WinXP starts. Why could I possibly need this? Does it support MF6 somehow? For now I've moved it to another folder. I'll move it back to Startup if I decide I need it.

QuickTime Task (qttask.exe) - this shows up because the MF6 installer also installed QuickTime. This has nothing to do with MF6 or Intervideo and always shows up every time QuickTime is installed by something. AMong other things it checks for an update on the internet every time Quicktime is launched, and displays a bothersome prompt if an update is available. Naturally I trashed it using the Registry Editor (regedit.exe).

Installshield Update Manager (ISUSPM.exe) - yes, there it is again. It shows up in memory every time an application uses Installshield. MF6 and/or Intervideo use(s) it despite anything you may have heard or read to the contrary. I prefer to check for program updates myself rather than have this intrusive program running in the background all the time, accessing the internet (who knows how often or when) to check for updates to all programs installed using it. This is another one that must be trashed using the Registry Editor (regedit.exe).

*****************************************

I'm sure there are other programs and processes lurking around that need closer inspection. If I learn of anything pertinent regarding the disposition of any of these programs, I'll post it here.

In the meantime, does anyone else know of any reasons why all these processes must be present?

Can we simply trash them or can the associated services be set to "Manual" startup mode?

Thanks for your time in reading this,
Big Al Mintaka