Trouble with new display and Device Manager

[Warren]

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

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.

 

[Warren]

Well I'll be a monkey's uncle !

I tried the sequence of steps shown below, but that did not work, because
after deleting the
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor key there
was nothing in the Device Manager to remove. I rebooted any how and the
same as last time there were no Monitor keys in Device Manager or
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class. But...there
were still Monitor keys in HKEY_LOCAL_MACHINE\Enum\Monitor. I deleted the
Default Monitor key and rebooted. Both Default Monitor & VP930b came back
in Device Manager and
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor, but this
time without the registry bloat in
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor, just two
monitors 0000 & 0001.

Now if I could only figure out how to rid myself of that pesky Default
Monitor. I'm thinking of removing from Device Manager and then from
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor and
reboot, that seems to be a pretty deadly combination. Unfortunately I think
the Default Monitor will still be in HKEY_LOCAL_MACHINE\Enum\Monitor, and if
I touch it all hell breaks loose again.

On a hunch I reversed the order of the steps and removed the monitors in
Device Manager first and then deleted the
"Warren" <nospam@nospam.com> wrote in message
news:eTHulekgIHA.5260@TK2MSFTNGP03.phx.gbl...
> 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
> > 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:
>
> 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.
>
>

 

[Warren]

That Default Monitor just won't go away.

"Warren" <nospam@nospam.com> wrote in message
news:uNFgR7kgIHA.5348@TK2MSFTNGP03.phx.gbl...
> Well I'll be a monkey's uncle !
>
> I tried the sequence of steps shown below, but that did not work, because
> after deleting the
> HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor key
there
> was nothing in the Device Manager to remove. I rebooted any how and the
> same as last time there were no Monitor keys in Device Manager or
> HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class. But...there
> were still Monitor keys in HKEY_LOCAL_MACHINE\Enum\Monitor. I deleted the
> Default Monitor key and rebooted. Both Default Monitor & VP930b came back
> in Device Manager and
> HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor, but
this
> time without the registry bloat in
> HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor, just
two
> monitors 0000 & 0001.
>
> Now if I could only figure out how to rid myself of that pesky Default
> Monitor. I'm thinking of removing from Device Manager and then from
> HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor and
> reboot, that seems to be a pretty deadly combination. Unfortunately I
think
> the Default Monitor will still be in HKEY_LOCAL_MACHINE\Enum\Monitor, and
if
> I touch it all hell breaks loose again.
>
> On a hunch I reversed the order of the steps and removed the monitors in
> Device Manager first and then deleted the
> "Warren" <nospam@nospam.com> wrote in message
> news:eTHulekgIHA.5260@TK2MSFTNGP03.phx.gbl...
> > 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
> > > 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:
> >
> > 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.
> >
> >
>
>

 

[PCR]

Warren wrote:
| That Default Monitor just won't go away.

I am glad to hear the bloat in...
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor
....is gone, & you are left with only two monitors there & the same two
in...
HKEY_LOCAL_MACHINE\Enum\MONITOR.

Maybe now start a new thread (this one shortly must explode) with the
postings I requested elsewhere...

