nvcpl

Do I really need this thing in my startup? With older versions of the
driver, I always just unchecked it. With the 52.16 drivers, even if I
uncheck it, it comes right back after the next reboot. It looks like it
using some CPU time.

Stuart

I am also looking for a fix. Most commercial / freeware start managers get
rid of it and it re-appears at boot up every time. Please post a fix if
there is one. I also see a file in msconfig on the same line labeled
nvstartup. A NV start routine ? Cant find it or disable it ?


remove nospam from address to reply


"Stuart Pierce" wrote in message
et...
Do I really need this thing in my startup? With older versions of the
driver, I always just unchecked it. With the 52.16 drivers, even if I
uncheck it, it comes right back after the next reboot. It looks like it
using some CPU time.

Stuart

On Tue, 28 Oct 2003 12:00:23 -0700, Knowing that it was a Hollywood
invention that lemmings jump off cliffs "IDAssociates Inc."
wrote :

I am also looking for a fix. Most commercial / freeware start managers get
rid of it and it re-appears at boot up every time. Please post a fix if
there is one. I also see a file in msconfig on the same line labeled
nvstartup. A NV start routine ? Cant find it or disable it ?


remove nospam from address to reply

Heh.Heh.It's really buggin' you innitgrin.
Leave it be it's doing no harm ;-)




"Stuart Pierce" wrote in message
. net...
Do I really need this thing in my startup? With older versions of the
driver, I always just unchecked it. With the 52.16 drivers, even if I
uncheck it, it comes right back after the next reboot. It looks like it
using some CPU time.

Stuart






--
Free Windows/PC help,
http://www.geocities.com/sheppola/trouble.html
email shepATpartyheld.de
Free songs download,
http://www.soundclick.com/bands/8/nomessiahsmusic.htm

You running coolbits and/or overclocking the card ?


"Stuart Pierce" wrote in message
et...
Do I really need this thing in my startup? With older versions of the
driver, I always just unchecked it. With the 52.16 drivers, even if I
uncheck it, it comes right back after the next reboot. It looks like it
using some CPU time.

Stuart

Coolbits running but not overclocked.


drop nospam to reply.


"Me" wrote in message
...
You running coolbits and/or overclocking the card ?


"Stuart Pierce" wrote in message
et...
Do I really need this thing in my startup? With older versions of the
driver, I always just unchecked it. With the 52.16 drivers, even if I
uncheck it, it comes right back after the next reboot. It looks like it
using some CPU time.

Stuart

As far as I remember, that is added by coolbits to enable the overclock
every time the system is booted. Or something like that.

Been a long time since I last looked it up.




"IDAssociates Inc." wrote in message
news:nWAnb.97735$La.31608@fed1read02...
Coolbits running but not overclocked.


drop nospam to reply.


"Me" wrote in message
...
You running coolbits and/or overclocking the card ?


"Stuart Pierce" wrote in message
et...
Do I really need this thing in my startup? With older versions of the
driver, I always just unchecked it. With the 52.16 drivers, even if I
uncheck it, it comes right back after the next reboot. It looks like
it
using some CPU time.

Stuart

Well maybe not directly by coolbits but as a result of it.


"Me" wrote in message
...
As far as I remember, that is added by coolbits to enable the overclock
every time the system is booted. Or something like that.

Been a long time since I last looked it up.




"IDAssociates Inc." wrote in message
news:nWAnb.97735$La.31608@fed1read02...
Coolbits running but not overclocked.


drop nospam to reply.


"Me" wrote in message
...
You running coolbits and/or overclocking the card ?


"Stuart Pierce" wrote in message
et...
Do I really need this thing in my startup? With older versions of
the
driver, I always just unchecked it. With the 52.16 drivers, even if
I
uncheck it, it comes right back after the next reboot. It looks
like
it
using some CPU time.

Stuart

Hmm. Deleted 52.16 and edited out coolbits, resinstalled and nvwiz and
nvcpl still turn up in msconfig. Gogle search only yields whatt hey are for
and nothing about how to get rid of them. They arent needed.




"Me" wrote in message
...
Well maybe not directly by coolbits but as a result of it.


"Me" wrote in message
...
As far as I remember, that is added by coolbits to enable the overclock
every time the system is booted. Or something like that.

Been a long time since I last looked it up.




"IDAssociates Inc." wrote in message
news:nWAnb.97735$La.31608@fed1read02...
Coolbits running but not overclocked.


drop nospam to reply.


"Me" wrote in message
...
You running coolbits and/or overclocking the card ?


"Stuart Pierce" wrote in message
et...
Do I really need this thing in my startup? With older versions of
the
driver, I always just unchecked it. With the 52.16 drivers, even
if
I
uncheck it, it comes right back after the next reboot. It looks
like
it
using some CPU time.

Stuart

Am Tue, 28 Oct 2003 15:03:24 -0700, "IDAssociates Inc."
schrieb:

Hmm. Deleted 52.16 and edited out coolbits, resinstalled and nvwiz and
nvcpl still turn up in msconfig. Gogle search only yields whatt hey are for
and nothing about how to get rid of them. They arent needed.


Think again.

nvcpl is the display manager itself.

nvcpl = Nvidia control panel. Got it?


DrFish

Bora Ugurlu

DrFish wrote:
Am Tue, 28 Oct 2003 15:03:24 -0700, "IDAssociates Inc."
schrieb:

Hmm. Deleted 52.16 and edited out coolbits, resinstalled and nvwiz
and nvcpl still turn up in msconfig. Gogle search only yields whatt
hey are for and nothing about how to get rid of them. They arent
needed.


Think again.

nvcpl is the display manager itself.

nvcpl = Nvidia control panel. Got it?


DrFish

Bora Ugurlu


Agreed. The extension .cpl is almost exclusively used for control panel
interfaces.

Ron