ms wrote:
| "PCR" <pcrrcp@netzero.net> wrote in news:eQ#Xo6#KJHA.5596
| @TK2MSFTNGP03.phx.gbl:
|
|> ms wrote:
|>| "PCR" <pcrrcp@netzero.net> wrote in
|>| news:#7piTczKJHA.1156@TK2MSFTNGP04.phx.gbl:
|>|
|>|> ms wrote:
|>|>| "PCR" <pcrrcp@netzero.net> wrote in news:eowg#XlKJHA.4324
|>|>| @TK2MSFTNGP05.phx.gbl:
|>|>|
|>|>|> ms wrote:
|>|>|>| I use Winpatrol, and it kept showing a warning that Script
|>|>|>| Sentry wanted to open reg extensions. I selected No.
|>|>|>|
|>|>|>| I uninstalled Script Sentry, no help, deleted all files on the
|>|>|>| drive for Script Sentry, no help.
|>|>|>|
|>|>|>| I ran RegSeeker, cleaned all "safe" entries, and searched for
|>|>|>| SS, no entries.
|>|>|>|
|>|>|>| I ran RegEdit, searched for SS, no entries.
|>|>|>|
|>|>|>| I don't like them, but ran a relatively safe cleaner, Wise
|>|>|>| Registry Cleaner, still get the WinPatrol warning screen, the
|>|>|>| path it shows does not exist in my Utilities folder.
|>|>|>|
|>|>|>| Cold boots in between.
|>|>|>|
|>|>|>| So it appears Script Sentry is still somewhere in my registry,
|>|>|>| how to locate it?
|>|>|>
|>|>|> What is the precise wording of the message WinPatrol is posting
|>|>|> including any spaces & punctuation marks? Does it say "Script
|>|>|> Sentry" with a space as you posted or without one?
|>|>|>
|>|>|>| ms
|>|>|>
|>|>| Thanks, PCR
|>|>|
|>|>| My cleaning must have worked, as the message has not reappeared
|>|>| today so it may finally be gone.
|>|>
|>|> All right. Very good. I see others have popped in who know more
|>|> about Script Sentry anyway.
|>|>
|>|>| If I may, a new subject, an old thread on this computer I'm using,
|>|>| this was the Dell with a shaded video problem, faint grey shading
|>|>| on each line of text. You felt it was a defective video card,
|>|>| that must be it.
|>|>|
|>|>| I had gone to the Dell site, identified the video driver,
|>|>| installed it, still got the shading, no help, but it added a
|>|>| minor error screen on boot up. I fired up the machine after a few
|>|>| weeks, figured if installing the driver caused the error screen,
|>|>| uninstalling the driver would remove the error screen.
|>|>|
|>|>| Uninstalling the driver, the display properties, etc caused new
|>|>| issues, so I reinstalled it and now just have the simple screen
|>|>| again. It says:
|>|>|
|>|>| Rndll error: Error in C:\Windows\System\NvCpl.dll. missing entry
|>|>| Nv Startup
|>|>|
|>|>| It relates to the driver, several driver entries are in my
|>|>| HKLM/RUN key placed there by the install. Any idea on how to
|>|>| clean up that error screen?
|>|>
|>|> I think you are right that it relates to an NVIDEA driver. I was
|>|> just about to research it, but am called away. Read through some of
|>|> these at Google...
|>|>
|>|>
|>
http://www.google.com/search?hl=en&q=Rundll+error+C:\Windows\Syst
|>|> em%5CNvCpl.dll&btnG=Search
|>|>
|>|> Do nothing rash, if it seems to get complex. Read through some,
|>|> work up a plan & post it. I'll be back tomorrow or someone else may
|>|> comment in the meantime.
|>|>
|>| Many thanks for that link, down in the page was the exact same
|>| issue I had, a fix, and the fix works for me also. Below:
|>| ---
|>| Go to Start > Run > Msconfig > Startup tab, and just uncheck the
|>| line
|>|
|>| NvCplDaemon = RUNDLL32.EXE c:\windows\SYSTEM\NvCpl.dll,NvStartup
|>|
|>| Click OK, and reboot.
|>| ---
|>|
|>| Just that simple.
|>|
|>| Thanks again for the help
|>
|> You are welcome. Maybe continue clicking a few more of those anyhow
|> just to see what that line was supposed to do. Can it be you'd
|> rather have it activated & working? (I don't know.)
|>
|> So... what about the grayness on monitor lines? Have you tried
|> adjusting colors at...?... "Control Panel, Display, Settings,
|> Advanced button, Color".
|>
| When I opened this thread 6 months ago, you suggested and I did that,
| no luck.
Hmm. OK. Too bad.
|> How old is the monitor? I've had TWO go dark on me-- & this one
|> suddenly will open its menu screen without my pressing the button
|> for it! It seems to be a tad better now that I've blown away most of
|> the dust though.
|>
|
| This is a good monitor, used OK on other computers.
Hmm. That's interesting. Did I know that 6 months ago too?
| This is only a backup machine, due to other issues, no energy here to
| solve this issue. But I thank you for your interest. I use this
| computer to browse when my W2K machine is sick. Right now it does
| not browse.
All right, then. If you should discover the Win2K never will browse, we
can get back to your monitor on the Win98. But you'll have to remind us
all over again what has been tried! Sounds like a driver or a settings
problem to me, if it works well on another machine without the gray
shading. Otherwise, I'd have suspected the monitor is going bad. Check
that all is plugged in solidly. Blow some dust out of the vents,
(although I less/less suspect that is my own issue with the menu screen
popping up). Run through the monitor's own settings screens & put things
to default if possible. (Suddenly my own monitor's auto & menu buttons
won't work-- but at least the menu screen is not being displayed!
Sheesh!)
| BTW, W2K and W98SE are my favorite OS's.
Ah, Win98SE, very good.
| ms
--
Thanks or Good Luck,
There may be humor in this post, and,
Naturally, you will not sue,
Should things get worse after this,
PCR
pcrrcp@netzero.net