(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 Registry keys have many values-- just post the
names of the Registry key & the value that contains "DEFAULT_MONITOR",
if different from mine! Get the value by "R-Clk, Modify" in the R-Pane.

| "Warren" <nospam@nospam.com> wrote in message
| news:uNFgR7kgIHA.5348@TK2MSFTNGP03.phx.gbl...
|> Well I'll be a monkey's uncle !
|>
|> I tried the sequence of steps shown below, but that did not work,
|> because after deleting the
|> HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor
|> key there was nothing in the Device Manager to remove. I rebooted
|> any how and the same as last time there were no Monitor keys in
|> Device Manager or
|> HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class.
|> But...there were still Monitor keys in
|> HKEY_LOCAL_MACHINE\Enum\Monitor. I deleted the Default Monitor key
|> and rebooted. Both Default Monitor & VP930b came back in Device
|> Manager and
|> HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor,
|> but this time without the registry bloat in
|> HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor,
|> just two monitors 0000 & 0001.
|>
|> Now if I could only figure out how to rid myself of that pesky
|> Default Monitor. I'm thinking of removing from Device Manager and
|> then from
|> HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor
|> and reboot, that seems to be a pretty deadly combination.
|> Unfortunately I think the Default Monitor will still be in
|> HKEY_LOCAL_MACHINE\Enum\Monitor, and if I touch it all hell breaks
|> loose again.
|>
|> On a hunch I reversed the order of the steps and removed the
|> monitors in Device Manager first and then deleted the
|> "Warren" <nospam@nospam.com> wrote in message
|> news:eTHulekgIHA.5260@TK2MSFTNGP03.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

 

[Lee]

On Mar 9, 5:42 pm, "Warren" <nos...@nospam.com> wrote:
> 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.

Hi Warren, glad to hear that you are using hunches and that they are
working out. It is a toss up as to which should be done first,
removing items from the Device Mangler or nuking entire registry
strings. Probably the best way would be to do the Device Mangler
first and then wipe up what ever is left behind in the registry.

OK we now may have a "ghost inf" situation. Particularly with modem
inf files, Windows likes to keep a copy of the installed device at
Windows\INF\Other folder and if a device's inf file is to be found in
there - Windows will automatically install it as a matter of fact with
no (normal) options allowed to the user. So double check your Other
folder for monitor files and delete them if you want to force Windows
to go looking for installation files anew. And it's my opinion that
you still do - this time make sure the ICM file is in the same folder
as the monitor's inf file where ever that may be.

Of course now what I'm asking that you do is everything you have
learned so far, remove items from the Device Mangler, then delete
entire monitor registry strings, delete INF\Other files that pertain
to your monitor and then Reboot to allow Windows to find and install
everything correctly.

The reason the registry did not build back the key in question is
because it did not need to. Somewhere else in the registry was the
old information anyway and Windows just used it as is. I do not know
how this happens exactly but it may also be tied to the "Default"
monitor that won't go away and/or that is not being removed from the
Device Mangler and/or perhaps with the Enum monitor branch of the
registry. When EVERYTHING is removed properly then you get your
devices reinstalled anew and the registry written with that instance
of reinstalled information - if there is no reinstallation then it
should not be a surprise that the registry doesn't get written to.

 

[Warren]

Hi Lee,

Yes I have made some progress.

There was a copy of the VP930 Series.inf in the Windows\Inf\Other folder
which I removed. I really have no idea where Windows finds the appropriate
inf & icm files for my Viewsonic monitor, but it seems to install nicely
since I installed the appropriate driver package from Viewsonic.

Removing the Default Monitor & the VP930Series Monitor in Device Manager,
cleaned out the HKEY_LOCAL_MACHINE\Enum\Monitor &
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor keys for
both monitors.

Unfortunately upon reboot the Default Monitor came back.

Your comments about a clean install intrigue me, but I'm a little confused
as to how far I should go. To clarify this question I have posted all
occurences of Default_Monitor & VSCE41B below. Clearly there are more
occurences than simply the HKEY_LOCAL_MACHINE\Enum\Monitor &
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor areas of
the Registry. Perhaps I still don't have a clean install ?


***************Search for "Default_Monitor"*********************

Data fields are: Key, Entry's name, Value

HKLM\Software\Microsoft\Windows\CurrentVersion\cfgmgr32\Phantom\3A\,
HardWareKey,
MONITOR\DEFAULT_MONITOR\PCI_VEN_1002&DEV_5961&SUBSYS_280117EE&REV_01_000800_
1

HKLM\System\CurrentControlSet\Services\Class\Monitor\0001\,
MatchingDeviceId, Monitor\Default_Monitor

HKLM\System\CurrentControlSet\Control\ASD\Prob\{CF2524C0-29AE-11CF-97EA-00AA
0034319D}\,
MONITOR\DEFAULT_MONITOR\PCI_VEN_1002&DEV_5961&SUBSYS_280117EE&REV_01_000800_
1, N/A

HKLM\System\CurrentControlSet\Control\ASD\Prob\{9B4E7760-3196-11CF-97EA-00AA
0034319D}\,
MONITOR\DEFAULT_MONITOR\PCI_VEN_1002&DEV_5961&SUBSYS_280117EE&REV_01_000800_
1, N/A

HKLM\Enum\MONITOR\DEFAULT_MONITOR\, {KEY}, {KEY}
HKLM\Enum\MONITOR\DEFAULT_MONITOR\PCI_VEN_1002&DEV_5961&SUBSYS_280117EE&REV_
01_000800_1\, {KEY}, {KEY}
HKLM\Enum\MONITOR\DEFAULT_MONITOR\PCI_VEN_1002&DEV_5961&SUBSYS_280117EE&REV_
01_000800_1\, HardwareID, MONITOR\DEFAULT_MONITOR


**************Search for "VSCE41B"***************

Data fields are: Key, Entry's name, Value

HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\Doc Find Spec MRU\,
g, vsce41b*.*

HKLM\System\CurrentControlSet\Services\Class\Monitor\0000\,
MatchingDeviceId, Monitor\VSCE41B

HKLM\System\CurrentControlSet\Control\ASD\Prob\{CF2524C0-29AE-11CF-97EA-00AA
0034319D}\,
MONITOR\VSCE41B\PCI_VEN_1002&DEV_5961&SUBSYS_280117EE&REV_01_000800, N/A

HKLM\System\CurrentControlSet\Control\ASD\Prob\{9B4E7760-3196-11CF-97EA-00AA
0034319D}\,
MONITOR\VSCE41B\PCI_VEN_1002&DEV_5961&SUBSYS_280117EE&REV_01_000800, N/A

HKLM\Enum\MONITOR\VSCE41B\, {KEY}, {KEY}
HKLM\Enum\MONITOR\VSCE41B\PCI_VEN_1002&DEV_5961&SUBSYS_280117EE&REV_01_00080
0\, {KEY}, {KEY}
HKLM\Enum\MONITOR\VSCE41B\PCI_VEN_1002&DEV_5961&SUBSYS_280117EE&REV_01_00080
0\, HardwareID, MONITOR\VSCE41B

"Lee" <melee5@my-deja.com> wrote in message
news:41e640b2-7b63-454d-85be-ae97a0392457@2g2000hsn.googlegroups.com...
On Mar 9, 5:42 pm, "Warren" <nos...@nospam.com> wrote:
> 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.

Hi Warren, glad to hear that you are using hunches and that they are
working out. It is a toss up as to which should be done first,
removing items from the Device Mangler or nuking entire registry
strings. Probably the best way would be to do the Device Mangler
first and then wipe up what ever is left behind in the registry.

OK we now may have a "ghost inf" situation. Particularly with modem
inf files, Windows likes to keep a copy of the installed device at
Windows\INF\Other folder and if a device's inf file is to be found in
there - Windows will automatically install it as a matter of fact with
no (normal) options allowed to the user. So double check your Other
folder for monitor files and delete them if you want to force Windows
to go looking for installation files anew. And it's my opinion that
you still do - this time make sure the ICM file is in the same folder
as the monitor's inf file where ever that may be.

Of course now what I'm asking that you do is everything you have
learned so far, remove items from the Device Mangler, then delete
entire monitor registry strings, delete INF\Other files that pertain
to your monitor and then Reboot to allow Windows to find and install
everything correctly.

The reason the registry did not build back the key in question is
because it did not need to. Somewhere else in the registry was the
old information anyway and Windows just used it as is. I do not know
how this happens exactly but it may also be tied to the "Default"
monitor that won't go away and/or that is not being removed from the
Device Mangler and/or perhaps with the Enum monitor branch of the
registry. When EVERYTHING is removed properly then you get your
devices reinstalled anew and the registry written with that instance
of reinstalled information - if there is no reinstallation then it
should not be a surprise that the registry doesn't get written to.

 

[Lee]

On Mar 16, 12:12 am, "Warren" <nos...@nospam.com> wrote:
> Hi Lee,
>
> Yes I have made some progress.
>
> There was a copy of the VP930 Series.inf in the Windows\Inf\Other folder
> which I removed.  I really have no idea where Windows finds the appropriate
> inf & icm files for my Viewsonic monitor, but it seems to install nicely
> since I installed the appropriate driver package from Viewsonic.
>
> Removing the Default Monitor & the VP930Series Monitor in Device Manager,
> cleaned out the HKEY_LOCAL_MACHINE\Enum\Monitor &
> HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor keys for
> both monitors.
>
> Unfortunately upon reboot the Default Monitor came back.
>
> Your comments about a clean install intrigue me, but I'm a little confused
> as to how far I should go.  To clarify this question I have posted all
> occurences of Default_Monitor & VSCE41B below.  Clearly there are more
> occurences than simply the HKEY_LOCAL_MACHINE\Enum\Monitor &
> HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor areas of
> the Registry.  Perhaps I still don't have a clean install ?

The terminology "clean install" is used elsewhere so your attempt at
kidnapping it for your own use will be frowned upon, kinda like saying
"reverting your hard drive" when you should have mentioned re-imaging
your hard drive with Go Back program instead. It makes you sound a
bit off in the head is all - we know you are not...?

I would not call a bogus Default monitor reinstalling itself a clean
install, so no, not a good thing at all.

How far should you go? As far as the road takes you, kinda like the
length of your legs, certainly far enough to reach the ground. The
really nice thing about all this is - it doesn't matter how far you
take the removal of devices from the Device Mangler. Please remove
them all just for kicks. It really doesn't matter, as it doesn't hurt
a thing. At reboot Windows will spend some time reinstalling all that
stuff and you might be right back where you are now - unless this
drastic measure actually fixes the Default Monitor problem in and of
itself. Which is very real possibility!!!

I won't tell you to do it right now because you are probably sweating
real bullets, but at least think it over some. Coincidently, the
deletion of the entire ENUM key just prior to shutdown is one quick
and dirty way to install Windows onto any machine by simply swapping
out the booting hard drive to the new machine. At boot up, in the new
machine, Windows will detect all the "new" hardware and install the
correct drivers and poof you got Windows - neat method, if the
legalities are a separate issue.

I have done this and it works just fine. Both via the registry and
the Device Mangler just to be sure both methods did pretty much the
same thing - they do. I would certainly remove all instances of the
Default Monitor found in the registry. Your ICM file is most likely
in the Windows\INF folder now if Windows is not asking for it's
location, and that's just fine - it's supposed to be there if it's not
too big along with the inf file. It's just nice to know exactly where
stuff like that is actually at for a possible future "clean" Windows
reinstallation. Clean Install is usually in reference to a Windows
installation denoting a blank hard drive prior to the actual
installation as in opposition to an "over the top" reinstallation of
Windows to a hard drive that already has a working or not working
Windows installed on it.

>
> ***************Search for "Default_Monitor"*********************
>
> Data fields are: Key, Entry's name, Value
>
> HKLM\Software\Microsoft\Windows\CurrentVersion\cfgmgr32\Phantom\3A\,
> HardWareKey,
> MONITOR\DEFAULT_MONITOR\PCI_VEN_1002&DEV_5961&SUBSYS_280117EE&REV_01_000800­_
> 1
>
> HKLM\System\CurrentControlSet\Services\Class\Monitor\0001\,
> MatchingDeviceId, Monitor\Default_Monitor
>
> HKLM\System\CurrentControlSet\Control\ASD\Prob\{CF2524C0-29AE-11CF-97EA-00A­A
> 0034319D}\,
> MONITOR\DEFAULT_MONITOR\PCI_VEN_1002&DEV_5961&SUBSYS_280117EE&REV_01_000800­_
> 1, N/A
>
> HKLM\System\CurrentControlSet\Control\ASD\Prob\{9B4E7760-3196-11CF-97EA-00A­A
> 0034319D}\,
> MONITOR\DEFAULT_MONITOR\PCI_VEN_1002&DEV_5961&SUBSYS_280117EE&REV_01_000800­_
> 1, N/A
>
> HKLM\Enum\MONITOR\DEFAULT_MONITOR\, {KEY}, {KEY}
> HKLM\Enum\MONITOR\DEFAULT_MONITOR\PCI_VEN_1002&DEV_5961&SUBSYS_280117EE&REV­_
> 01_000800_1\, {KEY}, {KEY}
> HKLM\Enum\MONITOR\DEFAULT_MONITOR\PCI_VEN_1002&DEV_5961&SUBSYS_280117EE&REV­_
> 01_000800_1\, HardwareID, MONITOR\DEFAULT_MONITOR
>
> **************Search for "VSCE41B"***************
>
> Data fields are: Key, Entry's name, Value
>
> HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\Doc Find Spec MRU\,
> g, vsce41b*.*
>
> HKLM\System\CurrentControlSet\Services\Class\Monitor\0000\,
> MatchingDeviceId, Monitor\VSCE41B
>
> HKLM\System\CurrentControlSet\Control\ASD\Prob\{CF2524C0-29AE-11CF-97EA-00A­A
> 0034319D}\,
> MONITOR\VSCE41B\PCI_VEN_1002&DEV_5961&SUBSYS_280117EE&REV_01_000800, N/A
>
> HKLM\System\CurrentControlSet\Control\ASD\Prob\{9B4E7760-3196-11CF-97EA-00A­A
> 0034319D}\,
> MONITOR\VSCE41B\PCI_VEN_1002&DEV_5961&SUBSYS_280117EE&REV_01_000800, N/A
>
> HKLM\Enum\MONITOR\VSCE41B\, {KEY}, {KEY}
> HKLM\Enum\MONITOR\VSCE41B\PCI_VEN_1002&DEV_5961&SUBSYS_280117EE&REV_01_0008­0
> 0\, {KEY}, {KEY}
> HKLM\Enum\MONITOR\VSCE41B\PCI_VEN_1002&DEV_5961&SUBSYS_280117EE&REV_01_0008­0
> 0\, HardwareID, MONITOR\VSCE41B
>
> "Lee" <mel...@my-deja.com> wrote in message
>
> news:41e640b2-7b63-454d-85be-ae97a0392457@2g2000hsn.googlegroups.com...
> On Mar 9, 5:42 pm, "Warren" <nos...@nospam.com> wrote:
>
>
>
>
>
> > 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.
>
> Hi Warren, glad to hear that you are using hunches and that they are
> working out.  It is a toss up as to which should be done first,
> removing items from the Device Mangler or nuking entire registry
> strings.  Probably the best way would be to do the Device Mangler
> first and then wipe up what ever is left behind in the registry.
>
> OK we now may have a "ghost inf" situation.  Particularly with modem
> inf files, Windows likes to keep a copy of the installed device at
> Windows\INF\Other folder and if a device's inf file is to be found in
> there - Windows will automatically install it as a matter of fact with
> no (normal) options allowed to the user.  So double check your Other
> folder for monitor files and delete them if you want to force Windows
> to go looking for installation files anew.  And it's my opinion that
> you still do - this time make sure the ICM file is in the same folder
> as the monitor's inf file where ever that may be.
>
> Of course now what I'm asking that you do is everything you have
> learned so far, remove items from the Device Mangler, then delete
> entire monitor registry strings, delete INF\Other files that pertain
> to your monitor and then Reboot to allow Windows to find and install
> everything correctly.
>
> The reason the registry did not build back the key in question is
> because it did not need to.  Somewhere else in the registry was the
> old information anyway and Windows just used it as is.  I do not know
> how this happens exactly but it may also be tied to the "Default"
> monitor that won't go away and/or that is not being removed from the
> Device Mangler and/or perhaps with the Enum monitor branch of the
> registry.  When EVERYTHING is removed properly then you get your
> devices reinstalled anew and the registry written with that instance
> of reinstalled information - if there is no reinstallation then it
> should not be a surprise that the registry doesn't get written to.- Hide quoted text -
>
> - Show quoted text -

 

[PCR]

Lee wrote:
| On Mar 16, 12:12 am, "Warren" <nos...@nospam.com> wrote:

....snip
| How far should you go? As far as the road takes you, kinda like the
| length of your legs, certainly far enough to reach the ground. The
| really nice thing about all this is - it doesn't matter how far you
| take the removal of devices from the Device Mangler. Please remove
| them all just for kicks. It really doesn't matter, as it doesn't hurt
| a thing. At reboot Windows will spend some time reinstalling all that
| stuff and you might be right back where you are now - unless this
| drastic measure actually fixes the Default Monitor problem in and of
| itself. Which is very real possibility!!!
|
| I won't tell you to do it right now because you are probably sweating
| real bullets, but at least think it over some. Coincidently, the
| deletion of the entire ENUM key just prior to shutdown is one quick
| and dirty way to install Windows onto any machine by simply swapping
| out the booting hard drive to the new machine. At boot up, in the new
| machine, Windows will detect all the "new" hardware and install the
| correct drivers and poof you got Windows - neat method, if the
| legalities are a separate issue.

Theree are usually scary warnings, such as...

(1) There could be multiple reboots for Windows to get it straight.
(2) The video adapter should be set to default, before removing it.
(3) There could be a request for the Windows Installation CD.

I wonder... if things go badly... could a Registry /Restore get one back
to go?

| I have done this and it works just fine. Both via the registry and
| the Device Mangler just to be sure both methods did pretty much the
| same thing - they do. I would certainly remove all instances of the
| Default Monitor found in the registry. Your ICM file is most likely
| in the Windows\INF folder now if Windows is not asking for it's
| location, and that's just fine - it's supposed to be there if it's not
| too big along with the inf file.

My own EN5400E.ICM is in C:\WINDOWS\SYSTEM\COLOR, along with 43 others.
And my "Envision Peripherals, IncEN5400E.INF" (that's its real name) is
in C:\WINDOWS\INF\OTHER, with two others.

I can find no other file with 5400 or Envision in its name-- I think
there are no other files associated with it. And I don't see any file
mentioned in Warren's own monstrous VS080114_I19.inf other than his
VP930_Series.ICM, (not that you said there would be another). I'm
showing only the lines that mention VP930...

[DestinationDirs]
VP930_Series.CopyFiles=23

[SourceDisksFiles]
VP930_Series.ICM=1

[ViewSonic]
%VP930_Series%=VP930_Series.Install,Monitor\VSCE41B VP930_Series

[ViewSonic.NTia64]
%VP930_Series%=VP930_Series.Install,Monitor\VSCE41B VP930_Series

[ViewSonic.NTamd64]
%VP930_Series%=VP930_Series.Install,Monitor\VSCE41B VP930_Series

[VP930_Series.Install] VP930_Series
DelReg=DEL_CURRENT_REG
AddReg=VP930_Series.AddReg,1280,DPMS
Copyfiles=VP930_Series.CopyFiles

[VP930_Series.AddReg] VP930_Series
HKR,"MODES\1280,1024",Mode1,,"30-82,50-75,+,+"
HKR,,ICMProfile,0,"VP930_Series.ICM"

[VP930_Series.CopyFiles]
VP930_Series.ICM

[Strings]
VP930_Series="ViewSonic VP930 Series"

Also, that Default_Monitor is not mentioned in his .inf. It is mentioned
in Monitor.inf that we all have. I show only the lines that mention
it...

[SysCfgClasses]
Monitor, %Unknown.DeviceDesc%,MONITOR,4,%MonitorClassName% Default
to "Unknown Monitor"

Monitors to hide from pick list
-------------------------------------------------
[ControlFlags]
ExcludeFromSelect=Monitor\Default_Monitor

[Generic]
%Unknown.DeviceDesc%=Unknown.Install,Monitor\Default_Monitor for
auto-install
%Unknown.DeviceDesc%=Unknown.Install for pick list
%*PNP09FF.DeviceDesc%=VESADDC.Install,*PNP09FF

[Strings]
MonitorClassName="Monitors"
MS="Microsoft"

Generic="(Standard monitor types)"
Unknown.DeviceDesc="Default Monitor"

*PNP09FF.DeviceDesc = "Plug and Play Monitor"

| It's just nice to know exactly where
| stuff like that is actually at for a possible future "clean" Windows
| reinstallation. Clean Install is usually in reference to a Windows
| installation denoting a blank hard drive prior to the actual
| installation as in opposition to an "over the top" reinstallation of
| Windows to a hard drive that already has a working or not working
| Windows installed on 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

 

[Warren]

That's okay guys, I'm going in armed with the big guns. First, I've backed
up my hard drive with Norton Ghost, so I have a mirror image of my hard
drive on a separate disconnected hard drive as baskup. Second I'm going to
run Roxio Go Back, which allows me to undo any changes made to my active
hard drive, 99.9999999% of the time.


"PCR" <pcrrcp@netzero.net> wrote in message
news:eySnQe9hIHA.4744@TK2MSFTNGP06.phx.gbl...
> Lee wrote:
> | On Mar 16, 12:12 am, "Warren" <nos...@nospam.com> wrote:
>
> ...snip
> | How far should you go? As far as the road takes you, kinda like the
> | length of your legs, certainly far enough to reach the ground. The
> | really nice thing about all this is - it doesn't matter how far you
> | take the removal of devices from the Device Mangler. Please remove
> | them all just for kicks. It really doesn't matter, as it doesn't hurt
> | a thing. At reboot Windows will spend some time reinstalling all that
> | stuff and you might be right back where you are now - unless this
> | drastic measure actually fixes the Default Monitor problem in and of
> | itself. Which is very real possibility!!!
> |
> | I won't tell you to do it right now because you are probably sweating
> | real bullets, but at least think it over some. Coincidently, the
> | deletion of the entire ENUM key just prior to shutdown is one quick
> | and dirty way to install Windows onto any machine by simply swapping
> | out the booting hard drive to the new machine. At boot up, in the new
> | machine, Windows will detect all the "new" hardware and install the
> | correct drivers and poof you got Windows - neat method, if the
> | legalities are a separate issue.
>
> Theree are usually scary warnings, such as...
>
> (1) There could be multiple reboots for Windows to get it straight.
> (2) The video adapter should be set to default, before removing it.
> (3) There could be a request for the Windows Installation CD.
>
> I wonder... if things go badly... could a Registry /Restore get one back
> to go?
>
> | I have done this and it works just fine. Both via the registry and
> | the Device Mangler just to be sure both methods did pretty much the
> | same thing - they do. I would certainly remove all instances of the
> | Default Monitor found in the registry. Your ICM file is most likely
> | in the Windows\INF folder now if Windows is not asking for it's
> | location, and that's just fine - it's supposed to be there if it's not
> | too big along with the inf file.
>
> My own EN5400E.ICM is in C:\WINDOWS\SYSTEM\COLOR, along with 43 others.
> And my "Envision Peripherals, IncEN5400E.INF" (that's its real name) is
> in C:\WINDOWS\INF\OTHER, with two others.
>
> I can find no other file with 5400 or Envision in its name-- I think
> there are no other files associated with it. And I don't see any file
> mentioned in Warren's own monstrous VS080114_I19.inf other than his
> VP930_Series.ICM, (not that you said there would be another). I'm
> showing only the lines that mention VP930...
>
> [DestinationDirs]
> VP930_Series.CopyFiles=23
>
> [SourceDisksFiles]
> VP930_Series.ICM=1
>
> [ViewSonic]
> %VP930_Series%=VP930_Series.Install,Monitor\VSCE41B VP930_Series
>
> [ViewSonic.NTia64]
> %VP930_Series%=VP930_Series.Install,Monitor\VSCE41B VP930_Series
>
> [ViewSonic.NTamd64]
> %VP930_Series%=VP930_Series.Install,Monitor\VSCE41B VP930_Series
>
> [VP930_Series.Install] VP930_Series
> DelReg=DEL_CURRENT_REG
> AddReg=VP930_Series.AddReg,1280,DPMS
> Copyfiles=VP930_Series.CopyFiles
>
> [VP930_Series.AddReg] VP930_Series
> HKR,"MODES\1280,1024",Mode1,,"30-82,50-75,+,+"
> HKR,,ICMProfile,0,"VP930_Series.ICM"
>
> [VP930_Series.CopyFiles]
> VP930_Series.ICM
>
> [Strings]
> VP930_Series="ViewSonic VP930 Series"
>
> Also, that Default_Monitor is not mentioned in his .inf. It is mentioned
> in Monitor.inf that we all have. I show only the lines that mention
> it...
>
> [SysCfgClasses]
> Monitor, %Unknown.DeviceDesc%,MONITOR,4,%MonitorClassName% Default
> to "Unknown Monitor"
>
> Monitors to hide from pick list
> -------------------------------------------------
> [ControlFlags]
> ExcludeFromSelect=Monitor\Default_Monitor
>
> [Generic]
> %Unknown.DeviceDesc%=Unknown.Install,Monitor\Default_Monitor for
> auto-install
> %Unknown.DeviceDesc%=Unknown.Install for pick list
> %*PNP09FF.DeviceDesc%=VESADDC.Install,*PNP09FF
>
> [Strings]
> MonitorClassName="Monitors"
> MS="Microsoft"
>
> Generic="(Standard monitor types)"
> Unknown.DeviceDesc="Default Monitor"
>
> *PNP09FF.DeviceDesc = "Plug and Play Monitor"
>
> | It's just nice to know exactly where
> | stuff like that is actually at for a possible future "clean" Windows
> | reinstallation. Clean Install is usually in reference to a Windows
> | installation denoting a blank hard drive prior to the actual
> | installation as in opposition to an "over the top" reinstallation of
> | Windows to a hard drive that already has a working or not working
> | Windows installed on 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
>
>

 

[Warren]

Well I deleted all Registry keys with references to Default_Monitor and
VSCE41B (my Viewsonic monitor)

The process cleaned out a few, seemingly unimportant items in the Registry
with regard to monitors, namely:

HKLM\Software\Microsoft\Windows\CurrentVersion\cfgmgr32\Phantom\3A\,
HardWareKey,
MONITOR\DEFAULT_MONITOR\PCI_VEN_1002&DEV_5961&SUBSYS_280117EE&REV_01_000800_
1

HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\Doc Find Spec MRU\,
g, vsce41b*.*


otherwise everything regenerated, including the Default_Monitor. Here's the
list of regenerated keys currently on my system now:

Data fields are: Key, Entry's name, Value

HKLM\System\CurrentControlSet\Services\Class\Monitor\0001\,
MatchingDeviceId, Monitor\Default_Monitor

HKLM\System\CurrentControlSet\Control\ASD\Prob\{CF2524C0-29AE-11CF-97EA-00AA
0034319D}\,
MONITOR\DEFAULT_MONITOR\PCI_VEN_1002&DEV_5961&SUBSYS_280117EE&REV_01_000800_
1, N/A

HKLM\System\CurrentControlSet\Control\ASD\Prob\{9B4E7760-3196-11CF-97EA-00AA
0034319D}\,
MONITOR\DEFAULT_MONITOR\PCI_VEN_1002&DEV_5961&SUBSYS_280117EE&REV_01_000800_
1, N/A

HKLM\Enum\MONITOR\DEFAULT_MONITOR\, {KEY}, {KEY}
HKLM\Enum\MONITOR\DEFAULT_MONITOR\PCI_VEN_1002&DEV_5961&SUBSYS_280117EE&REV_
01_000800_1\, {KEY}, {KEY}
HKLM\Enum\MONITOR\DEFAULT_MONITOR\PCI_VEN_1002&DEV_5961&SUBSYS_280117EE&REV_
01_000800_1\, HardwareID, MONITOR\DEFAULT_MONITOR

HKLM\System\CurrentControlSet\Services\Class\Monitor\0000\,
MatchingDeviceId, Monitor\VSCE41B

HKLM\System\CurrentControlSet\Control\ASD\Prob\{CF2524C0-29AE-11CF-97EA-00AA
0034319D}\,
MONITOR\VSCE41B\PCI_VEN_1002&DEV_5961&SUBSYS_280117EE&REV_01_000800, N/A

HKLM\System\CurrentControlSet\Control\ASD\Prob\{9B4E7760-3196-11CF-97EA-00AA
0034319D}\,
MONITOR\VSCE41B\PCI_VEN_1002&DEV_5961&SUBSYS_280117EE&REV_01_000800, N/A

HKLM\Enum\MONITOR\VSCE41B\, {KEY}, {KEY}
HKLM\Enum\MONITOR\VSCE41B\PCI_VEN_1002&DEV_5961&SUBSYS_280117EE&REV_01_00080
0\, {KEY}, {KEY}
HKLM\Enum\MONITOR\VSCE41B\PCI_VEN_1002&DEV_5961&SUBSYS_280117EE&REV_01_00080
0\, HardwareID, MONITOR\VSCE41B


"Warren" <nospam@nospam.com> wrote in message
news:%23f2Own9hIHA.2304@TK2MSFTNGP05.phx.gbl...
> That's okay guys, I'm going in armed with the big guns. First, I've
backed
> up my hard drive with Norton Ghost, so I have a mirror image of my hard
> drive on a separate disconnected hard drive as baskup. Second I'm going
to
> run Roxio Go Back, which allows me to undo any changes made to my active
> hard drive, 99.9999999% of the time.
>
>
> "PCR" <pcrrcp@netzero.net> wrote in message
> news:eySnQe9hIHA.4744@TK2MSFTNGP06.phx.gbl...
> > Lee wrote:
> > | On Mar 16, 12:12 am, "Warren" <nos...@nospam.com> wrote:
> >
> > ...snip
> > | How far should you go? As far as the road takes you, kinda like the
> > | length of your legs, certainly far enough to reach the ground. The
> > | really nice thing about all this is - it doesn't matter how far you
> > | take the removal of devices from the Device Mangler. Please remove
> > | them all just for kicks. It really doesn't matter, as it doesn't hurt
> > | a thing. At reboot Windows will spend some time reinstalling all that
> > | stuff and you might be right back where you are now - unless this
> > | drastic measure actually fixes the Default Monitor problem in and of
> > | itself. Which is very real possibility!!!
> > |
> > | I won't tell you to do it right now because you are probably sweating
> > | real bullets, but at least think it over some. Coincidently, the
> > | deletion of the entire ENUM key just prior to shutdown is one quick
> > | and dirty way to install Windows onto any machine by simply swapping
> > | out the booting hard drive to the new machine. At boot up, in the new
> > | machine, Windows will detect all the "new" hardware and install the
> > | correct drivers and poof you got Windows - neat method, if the
> > | legalities are a separate issue.
> >
> > Theree are usually scary warnings, such as...
> >
> > (1) There could be multiple reboots for Windows to get it straight.
> > (2) The video adapter should be set to default, before removing it.
> > (3) There could be a request for the Windows Installation CD.
> >
> > I wonder... if things go badly... could a Registry /Restore get one back
> > to go?
> >
> > | I have done this and it works just fine. Both via the registry and
> > | the Device Mangler just to be sure both methods did pretty much the
> > | same thing - they do. I would certainly remove all instances of the
> > | Default Monitor found in the registry. Your ICM file is most likely
> > | in the Windows\INF folder now if Windows is not asking for it's
> > | location, and that's just fine - it's supposed to be there if it's not
> > | too big along with the inf file.
> >
> > My own EN5400E.ICM is in C:\WINDOWS\SYSTEM\COLOR, along with 43 others.
> > And my "Envision Peripherals, IncEN5400E.INF" (that's its real name) is
> > in C:\WINDOWS\INF\OTHER, with two others.
> >
> > I can find no other file with 5400 or Envision in its name-- I think
> > there are no other files associated with it. And I don't see any file
> > mentioned in Warren's own monstrous VS080114_I19.inf other than his
> > VP930_Series.ICM, (not that you said there would be another). I'm
> > showing only the lines that mention VP930...
> >
> > [DestinationDirs]
> > VP930_Series.CopyFiles=23
> >
> > [SourceDisksFiles]
> > VP930_Series.ICM=1
> >
> > [ViewSonic]
> > %VP930_Series%=VP930_Series.Install,Monitor\VSCE41B VP930_Series
> >
> > [ViewSonic.NTia64]
> > %VP930_Series%=VP930_Series.Install,Monitor\VSCE41B VP930_Series
> >
> > [ViewSonic.NTamd64]
> > %VP930_Series%=VP930_Series.Install,Monitor\VSCE41B VP930_Series
> >
> > [VP930_Series.Install] VP930_Series
> > DelReg=DEL_CURRENT_REG
> > AddReg=VP930_Series.AddReg,1280,DPMS
> > Copyfiles=VP930_Series.CopyFiles
> >
> > [VP930_Series.AddReg] VP930_Series
> > HKR,"MODES\1280,1024",Mode1,,"30-82,50-75,+,+"
> > HKR,,ICMProfile,0,"VP930_Series.ICM"
> >
> > [VP930_Series.CopyFiles]
> > VP930_Series.ICM
> >
> > [Strings]
> > VP930_Series="ViewSonic VP930 Series"
> >
> > Also, that Default_Monitor is not mentioned in his .inf. It is mentioned
> > in Monitor.inf that we all have. I show only the lines that mention
> > it...
> >
> > [SysCfgClasses]
> > Monitor, %Unknown.DeviceDesc%,MONITOR,4,%MonitorClassName% Default
> > to "Unknown Monitor"
> >
> > Monitors to hide from pick list
> > -------------------------------------------------
> > [ControlFlags]
> > ExcludeFromSelect=Monitor\Default_Monitor
> >
> > [Generic]
> > %Unknown.DeviceDesc%=Unknown.Install,Monitor\Default_Monitor for
> > auto-install
> > %Unknown.DeviceDesc%=Unknown.Install for pick list
> > %*PNP09FF.DeviceDesc%=VESADDC.Install,*PNP09FF
> >
> > [Strings]
> > MonitorClassName="Monitors"
> > MS="Microsoft"
> >
> > Generic="(Standard monitor types)"
> > Unknown.DeviceDesc="Default Monitor"
> >
> > *PNP09FF.DeviceDesc = "Plug and Play Monitor"
> >
> > | It's just nice to know exactly where
> > | stuff like that is actually at for a possible future "clean" Windows
> > | reinstallation. Clean Install is usually in reference to a Windows
> > | installation denoting a blank hard drive prior to the actual
> > | installation as in opposition to an "over the top" reinstallation of
> > | Windows to a hard drive that already has a working or not working
> > | Windows installed on 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
> >
> >
>
>

 

[PCR]

Warren wrote:
| Well I deleted all Registry keys with references to Default_Monitor
| and VSCE41B (my Viewsonic monitor)

Hmm. I thought you meant you were about to delete the entire ENUM key or
otherwise decimate all manner of devices listed in Device Manager--
which is a far more perilous affair! I don't want it on my head-- even
if you do have two full backups. Of the two, Norton Ghost sounds to be
independent of Windows. Does Roxio Go Back require a boot to Windows for
it to work? (I use neither of those two.) Therefore... let it be on
Lee's head, or even on Terhune's or glee's, who also have posted of such
things in the past!

If using Device Manager, I know you must remove the child devices,
before you may remove the parents. Also, it may be advisable to set the
display adapter to "Standard Display Adapter (VGA)" first, if you intend
to remove that one. Finally, I've read you may expect multiple reboots
for some of them to come back. And I hope you won't be requested to
insert the Windows Installation CD or any other CD-- especially if
that's one of the devices you've removed!

| The process cleaned out a few, seemingly unimportant items in the
| Registry with regard to monitors, namely:
|
| HKLM\Software\Microsoft\Windows\CurrentVersion\cfgmgr32\Phantom\3A\,
| HardWareKey,
|
MONITOR\DEFAULT_MONITOR\PCI_VEN_1002&DEV_5961&SUBSYS_280117EE&REV_01_000
800_
| 1

Hmm. Interesting that should be gone. That one kept coming back for you
before. It's one of 3 we kind of had in common. As you recall, mine
is...

[HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\cfgmgr32\P
hantom\C]
"HardWareKey"="MONITOR\\DEFAULT_MONITOR\\0001"
"DevNode"=dword:0000000c

We tried to make your three look like my three to no avail-- you still
had the Default Monitor showing in Device Manager at reboot.

| HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\Doc Find Spec
| MRU\, g, vsce41b*.*

Values in MRU (Most Recently Used) lists generally may be ignored. They
will go on their own eventually. Doc Find Spec is the list you see at
"START button, Find, F/F" by clicking the D-Arrow to the right of the
Named box.

| otherwise everything regenerated, including the Default_Monitor.
| Here's the list of regenerated keys currently on my system now:
|
| Data fields are: Key, Entry's name, Value
|
| HKLM\System\CurrentControlSet\Services\Class\Monitor\0001\,
| MatchingDeviceId, Monitor\Default_Monitor

That's one of your extras. We tried deleting it along with the
corresponding one in ENUM to no avail. You did finally succeed in
deleting for good a ton of junk under this Monitor key-- but one
instance of Default Monitor just won't go!

|
HKLM\System\CurrentControlSet\Control\ASD\Prob\{CF2524C0-29AE-11CF-97EA-
00AA
| 0034319D}\,
|
MONITOR\DEFAULT_MONITOR\PCI_VEN_1002&DEV_5961&SUBSYS_280117EE&REV_01_000
800_
| 1, N/A

That's the 2nd of the three we kind of had in common. Mine is...

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

|
HKLM\System\CurrentControlSet\Control\ASD\Prob\{9B4E7760-3196-11CF-97EA-
00AA
| 0034319D}\,
|
MONITOR\DEFAULT_MONITOR\PCI_VEN_1002&DEV_5961&SUBSYS_280117EE&REV_01_000
800_
| 1, N/A

And that's the 3rd...

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

We had your 3 looking like mine-- to no avail! (Interesting you've
suddenly lost one, though.)

| HKLM\Enum\MONITOR\DEFAULT_MONITOR\, {KEY}, {KEY}
|
HKLM\Enum\MONITOR\DEFAULT_MONITOR\PCI_VEN_1002&DEV_5961&SUBSYS_280117EE&
REV_
| 01_000800_1\, {KEY}, {KEY}
|
HKLM\Enum\MONITOR\DEFAULT_MONITOR\PCI_VEN_1002&DEV_5961&SUBSYS_280117EE&
REV_
| 01_000800_1\, HardwareID, MONITOR\DEFAULT_MONITOR

We tried deleting that DEFAULT_MONITOR with the "Monitor\0001" above--
to no avail. The Default Monitor would not go! There was a bit of
success getting rid of the stuff in you mirror HKEY_CURRENT_CONFIG\Enum
key, though.

| HKLM\System\CurrentControlSet\Services\Class\Monitor\0000\,
| MatchingDeviceId, Monitor\VSCE41B
|
|
HKLM\System\CurrentControlSet\Control\ASD\Prob\{CF2524C0-29AE-11CF-97EA-
00AA
| 0034319D}\,
| MONITOR\VSCE41B\PCI_VEN_1002&DEV_5961&SUBSYS_280117EE&REV_01_000800,
| N/A
|
|
HKLM\System\CurrentControlSet\Control\ASD\Prob\{9B4E7760-3196-11CF-97EA-
00AA
| 0034319D}\,
| MONITOR\VSCE41B\PCI_VEN_1002&DEV_5961&SUBSYS_280117EE&REV_01_000800,
| N/A
|
| HKLM\Enum\MONITOR\VSCE41B\, {KEY}, {KEY}
|
HKLM\Enum\MONITOR\VSCE41B\PCI_VEN_1002&DEV_5961&SUBSYS_280117EE&REV_01_0
0080
| 0\, {KEY}, {KEY}
|
HKLM\Enum\MONITOR\VSCE41B\PCI_VEN_1002&DEV_5961&SUBSYS_280117EE&REV_01_0
0080
| 0\, HardwareID, MONITOR\VSCE41B

Those VSCE41B keys are appearing in the same places as Default_Monitor,
I think. Therefore, they too were deleted with the aforementioned
deletes, & it no longer helps to post them. It was a good thought,
though.

I'm online & hope to get to that other thread & resume my search at the
MS Library.

|
| "Warren" <nospam@nospam.com> wrote in message
| news:%23f2Own9hIHA.2304@TK2MSFTNGP05.phx.gbl...
|> That's okay guys, I'm going in armed with the big guns. First, I've
|> backed up my hard drive with Norton Ghost, so I have a mirror image
|> of my hard drive on a separate disconnected hard drive as baskup.
|> Second I'm going to run Roxio Go Back, which allows me to undo any
|> changes made to my active hard drive, 99.9999999% of the time.
|>
|>
|> "PCR" <pcrrcp@netzero.net> wrote in message
|> news:eySnQe9hIHA.4744@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