Trouble with new display and Device Manager

G

Gary S. Terhune

Well, if it seems to run OK, it's time to leave it alone. Yes, Device
Manager isn't neat and tidy like you'd want, but a less than perfect DM is
actually pretty common.

--
Gary S. Terhune
MS-MVP Shell/User
www.grystmill.com

"Warren" <nospam@nospam.com> wrote in message
news:OHQz12NfIHA.4608@TK2MSFTNGP06.phx.gbl...
> See comments below:
>
> "Gary S. Terhune" <none> wrote in message
> news:OqRi97MfIHA.4476@TK2MSFTNGP06.phx.gbl...
>> Unsigned, signed, no diff, really.
>>
>> Let's see if we can go over this one more time:
>> You have a video adapter with dual monitor capability, but only one

> monitor.
>> Is that correct? Is it a new adapter?

>
> I've had the video adapter (ATI 9200 Radeon) quite some time, the
> Viewsonic
> VP930b monitor was new to the system. I have updated the drivers for the
> video adapter on several occassions.
>
>> Or is the monitor (NOT "display") that's new and you are having a

> difficult
>> time getting it right?

>
> The supplied Win98 drivers on the CD-ROM would not install. I downloaded
> the Unsigned driver pack from Viewsonic site, and the Monitor picked up
> drivers on it's own. An unknown device was detected on the video adapter
> and a Default Monitor was also installed.
>
>> Have you removed ALL monitors and ALL video adapters? and then

> reinstalled?,
>> adapter first?

>
> Yes I've removed all monitors & adapters in device manager and then
> rebooted, but everything stays the same.
>
>> If this is a dual monitor adapter, have you looked in the instructions to
>> see if there's a way to turn it back into a single-monitor adapter?

>
> I have set the video adapter to dingle display mode.
>
>> Did you try the first three replies to your post?

>
> Yes, if you are asking if I disabled the Default Monitor
>
>> It is NOT unusual to see Default Monitor installed alongside the more up

> to
>> date drivers --- I sometimes wonder if it isn't NEEDED for certain types

> of
>> installations.
>> --
>> Gary S. Terhune
>> MS-MVP Shell/User
>> www.grystmill.com
>>
>> "Warren" <nospam@nospam.com> wrote in message
>> news:OzQq8yMfIHA.4696@TK2MSFTNGP05.phx.gbl...
>> > Yes, everything looks good except the Device Manager and it's ugly
>> > behaviour
>> > with the ICM and the extra Default Monitor attached to the video

> adapter.
>> > I
>> > think I've exhausted any doubt that it can not get any better with

