Trouble with new display and Device Manager

March 6, 2008

Re: Trouble with new display and Device Manager

Thanks PCR, I'll take a look for Registry Detective and see what I can do

with it.

"PCR" <pcrrcp@netzero.net> wrote in message

news:%23b5VCZzfIHA.4744@TK2MSFTNGP06.phx.gbl...

> Warren wrote:

> | Yes, I'm' not very happy with the growing monitor list. I should have

> | noticed this earlier and started reverting my hard drive when the

> | number got larger. It would be nice to clear out the registry bloat

> | created by all this testing but I may have to live with it.

>

> Alright. I've posted the promised response. You may find it helpful to

> get...

>

> http://www.pcmag.com/

> PCMag's "Registry Detective" (take "RegEdit+ too) is better than a naked

> RegEdit search, because it will only find an item once, if there is a

> "mirror" elsewhere. Also, it will find items in binary fields, which

> RegEdit does not. Finally, it finds ALL matches in 10 seconds & puts

> them ALL to the screen. There is a Details button for further

> examination of the Key. The search criteria can be adjusted and narrowed

> in various ways. There is a button to click that will get one into

> RegEdit+ (or RegEdit) open to that Key. I only wish there were an easy

> way to copy/post the Keys that were found in the search.

>

> They may be available at free sites too.

>

> | "PCR" <pcrrcp@netzero.net> wrote in message

> | news:utrLHuyfIHA.1660@TK2MSFTNGP02.phx.gbl...

> |> Warren wrote:

> |> | Come on guys, let's be polite, no need to refer to me in the third

> |> | person. I need some help to clean up this registry mess, not

> |> | insults to my personal integrity. I've tried my best to follow

> |> | your instructions to the letter. I may have missed something, but

> |> | it was not intentional. If I wasn't willing to take your advise I

> |> | wouldn't be continuing to participate in this thread. I've learned

> |> | quite a bit about the registry from this thread and I appreciate

> |> | this very much, but the problems at hand have not been resolved.

> |> |

> |> | Lee made some comment about not deleting the hardware correctly

> |> | from the registry, that I've been "piddling" around, which is

> |> | causing the monitor registry bloat in

> |> |