> Windows
>> > 98SE. I guess that's to be expected with unsigned drivers, which is
>> > all
>> > that is available for Windows 98SE..
>> >
>> > "Gary S. Terhune" <none> wrote in message
>> > news:uEPAKFMfIHA.6136@TK2MSFTNGP03.phx.gbl...
>> >> Warren,
>> >>
>> >> Does your monitor look right? Does it behave properly. Anything wrong
>> >> that
>> >> you can describe (or even anything wrong that you can't put your
>> >> finger
>> > on?
>> >>
>> >> --
>> >> Gary S. Terhune
>> >> MS-MVP Shell/User
>> >> www.grystmill.com
>> >>
>> >> "Warren" <nospam@nospam.com> wrote in message
>> >> news:efjA9zseIHA.2000@TK2MSFTNGP05.phx.gbl...
>> >> > Your comments are interesting but I don't understand what you want
>> >> > me
>> >> > to
>> >> > do
>> >> > in order to completly remove the monitors. I've been trying and I

> amm
>> >> > confused as to why I'm at Monitor_16 or whatever. Do you have any
>> >> > specific
>> >> > instructions on how to delete monitors properly ?
>> >> >
>> >> > "Lee" <melee5@my-deja.com> wrote in message
>> >> >
>> >

> news:0de89406-5ce7-4a51-b56b-3d65c765844e@s13g2000prd.googlegroups.com...
>> >> > On Feb 27, 10:04 pm, "Warren" <nos...@nospam.com> wrote:
>> >> >> I swapped drivers, it was kind of scary, but it came back. The only
>> > thing
>> >> > I
>> >> >> didn't do was reboot in between changes. Does that matter ?
>> >> >>
>> >> >> "PCR" <pcr...@netzero.net> wrote in message
>> >> >>
>> >> >> news:%23MRE$8beIHA.3368@TK2MSFTNGP02.phx.gbl...
>> >> >>
>> >> >>
>> >> >>
>> >> >> > | "Warren" <nos...@nospam.com> wrote in message
>> >> >> > |news:eaekKAPeIHA.4464@TK2MSFTNGP02.phx.gbl...
>> >> >> > |> See comments below: $$$
>> >> >> > |>
>> >> >> > |> "PCR" <pcr...@netzero.net> wrote in message
>> >> >> > |>news:%23AFw64MeIHA.5400@TK2MSFTNGP04.phx.gbl...
>> >> >> > |> > Warren wrote:
>> >> >> > |> > | Thanks PCR,that solved the problem perfectly. Good fix.
>> >> >> > |> >
>> >> >> > |> > You are welcome. So... on Brian A.'s head & 1/3 the blame

> going
>> > to
>> >> >> > |> > Badour... go on and R-Clk that monster VS080114_I19.inf, &
>> > select
>> >> >> > |> > "Install".
>> >> >> > |> >
>> >> >> > |> > (1) What happened?
>> >> >> > |> > (There's a chance you get no feedback.)
>> >> >> > |> > But do you still have both a Default Monitor & the
>> >> >> > |> > ViewSonic VP930 Series showing in Device Manager?
>> >> >> > |>
>> >> >> > |> $$$ They are still both there
>> >> >>
>> >> >> > Uhuh.
>> >> >>
>> >> >> > |> > (2) Do this again...
>> >> >> > |> >
>> >> >> > |> > (a) Boot to Safe Mode
>> >> >> > |> > (Hold F5 as you boot or CTRL for the Startup Menu)
>> >> >> > |> > (b) "START, Settings, Control Panel, System,
>> >> >> > |> > Device Manager tab"
>> >> >> > |> > (c) Open the Monitors branch,
>> >> >> > |> > & Remove all entries under it.
>> >> >> > |> > (d) Boot to Normal Mode.
>> >> >> > |> >
>> >> >> > |> > Is the ViewSonic VP930 Series monitor rediscovered &
>> >> >> > |> > installed? Did the Default Monitor disappear?
>> >> >> > |>
>> >> >> > |> $$$ Unfortunately it picked both monitors upagain
>> >> >>
>> >> >> > That's the procedure that really should be working for this!
>> >> >>
>> >> >> > |> > (3) "Control Panel, Display, Settings tab, Advanced button,
>> >> >> > |> > Monitor tab"
>> >> >> > |> >
>> >> >> > |> > (a) What monitor is stated by the monitor icon?
>> >> >> > |> > (You should see ViewSonic VP930 Series.)
>> >> >>
>> >> >> > You didn't answer. You did see that there?
>> >> >>
>> >> >> > |> > (b) Click the Change button, & the Next button.
>> >> >> > |> > (c) Bolt "Display a list...", & click "Next".
>> >> >> > |> > Does ViewSonic VP930 Series show in the Models box?
>> >> >>
>> >> >> > Same here.
>> >> >>
>> >> >> > |> > (d) Bolt "Show all hardware".
>> >> >> > |> > Examine the two panes to see what is currently
>> >> >> > |> > installed.
>> >> >>
>> >> >> > At this point, did Windows rebuild its "driver information
>> >> >> > database"?
>> >> >>
>> >> >> > |> > In the left (Manufacturers) pane, you should see ViewSonic,
>> >> >> > &
>> >> >> > in
>> >> >> > |> > the right (Models) pane, you should see ViewSonic VP930

> Series
>> >> >> > |> > selected & highlighted.
>> >> >> > |>
>> >> >> > |> $$$ It is just highlighting the first Viewsonic monitor in the
>> >> >> > |> driver list "OPTIQUEST 1000S"
>> >> >>
>> >> >> > Uhuh. That's the top one, & is the one mine points to when I
>> >> >> > click
>> >> >> > ViewSonic in the left pane. Yours should be pointing at the
>> >> >> > VP930,
>> >> >> > because that was installed! That's what normally happens at that
>> >> >> > requestor!
>> >> >>
>> >> >> > We have to try Registry deletes again, I guess. I'll post it
>> > elsewhere
>> >> >> > in this thread. Maybe try removing the adapter first.
>> >> >>
>> >> >> > Warren wrote:
>> >> >> > | One thought I've had is that the Device Manager may be
>> >> >> > insisting
>> >> >> > on
>> >> >> > | building a second monitor is because the video adapter has
>> > provision
>> >> >> > | for two monitors. I have set the video card for having only one
>> >> >> > | monitor, but maybe the Device Manager doesn't look at this

> setting
>> > on
>> >> >> > | the video adapter ?
>> >> >>
>> >> >> > Where do you see a setting for that? Here is how to remove the
>> > Adapter,
>> >> >> > as I posted elsewhere, (but it's something I, myself, might be a

> tad
>> >> >> > fearful to do)...
>> >> >>
>> >> >> > Important: At the point below where you "bolt
>> >> >> > 'Show all hardware'", ensure you copy down what is in the left &
>> > right
>> >> >> > panes. Then, if you have no other way to get back your current
>> > display
>> >> >> > adapter, you may go back into that screen to select it.
>> >> >>
>> >> >> > ......Quote..........
>> >> >> > The first thing to do is to remove the video adapter you have
>> >> >> > installed. Right-click on the desktop choose "Properties" from

> the
>> >> >> > drop-down menu select "Settings" click on the "Advanced"
>> >> >> > button
>> > and
>> >> >> > click on "Adapter". An adapter is a program that tells Windows
>> >> >> > how
>> >> >> > to
>> >> >> > deal with a specific video card. Make note of the adapter that is
>> >> >> > currently installed. Then, change the adapter to "Standard
>> >> >> > Display
>> >> >> > Adapter (VGA)" and restart the system.
>> >> >>
>> >> >> > [That is: Click "Change button, Next, bolt 'Display a List...',
>> >> >> > Next,
>> >> >> > bolt 'Show all hardware', scroll left pane to top, select

> '(Standard
>> >> >> > display types)', select 'Standard Display Adapter (VGA)' in right
>> > pane,
>> >> >> > click 'Next'"... PCR]
>> >> >>
>> >> >> > This will remove the current adapter and replace it with a
>> >> >> > generic
>> > VGA
>> >> >> > adapter that works with all video cards. You will not like VGA
>> > because
>> >> >> > it supports only 16 colors, but the purpose of installing it is
>> >> >> > to
>> > get
>> >> >> > rid of whatever was there before.
>> >> >>
>> >> >> > Next, return to the adapter screen and install an adapter that
>> > matches
>> >> >> > your video card. This may or may not be the adapter that you are
>> >> >> > using now. Examine the materials you received with your computer

> to
>> >> >> > see if they include a CD-ROM or floppy disk that contains the
>> >> >> > correct
>> >> >> > video adapter. Or go to the Gateway website and see if they have

> an
>> >> >> > adapter for you to download. Or check the website of the company
>> >> >> > that
>> >> >> > made your video card.
>> >> >>
>> >> >> > Bill Starbuck (MVP)
>> >> >> > ......End....of quote....
>> >> >>
>> >> >> > |>
>> >> >> > |> >
>> >> >> > |> > | "PCR" <pcr...@netzero.net> wrote in message
>> >> >> > |> > |news:O$5VlXCeIHA.288@TK2MSFTNGP02.phx.gbl...
>> >> >>
>> >> >> > ...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
>> >> >> > pcr...@netzero.net- Hide quoted text -
>> >> >>
>> >> >> - Show quoted text -
>> >> >
>> >> >>The only thing I
>> >> >> didn't do was reboot in between changes. Does that matter ?
>> >> > Rebooting is only the most important part of the whole process.
>> >> > That
>> >> > and deleting the correct things, take the line below for an example.
>> >> >
>> >> > [HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor
>> >> > \0015
>> >> >
>> >> > When the hardware item for monitors is properly deleted, the
>> >> > registry
>> >> > should be missing the entire Monitor key itself along with the 0016
>> >> > copies of non-functioning monitor bloat in the registry. When you
>> >> > then reboot, Windows notices that there is NO monitor info (valid or
>> >> > otherwise) in the registry and sets about looking through the inf
>> >> > files to install one (or two) that matches the seen hardware pronto.
>> >> > And this is HOW to do it in the first place. Gee whiz. You can't
>> >> > just delete the ones you want to or the ones you happen to don't
>> >> > like
>> >> > - it's not up to you at all. That's why you wound up with so many
>> >> > because everytime you piddle with it wrong Windows has to chuck all
>> >> > those monitors and start counting from the last good entry all over
>> >> > again. Which is why we clear the bloat out of the registry at times
>> >> > like this.
>> >> >
>> >> > You can't manually install hardware inf files with a right click.

> Any
>> >> > inf file with the word "Base" in it is hands off and you can't get
>> >> > there from here anyway - so just fugetaboutit. You have only one
>> >> > option and that is to do it the right way. Remove the hardware from
>> >> > the Device Mangler and reboot to redetect it and install the proper
>> >> > files for it. If that doesn't work then you didn't remove enough
>> >> > hardware the first time around.
>> >> >
>> >> > The only exception is when custom hardware installation disks
>> >> > require
>> >> > you to do it the way they say to do it. In such cases - read the
>> >> > manual and do it how they say.
>> >> >
>> >> >
>> >>
>> >
>> >

>>

>
>
 
W

Warren

RADEON 9200 SERIES
Display
Registry Key:
HKEY_LOCAL_MACHINE\enum\PCI\VEN_1002&DEV_5961&SUBSYS_280117EE&REV_01\000800
Alloc resources: Logical Configuration 0
IRQ: 11 Mask: xFFFF

Forced resources: None
Boot resources: None
Filtered resources: Logical Configuration 0
IRQ: 11 Mask: xFFFF

Basic resources: Logical Configuration 0
IRQ: 0 Mask: xFFFF

HW Revision: 001
Driver: Display\0000
Driver Date: 2- 3-2006

ViewSonic VP930 Series
Monitor
Registry Key:
HKEY_LOCAL_MACHINE\enum\MONITOR\VSCE41B\PCI_VEN_1002&DEV_5961&SUBSYS_280117E
E&REV_01_000800
Alloc resources: None
Forced resources: None
Boot resources: None
Filtered resources: None
Basic resources: None
Driver: Monitor\0018
Driver Date: 2-16-2008
Driver: VP930_Series.ICM
File Size: Driver Not
Installed
File Date: Driver Not
Installed

Default Monitor
Monitor
This device is disabled.
Registry Key:
HKEY_LOCAL_MACHINE\enum\MONITOR\DEFAULT_MONITOR\PCI_VEN_1002&DEV_5961&SUBSYS
_280117EE&REV_01_000800_1
Alloc resources: None
Forced resources: None
Boot resources: None
Filtered resources: None
Basic resources: None
Driver: Monitor\0019
Driver Date: 4-23-1999

"PCR" <pcrrcp@netzero.net> wrote in message
news:uKLuzuNfIHA.5996@TK2MSFTNGP04.phx.gbl...
> Warren wrote:
> | See comments below"
> |
> | "PCR" <pcrrcp@netzero.net> wrote in message
> | news:eWNghPpeIHA.6136@TK2MSFTNGP03.phx.gbl...
> |> Warren wrote:
> |> | Okay, I dusted off my copy of Roxio GoBack and went through the
> |> | entire process.
> |>
> |> Very good! That's very important to have a current full system
> |> backup!
> |>
> |> | I selected the same ATI driver as before because it was most
> |> | suitable and most current. Unfortunately it seemed to drag all the
> |> | garbage with it.
> |> |
> |> | Everything is the same as before.
> |>
> |> Too bad. Well, it was only a guess that it was the ATI adapter
> |> trying to hold on to two monitors. But I'm not sure you've done
> |> enough...
> |>
> |> (a) After reverting to the Standard Display Adapter (VGA),
> |> how many monitors were there?
> |
> | There were still two displays
> |
> |> (b) If still two, did you try removing one?
> |
> | Yes I did remove the "Default Monitor" in Safe Mode and then
> | rebooted. The "Defaulty Monitor" remained gone.
> |
> | I then changed back to the correct video adapter driver and rebooted.
> | An "Unkown" device was detecting and the "Default Monitor" was
> | instaaled
>
> That's interesting that the Default Monitor was able to be removed when
> you reverted to the Standard Display Adapter (VGA). Then, it came back
> when you reinstated the ATI Adapter. I see Terhune has become involved,
> & it may be wise to let him have a shot. Tell him the exact name of your
> Adapter. Maybe post your MSInfo32 information again-- this time
> including the Adapter information...
>
> "START button, Run, MSInfo32, Components, Display"
> Use the Edit menu to select all, copy, & then post it. Here is mine...
>
> Trident Blade3D/MVP4 (63)
> Display
> Registry Key:
> HKEY_LOCAL_MACHINE\enum\PCI\VEN_1023&DEV_8400&SUBSYS_B1AB0E11&REV_5C\000
> 800
> Alloc resources: Logical Configuration 0
> IRQ: 3 Mask: xFFFF
> ...snip of IO & Memory Address Ranges....
> Forced resources: None
> Boot resources: None
> Filtered resources: Logical Configuration 0
> IRQ: 3 Mask: xFFFF
> ...snip of IO & Memory Address Ranges....
> Basic resources: Logical Configuration 0
> IRQ: 0 Mask: xFFFF
> ...snip of IO & Memory Address Ranges....
> HW Revision: 092
> ...snip of numerous drivers...
>
> Envision EN5400e
> Monitor
> Registry Key:
> HKEY_LOCAL_MACHINE\enum\MONITOR\EPIE564\PCI_VEN_1023&DEV_8400&SUBSYS_B1A
> B0E11&REV_5C_000800
> Alloc resources: None
> Forced resources: None
> Boot resources: None
> Filtered resources: None
> Basic resources: None
> Driver: Monitor\0000
> Driver Date: 8-20-2004
> Driver: EN5400e.icm
> File Size: Driver Not Installed
> File Date: Driver Not Installed
>
> Maybe try those registry deletes I've posted, including that real big
> one...
> news:OCSbgi0eIHA.2000@TK2MSFTNGP05.phx.gbl
>
> |> Using Device Manager maybe in Safe Mode, I would have tried first to
> |> remove the Default Monitor. If that wouldn't go, I'd try to remove
> |> the ViewSonic VP930 Series, or both of them. If neither would go--
> |> that would definitively prove the ATI adapter isn't the thing
> |> holding on to them.
>
>
> --
> 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
>
>
 
B

Buffalo

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.
If the only problem he is having is that a 'default monitor' is listed in
DM, so what?
If that default monitor is actually causing problems, then let's get with
it.
Buffalo
 
W

Warren

I notice that my monitor enumeration has climbed from 0002 at the beginning
of this exercise to 0018 & 0019. What does this mean ?
Is there a way of resetting the enumeration of monitors or does Device
Manager keep counting each time you delete a monitor ? I really hope Device
Manager doesn't think I have 19 monitors ?

"Warren" <nospam@nospam.com> wrote in message
news:OtqhZxZfIHA.6092@TK2MSFTNGP06.phx.gbl...
>
> RADEON 9200 SERIES
> Display
> Registry Key:
>

HKEY_LOCAL_MACHINE\enum\PCI\VEN_1002&DEV_5961&SUBSYS_280117EE&REV_01\000800
> Alloc resources: Logical Configuration 0
> IRQ: 11 Mask: xFFFF
>
> Forced resources: None
> Boot resources: None
> Filtered resources: Logical Configuration 0
> IRQ: 11 Mask: xFFFF
>
> Basic resources: Logical Configuration 0
> IRQ: 0 Mask: xFFFF
>
> HW Revision: 001
> Driver: Display\0000
> Driver Date: 2- 3-2006
>
> ViewSonic VP930 Series
> Monitor
> Registry Key:
>

HKEY_LOCAL_MACHINE\enum\MONITOR\VSCE41B\PCI_VEN_1002&DEV_5961&SUBSYS_280117E
> E&REV_01_000800
> Alloc resources: None
> Forced resources: None
> Boot resources: None
> Filtered resources: None
> Basic resources: None
> Driver: Monitor\0018
> Driver Date: 2-16-2008
> Driver: VP930_Series.ICM
> File Size: Driver Not
> Installed
> File Date: Driver Not
> Installed
>
> Default Monitor
> Monitor
> This device is disabled.
> Registry Key:
>

HKEY_LOCAL_MACHINE\enum\MONITOR\DEFAULT_MONITOR\PCI_VEN_1002&DEV_5961&SUBSYS
> _280117EE&REV_01_000800_1
> Alloc resources: None
> Forced resources: None
> Boot resources: None
> Filtered resources: None
> Basic resources: None
> Driver: Monitor\0019
> Driver Date: 4-23-1999
>
> "PCR" <pcrrcp@netzero.net> wrote in message
> news:uKLuzuNfIHA.5996@TK2MSFTNGP04.phx.gbl...
> > Warren wrote:
> > | See comments below"
> > |
> > | "PCR" <pcrrcp@netzero.net> wrote in message
> > | news:eWNghPpeIHA.6136@TK2MSFTNGP03.phx.gbl...
> > |> Warren wrote:
> > |> | Okay, I dusted off my copy of Roxio GoBack and went through the
> > |> | entire process.
> > |>
> > |> Very good! That's very important to have a current full system
> > |> backup!
> > |>
> > |> | I selected the same ATI driver as before because it was most
> > |> | suitable and most current. Unfortunately it seemed to drag all the
> > |> | garbage with it.
> > |> |
> > |> | Everything is the same as before.
> > |>
> > |> Too bad. Well, it was only a guess that it was the ATI adapter
> > |> trying to hold on to two monitors. But I'm not sure you've done
> > |> enough...
> > |>
> > |> (a) After reverting to the Standard Display Adapter (VGA),
> > |> how many monitors were there?
> > |
> > | There were still two displays
> > |
> > |> (b) If still two, did you try removing one?
> > |
> > | Yes I did remove the "Default Monitor" in Safe Mode and then
> > | rebooted. The "Defaulty Monitor" remained gone.
> > |
> > | I then changed back to the correct video adapter driver and rebooted.
> > | An "Unkown" device was detecting and the "Default Monitor" was
> > | instaaled
> >
> > That's interesting that the Default Monitor was able to be removed when
> > you reverted to the Standard Display Adapter (VGA). Then, it came back
> > when you reinstated the ATI Adapter. I see Terhune has become involved,
> > & it may be wise to let him have a shot. Tell him the exact name of your
> > Adapter. Maybe post your MSInfo32 information again-- this time
> > including the Adapter information...
> >
> > "START button, Run, MSInfo32, Components, Display"
> > Use the Edit menu to select all, copy, & then post it. Here is mine...
> >
> > Trident Blade3D/MVP4 (63)
> > Display
> > Registry Key:
> > HKEY_LOCAL_MACHINE\enum\PCI\VEN_1023&DEV_8400&SUBSYS_B1AB0E11&REV_5C\000
> > 800
> > Alloc resources: Logical Configuration 0
> > IRQ: 3 Mask: xFFFF
> > ...snip of IO & Memory Address Ranges....
> > Forced resources: None
> > Boot resources: None
> > Filtered resources: Logical Configuration 0
> > IRQ: 3 Mask: xFFFF
> > ...snip of IO & Memory Address Ranges....
> > Basic resources: Logical Configuration 0
> > IRQ: 0 Mask: xFFFF
> > ...snip of IO & Memory Address Ranges....
> > HW Revision: 092
> > ...snip of numerous drivers...
> >
> > Envision EN5400e
> > Monitor
> > Registry Key:
> > HKEY_LOCAL_MACHINE\enum\MONITOR\EPIE564\PCI_VEN_1023&DEV_8400&SUBSYS_B1A
> > B0E11&REV_5C_000800
> > Alloc resources: None
> > Forced resources: None
> > Boot resources: None
> > Filtered resources: None
> > Basic resources: None
> > Driver: Monitor\0000
> > Driver Date: 8-20-2004
> > Driver: EN5400e.icm
> > File Size: Driver Not Installed
> > File Date: Driver Not Installed
> >
> > Maybe try those registry deletes I've posted, including that real big
> > one...
> > news:OCSbgi0eIHA.2000@TK2MSFTNGP05.phx.gbl
> >
> > |> Using Device Manager maybe in Safe Mode, I would have tried first to
> > |> remove the Default Monitor. If that wouldn't go, I'd try to remove
> > |> the ViewSonic VP930 Series, or both of them. If neither would go--
> > |> that would definitively prove the ATI adapter isn't the thing
> > |> holding on to them.
> >
> >
> > --
> > 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
> >
> >

>
>
 
P

PCR

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
 
P

PCR

Warren wrote:
| I notice that my monitor enumeration has climbed from 0002 at the
| beginning of this exercise to 0018 & 0019. What does this mean ?
| Is there a way of resetting the enumeration of monitors or does Device
| Manager keep counting each time you delete a monitor ? I really hope
| Device Manager doesn't think I have 19 monitors ?

I see nothing wrong with your MSInfo32 information, except that the
monitor numbers are growing.

Try that 2nd set of Registry deletes I've posted several times, the one
of the monitors in the ENUM key & the trillion monitors at...
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor

Here is the post one last time...
I think you can risk the registry key deletes...
news:uaU068beIHA.4696@TK2MSFTNGP05.phx.gbl

You know how to export & restore them, if the deletes go bad. Also, I
posted how to do a ScanReg /Restore, not to mention you now have a
refreshed full system backup.

When you get to this key...
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor

...., R-Clk "Monitor" in the left pane, export & then delete it. That
gets them all! Maybe, first, just click "Monitor" to highlight it, & use
the Edit menu to export it.

After that, we could consider deleted one or both of these...
DRVDATA.bin &/or DRVIDX.bin.

Remember this...?...

(a) "START button, Find, F/F"
(b) Leave "Named" empty.
(c) In "Containing text", enter... %VCDTS21367-1%
(d) In "Look in", browse to... "C:\WINDOWS\INF".
(e) If it is found, post the .inf.

(1) You said %VCDTS21367-1% was indisde Drvidx.bin.
Is it still in there?

(2) What are the dates on DRVDATA.bin & DRVIDX.bin?

| "Warren" <nospam@nospam.com> wrote in message
| news:OtqhZxZfIHA.6092@TK2MSFTNGP06.phx.gbl...


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

Warren

Sorry PCR but your links don't work and I'm not sure what registry deletes
you are talking about. Perhaps at date/time might help ?

"PCR" <pcrrcp@netzero.net> wrote in message
news:ufvJOzmfIHA.5164@TK2MSFTNGP03.phx.gbl...
> Warren wrote:
> | I notice that my monitor enumeration has climbed from 0002 at the
> | beginning of this exercise to 0018 & 0019. What does this mean ?
> | Is there a way of resetting the enumeration of monitors or does Device
> | Manager keep counting each time you delete a monitor ? I really hope
> | Device Manager doesn't think I have 19 monitors ?
>
> I see nothing wrong with your MSInfo32 information, except that the
> monitor numbers are growing.
>
> Try that 2nd set of Registry deletes I've posted several times, the one
> of the monitors in the ENUM key & the trillion monitors at...
> HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor
>
> Here is the post one last time...
> I think you can risk the registry key deletes...
> news:uaU068beIHA.4696@TK2MSFTNGP05.phx.gbl
>
> You know how to export & restore them, if the deletes go bad. Also, I
> posted how to do a ScanReg /Restore, not to mention you now have a
> refreshed full system backup.
>
> When you get to this key...
> HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor
>
> ..., R-Clk "Monitor" in the left pane, export & then delete it. That
> gets them all! Maybe, first, just click "Monitor" to highlight it, & use
> the Edit menu to export it.
>
> After that, we could consider deleted one or both of these...
> DRVDATA.bin &/or DRVIDX.bin.
>
> Remember this...?...
>
> (a) "START button, Find, F/F"
> (b) Leave "Named" empty.
> (c) In "Containing text", enter... %VCDTS21367-1%
> (d) In "Look in", browse to... "C:\WINDOWS\INF".
> (e) If it is found, post the .inf.
>
> (1) You said %VCDTS21367-1% was indisde Drvidx.bin.
> Is it still in there?
>
> (2) What are the dates on DRVDATA.bin & DRVIDX.bin?
>
> | "Warren" <nospam@nospam.com> wrote in message
> | news:OtqhZxZfIHA.6092@TK2MSFTNGP06.phx.gbl...
>
>
> ...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
>
>
 
W

Warren

Well I took a stab at what I think you are asking me to do and deleted the
Monitor keys in locations
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor
&
HKEY_LOCAL_MACHINE\Enum\Monitor

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. Obviously I have misunderstood your
instructions as the monitor numbering continued to get worse (I subsequently
reverted my hard drive prior to these changes).


"PCR" <pcrrcp@netzero.net> wrote in message
news:ufvJOzmfIHA.5164@TK2MSFTNGP03.phx.gbl...
> Warren wrote:
> | I notice that my monitor enumeration has climbed from 0002 at the
> | beginning of this exercise to 0018 & 0019. What does this mean ?
> | Is there a way of resetting the enumeration of monitors or does Device
> | Manager keep counting each time you delete a monitor ? I really hope
> | Device Manager doesn't think I have 19 monitors ?
>
> I see nothing wrong with your MSInfo32 information, except that the
> monitor numbers are growing.
>
> Try that 2nd set of Registry deletes I've posted several times, the one
> of the monitors in the ENUM key & the trillion monitors at...
> HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor
>
> Here is the post one last time...
> I think you can risk the registry key deletes...
> news:uaU068beIHA.4696@TK2MSFTNGP05.phx.gbl
>
> You know how to export & restore them, if the deletes go bad. Also, I
> posted how to do a ScanReg /Restore, not to mention you now have a
> refreshed full system backup.
>
> When you get to this key...
> HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor
>
> ..., R-Clk "Monitor" in the left pane, export & then delete it. That
> gets them all! Maybe, first, just click "Monitor" to highlight it, & use
> the Edit menu to export it.
>
> After that, we could consider deleted one or both of these...
> DRVDATA.bin &/or DRVIDX.bin.
>
> Remember this...?...
>
> (a) "START button, Find, F/F"
> (b) Leave "Named" empty.
> (c) In "Containing text", enter... %VCDTS21367-1%
> (d) In "Look in", browse to... "C:\WINDOWS\INF".
> (e) If it is found, post the .inf.
>
> (1) You said %VCDTS21367-1% was indisde Drvidx.bin.
> Is it still in there?
>
> (2) What are the dates on DRVDATA.bin & DRVIDX.bin?


I don't exactly remember what we were doing at the time (wasn't it a rogue
driver that you fixed), but %VCDTS21367-1% only is found in Monitr11.inf
now. DRVDATA.bin & DRVIDX.bin are both dated March 3, 2008.

> | "Warren" <nospam@nospam.com> wrote in message
> | news:OtqhZxZfIHA.6092@TK2MSFTNGP06.phx.gbl...
>
>
> ...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
>
>
 
W

Warren

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.

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

PCR

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
 
B

Buffalo

Warren wrote:
> Come on guys, let's be polite, no need to refer to me in the third
> person.

I stand by what I said and , if you reread my post, I referred to you as
Warren.
My opening sentence:
"I honestly believe that Warren did not follow all your advice on how to
remove all traces of his Display Adapter and his Monitor."
 
W

Warren

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

PCR

Warren wrote:
| Well I took a stab at what I think you are asking me to do and
| deleted the Monitor keys in locations
| HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor
| &
| HKEY_LOCAL_MACHINE\Enum\Monitor

Yea, that was it.

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

Yow! I'm trying to think... what would make that entire Registry key
come back?

| Obviously I have misunderstood your
| instructions as the monitor numbering continued to get worse (I
| subsequently reverted my hard drive prior to these changes).

Alright. That possibly was over-kill, though. I probably would have
tried importing the deleted key or reverting just to the original
Registry first.

|
| "PCR" <pcrrcp@netzero.net> wrote in message
| news:ufvJOzmfIHA.5164@TK2MSFTNGP03.phx.gbl...
|> Warren wrote:
|> | I notice that my monitor enumeration has climbed from 0002 at the
|> | beginning of this exercise to 0018 & 0019. What does this mean ?
|> | Is there a way of resetting the enumeration of monitors or does
|> | Device Manager keep counting each time you delete a monitor ? I
|> | really hope Device Manager doesn't think I have 19 monitors ?
|>
|> I see nothing wrong with your MSInfo32 information, except that the
|> monitor numbers are growing.
|>
|> Try that 2nd set of Registry deletes I've posted several times, the
|> one of the monitors in the ENUM key & the trillion monitors at...
|> HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor
|>
|> Here is the post one last time...
|> I think you can risk the registry key deletes...
|> news:uaU068beIHA.4696@TK2MSFTNGP05.phx.gbl
|>
|> You know how to export & restore them, if the deletes go bad. Also, I
|> posted how to do a ScanReg /Restore, not to mention you now have a
|> refreshed full system backup.
|>
|> When you get to this key...
|> HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor
|>
|> ..., R-Clk "Monitor" in the left pane, export & then delete it. That
|> gets them all! Maybe, first, just click "Monitor" to highlight it, &
|> use the Edit menu to export it.
|>
|> After that, we could consider deleted one or both of these...
|> DRVDATA.bin &/or DRVIDX.bin.
|>
|> Remember this...?...
|>
|> (a) "START button, Find, F/F"
|> (b) Leave "Named" empty.
|> (c) In "Containing text", enter... %VCDTS21367-1%
|> (d) In "Look in", browse to... "C:\WINDOWS\INF".
|> (e) If it is found, post the .inf.
|>
|> (1) You said %VCDTS21367-1% was indisde Drvidx.bin.
|> Is it still in there?
|>
|> (2) What are the dates on DRVDATA.bin & DRVIDX.bin?
|
| I don't exactly remember what we were doing at the time (wasn't it a
| rogue driver that you fixed), but %VCDTS21367-1% only is found in
| Monitr11.inf now.

No. %VCDTS21367-1% was a rogue variable in Monitr11.inf that we fixed.
It showed in our Update Driver requestor as one of the ViewSonic
drivers. Now "Optiquest V115" shows instead, but not on top!

By the way, that %VCDTS21367-1% also was in one of the junk monitors in
your original Monitor Registry key...

[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor\0003
]
"InfPath"="MONITR11.INF"
"InfSection"="VCDTS21367-1.Install"
"ProviderName"="Microsoft"
"DriverDesc"="%VCDTS21367-1%"
"MatchingDeviceId"="Monitor\\OQI4D31"
"DPMS"="1"
"DriverDate"=" 4-23-1999"

(a) Is at least that one gone now?
(b) Back then, you had 15 monitors in that key-- is it 19 now?

I still have just one, & it's the right one. And this is the third
monitor I have attached to this machine. I think this thread has become
too huge to be useful. Maybe start a new one entitled "Trying to be rid
of Default Monitor". Include the following in the post...

(1) These Registry keys...

HKEY_LOCAL_MACHINE\Enum\MONITOR
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor

(2) "START button, Run, MSInfo32, Components, Display"
Show it all, except the IO & Memory Address ranges.

(3) Post your dates again for DRVDATA.bin & DRVIDX.bin.
(I just want to be sure neither changes every day.)

(4) "START button, Run, SysEdit"
Post your Config.sys & Autoexec.bat files.

(5) How many Registry keys contain the word "Default_Monitor"?
Note: That is an underline between the words.
I have only 3...

HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\cfgmgr32\Ph
antom\C
HardWareKey "MONITOR\DEFAULT_MONITOR\0001" <<String value

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\ASD\Prob\{9B4E7760-3
196-11CF-97EA-00AA0034319D}
MONITOR\DEFAULT_MONITOR\0001 00 <<Binary Value

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\ASD\Prob\{CF2524C0-2
9AE-11CF-97EA-00AA0034319D}
MONITOR\DEFAULT_MONITOR\0001 00 <<Binary Value

....But those bottom 2 are HUGE-- just post the names & the value! Get
the value by "R-Clk, Modify". If any sounds interesting, someone may ask
the full thing be posted.

| DRVDATA.bin & DRVIDX.bin are both dated March 3,
| 2008.

That's fairly recent. My dates for those files are both 2/25/08, which
is when I repaired my own Monitr11.inf. Looks like they regenerate
automatically when necessary-- either a certain .inf has changed or
certain Registry keys are deleted. Therefore, there is no sense in
deleting them ourselves.

|> | "Warren" <nospam@nospam.com> wrote in message
|> | news:OtqhZxZfIHA.6092@TK2MSFTNGP06.phx.gbl...
|>
|>
|> ...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

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

PCR

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
 
L

Lee

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

Warren

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

Warren

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

>
>
 
P

PCR

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
 
W

Warren

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

Lee

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.
 
Back
Top Bottom