> [HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor.

> |> | When I asked for clarification on what I was doing wrong, he

> |> | responded with silence. As I've recently found out deleting the

> |> | "Monitor key" just makes things worse as far as registry bloat is

> |> | concerned.

> |>

> |> Alright. I'll answer over there. I fully apologize for referring to

> |> you in the 3rd person, although I can't spot where I did it! Indeed,

> |> when you answered my posts, you answered every part & posted the

> |> results-- except that 2nd Registry delete, which finally you did do.

> |> It is very perplexing why these things aren't working, is all.

> |>

> |> | "PCR" <pcrrcp@netzero.net> wrote in message

> |> | news:ubSUtpmfIHA.6136@TK2MSFTNGP03.phx.gbl...

> |> |> Buffalo wrote:

> |> |> | PCR wrote:

> |> |> |> > Maybe try those registry deletes I've posted, including that

> |> |> |> > real big

> |> |> |> one...

> |> |> | I honestly believe that Warren did not follow all your advice on

> |> |> | how to remove all traces of his Display Adapter and his Monitor.

> |> |> | I think he was leary of the advice given and that is what is

> |> |> | causing the problem.

> |> |>

> |> |> He seems to be blind to the Registry keys deletes this 2nd time

> |> |> around-- the one that includes his monster...

> |> |> HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor

> |> |>

> |> |> He's got a trillion monitors in there! I have only one!

> |> |>

> |> |> | If the only problem he is having is that a 'default monitor' is

> |> |> | listed in DM, so what?

> |> |>

> |> |> It's that & that fact he's got a Registry key that won't stop

> |> |> growing. At one point this was the highest it went...

> |> |>

> |>

> HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor\0015

> |> |>

> |> |> NOW-- it is over 18! And it may begin legally to drink!

> |> |>

> |> |> | If that default monitor is actually causing problems, then let's

> |> |> | get with it.

> |> |>

> |> |> I'm thinking he does need to try the deletes. After that, maybe we

> |> |> could go after a .bin or two... DRVDATA.bin &/or DRVIDX.bin.

> |> |>

> |> |> | Buffalo

> |> |>

> |> |> --

> |> |> 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

> |>

> |> --

> |> 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

>

> --

> 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

>

March 6, 2008

Re: Trouble with new display and Device Manager

I have a Registry Finder search tool that I think is pretty good. What

would you suggest I search for ? I'll try to post the results.

"Warren" <nospam@nospam.com> wrote in message

news:uYQN%23y0fIHA.1212@TK2MSFTNGP05.phx.gbl...

> Thanks PCR, I'll take a look for Registry Detective and see what I can do

> with it.

>

> "PCR" <pcrrcp@netzero.net> wrote in message

> news:%23b5VCZzfIHA.4744@TK2MSFTNGP06.phx.gbl...

> > Warren wrote:

> > | Yes, I'm' not very happy with the growing monitor list. I should have

> > | noticed this earlier and started reverting my hard drive when the

> > | number got larger. It would be nice to clear out the registry bloat

> > | created by all this testing but I may have to live with it.

> >

> > Alright. I've posted the promised response. You may find it helpful to

> > get...

> >

> > http://www.pcmag.com/

> > PCMag's "Registry Detective" (take "RegEdit+ too) is better than a naked

> > RegEdit search, because it will only find an item once, if there is a

> > "mirror" elsewhere. Also, it will find items in binary fields, which

> > RegEdit does not. Finally, it finds ALL matches in 10 seconds & puts

> > them ALL to the screen. There is a Details button for further

> > examination of the Key. The search criteria can be adjusted and narrowed

> > in various ways. There is a button to click that will get one into

> > RegEdit+ (or RegEdit) open to that Key. I only wish there were an easy

> > way to copy/post the Keys that were found in the search.

> >

> > They may be available at free sites too.

> >

> > | "PCR" <pcrrcp@netzero.net> wrote in message

> > | news:utrLHuyfIHA.1660@TK2MSFTNGP02.phx.gbl...

> > |> Warren wrote:

> > |> | Come on guys, let's be polite, no need to refer to me in the third

> > |> | person. I need some help to clean up this registry mess, not

> > |> | insults to my personal integrity. I've tried my best to follow

> > |> | your instructions to the letter. I may have missed something, but

> > |> | it was not intentional. If I wasn't willing to take your advise I

> > |> | wouldn't be continuing to participate in this thread. I've learned

> > |> | quite a bit about the registry from this thread and I appreciate

> > |> | this very much, but the problems at hand have not been resolved.

> > |> |

> > |> | Lee made some comment about not deleting the hardware correctly

> > |> | from the registry, that I've been "piddling" around, which is

> > |> | causing the monitor registry bloat in

> > |> |

> > [HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor.

> > |> | When I asked for clarification on what I was doing wrong, he

> > |> | responded with silence. As I've recently found out deleting the

> > |> | "Monitor key" just makes things worse as far as registry bloat is

> > |> | concerned.

> > |>

> > |> Alright. I'll answer over there. I fully apologize for referring to

> > |> you in the 3rd person, although I can't spot where I did it! Indeed,

> > |> when you answered my posts, you answered every part & posted the

> > |> results-- except that 2nd Registry delete, which finally you did do.

> > |> It is very perplexing why these things aren't working, is all.

> > |>

> > |> | "PCR" <pcrrcp@netzero.net> wrote in message

> > |> | news:ubSUtpmfIHA.6136@TK2MSFTNGP03.phx.gbl...

> > |> |> Buffalo wrote:

> > |> |> | PCR wrote:

> > |> |> |> > Maybe try those registry deletes I've posted, including that

> > |> |> |> > real big

> > |> |> |> one...

> > |> |> | I honestly believe that Warren did not follow all your advice on

> > |> |> | how to remove all traces of his Display Adapter and his Monitor.

> > |> |> | I think he was leary of the advice given and that is what is

> > |> |> | causing the problem.

> > |> |>

> > |> |> He seems to be blind to the Registry keys deletes this 2nd time

> > |> |> around-- the one that includes his monster...

> > |> |> HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor

> > |> |>

> > |> |> He's got a trillion monitors in there! I have only one!

> > |> |>

> > |> |> | If the only problem he is having is that a 'default monitor' is

> > |> |> | listed in DM, so what?

> > |> |>

> > |> |> It's that & that fact he's got a Registry key that won't stop

> > |> |> growing. At one point this was the highest it went...

> > |> |>

> > |>

> > HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor\0015

> > |> |>

> > |> |> NOW-- it is over 18! And it may begin legally to drink!

> > |> |>

> > |> |> | If that default monitor is actually causing problems, then let's

> > |> |> | get with it.

> > |> |>

> > |> |> I'm thinking he does need to try the deletes. After that, maybe we

> > |> |> could go after a .bin or two... DRVDATA.bin &/or DRVIDX.bin.

> > |> |>

> > |> |> | Buffalo

> > |> |>

> > |> |> --

> > |> |> 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

> > |>

> > |> --

> > |> 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

> >

> > --

> > 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

> >

>

March 7, 2008

Re: Trouble with new display and Device Manager

Warren wrote:

| I have a Registry Finder search tool that I think is pretty good.

| What would you suggest I search for ? I'll try to post the results.

It's pretty much the same old keys & MSInfo32 stuff, just to see whether

they've changed at all. Also, I've added all "Default_Monitor" to that

(with that underline [_]. The request is posted not terribly far above

above...

Subject: Re: Trouble with new display and Device Manager

Date: Wed, 5 Mar 2008 21:54:57 (or... 3/5/08 9:54 AM)

Scroll it down to see. Post the response up there, or start a new thread

with it.

| "Warren" <nospam@nospam.com> wrote in message

| news:uYQN%23y0fIHA.1212@TK2MSFTNGP05.phx.gbl...

|> Thanks PCR, I'll take a look for Registry Detective and see what I

|> can do with it.

....snip

--

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

March 7, 2008

Re: Trouble with new display and Device Manager

Well that was a little different. After the reboot the "Monitor" key in

both Device Manager &

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class was simply not

there. I wasn't comfortable with this so I reverted my hard drive to before

the change

"Lee" <melee5@my-deja.com> wrote in message

news:ebbe556e-d3e3-41c1-b487-b721c8cc6ff2@e60g2000hsh.googlegroups.com...

On Mar 5, 7:43 pm, "Warren" <nos...@nospam.com> wrote:

> Yes, I'm' not very happy with the growing monitor list. I should have

> noticed this earlier and started reverting my hard drive when the number

got

> larger. It would be nice to clear out the registry bloat created by all

> this testing but I may have to live with it.

>

> "PCR" <pcr...@netzero.net> wrote in message

>

> news:utrLHuyfIHA.1660@TK2MSFTNGP02.phx.gbl...

>

> > Warren wrote:

> > | Come on guys, let's be polite, no need to refer to me in the third

> > | person. I need some help to clean up this registry mess, not insults

> > | to my personal integrity. I've tried my best to follow your

> > | instructions to the letter. I may have missed something, but it was

> > | not intentional. If I wasn't willing to take your advise I wouldn't

> > | be continuing to participate in this thread. I've learned quite a bit

> > | about the registry from this thread and I appreciate this very much,

> > | but the problems at hand have not been resolved.

> > |

> > | Lee made some comment about not deleting the hardware correctly from

> > | the registry, that I've been "piddling" around, which is causing the

> > | monitor registry bloat in

> > | [HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor.

> > | When I asked for clarification on what I was doing wrong, he

> > | responded with silence. As I've recently found out deleting the

> > | "Monitor key" just makes things worse as far as registry bloat is

> > | concerned.

>

> > Alright. I'll answer over there. I fully apologize for referring to you

> > in the 3rd person, although I can't spot where I did it! Indeed, when

> > you answered my posts, you answered every part & posted the results--

> > except that 2nd Registry delete, which finally you did do. It is very

> > perplexing why these things aren't working, is all.

>

> > | "PCR" <pcr...@netzero.net> wrote in message

> > |news:ubSUtpmfIHA.6136@TK2MSFTNGP03.phx.gbl...

> > |> Buffalo wrote:

> > |> | PCR wrote:

> > |> |> > Maybe try those registry deletes I've posted, including that

> > |> |> > real big

> > |> |> one...

> > |> | I honestly believe that Warren did not follow all your advice on

> > |> | how to remove all traces of his Display Adapter and his Monitor.

> > |> | I think he was leary of the advice given and that is what is

> > |> | causing the problem.

> > |>

> > |> He seems to be blind to the Registry keys deletes this 2nd time

> > |> around-- the one that includes his monster...

> > |> HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor

> > |>

> > |> He's got a trillion monitors in there! I have only one!

> > |>

> > |> | If the only problem he is having is that a 'default monitor' is

> > |> | listed in DM, so what?

> > |>

> > |> It's that & that fact he's got a Registry key that won't stop

> > |> growing. At one point this was the highest it went...

> > |>

> > HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor\0015

> > |>

> > |> NOW-- it is over 18! And it may begin legally to drink!

> > |>

> > |> | If that default monitor is actually causing problems, then let's

> > |> | get with it.

> > |>

> > |> I'm thinking he does need to try the deletes. After that, maybe we

> > |> could go after a .bin or two... DRVDATA.bin &/or DRVIDX.bin.

> > |>

> > |> | Buffalo

> > |>

> > |> --

> > |> Thanks or Good Luck,

> > |> There may be humor in this post, and,

> > |> Naturally, you will not sue,

> > |> Should things get worse after this,

> > |> PCR

> > |> pcr...@netzero.net

>

> > --

> > Thanks or Good Luck,

> > There may be humor in this post, and,

> > Naturally, you will not sue,

> > Should things get worse after this,

> > PCR

> > pcr...@netzero.net- Hide quoted text -

>

> - Show quoted text -

Warren, in the left panel of regedit, while viewing the key of

[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor

\0000]

highlight and then right click on the word Monitor in the left pane

and select delete. It will be rebuilt on the next reboot.

My silence is only indicative of my life outside this newsgroup - I do

have one in other words, I meant no snub.

March 9, 2008

Re: Trouble with new display and Device Manager

On Mar 6, 9:50 pm, "Warren" <nos...@nospam.com> wrote:

> Well that was a little different. After the reboot the "Monitor" key in

> both Device Manager &

> HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class was simply not

> there. I wasn't comfortable with this so I reverted my hard drive to before

> the change

>

> "Lee" <mel...@my-deja.com> wrote in message

>

> news:ebbe556e-d3e3-41c1-b487-b721c8cc6ff2@e60g2000hsh.googlegroups.com...

> On Mar 5, 7:43 pm, "Warren" <nos...@nospam.com> wrote:

>

> > Yes, I'm' not very happy with the growing monitor list. I should have

> > noticed this earlier and started reverting my hard drive when the number

> got

> > larger. It would be nice to clear out the registry bloat created by all

> > this testing but I may have to live with it.

>

> > "PCR" <pcr...@netzero.net> wrote in message

>

> >news:utrLHuyfIHA.1660@TK2MSFTNGP02.phx.gbl...

>

> > > Warren wrote:

> > > | Come on guys, let's be polite, no need to refer to me in the third

> > > | person. I need some help to clean up this registry mess, not insults

> > > | to my personal integrity. I've tried my best to follow your

> > > | instructions to the letter. I may have missed something, but it was

> > > | not intentional. If I wasn't willing to take your advise I wouldn't

> > > | be continuing to participate in this thread. I've learned quite a bit

> > > | about the registry from this thread and I appreciate this very much,

> > > | but the problems at hand have not been resolved.

> > > |

> > > | Lee made some comment about not deleting the hardware correctly from

> > > | the registry, that I've been "piddling" around, which is causing the

> > > | monitor registry bloat in

> > > | [HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor.

> > > | When I asked for clarification on what I was doing wrong, he

> > > | responded with silence. As I've recently found out deleting the

> > > | "Monitor key" just makes things worse as far as registry bloat is

> > > | concerned.

>

> > > Alright. I'll answer over there. I fully apologize for referring to you

> > > in the 3rd person, although I can't spot where I did it! Indeed, when

> > > you answered my posts, you answered every part & posted the results--

> > > except that 2nd Registry delete, which finally you did do. It is very

> > > perplexing why these things aren't working, is all.

>

> > > | "PCR" <pcr...@netzero.net> wrote in message

> > > |news:ubSUtpmfIHA.6136@TK2MSFTNGP03.phx.gbl...

> > > |> Buffalo wrote:

> > > |> | PCR wrote:

> > > |> |> > Maybe try those registry deletes I've posted, including that

> > > |> |> > real big

> > > |> |> one...

> > > |> | I honestly believe that Warren did not follow all your advice on

> > > |> | how to remove all traces of his Display Adapter and his Monitor.

> > > |> | I think he was leary of the advice given and that is what is

> > > |> | causing the problem.

> > > |>

> > > |> He seems to be blind to the Registry keys deletes this 2nd time

> > > |> around-- the one that includes his monster...

> > > |> HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor

> > > |>

> > > |> He's got a trillion monitors in there! I have only one!

> > > |>

> > > |> | If the only problem he is having is that a 'default monitor' is

> > > |> | listed in DM, so what?

> > > |>

> > > |> It's that & that fact he's got a Registry key that won't stop

> > > |> growing. At one point this was the highest it went...

> > > |>

> > > HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor\0015

> > > |>

> > > |> NOW-- it is over 18! And it may begin legally to drink!

> > > |>

> > > |> | If that default monitor is actually causing problems, then let's

> > > |> | get with it.

> > > |>

> > > |> I'm thinking he does need to try the deletes. After that, maybe we

> > > |> could go after a .bin or two... DRVDATA.bin &/or DRVIDX.bin.

> > > |>

> > > |> | Buffalo

> > > |>

> > > |> --

> > > |> Thanks or Good Luck,

> > > |> There may be humor in this post, and,

> > > |> Naturally, you will not sue,

> > > |> Should things get worse after this,

> > > |> PCR

> > > |> pcr...@netzero.net

>

> > > --

> > > Thanks or Good Luck,

> > > There may be humor in this post, and,

> > > Naturally, you will not sue,

> > > Should things get worse after this,

> > > PCR

> > > pcr...@netzero.net- Hide quoted text -

>

> > - Show quoted text -

>

> Warren, in the left panel of regedit, while viewing the key of

> [HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor

> \0000]

>

> highlight and then right click on the word Monitor in the left pane

> and select delete. It will be rebuilt on the next reboot.

>

> My silence is only indicative of my life outside this newsgroup - I do

> have one in other words, I meant no snub.- Hide quoted text -

>

> - Show quoted text -

So the methods DO work, you just won't allow that. You will need to

stop interfering like that at some point real soon. This problem is

fully involved with the nut behind the wheel if we can borrow parlance

from the auto repair world and that is in reference to the steering

wheel.

Do it again, don't revert the registry (don't call it the hard drive

ever again), but instead just before you reboot, open the device

mangler and remove every single item even remotely connected to the

subject of monitors and then reboot. The monitor key will start anew

which is what you want. This is standard practice, don't feel

uncomfortable, you are wrong to do so. Windows will just install the

wrong default drivers until you make the situation such that Windows

has and can find and install the correct drivers - in either case you

will not be blind.

I strongly suspect that you have attempted to install your LCD monitor

incorrectly. Somewhere, there are instructions to run a certain

executable on your installation CD that will make Windows 98 "see" the

new monitor and install the correct drivers for it with NONE of the

problems you have had with it. That's the way it was with my sound

card that wasn't around when 98 was released such that 98 authors

would have had a chance to include the drivers for it in the inf

files. Other hardware has other ways of latter days installation,

again I'm thinking somewhere, you have missed some really important

angle on the installation method to be used - please revisit the issue

with this in mind.

March 10, 2008

Re: Trouble with new display and Device Manager

Hi Lee,

The action of only deleting the

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor key was

different from anything I have been asked to do before, and the results was

different and uncomfortable for me, no Monitor keys in Device Manager or

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class after the reboot.

The Registry did not rebuild after the reboot, as you had indicated it

would. As I felt uncomfortable with no Monitor keys I really did revert my

hard drive (not just my Registry) as I had Roxio GoBack running in the

background to back out of any changes that I don't feel comfortable with.

Probably a bit of overkill, but I want to make sure I backed out 100%.

The last time PCR asked me to delete the

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor key, he

also asked me to delete the HKEY_LOCAL_MACHINE\Enum\Monitor key as well.

After a reboot, both the Default & VP930 monitors came back and the monitor

list in HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor

increased by two more monitors.

Now I'm afraid I don't quite understand what you're asking me to do this

time round. I think what you are asking is:

(1) Open the Registry with Regedit and delete the

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor key by

R-Clicking

(2) Open the Device Manager and remove both monitor (Viewsonic VP930b &

Default Monitor) devices

(3) Reboot the computer

As far as installing my Viewsonic monitor, I followed the manufacturers

instructions explicitly. When I turned the power on the computer I could

see Default Monitor being installed because the monitor was an unknown

device. I then inserted the Viewsonic CD as instructed and followed the

instructions for installing the drivers. It read the INF it was looking for

off the CD but it would not read the ICM file off the CD, and then I get a

message that driver installation failed. I had to download and install the

driver pack from Viewsonic and then reboot before the Viewsonic monitor

installed with the correct drivers. Unfortunately I've never been able to

get rid of the Default Monitor originally created when I first installed the

monitor.

"Lee" <melee5@my-deja.com> wrote in message

news:014b847c-564c-4475-ace5-20a0fb71a3f5@59g2000hsb.googlegroups.com...

On Mar 6, 9:50 pm, "Warren" <nos...@nospam.com> wrote:

> Well that was a little different. After the reboot the "Monitor" key in

> both Device Manager &

> HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class was simply not

> there. I wasn't comfortable with this so I reverted my hard drive to

before