Trouble with new display and Device Manager

Warren · Feb 22, 2008

Re: Trouble with new display and Device Manager

Yes Brian, that is exactly the file I downloaded from Viewsonic and
installed.

I found VS080114_I19.inf in C:\Windows\Inf and typed the whole path to the
file but the computer said there is no information about my hardware in this
file.

"Brian A." <gonefish'n@afarawaylake> wrote in message
news:%234WkRjcdIHA.5200@TK2MSFTNGP06.phx.gbl...
> Open Explorer.
> Expand the tree to C:\Windows\Inf.
> Scroll through the files in the Right pane and see if VS080114_I19.inf is
present in
> the folder.
> If it is then you need to remove the "Hidden" attribute on the INF folder.
When the
> folder is set as hidden you will not be able to see it using browse to get
to and
> select the file.
>
> If it isn't there or you would rather get the driver files from
ViewSonics support
> site, they can be obtained here:
>
http://www.viewsonic.com/support/drivers/driver_information.cfm?category=1&formName=monitor&key=36
>
> This is an updated file VS080115.
> Create a new folder to save the file to.
> Extract the contents of the file into the same folder.
> Run the Setup.exe from the folder.
>
> --
>
>
> Brian A. Sesko { MS MVP_Windows Desktop User Experience }
> Conflicts start where information lacks.
> http://basconotw.mvps.org/
>
> Suggested posting do's/don'ts: http://www.dts-l.org/goodpost.htm
> How to ask a question: http://support.microsoft.com/kb/555375
>
>
> "Warren" <nospam@nospam.com> wrote in message
> news:OYD9xbcdIHA.4164@TK2MSFTNGP05.phx.gbl...
> > Brian,
> >
> > Unfortunately when I search for a file"VS080114_I19.inf" it cannot be
found
> > on my hard drive. I think I successfuly converted to a Viewsonic
monitor by
> > pointing to "%VCDTS21367-1%" , the driver being used for my VP930b
monitor
> > but I still end up with two monitors, which I don't want.
> >
> >
> > "Brian A." <gonefish'n@afarawaylake> wrote in message
> > news:%23wP%23hBcdIHA.4172@TK2MSFTNGP02.phx.gbl...
> >> "Warren" <nospam@nospam.com> wrote in message
> >> news:%235fmYYEdIHA.4144@TK2MSFTNGP05.phx.gbl...
> >> <snipped>
> >> >>
> >> >> (a) "START button, Find, F/F"
> >> >> (b) Leave "Named" empty.
> >> >> (c) In "Containing text", enter... "ViewSonic VP930 Series"
> >> >> with the quotes.
> >> >> (d) In "Look in", browse to... "C:\WINDOWS\INF".
> >> >
> >> > !!!Nothing found searching for text "VSCE41B"
> >> > !!!VS080114_I19.inf found searching for text "ViewSonic VP930
Series".
> >> >
> >> <snipped>
> >>
> >> Right click MyComputer.
> >> Click "Properties" in the popup menu.
> >> Click the "Device Manager" tab.
> >> Expand "Monitors".
> >> Double click on the "Default Monitor" device listed to open its
> > properties.
> >> Click the "Driver" tab > "Update Driver" button.
> >> Click "Next".
> >> Select "Display a list of all drivers in a specific location,......"
and
> > click
> >> "Next".
> >> Click the "Have Disk" Button.
> >> Click the "Browse" button and navigate to the
> > Directory\Folder\VS080114_I19.inf file
> >> you found earlier.
> >> Select the VS080114_I19.inf file in the Left pane and click Ok > Ok >
> > Next.
> >> Follow the prompts to finish installing the driver.
> >>
> >>
> >> --
> >>
> >>
> >> Brian A. Sesko { MS MVP_Windows Desktop User Experience }
> >> Conflicts start where information lacks.
> >> http://basconotw.mvps.org/
> >>
> >> Suggested posting do's/don'ts: http://www.dts-l.org/goodpost.htm
> >> How to ask a question: http://support.microsoft.com/kb/555375
> >>
> >>
> >
> >
>

Franc Zabkar · Feb 23, 2008

Re: Trouble with new display and Device Manager

On Sat, 16 Feb 2008 18:30:15 -0500, "Warren" <nospam@nospam.com> put
finger to keyboard and composed:

>I had trouble getting the right drivers installed for my Viewsonic LCD.
>Essentially I ended up booting up the machine with no drivers and Windows
>installed a Default Monitor. After finally getting the correct drivers
>installed on my computer the correct drivers where installed but the
>computer still thinks there's an unknown monitor attached to the machine and
>keeps recreating the Default Monitor at start-up.
>
>How do I fix this false detection of an unknown monitor ?

I just checked my other Win98SE box. It has an SiS Xabre AGP card.
Just as in your case, there are two entries in DM, one for a Default
Monitor, the second for an AOC LCD monitor. Deleting the Default
monitor causes it to be redetected on reboot.

If the default entry really bugs you, then perhaps you could disable
PnP monitor detection by r-clicking a blank area of your desktop,
select Properties -> Settings -> Advanced -> Monitor and uncheck
"Automatically detect PnP monitors". Delete the monitors from DM and
reboot. You will then need to manually reinstall your monitor by
pointing Windows to the appropriate INF file.

- Franc Zabkar
--
Please remove one 'i' from my address when replying by email.

Warren · Feb 23, 2008

Re: Trouble with new display and Device Manager

Unfortunately part of my problem is I can't figure out where to point
Windows. I can point to the VP930_Series.inf on the CD-ROM and it seems
happy until it looks for the VP930_Series.icm file. I have this file on the
CD-ROM, C:\Windows\Inf directory and yet the installer won't accept either
version of this file. Very strange

"Franc Zabkar" <fzabkar@iinternode.on.net> wrote in message
news:ks01s3d8fufqfgp7oj50kdchuj9jtopvuk@4ax.com...
> On Sat, 16 Feb 2008 18:30:15 -0500, "Warren" <nospam@nospam.com> put
> finger to keyboard and composed:
>
> >I had trouble getting the right drivers installed for my Viewsonic LCD.
> >Essentially I ended up booting up the machine with no drivers and Windows
> >installed a Default Monitor. After finally getting the correct drivers
> >installed on my computer the correct drivers where installed but the
> >computer still thinks there's an unknown monitor attached to the machine
and
> >keeps recreating the Default Monitor at start-up.
> >
> >How do I fix this false detection of an unknown monitor ?
>
> I just checked my other Win98SE box. It has an SiS Xabre AGP card.
> Just as in your case, there are two entries in DM, one for a Default
> Monitor, the second for an AOC LCD monitor. Deleting the Default
> monitor causes it to be redetected on reboot.
>
> If the default entry really bugs you, then perhaps you could disable
> PnP monitor detection by r-clicking a blank area of your desktop,
> select Properties -> Settings -> Advanced -> Monitor and uncheck
> "Automatically detect PnP monitors". Delete the monitors from DM and
> reboot. You will then need to manually reinstall your monitor by
> pointing Windows to the appropriate INF file.
>
> - Franc Zabkar
> --
> Please remove one 'i' from my address when replying by email.

PCR · Feb 23, 2008

Re: Trouble with new display and Device Manager

Warren wrote:
| !!!Please see comments below
|
| "PCR" <pcrrcp@netzero.net> wrote in message
| news:u2ynvpDdIHA.2404@TK2MSFTNGP05.phx.gbl...

Continue to work with Brian A. I hesitate to say you should R-Clk your
..inf & select "Install". I'm just not sure that monster will itself know
you are Win98 istead of the other OS it also will work for. There might
be something else the full install process must do first-- I don't know.

You owe me a response to a nearby post. Also, I have found another
interesting Registry key. Post yours...

[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor]
@="Monitors"
"Installer"="SetupX.Dll, Monitor_ClassInstaller"
"Icon"="-1"
"Link"="{4d36e96e-e325-11ce-bfc1-08002be10318}"

[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor\0000
]
"ICMProfile"=hex:45,4e,35,34,30,30,65,2e,69,63,6d,00,00
"MaxResolution"="1024,768"
"DPMS"="1"
"InfPath"="ENVISI~1.INF"
"InfSection"="E564.Install"
"ProviderName"="Envision Peripherals, Inc"
"DriverDate"=" 8-20-2004"
"DriverDesc"="Envision EN5400e"
"MatchingDeviceId"="Monitor\\EPIE564"

[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor\0000
\MODES]

[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor\0000
\MODES\640,480]
"Mode1"="30.0-63.0,55.0-75.0,-,-"

[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor\0000
\MODES\800,600]
"Mode1"="30.0-63.0,55.0-75.0,+,+"

[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor\0000
\MODES\1024,768]
"Mode1"="30.0-63.0,55.0-75.0,+,+"

NOTE... "ICMProfile" actually says "EN5400e.icm". Yours hopefully
will say "VP930_Series.ICM"; R-Clk it in RegEdit & select "Modify" to
see.

--
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 · Feb 23, 2008

Re: Trouble with new display and Device Manager

Wow!

[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor]
@="Monitors"
"Installer"="SetupX.Dll, Monitor_ClassInstaller"
"Icon"="-1"
"Link"="{4D36E96E-E325-11CE-BFC1-08002BE10318}"

[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor\0001]
"InfPath"="MONITOR.INF"
"InfSection"="Unknown.Install"
"ProviderName"="Microsoft"
"DriverDate"=" 4-23-1999"
"DriverDesc"="Default Monitor"
"MatchingDeviceId"="Monitor\\Default_Monitor"

[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor\0001\MOD
ES]

[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor\0001\MOD
ES\640,480]
@=""

[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor\0004]
"MaxResolution"="1600,1200"
"DPMS"="1"
"InfPath"="MONITOR.INF"
"InfSection"="VESADDC.Install"
"ProviderName"="Microsoft"
"DriverDate"=" 4-23-1999"
"DriverDesc"="Plug and Play Monitor"
"MatchingDeviceId"="*PNP09FF"

[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor\0004\MOD
ES]

[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor\0004\MOD
ES\1600,1200]
@=""

[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor\0005]
"MaxResolution"="1600,1200"
"DPMS"="1"
"InfPath"="MONITOR.INF"
"InfSection"="VESADDC.Install"
"ProviderName"="Microsoft"
"DriverDate"=" 4-23-1999"
"DriverDesc"="Plug and Play Monitor"
"MatchingDeviceId"="*PNP09FF"

[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor\0005\MOD
ES]

[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor\0005\MOD
ES\1600,1200]
@=""

[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor\0006]
"InfPath"="MONITOR.INF"
"InfSection"="Unknown.Install"
"ProviderName"="Microsoft"
"DriverDate"=" 4-23-1999"
"DriverDesc"="Default Monitor"
"MatchingDeviceId"="Monitor\\Default_Monitor"

[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor\0006\MOD
ES]

[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor\0006\MOD
ES\640,480]
@=""

[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor\0007]
"InfPath"="MONITOR.INF"
"InfSection"="Unknown.Install"
"ProviderName"="Microsoft"
"DriverDate"=" 4-23-1999"
"DriverDesc"="Default Monitor"
"MatchingDeviceId"="Monitor\\Default_Monitor"

[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor\0007\MOD
ES]

[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor\0007\MOD
ES\640,480]
@=""

[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor\0008]
"ICMProfile"=hex:56,50,39,33,30,5f,53,65,72,69,65,73,2e,49,43,4d,00,00
"MaxResolution"="1280,1024"
"DPMS"="1"
"InfPath"="VIEWSO~1.INF"
"InfSection"="VP930_Series.Install"
"ProviderName"="ViewSonic"
"DriverDate"=" 2-16-2008"
"DriverDesc"="ViewSonic VP930 Series"
"MatchingDeviceId"="Monitor\\VSCE41B"

[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor\0008\MOD
ES]

[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor\0008\MOD
ES\1280,1024]
"Mode1"="30-82,50-75,+,+"

[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor\0009]
"InfPath"="MONITOR.INF"
"InfSection"="Unknown.Install"
"ProviderName"="Microsoft"
"DriverDate"=" 4-23-1999"
"DriverDesc"="Default Monitor"
"MatchingDeviceId"="Monitor\\Default_Monitor"

[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor\0009\MOD
ES]

[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor\0009\MOD
ES\640,480]
@=""

[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor\0010]
"ICMProfile"=hex:56,50,39,33,30,5f,53,65,72,69,65,73,2e,49,43,4d,00,00
"MaxResolution"="1280,1024"
"DPMS"="1"
"InfPath"="VIEWSO~1.INF"
"InfSection"="VP930_Series.Install"
"ProviderName"="ViewSonic"
"DriverDate"=" 2-16-2008"
"DriverDesc"="ViewSonic VP930 Series"
"MatchingDeviceId"="Monitor\\VSCE41B"

[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor\0010\MOD
ES]

[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor\0010\MOD
ES\1280,1024]
"Mode1"="30-82,50-75,+,+"

[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor\0011]
"InfPath"="MONITOR.INF"
"InfSection"="Unknown.Install"
"ProviderName"="Microsoft"
"DriverDate"=" 4-23-1999"
"DriverDesc"="Default Monitor"
"MatchingDeviceId"="Monitor\\Default_Monitor"

[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor\0011\MOD
ES]

[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor\0011\MOD
ES\640,480]
@=""

[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor\0000]
"ICMProfile"=hex:56,50,39,33,30,5f,53,65,72,69,65,73,2e,49,43,4d,00,00
"MaxResolution"="1280,1024"
"DPMS"="1"
"InfPath"="VIEWSO~1.INF"
"InfSection"="VP930_Series.Install"
"ProviderName"="ViewSonic"
"DriverDate"=" 2-16-2008"
"DriverDesc"="ViewSonic VP930 Series"
"MatchingDeviceId"="Monitor\\VSCE41B"

[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor\0000\MOD
ES]

[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor\0000\MOD
ES\1280,1024]
"Mode1"="30-82,50-75,+,+"

[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor\0002]
"InfPath"="MONITOR.INF"
"InfSection"="Unknown.Install"
"ProviderName"="Microsoft"
"DriverDate"=" 4-23-1999"
"DriverDesc"="Default Monitor"
"MatchingDeviceId"="Monitor\\Default_Monitor"

[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor\0002\MOD
ES]

[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor\0002\MOD
ES\640,480]
@=""

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

[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor\0003\MOD
ES]

[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor\0003\MOD
ES\1600,1280]
"Mode1"="30-95,50-160,+,+"

[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor\0012]
"ICMProfile"=hex:56,50,39,33,30,5f,53,65,72,69,65,73,2e,49,43,4d,00,00
"MaxResolution"="1280,1024"
"DPMS"="1"
"InfPath"="VIEWSO~1.INF"
"InfSection"="VP930_Series.Install"
"ProviderName"="ViewSonic"
"DriverDate"=" 2-16-2008"
"DriverDesc"="ViewSonic VP930 Series"
"MatchingDeviceId"="Monitor\\VSCE41B"

[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor\0012\MOD
ES]

[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor\0012\MOD
ES\1280,1024]
"Mode1"="30-82,50-75,+,+"

[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor\0013]
"InfPath"="MONITOR.INF"
"InfSection"="Unknown.Install"
"ProviderName"="Microsoft"
"DriverDate"=" 4-23-1999"
"DriverDesc"="Default Monitor"
"MatchingDeviceId"="Monitor\\Default_Monitor"

[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor\0013\MOD
ES]

[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor\0013\MOD
ES\640,480]
@=""

[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor\0014]
"ICMProfile"=hex:56,50,39,33,30,5f,53,65,72,69,65,73,2e,49,43,4d,00,00
"MaxResolution"="1280,1024"
"DPMS"="1"
"InfPath"="VIEWSO~1.INF"
"InfSection"="VP930_Series.Install"
"ProviderName"="ViewSonic"
"DriverDate"=" 2-16-2008"
"DriverDesc"="ViewSonic VP930 Series"
"MatchingDeviceId"="Monitor\\VSCE41B"

[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor\0014\MOD
ES]

[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor\0014\MOD
ES\1280,1024]
"Mode1"="30-82,50-75,+,+"

[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor\0015]
"InfPath"="MONITOR.INF"
"InfSection"="Unknown.Install"
"ProviderName"="Microsoft"
"DriverDate"=" 4-23-1999"
"DriverDesc"="Default Monitor"
"MatchingDeviceId"="Monitor\\Default_Monitor"

[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor\0015\MOD
ES]

[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor\0015\MOD
ES\640,480]
@=""

"PCR" <pcrrcp@netzero.net> wrote in message
news:%23IdnEpodIHA.2448@TK2MSFTNGP03.phx.gbl...
> Warren wrote:
> | !!!Please see comments below
> |
> | "PCR" <pcrrcp@netzero.net> wrote in message
> | news:u2ynvpDdIHA.2404@TK2MSFTNGP05.phx.gbl...
>
> Continue to work with Brian A. I hesitate to say you should R-Clk your
> .inf & select "Install". I'm just not sure that monster will itself know
> you are Win98 istead of the other OS it also will work for. There might
> be something else the full install process must do first-- I don't know.
>
> You owe me a response to a nearby post. Also, I have found another
> interesting Registry key. Post yours...
>
> [HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor]
> @="Monitors"
> "Installer"="SetupX.Dll, Monitor_ClassInstaller"
> "Icon"="-1"
> "Link"="{4d36e96e-e325-11ce-bfc1-08002be10318}"
>
> [HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor\0000
> ]
> "ICMProfile"=hex:45,4e,35,34,30,30,65,2e,69,63,6d,00,00
> "MaxResolution"="1024,768"
> "DPMS"="1"
> "InfPath"="ENVISI~1.INF"
> "InfSection"="E564.Install"
> "ProviderName"="Envision Peripherals, Inc"
> "DriverDate"=" 8-20-2004"
> "DriverDesc"="Envision EN5400e"
> "MatchingDeviceId"="Monitor\\EPIE564"
>
> [HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor\0000
> \MODES]
>
> [HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor\0000
> \MODES\640,480]
> "Mode1"="30.0-63.0,55.0-75.0,-,-"
>
> [HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor\0000
> \MODES\800,600]
> "Mode1"="30.0-63.0,55.0-75.0,+,+"
>
> [HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor\0000
> \MODES\1024,768]
> "Mode1"="30.0-63.0,55.0-75.0,+,+"
>
>
> NOTE... "ICMProfile" actually says "EN5400e.icm". Yours hopefully
> will say "VP930_Series.ICM"; R-Clk it in RegEdit & select "Modify" to
> see.
>
>
> --
> 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 · Feb 23, 2008

Re: Trouble with new display and Device Manager

***See responses below

"PCR" <pcrrcp@netzero.net> wrote in message
news:%23917VgcdIHA.4164@TK2MSFTNGP05.phx.gbl...
> Warren wrote:
> | !!!Please see comments below
> |
> | "PCR" <pcrrcp@netzero.net> wrote in message
> | news:u2ynvpDdIHA.2404@TK2MSFTNGP05.phx.gbl...
> |> Warren wrote:
>
> You did everything right in Safe Mode to try & remove the Default
> Monitor. I posted separately how to try it directly in the Registry.
>
> ...snip
> |> | (c) Default monitor - Generic Television
> |>
> |> If I were to select "(Standard monitor types)" in the left
> |> (Manufacturers) pane, then (among others), I am offered "Generic
> |> Television" in the right (Models) pane. So, that almost sounds
> |> right-- IF you wanted it.
> |
> | !!!Yes, "Standard monitor types was in left window" and "Generic
> | Television" in the right window
>
> OK. That is as it should be in the Update Driver screen. But we don't
> want it also showing up in Device Manager.
>
> |> | VP930 monitor - %VCDTS21367-1% (I have no idea what this
> |> | garbage is but the seemingly more appropriate driver for VP 930
> |> | Series seems to be available)
> |>
> |> That doesn't sound exactly right. At that screen...
> |>
> |> "Device Manager, Monitors branch, D-Clk 'Envision EN5400e', Driver
> |> tab, Update Driver button, Next, bolt 'Display a list...", Next,
> |> bolt 'Show all hardware"
> |>
> |> ..., in the left (Manufacturers) pane, I see...
> |>
> |> Envision Peripherals, Inc
> |>
> |> ..., &, in the right (Models) pane, I see...
> |>
> |> Envision EN5400e
> |>
> |> ...You seem to be seeing gobbledygook in the Models pane at least!
> |> YET, the following ViewSonic VP930 Series entry looks perfectly fine
> |> to me in your MSInfo32 screen...
> |
> | !!!Yes I have "Viewsonic" in the left window and "%VCDTS21367-1%" in
> | the right window. Unfortunately when I select the VP930 Series entry
> | in the right window, it wants the CD_ROM but can't find the files it
> | wants (even though I know they are there). This is the scenario that
> | caused the creation of the Default Monitor in the first place, the
> | machine couldn't get the drivers off the CD-ROM for some silly reason.
> |
> | !!!I've sent an e-mail to Viewsonic asking if this driver
> | "%VCDTS21367-1%" is appropriate, and if not how to change it. I'm
> | also not sure where the driver installer placed all the drivers.
>
> That is a mess! But there is no such driver as "%VCDTS21367-1%". It
> looks to me like it is a variable that should have changed to a model
> name. You did also get the correct model -- ViewSonic VP930 Series -- in
> the right pane, though. However, "%VCDTS21367-1%" is the one highlighted
> in the R-Pane. When you try to switch to VP930, a disk is requested &
> the drivers won't be found. Yucky!
>
> |> | (d) ViewSonic VP930 Series
> |> | Monitor
> |> | Registry Key:
> |> |
> |>
> HKEY_LOCAL_MACHINE\enum\MONITOR\VSCE41B\PCI_VEN_1002&DEV_5961&SUBSYS_280
> |> 117E
> |> | E&REV_01_000800
> |> | Alloc resources: None
> |> | Forced resources: None
> |> | Boot resources: None
> |> | Filtered resources: None
> |> | Basic resources: None
> |> | Driver: Monitor\0000
> |> | Driver Date: 2-16-2008
> |> | Driver: VP930_Series.ICM
> |> | File Size:
> |> | Driver Not Installed
> |> | File Date:
> |> | Driver Not Installed
> |>
> |> The above looks a lot like mine-- which works perfectly! And I get no
> |> Default Monitor anywhere.
> |>
> |> (1) Post your Registry key, as Zabcar did...
> |>
> |> HKEY_LOCAL_MACHINE\Enum\MONITOR
> |>
> |> (a) "START button, Run, RegEdit".
> |> (b) Click the plus sign to left of "HKEY_LOCAL_MACHINE".
> |> (c) Click the plus sign left of "Enum".
> |> (d) Click "MONITOR" in the left pane.
> |> (e) Click "Export Registry File" in the "Registry" menu.
> |>
> |> Have it create a ".txt" file. It will contain the Key that is
> |> selected in the left pane, it's sub-keys & the data in the
> |> right pane.
> |>
> |> (f) Close RegEdit, & post the file.
> |
> | [HKEY_LOCAL_MACHINE\Enum\MONITOR]
> |
> | [HKEY_LOCAL_MACHINE\Enum\MONITOR\VSCE41B]
> |
> |
> [HKEY_LOCAL_MACHINE\Enum\MONITOR\VSCE41B\PCI_VEN_1002&DEV_5961&SUBSYS_28
> 0117
> | EE&REV_01_000800]
> | "Capabilities"=hex:14,00,00,00
> | "InitMonitorPowerState"="0f"
> |
> "EDID"=hex:00,ff,ff,ff,ff,ff,ff,00,5a,63,1b,e4,01,01,01,01,14,10,01,03,0
> e,26
> | ,\
> |
> |
> 1f,78,2e,11,45,a4,5a,4a,a0,24,14,50,54,bf,ef,80,81,80,81,40,71,4f,01,01,
> 01,\
> |
> |
> 01,01,01,01,01,01,01,30,2a,00,98,51,00,2a,40,30,70,13,00,78,36,11,00,00,
> 1e,\
> |
> |
> 00,00,00,ff,00,51,38,48,30,36,32,30,30,31,32,35,30,0a,00,00,00,fd,00,32,
> 4b,\
> |
> |
> 1e,52,0e,00,0a,20,20,20,20,20,20,00,00,00,fc,00,56,50,39,33,30,20,53,65,
> 72,\
> | 69,65,73,0a,00,e5
> | "HardwareID"="Monitor\\VSCE41B"
> | "Class"="Monitor"
> | "SerialNum"="Q8H062001250"
> | "DeviceDesc"="ViewSonic VP930 Series"
> | "MaxResolution"="1280,1024"
> | "MonitorRanges"="30-82,50-75,+,+"
> | "DPMS"="1"
> | "ClassGUID"="{4D36E96E-E325-11CE-BFC1-08002BE10318}"
> | "Driver"="Monitor\\0000"
> | "Mfg"="ViewSonic"
> | "ConfigFlags"=hex:00,00,00,00
>
> The above looks GOOD to me-- it compares well to mine, as did your
> MSInfo! And you haven't complained it isn't working. Problems...
>
> (a) There is gobbledygook in your Update Driver requestor,
> which comes up showing the gobbledygook selected.
> (b) Default Monitor won't go!
>
> | [HKEY_LOCAL_MACHINE\Enum\MONITOR\DEFAULT_MONITOR]
> |
> |
> [HKEY_LOCAL_MACHINE\Enum\MONITOR\DEFAULT_MONITOR\PCI_VEN_1002&DEV_5961&S
> UBSY
> | S_280117EE&REV_01_000800_1]
> | "Capabilities"=hex:14,00,00,00
> | "InitMonitorPowerState"="0f"
> | "HardwareID"="Monitor\\Default_Monitor"
> | "ClassGUID"="{4D36E96E-E325-11CE-BFC1-08002BE10318}"
> | "Class"="Monitor"
> | "Driver"="Monitor\\0002"
> | "Mfg"="(Standard monitor types)"
> | "DeviceDesc"="Default Monitor"
> | "ConfigFlags"=hex:00,00,00,00
>
> Try deleting just the above as I posted separately.
>
> |> I expect we will see two sub-keys under "MONITOR". Also, post the
> |> .inf that creates the ViewSonic VP930 Series entry...
> |>
> |> (a) "START button, Find, F/F"
> |> (b) Leave "Named" empty.
> |> (c) In "Containing text", enter... "ViewSonic VP930 Series"
> |> with the quotes.
> |> (d) In "Look in", browse to... "C:\WINDOWS\INF".
> |
> | !!!Nothing found searching for text "VSCE41B"
>
> Hmm, it wouldn't work for mine, either-- until I removed the quotes.
> Apparently they shouldn't be used, unless there is a space (& possibly
> other special characters) involved. But no matter!
>
> | !!!VS080114_I19.inf found searching for text "ViewSonic VP930 Series".
>
> Good. My .inf is much, much smaller, & I've deleted what I consider to
> be extraneous lines in yours below. I do not see that your .inf actually
> creates the Registry entries for that Default Monitor-- something else
> is doing it! Your .inf DOES properly create the Registry entries for the
> "ViewSonic VP930 Series". And your MSInfo data looks also quite good to
> me.
>
> Comparing your abridged .inf to mine, I see nothing startlingly bad.
> Although I'm not a perfect expert, my impression seems corroborated in
> that your Registry & MSInfo32 stuff look fine for the VP930.
>
> (a) You do actually have a... VP930_Series.ICM?
> (My own EN5400e.icm is located in...
> C:\WINDOWS\SYSTEM\COLOR.)

>*** YES

> (b) In that Update Driver requestor, when "ViewSonic" is
> selected in the left (Manufacturers) pane, do you
> have a trillion entries in the right (Models) pane?
> (I have just "Envision EN5400e" there.)

> *** Well it depends on whether or not you ask the list to be "all
hardware" or "only compatible hardware"

> (c) In that requestor, what are a few Models immediately
> before & after "%VCDTS21367-1%"?
> (I might be able to spot a syntax error in your .inf, but
> oddly I can't spot "%VCDTS21367-1%" itself in there.)
>
> (d) I'm not sure where the Manufacturers & Models that show
> up in the Update Drivers requestor come from. There does
> not seem to be a list of them in my Registry. I'm thinking
> they may be built on the fly from the .inf's in
> C:\Windows\Inf. Therefore...
>
> Look through that folder & subfolders for something unusal,
> &...
>
> (1) "START button, Find, F/F"
> (2) Leave "Named" empty.
> (3) In "Containing text", enter... %VCDTS21367-1%
> (4) In "Look in", browse to... "C:\WINDOWS\INF".
> (5) If it is found, post the .inf.
>

*** Monitr11.inf, Drvidx.bin

; MONITR11.INF
;
; This is a Setup information file for monitors P-Z

[Version]
LayoutFile= Layout.inf, Layout1.inf, Layout2.inf
signature="$CHICAGO$"
Class=Monitor
ClassGuid={4D36E96E-E325-11CE-BFC1-08002BE10318}
Provider=%MS%
SetupClass=BASE
CatalogFile=monitr11.cat

; Manufacturers
;-------------------------------------------------
[Manufacturer]
%Panasonic%=Panasonic
%Princeton%=Princeton
%Philips%=Philips
%PROVIEW%=PROVIEW
%Relisys%=Relisys
%Samsung%=Samsung
%Samtron%=Samtron
%STC%=STC
%SMILE%=SMILE
%SONY%=Sony
%TAT%=TAT
%Taxan%=Taxan
%TVM%=TVM
%Unisys%=Unisys
%ViewSonic%=ViewSonic

; Manufacturer sections
;-------------------------------------------------

[Panasonic]
%LC50S%=LC50S.Install, Monitor\MEI1E07
%SL90%=SL90.Install, Monitor\MEI120D
%SL70i%=SL70i.Install, Monitor\MEI0C96
%PL70i%=PL70i.Install, Monitor\MEI0C9B

[Princeton]
%EO500%=EO500.Install, Monitor\PGS008E
%EO710%=EO710.Install, Monitor\PGS008F
%EO700%=EO700.Install, Monitor\PGS00B6
%EO720%=EO720.Install, Monitor\PGS00B7
%EO400%=EO400.Install, Monitor\PGS009D

[Philips]
%0107%=0107.Install, Monitor\PHL0107
%201A%=201A.Install, Monitor\PHL201A
%201B%=201B.Install, Monitor\PHL201B
%200D%=200D.Install, Monitor\PHL200D
%104B%=104B.Install, Monitor\PHL104B
%105B%=105B.Install, Monitor\PHLA15B
%105C%=105C.Install, Monitor\PHL105C
%105A%=105A.Install, Monitor\PHL105A
%107B%=107B.Install, Monitor\PHL6800
%107C%=107C.Install, Monitor\PHL107C
%A17B%=A17B.Install, Monitor\PHLA17B
%PH_CM0201%=PH_CM0201.Install, Monitor\PHL0201
%29PX8031%=29PX8031.Install, Monitor\PHL5F1F
%PD5029S%=PD5029S.Install, Monitor\PHLA513
%4500%=4500.Install, Monitor\PHL4500
%1109%=1109.Install, Monitor\PHL1109
%1107%=1107.Install, Monitor\PHL1107
%A17C%=A17C.Install, Monitor\PHLA17C
%B15C%=B15C.Install, Monitor\PHLB15C
%B14B%=B14B.Install, Monitor\PHLB14B
%3109%=3109.Install, Monitor\PHL3109
%4109%=4109.Install, Monitor\PHL4109

[PROVIEW]
%860%=860.Install, Monitor\PTS035C
%570%=570.Install, Monitor\PTS023A
%770%=770.Install, Monitor\PTS0302

[RELISYS]
%REL0451%=RE451, Monitor\REL0451
%REL0551%=RE551, Monitor\REL0551
%REL0518%=RE518, Monitor\REL0518
%REL0767%=RE767, Monitor\REL0767

[Samsung]
%208DXL+%=208DXL+, Monitor\SDI4690
%500bp%=500bp.Install, Monitor\SAM0D66
%500sp%=500sp.Install, Monitor\SAM0D65
%900p%=900p.Install, Monitor\SAM4F26
%700sp%=700sp.Install, Monitor\SAM0D67
%700pp%=700pp.Install, Monitor\SAM4EE6
%st9p%=st9p.Install, Monitor\SAM4F27
%1000b%=1000b.Install, Monitor\SAM1F14
%1000s%=1000s.Install, Monitor\SAM0CF1
%320TFT%=320TFT.Install, Monitor\SAM6053
%520TFT%=520TFT.Install, Monitor\SAM6055
%40b%=40b.Install, Monitor\SAM2034
%50e%=50e.Install, Monitor\SAM2036
%50b%=50b.Install, Monitor\SAM2056
%70e%=70e.Install, Monitor\SAM2058
%510b%=510b.Install, Monitor\SAM2055
%510s%=510s.Install, Monitor\SAM2035
%410b%=410b.Install, Monitor\SAM2033
%710s%=710s.Install, Monitor\SAM2057
%60b%=60b.Install, Monitor\SAM2042
%610b%=610b.Install, Monitor\SAM2041
%700ift%=700ift.Install, Monitor\SAM4EE9
%40bn%=40bn.Install, Monitor\SAM202E
%530TFT%=530TFT.Install, Monitor\SAM6056
%330TFT%=330TFT.Install, Monitor\SAM6054
%700bp%=700bp.Install, Monitor\SAM2CF8
%900ift%=900ift.Install, Monitor\SAM4F29
%900sl%=900sl.Install, Monitor\SAM4DB9
%710b%=710b.Install, Monitor\SAM2059

[STC]
%KM-711%=KM-711.Install, Monitor\STC02C7
%KM-811%=KM-811.Install, Monitor\STC032B
%KM-712%=KM-712.Install, Monitor\STC02C8
%KM-800S%=KM-800S.Install, Monitor\STC0800

[SMILE]
%SMILE_CA6425%=SMILE_CA6425.Install, Monitor\SML6425
%SMILE_CA6525%=SMILE_CA6525.Install, Monitor\SML6525
%SMILE_CA6546%=SMILE_CA6546.Install, Monitor\SML6546
%SMILE_CA6746%=SMILE_CA6746.Install, Monitor\SML6746
%SMILE_CA6738%=SMILE_CA6738.Install, Monitor\SML6738
%SMILE_CA6748%=SMILE_CA6748.Install, Monitor\SML6748
%SMILE_CA6719%=SMILE_CA6719.Install, Monitor\SML6719
%SMILE_CA6919%=SMILE_CA6919.Install, Monitor\SML6919

[SONY]
%CPD-L150%=CPD-L150.Install, Monitor\SNY0950
%CPD-101VS_iGPE%=CPD-101VS_iGPE.Install, Monitor\SNY0A50
%CPD-520GS%=CPD-520GS.Install, Monitor\SNY02B0
%CPD-2003GT%=CPD-2003GT.Install, Monitor\SNY017B
%CPD-220GS%=CPD-220GS.Install, Monitor\SNY0071
%CPD-420GS%=CPD-420GS.Install, Monitor\SNY0091
%KL-W7000%=KL-W7000.Install, Monitor\SNY01F2
%CPD-L133%=CPD-L133.Install, Monitor\SNY0030

[Tatung]
%TATUNG_C9N% =TATUNG_C9N.Install, Monitor\TAT304E

[Taxan]
%EV430%=EV430.Install, Monitor\TAXE430
%EV550%=EV550.Install, Monitor\TAXE550
%EV730%=EV730.Install, Monitor\TAXE730
%EV740%=EV740.Install, Monitor\TAXE740
%EV750%=EV750.Install, Monitor\TAXE750
%EV760%=EV760.Install, Monitor\TAXE760
%EV975%=EV975.Install, Monitor\TAXE975

[TVM]
%AS5S%=AS5S.Install, Monitor\TVM0588
%TCO5S%=TCO5S.Install, Monitor\TVM0589
%AS4Dp%=AS4Dp.Install, Monitor\TVM0487
%TCO6S%=TCO6S.Install, Monitor\TVM0688

[Unisys]
%UNM_5002%=UNM5002.Install, Monitor\UNM5002
%UNM_4002%=UNM4002.Install, Monitor\UNM4002
%UNM_2101%=UNM2101.Install, Monitor\UNM2101
%UNM_2102%=UNM2102.Install, Monitor\UNM2102

[ViewSonic]
%VCDTS21367-1%=VCDTS21367-1.Install,Monitor\OQI4D31
%VPRJ21408-1%=VPRJ21408-1.Install,Monitor\VSC3554
%VCDTS21356-2%=VCDTS21356-2.Install,Monitor\VSC3641
%VCDTS21386-1%=VCDTS21386-1.Install,Monitor\VSC564A
%VCDTS21349-1%=VCDTS21349-1.Install,Monitor\VSC4D4A
%VCDTS21349-2%=VCDTS21349-2.Install,Monitor\VSC4244
%VCDTS21383-1%=VCDTS21383-1.Install,Monitor\OQI4A32
%VCDTS21353-1%=VCDTS21353-1.Install,Monitor\VSC4C4A
%G810-2%=G810-2.Install,Monitor\VSC4951
%VCDTS21375-1%=VCDTS21375-1.Install,Monitor\OQI4435
%P810-3%=P810-3.Install,Monitor\VSC4851
%VCDTS21406-1%=VCDTS21406-1.Install,Monitor\VSC594A
%VCDTS21404-1%=VCDTS21404-1.Install,Monitor\VSC4245
%VCDTS21397-1%=VCDTS21397-1.Install,Monitor\VSC5A4A
%VPRJ21402-1%=VPRJ21402-1.Install,Monitor\VSC3454
%VPRJ21357-2%=VPRJ21357-2.Install,Monitor\VSC3854
%VLCDS21434-1%=VLCDS21434-1.Install,Monitor\VSC3845
%VCDTS21403-1%=VCDTS21403-1.Install,Monitor\VSC4145
%VCDTS21420-1%=VCDTS21420-1.Install,Monitor\VSC434D
%VCDTS21431-1%=VCDTS21431-1.Install,Monitor\OQI4739
%VCDTS21433-1%=VCDTS21433-1.Install,Monitor\OQI5634
%VCDTS21399-1%=VCDTS21399-1.Install,Monitor\OQI4436
%VCDTS21348-2%=VCDTS21348-2.Install,Monitor\OQI4738

; Install sections
;-------------------------------------------------

; ---------- [Panasonic]

[LC50S.Install]
DelReg=DEL_CURRENT_REG
AddReg=LC50S.AddReg,1024,DPMS

[SL90.Install]
DelReg=DEL_CURRENT_REG
AddReg=SL90.AddReg,1600,DPMS

[SL70i.Install]
DelReg=DEL_CURRENT_REG
AddReg=SL70i.AddReg,1280,DPMS

[PL70i.Install]
DelReg=DEL_CURRENT_REG
AddReg=PL70i.AddReg,1600,DPMS

; ---------- [Princeton Graphics]

[EO500.Install]
DelReg=DEL_CURRENT_REG
AddReg=EO500.AddReg, 1280, DPMS

[EO710.Install]
DelReg=DEL_CURRENT_REG
AddReg=EO710.AddReg, 1280, DPMS

[EO700.Install]
DelReg=DEL_CURRENT_REG
AddReg=EO700.AddReg, 1280, DPMS

[EO720.Install]
DelReg=DEL_CURRENT_REG
AddReg=EO720.AddReg, 1280, DPMS

[EO400.Install]
DelReg=DEL_CURRENT_REG
AddReg=EO400.AddReg, 1024, DPMS

; ---------- [Philips]

[0107.Install]
DelReg=DEL_CURRENT_REG
AddReg=0107.AddReg, 1600, DPMS

[201A.Install]
DelReg=DEL_CURRENT_REG
AddReg=201A.AddReg, 1600, DPMS

[201B.Install]
DelReg=DEL_CURRENT_REG
AddReg=201B.AddReg, 1600, DPMS

[200D.Install]
DelReg=DEL_CURRENT_REG
AddReg=200D.AddReg, 1600, DPMS

[104B.Install]
DelReg=DEL_CURRENT_REG
AddReg=104B.AddReg, 1024, DPMS

[105B.Install]
DelReg=DEL_CURRENT_REG
AddReg=105B.AddReg, 1280, DPMS

[105C.Install]
DelReg=DEL_CURRENT_REG
AddReg=105C.AddReg, 1024, DPMS

[105A.Install]
DelReg=DEL_CURRENT_REG
AddReg=105A.AddReg, 1280, DPMS

[107B.Install]
DelReg=DEL_CURRENT_REG
AddReg=107B.AddReg, 1280, DPMS

[107C.Install]
DelReg=DEL_CURRENT_REG
AddReg=107C.AddReg, 1280, DPMS

[A17B.Install]
DelReg=DEL_CURRENT_REG
AddReg=A17B.AddReg, 1280, DPMS

[PH_CM0201.Install]
DelReg=DEL_CURRENT_REG
AddReg=PH_CM0201.Addreg, 1600, DPMS

[29PX8031.Install]
DelReg=DEL_CURRENT_REG
AddReg=29PX8031.AddReg, 800, DPMS

[PD5029S.Install]
DelReg=DEL_CURRENT_REG
AddReg=PD5029S.AddReg, 800, DPMS

[4500.Install]
DelReg=DEL_CURRENT_REG
AddReg=4500.AddReg, 1024, DPMS

[1109.Install]
DelReg=DEL_CURRENT_REG
AddReg=1109.AddReg, 1600, DPMS

[1107.Install]
DelReg=DEL_CURRENT_REG
AddReg=1107.AddReg, 1600, DPMS

[A17C.Install]
DelReg=DEL_CURRENT_REG
AddReg=A17C.AddReg, 1280, DPMS

[B15C.Install]
DelReg=DEL_CURRENT_REG
AddReg=B15C.AddReg,1024,DPMS

[B14B.Install]
DelReg=DEL_CURRENT_REG
AddReg=B14B.AddReg,1024,DPMS

[3109.Install]
DelReg=DEL_CURRENT_REG
AddReg=3109.AddReg,1600,DPMS

[4109.Install]
DelReg=DEL_CURRENT_REG
AddReg=4109.AddReg,1600,DPMS

; ---------- [Proview]

[860.Install]
DelReg=DEL_CURRENT_REG
AddReg=860.AddReg, 1024, DPMS

[570.Install]
DelReg=DEL_CURRENT_REG
AddReg=570.AddReg, 1280, DPMS

[770.Install]
DelReg=DEL_CURRENT_REG
AddReg=770.AddReg, 1600, DPMS

; ---------- [Relisys]

[RE451]
DelReg=DEL_CURRENT_REG
AddReg=RE451.AddReg, 1024, DPMS

[RE551]
DelReg=DEL_CURRENT_REG
AddReg=RE551.AddReg, 1024, DPMS

[RE518]
DelReg=DEL_CURRENT_REG
AddReg=RE518.AddReg, 1280, DPMS

[RE767]
DelReg=DEL_CURRENT_REG
AddReg=RE767.AddReg, 1280, DPMS

[RE550]
DelReg=DEL_CURRENT_REG
AddReg=RE550.AddReg, 1024, DPMS

; ---------- [Sammon]

[208DXL+]
DelReg=DEL_CURRENT_REG
AddReg=208DXL+.AddReg, 1280, DPMS

[500bp.Install]
DelReg=DEL_CURRENT_REG
AddReg=500bp.AddReg, 1280, DPMS

[500sp.Install]
DelReg=DEL_CURRENT_REG
AddReg=500sp.AddReg, 1024, DPMS

[900p.Install]
DelReg=DEL_CURRENT_REG
AddReg=900p.AddReg, 1600, DPMS

[700sp.Install]
DelReg=DEL_CURRENT_REG
AddReg=700sp.AddReg, 1280, DPMS

[700pp.Install]
DelReg=DEL_CURRENT_REG
AddReg=700pp.AddReg, 1600, DPMS

[st9p.Install]
DelReg=DEL_CURRENT_REG
AddReg=st9p.AddReg, 1600, DPMS

[1000b.Install]
DelReg=DEL_CURRENT_REG
AddReg=1000b.AddReg, 1600, DPMS

[1000s.Install]
DelReg=DEL_CURRENT_REG
AddReg=1000s.AddReg, 1600, DPMS

[320TFT.Install]
DelReg=DEL_CURRENT_REG
AddReg=320TFT.AddReg, 1024, DPMS

[520TFT.Install]
DelReg=DEL_CURRENT_REG
AddReg=520TFT.AddReg, 1024, DPMS

[40b.Install]
DelReg=DEL_CURRENT_REG
AddReg=40b.AddReg, 1024, DPMS

[50e.Install]
DelReg=DEL_CURRENT_REG
AddReg=50e.AddReg, 1024, DPMS

[50b.Install]
DelReg=DEL_CURRENT_REG
AddReg=50b.AddReg, 1280, DPMS

[70e.Install]
DelReg=DEL_CURRENT_REG
AddReg=70e.AddReg, 1280, DPMS

[510b.Install]
DelReg=DEL_CURRENT_REG
AddReg=510b.AddReg, 1280, DPMS

[510s.Install]
DelReg=DEL_CURRENT_REG
AddReg=510s.AddReg, 1024, DPMS

[410b.Install]
DelReg=DEL_CURRENT_REG
AddReg=410b.AddReg, 1024, DPMS

[710s.Install]
DelReg=DEL_CURRENT_REG
AddReg=710s.AddReg, 1280, DPMS

[60b.Install]
DelReg=DEL_CURRENT_REG
AddReg=60b.AddReg, 1280, DPMS

[610b.Install]
DelReg=DEL_CURRENT_REG
AddReg=610b.AddReg, 1280, DPMS

[700ift.Install]
DelReg=DEL_CURRENT_REG
AddReg=700ift.AddReg, 1600, DPMS

[40bn.Install]
DelReg=DEL_CURRENT_REG
AddReg=40bn.AddReg, 1024, DPMS

[530TFT.Install]
DelReg=DEL_CURRENT_REG
AddReg=530TFT.AddReg, 1024, DPMS

[330TFT.Install]
DelReg=DEL_CURRENT_REG
AddReg=330TFT.AddReg, 1024, DPMS

[700bp.Install]
DelReg=DEL_CURRENT_REG
AddReg=700bp.AddReg, 1280, DPMS

[900ift.Install]
DelReg=DEL_CURRENT_REG
AddReg=900ift.AddReg, 1600, DPMS

[900sl.Install]
DelReg=DEL_CURRENT_REG
AddReg=900sl.AddReg, 1600, DPMS

[710b.Install]
DelReg=DEL_CURRENT_REG
AddReg=710b.AddReg, 1280, DPMS

; ---------- [STC]

[KM-711.Install]
DelReg=DEL_CURRENT_REG
AddReg=KM-711.AddReg, 1280, DPMS

[KM-811.Install]
DelReg=DEL_CURRENT_REG
AddReg=KM-811.AddReg, 1600, DPMS

[KM-712.Install]
DelReg=DEL_CURRENT_REG
AddReg=KM-712.AddReg, 1280, DPMS

[KM-800S.Install]
DelReg=DEL_CURRENT_REG
AddReg=KM-800S.AddReg, 1600, DPMS

; ---------- [Smile]

[SMILE_CA6425.Install]
DelReg=DEL_CURRENT_REG
AddReg=SMILE_CA6425.AddReg, 1024, DPMS

[SMILE_CA6525.Install]
DelReg=DEL_CURRENT_REG
AddReg=SMILE_CA6525.AddReg, 1024, DPMS

[SMILE_CA6546.Install]
DelReg=DEL_CURRENT_REG
AddReg=SMILE_CA6546.AddReg, 1280, DPMS

[SMILE_CA6746.Install]
DelReg=DEL_CURRENT_REG
AddReg=SMILE_CA6746.AddReg, 1280, DPMS

[SMILE_CA6738.Install]
DelReg=DEL_CURRENT_REG
AddReg=SMILE_CA6738.AddReg, 1600, DPMS

[SMILE_CA6748.Install]
DelReg=DEL_CURRENT_REG
AddReg=SMILE_CA6748.AddReg, 1600, DPMS

[SMILE_CA6719.Install]
DelReg=DEL_CURRENT_REG
AddReg=SMILE_CA6719.AddReg, 1600, DPMS

[SMILE_CA6919.Install]
DelReg=DEL_CURRENT_REG
AddReg=SMILE_CA6919.AddReg, 1600, DPMS

[VX700.Install]
DelReg=DEL_CURRENT_REG
AddReg=VX700.AddReg, 1600, DPMS, ICM

; ---------- [Sony]

[CPD-L150.Install]
DelReg=DEL_CURRENT_REG
AddReg=CPD-L150.AddReg, 1024, DPMS

[CPD-101VS_iGPE.Install]
DelReg=DEL_CURRENT_REG
AddReg=CPD-101VS_iGPE.AddReg, 1280, DPMS

[CPD-520GS.Install]
DelReg=DEL_CURRENT_REG
AddReg=CPD-520GS.AddReg, 1800, DPMS

[CPD-2003GT.Install]
DelReg=DEL_CURRENT_REG
AddReg=CPD-2003GT.AddReg, 1280, DPMS

[CPD-220GS.Install]
DelReg=DEL_CURRENT_REG
AddReg=CPD-220GS.AddReg, 1280, DPMS

[CPD-420GS.Install]
DelReg=DEL_CURRENT_REG
AddReg=CPD-420GS.AddReg, 1600, DPMS

[KL-W7000.Install]
DelReg=DEL_CURRENT_REG
AddReg=KL-W7000.AddReg, 1376, DPMS

[CPD-L133.Install]
DelReg=DEL_CURRENT_REG
AddReg=CPD-L133.AddReg, 1024, DPMS

; ---------- [Tatung]

[TATUNG_C9N.Install]
DelReg=DEL_CURRENT_REG
AddReg=TATUNG_C9N.AddReg, 1600, DPMS

; ----------- [Taxan]

[EV430.Install]
DelReg=DEL_CURRENT_REG
AddReg=EV430.AddReg, 1024, DPMS

[EV550.Install]
DelReg=DEL_CURRENT_REG
AddReg=EV550.AddReg, 1024, DPMS

[EV730.Install]
DelReg=DEL_CURRENT_REG
AddReg=EV730.AddReg, 1024, DPMS

[EV740.Install]
DelReg=DEL_CURRENT_REG
AddReg=EV740.AddReg, 1600, DPMS

[EV750.Install]
DelReg=DEL_CURRENT_REG
AddReg=EV750.AddReg, 1280, DPMS

[EV760.Install]
DelReg=DEL_CURRENT_REG
AddReg=EV760.AddReg, 1280, DPMS

[EV975.Install]
DelReg=DEL_CURRENT_REG
AddReg=EV975.AddReg, 1600, DPMS

; ---------- [TVM]

[AS5S.Install]
DelReg=DEL_CURRENT_REG
AddReg=AS5S.AddReg, 1280, DPMS

[TCO5S.Install]
DelReg=DEL_CURRENT_REG
AddReg=TCO5S.AddReg, 1280, DPMS

[AS4Dp.Install]
DelReg=DEL_CURRENT_REG
AddReg=AS4Dp.AddReg, 1024, DPMS

[TCO6S.Install]
DelReg=DEL_CURRENT_REG
AddReg=TCO6S.AddReg, 1280, DPMS

; ---------- [Unisys]

[UNM5002.Install]
DelReg=DEL_CURRENT_REG
AddReg=UNM_5002.AddReg, 1600, DPMS

[UNM4002.Install]
DelReg=DEL_CURRENT_REG
AddReg=UNM_4002.AddReg, 1600, DPMS

[UNM2101.Install]
DelReg=DEL_CURRENT_REG
AddReg=UNM_2101.AddReg, 1024, DPMS

[UNM2102.Install]
DelReg=DEL_CURRENT_REG
AddReg=UNM_2102.AddReg, 1280, DPMS

; ---------- [Viewsonic]

[VCDTS21368-1.Install]
DelReg=DEL_CURRENT_REG
AddReg=VCDTS21368-1.AddReg,1280,DPMS

[VCDTS21367-1.Install]
DelReg=DEL_CURRENT_REG
AddReg=VCDTS21367-1.AddReg,DPMS

[VPRJ21408-1.Install]
DelReg=DEL_CURRENT_REG
AddReg=VPRJ21408-1.AddReg,1024,DPMS

[VCDTS21356-2.Install]
DelReg=DEL_CURRENT_REG
AddReg=VCDTS21356-2.AddReg,1024,DPMS

[VCDTS21386-1.Install]
DelReg=DEL_CURRENT_REG
AddReg=VCDTS21386-1.AddReg,1280,DPMS

[VCDTS21349-1.Install]
DelReg=DEL_CURRENT_REG
AddReg=VCDTS21349-1.AddReg,1280,DPMS

[VCDTS21349-2.Install]
DelReg=DEL_CURRENT_REG
AddReg=VCDTS21349-2.AddReg,1280,DPMS

[VCDTS21383-1.Install]
DelReg=DEL_CURRENT_REG
AddReg=VCDTS21383-1.AddReg,1600,DPMS

[VCDTS21353-1.Install]
DelReg=DEL_CURRENT_REG
AddReg=VCDTS21353-1.AddReg,1280,DPMS

[G810-2.Install]
DelReg=DEL_CURRENT_REG
AddReg=G810-2.AddReg,1600,DPMS

[VCDTS21375-1.Install]
DelReg=DEL_CURRENT_REG
AddReg=VCDTS21375-1.AddReg,1024,DPMS

[P810-3.Install]
DelReg=DEL_CURRENT_REG
AddReg=P810-3.AddReg,1600,DPMS

[VCDTS21406-1.Install]
DelReg=DEL_CURRENT_REG
AddReg=VCDTS21406-1.AddReg,1280,DPMS

[VCDTS21404-1.Install]
DelReg=DEL_CURRENT_REG
AddReg=VCDTS21404-1.AddReg,1280,DPMS

[VCDTS21397-1.Install]
DelReg=DEL_CURRENT_REG
AddReg=VCDTS21397-1.AddReg,1600,DPMS

[VPRJ21402-1.Install]
DelReg=DEL_CURRENT_REG

ddReg=VPRJ21402-1.AddReg,1280

[VPRJ21357-2.Install]
DelReg=DEL_CURRENT_REG
AddReg=VPRJ21357-2.AddReg,1024

[VLCDS21434-1.Install]
DelReg=DEL_CURRENT_REG
AddReg=VLCDS21434-1.AddReg,1024,DPMS

[VCDTS21403-1.Install]
DelReg=DEL_CURRENT_REG
AddReg=VCDTS21403-1.AddReg,1280,DPMS

[VCDTS21420-1.Install]
DelReg=DEL_CURRENT_REG
AddReg=VCDTS21420-1.AddReg,1600,DPMS

[VCDTS21431-1.Install]
DelReg=DEL_CURRENT_REG
AddReg=VCDTS21431-1.AddReg,1600,DPMS

[VCDTS21433-1.Install]
DelReg=DEL_CURRENT_REG
AddReg=VCDTS21433-1.AddReg,1280,DPMS

[VCDTS21399-1.Install]
DelReg=DEL_CURRENT_REG
AddReg=VCDTS21399-1.AddReg,1280,DPMS

[VCDTS21348-2.Install]
DelReg=DEL_CURRENT_REG
AddReg=VCDTS21348-2.AddReg,1280,DPMS

; AddReg sections
;-------------------------------------------------

; ---------- [Panasonic]

[LC50S.AddReg]
HKR,"MODES\1024,768",Mode1,,"30.0-61.0,50.0-77.0,+,+"

[SL90.AddReg]
HKR,"MODES\1600,1200",Mode1,,"30.0-95.0,50.0-180.0,+,+"

[SL70i.AddReg]
HKR,"MODES\1280,1024",Mode1,,"30.0-70.0,50.0-180.0,+,+"

[PL70i.AddReg]
HKR,"MODES\1600,1200",Mode1,,"30.0-97.0,50.0-180.0,+,+"

; ---------- [Princeton Graphics]

[EO500.AddReg]
HKR,"MODES\1280,1024",Mode1,,"30.0-70.0,50.0-120.0,+,+"

[EO710.AddReg]
HKR,"MODES\1280,1024",Mode1,,"30.0-70.0,50.0-120.0,+,+"

[EO700.AddReg]
HKR,"MODES\1280,1024",Mode1,,"30.0-70.0,50.0-120.0,+,+"

[EO720.AddReg]
HKR,"MODES\1280,1024",Mode1,,"30.0-70.0,50.0-120.0,+,+"

[Eo400.AddReg]
HKR,"MODES\1024,768",Mode1,,"30.0-54.0,50.0-90.0,+,+"

; ---------- [Philips]

[0107.AddReg]
HKR,"MODES\1600,1200",Mode1,,"30.0-86.0,50.0-160.0,+,-"

[201A.AddReg]
HKR,"MODES\1600,1200",Mode1,,"31.5-107.0,50.0-170.0,+,-"

[201B.AddReg]
HKR,"MODES\1600,1200",Mode1,,"30.0-94.0,48.0-160.0,+,-"

[200D.AddReg]
HKR,"MODES\1600,1200",Mode1,,"30.0-90.0,50.0-160.0,+,-"

[104B.AddReg]
HKR,"MODES\1024,768",Mode1,,"30.0-54.0,50.0-110.0,+,-"

[105B.AddReg]
HKR,"MODES\1280,1024",Mode1,,"30.0-66.0,50.0-110.0,+,-"

[105C.AddReg]
HKR,"MODES\1024,768",Mode1,,"30.0-54.0,50.0-110.0,+,-"

[105A.AddReg]
HKR,"MODES\1280,1024",Mode1,,"30.0-69.0,50.0-120.0,+,-"

[107B.AddReg]
HKR,"MODES\1280,1024",Mode1,,"30.0-69.0,50.0-130.0,+,-"

[107C.AddReg]
HKR,"MODES\1280,1024",Mode1,,"30.0-66.0,50.0-130.0,+,-"

[A17B.AddReg]
HKR,"MODES\1280,1024",Mode1,,"30.0-66.0,50.0-130.0,+,-"

[PH_CM0201.Addreg]
HKR,"MODES\1600,1200",Mode1,,"30.0-107.0,50-170,+,+"
HKR,,ICMProfile,1,9

[29PX8031.AddReg]
HKR,"MODES\640,480",Mode1,,"31.5-35.2,50.0-70.0,+,+"
HKR,"MODES\800,600",Mode1,,"31.5-35.2,50.0-56.0,+,+"
HKR,,ICMProfile,1,5

[PD5029S.AddReg]
HKR,"MODES\640,480",Mode1,,"31.5-35.2,50.0-70.0,+,+"
HKR,"MODES\800,600",Mode1,,"31.5-35.2,50.0-56.0,+,+"
HKR,,ICMProfile,1,5

[105S.AddReg]
HKR,"MODES\1024,768",Mode1,,"30.0-54.0,50.0-110.0,+,-"
HKR,,ICMProfile,1,9

[4500.AddReg]
HKR,"MODES\1024,768",Mode1,,"30.0-60.0,56.0-75.0,+,-"
HKR,,ICMProfile,1,9

[1109.AddReg]
HKR,"MODES\1600,1200",Mode1,,"30.0-95.0,50.0-160.0,+,-"

[1107.AddReg]
HKR,"MODES\1600,1200",Mode1,,"30.0-95.0,50.0-160.0,+,-"

[A17C.AddReg]
HKR,"MODES\1280,1024",Mode1,,"30.0-69.0,50.0-120.0,+,-"

[B15C.AddReg]
HKR,"MODES\1024,768",Mode1,,"30.0-60.0,50.0-120.0,+,-"

[B14B.AddReg]
HKR,"MODES\1024,768",Mode1,,"30.0-54.0,50.0-120.0,+,-"

[3109.AddReg]
HKR,"MODES\1600,1200",Mode1,,"30.0-95.0,50.0-160.0,+,-"

[4109.AddReg]
HKR,"MODES\1600,1200",Mode1,,"30.0-95.0,50.0-160.0,+,-"

; ---------- [ProView]

[860.AddReg]
HKR,"MODES\1024,768",Mode1,,"30.0-54.0,50.0-150.0,+,+"

[570.AddReg]
HKR,"MODES\1280,1024",Mode1,,"30.0-70.0,50.0-150.0,+,+"

[770.AddReg]
HKR,"MODES\1600,1200",Mode1,,"30.0-76.0,50.0-150.0,+,+"

; ---------- [Relisys]

[RE451.AddReg]
HKR,"MODES\1024,768",Mode1,,"30-54,50-100,+,+"
HKR,,ICMProfile,1,9

[RE551.AddReg]
HKR,"MODES\1024,768",Mode1,,"30-54,50-100,+,+"
HKR,,ICMProfile,1,9

[RE518.AddReg]
HKR,"MODES\1280,1024",Mode1,,"30-69,50-100,+,+"
HKR,,ICMProfile,1,9

[RE767.AddReg]
HKR,"MODES\1280,1024",Mode1,,"30-69,50-100,+,+"
HKR,,ICMProfile,1,9

; ---------- [Sansung/Samtron]

[208DXL+.AddReg]
HKR,"MODES\1280,1024",Mode1,,"30.0-82.0,50.0-120.0,-,-"
HKR,,ICMProfile,1,8

[5Ei.AddReg]
HKR,"MODES\1024,768",Mode1,,"30-55,50-120,-,-"

[500bp.AddReg]
HKR,"MODES\1280,1024",Mode1,,"30-69,50-160,+,+"

[500sp.AddReg]
HKR,"MODES\1024,768",Mode1,,"30-60,50-120,+,+"

[900p.AddReg]
HKR,"MODES\1600,1200",Mode1,,"30-96,50-160,+,+"

[700sp.AddReg]
HKR,"MODES\1280,1024",Mode1,,"30-69,50-160,+,+"

[700pp.AddReg]
HKR,"MODES\1600,1200",Mode1,,"30-96,50-160,+,+"

[st9p.AddReg]
HKR,"MODES\1600,1200",Mode1,,"30-96,50-160,+,+"

[1000b.AddReg]
HKR,"MODES\1600,1200",Mode1,,"30-107,50-160,+,+"

[1000s.AddReg]
HKR,"MODES\1600,1200",Mode1,,"30-96,50-160,+,+"

[320TFT.AddReg]
HKR,"MODES\1024,768",Mode1,,"30-61,50-75,+,+"

[520TFT.AddReg]
HKR,"MODES\1024,768",Mode1,,"30-61,50-75,+,+"

[40b.AddReg]
HKR,"MODES\1024,768",Mode1,,"30-55,50-120,-,-"

[50e.AddReg]
HKR,"MODES\1024,768",Mode1,,"30-61,50-120,-,-"

[50b.AddReg]
HKR,"MODES\1280,1024",Mode1,,"30-70,50-160,+,+"

[70e.AddReg]
HKR,"MODES\1280,1024",Mode1,,"30-70,50-160,+,+"

[510b.AddReg]
HKR,"MODES\1280,1024",Mode1,,"30-70,50-160,+,+"

[510s.AddReg]
HKR,"MODES\1024,768",Mode1,,"30-61,50-120,-,-"

[410b.AddReg]
HKR,"MODES\1024,768",Mode1,,"30-55,50-120,-,-"

[710s.AddReg]
HKR,"MODES\1280,1024",Mode1,,"30-70,50-160,+,+"

[60b.AddReg]
HKR,"MODES\1280,1024",Mode1,,"30-70,50-160,+,+"

[610b.AddReg]
HKR,"MODES\1280,1024",Mode1,,"30-70,50-160,+,+"

[700ift.AddReg]
HKR,"MODES\1600,1200",Mode1,,"30-96,50-160,+,+"

[40bn.AddReg]
HKR,"MODES\1024,768",Mode1,,"30-55,50-120,-,-"

[530TFT.AddReg]
HKR,"MODES\1024,768",Mode1,,"30-61,50-75,+,+"

[330TFT.AddReg]
HKR,"MODES\1024,768",Mode1,,"30-61,50-75,+,+"

[700bp.AddReg]
HKR,"MODES\1280,1024",Mode1,,"30-70,50-160,+,+"

[900ift.AddReg]
HKR,"MODES\1600,1200",Mode1,,"30-96,50-160,+,+"

[900sl.AddReg]
HKR,"MODES\1600,1200",Mode1,,"30-96,50-160,+,+"

[710b.AddReg]
HKR,"MODES\1280,1024",Mode1,,"30-70,50-160,+,+"

; ---------- [STC]

[KM-711.AddReg]
HKR,"MODES\1280,1024",Model,,"30.0-70.0,50.0-120.0,+,+"

[KM-811.AddReg]
HKR,"MODES\1600,1200",Mode1,,"30.0-95.0,50.0-150.0,+,+"

[KM-712.AddReg]
HKR,"MODES\1280,1024",Mode1,,"30.0-70.0,50.0-120.0,+,+"

[KM-800S.AddReg]
HKR,"MODES\1600,1200",Mode1,,"30.0-95.0,50.0-150.0,+,+"

; ---------- [Smile]

[SMILE_CA6425.AddReg]
HKR,"MODES\1024,768",Mode1,,"30.0-54.0,50.0-100.0,+,+"

[SMILE_CA6525.AddReg]
HKR,"MODES\1024,768",Mode1,,"30.0-54.0,50.0-100.0,+,+"

[SMILE_CA6546.AddReg]
HKR,"MODES\1280,1024",Mode1,,"30.0-69.0,50.0-120.0,+,+"

[SMILE_CA6746.AddReg]
HKR,"MODES\1280,1024",Mode1,,"30.0-69.0,50.0-120.0,+,+"

[SMILE_CA6738.AddReg]
HKR,"MODES\1600,1200",Mode1,,"30.0-86.0,50.0-150.0,+,+"

[SMILE_CA6748.AddReg]
HKR,"MODES\1600,1200",Mode1,,"30.0-86.0,50.0-150.0,+,+"

[SMILE_CA6719.AddReg]
HKR,"MODES\1600,1200",Mode1,,"30.0-95.0,50.0-150.0,+,+"

[SMILE_CA6919.AddReg]
HKR,"MODES\1600,1200",Mode1,,"30.0-95.0,50.0-150.0,+,+"

; ---------- [Sony]

[CPD-L150.AddReg]
HKR,"MODES\1024,768",Mode1,,"30.0-70.0,50.0-65.0,+,+"

[CPD-101VS_iGPE.AddReg]
HKR,"MODES\1280,1024",Mode1,,"30.0-70.0,50.0-120.0,+,+"

[CPD-520GS.AddReg]
HKR,"MODES\1800,1440",Mode1,,"30.0-96.0,48.0-160.0,+,+"

[CPD-2003GT.AddReg]
HKR,"MODES\1280,1024",Mode1,,"30.0-85.0,50.0-120.0,+,+"

[CPD-220GS.AddReg]
HKR,"MODES\1280,1024",Mode1,,"30.0-85.0,48.0-120.0,+,+"

[CPD-420GS.AddReg]
HKR,"MODES\1600,1200",Mode1,,"30.0-96.0,48.0-120.0,+,+"

[KL-W7000.AddReg]
HKR,"MODES\1376,768",Mode1,,"30.0-50.0,50.0-85.0,+,+"

[CPD-L133.AddReg]
HKR,"MODES\1024,768",Mode1,,"30.0-70.0,50.0-65.0,+,+"

; ---------- [Tatung]
[TATUNG_C9N.AddReg]
HKR,"MODES\1600,1200",Mode1,,"30-95,50-160,+,+"

; ---------- [Taxan]

[EV430.AddReg]
HKR,"MODES\1024,768",Mode1,,"30.0-54.0,50.0-110.0,+,+"

[EV550.AddReg]
HKR,"MODES\1024,768",Mode1,,"30.0-69.0,55.0-110.0,+,+"

[EV730.AddReg]
HKR,"MODES\1024,768",Mode1,,"30.0-69.0,50.0-120.0,+,+"

[EV740.AddReg]
HKR,"MODES\1600,1200",Mode1,,"30.0-85.0,55.0-120.0,+,+"

[EV750.AddReg]
HKR,"MODES\1280,1024",Mode1,,"30.0-86.0,50.0-130.0,+,+"

[EV760.AddReg]
HKR,"MODES\1280,1024",Mode1,,"30.0-70.0,50.0-120.0,+,+"

[EV975.AddReg]
HKR,"MODES\1600,1200",Mode1,,"30.0-95.0,50.0-150.0,+,+"

; ---------- [TVM]

[AS5S.AddReg]
HKR,"MODES\1280,1024",Mode1,,"30.0-69.0,50.0-120.0,+,+"

[TCO5S.AddReg]
HKR,"MODES\1280,1024",Mode1,,"30.0-69.0,50.0-120.0,+,+"

[AS4Dp.AddReg]
HKR,"MODES\1024,768",Mode1,,"30.0-55.0,50.0-120.0,-,-"

[TCO6S.AddReg]
HKR,"MODES\1280,1024",Mode1,,"30.0-69.0,50.0-120.0,+,+"

; ---------- [Unisys]

[UNM_5002.AddReg]
HKR,"MODES\1600,1200",Mode1,,"30.0-95.0,50.0-160.0,+,+"

[UNM_4002.AddReg]
HKR,"MODES\1600,1200",Mode1,,"30.0-95.0,50.0-160.0,+,+"

[UNM_2101.AddReg]
HKR,"MODES\1024,768",Mode1,,"30.0-54.0,50.0-130.0,+,+"

[UNM_2102.AddReg]
HKR,"MODES\1024,768",Mode1,,"30.0-70.0,50.0-150.0,+,+"
HKR,"MODES\1280,1024",Mode1,,"30.0-65.0,50.0-75.0,-,-"

; ---------- [Viewsonic]

[VCDTS21368-1.AddReg]
HKR,"MODES\1280,1024",Mode1,,"30-70,50-180,+,+"

[VCDTS21367-1.AddReg]
HKR,"MODES\1600,1280",Mode1,,"30-95,50-160,+,+"

[VPRJ21408-1.AddReg]
HKR,"MODES\1024,768",Mode1,,"31-61,50-85,+,+"

[VCDTS21356-2.AddReg]
HKR,"MODES\1024,768",Mode1,,"30-54,50-100,+,+"

[VCDTS21386-1.AddReg]
HKR,"MODES\1280,1024",Mode1,,"30-70,50-120,+,+"

[VCDTS21349-1.AddReg]
HKR,"MODES\1280,1024",Mode1,,"30-70,50-120,+,+"

[VCDTS21349-2.AddReg]
HKR,"MODES\1280,1024",Mode1,,"30-70,50-120,+,+"

[VCDTS21383-1.AddReg]
HKR,"MODES\1600,1200",Mode1,,"30-95,50-150,+,+"

[VCDTS21353-1.AddReg]
HKR,"MODES\1280,1024",Mode1,,"30-70,50-180,+,+"

[G810-2.AddReg]
HKR,"MODES\1600,1200",Mode1,,"30-92,50-180,+,+"

[VCDTS21375-1.AddReg]
HKR,"MODES\1024,768",Mode1,,"30-54,50-100,+,+"

[P810-3.AddReg]
HKR,"MODES\1600,1200",Mode1,,"30-95,50-180,+,+"

[VCDTS21406-1.AddReg]
HKR,"MODES\1280,1024",Mode1,,"30-70,50-180,+,+"

[VCDTS21404-1.AddReg]
HKR,"MODES\1280,1024",Mode1,,"30-70,50-180,+,+"

[VCDTS21397-1.AddReg]
HKR,"MODES\1600,1200",Mode1,,"30-92,50-160,+,+"

[VPRJ21402-1.AddReg]
HKR,"MODES\1280,1024",Mode1,,"31-64,50-85,+,+"

[VPRJ21357-2.AddReg]
HKR,"MODES\1024,768",Mode1,,"30-69,50-85,+,+"

[VLCDS21434-1.AddReg]
HKR,"MODES\1024,768",Mode1,,"30-61,50-77,+,+"

[VCDTS21403-1.AddReg]
HKR,"MODES\1280,1024",Mode1,,"30-70,50-180,+,+"

[VCDTS21420-1.AddReg]
HKR,"MODES\1600,1280",Mode1,,"30-95,50-180,+,+"

[VCDTS21431-1.AddReg]
HKR,"MODES\1600,1280",Mode1,,"30-96,50-160,+,+"

[VCDTS21433-1.AddReg]
HKR,"MODES\1280,1024",Mode1,,"30-70,50-160,+,+"

[VCDTS21399-1.AddReg]
HKR,"MODES\1280,1024",Mode1,,"30-70,50-160,+,+"

[VCDTS21348-2.AddReg]
HKR,"MODES\1280,1024",Mode1,,"30-70,50-120,+,+"

[DEL_CURRENT_REG]

HKR,MODES
HKR,,MaxResolution
HKR,,DPMS

[640]
HKR,,MaxResolution,,"640,480"
[800]
HKR,,MaxResolution,,"800,600"
[1024]
HKR,,MaxResolution,,"1024,768"
[1280]
HKR,,MaxResolution,,"1280,1024"
[1376]
HKR,,MaxResolution,,"1376,768"
[1600]
HKR,,MaxResolution,,"1600,1200"
[1800]
HKR,,MaxResolution,,"1800,1440"
[1856]
HKR,,MaxResolution,,"1856,1392"
[1920]
HKR,,MaxResolution,,"1920,1200"
[2048]
HKR,,MaxResolution,,"2048,1536"

[DPMS]
HKR,,DPMS,,1

; User visible strings
;-------------------------------------------------
[Strings]
MS="Microsoft"

Panasonic="Panasonic"
LC50S="Panasonic LC50S (TX-D5L31F)"
SL90="Panasonic SL90 (TX-D9S54)"
SL70i="Panasonic SL70i(TX-D7S36)"
PL70i="Panasonic PL70i(TX-D7S55)"

Princeton="Princeton Graphic Systems"
EO500="Princeton Graphic Systems EO500"
EO710="Princeton Graphic Systems EO710"
EO700="Princeton Graphic Systems EO700"
EO720="Princeton Graphic Systems EO720"
EO400="Princeton Graphic Systems EO400"

Philips="Philips Consumer Electronics Co."
PH_CM0201="Philips Brilliance 201CS"
0107="Philips Brilliance 107(17inch/CM8800)"
201A="Philips Brilliance 201(21inch/CM1700)"
201B="Philips 201B(21inch/CM0770)"
200D="Philips 200T(20inch/CM0700)"
104B="Philips 104B(14inch/CM1300)"
105B="Philips 105B(15inch/CM1200)"
105C="Philips 105S(15inch/CM1300)"
105A="Philips Brilliance 105(15inch/CM2200)"
107B="Philips 107B(17inch/CM6800)"
107C="Philips 107S(17inch/CM6800)"
A17B="Magnavox MB7000(17inch/CM6800)"
1109="Philips Brilliance 109(PRODUCT ID 19A58...)"
29PX8031="Philips 29PX8031 Monitor/TV"
PD5029S="Philips PD5029S Monitor/TV"
4500="Philips Brilliance AX4500(14.5 LCD MONITOR)"
1107="Philips Brilliance 107(PRODUCT ID 17A58...)"
A17C="Philips 107S(17inch/CM1300)"
B15C="Philips 105S(15inch/CM2300)"
B14B="Philips 104B(14inch/CM2300)"
3109="Philips Magnavox 109S"
4109="Philips 109S"

PROVIEW="Proview Technology Corp."
860="Proview 860"
570="Proview 570"
770="Proview 770"

Relisys="Relisys"
REL0451="Relisys RE451"
REL0551="Relisys RE551"
REL0518="Relisys RE518"
REL0767="Relisys RE767"

Samsung="Samsung"
Samtron="Samtron"
208DXL+="Samtron SC-208DXL+"
500bp="Samsung SyncMaster 500b Plus (CKF5607*)"
500sp="Samsung SyncMaster 500(M)s Plus (CKE5507*)"
900p="Samsung SyncMaster 900p (CSH9839*)"
700sp="Samsung SyncMaster 700(M)s Plus (CKG7507*)"
700pp="Samsung SyncMaster 700p Plus (CSH7839*)"
st9p="Samsung Samtron 9P"
1000b="Samsung SyncMaster 1000b (CGX1607*)"
1000s="Samsung SyncMaster 1000s (CGP1607*)"
320TFT="Samsung SyncMaster 320TFT (LXB310*)"
520TFT="Samsung SyncMaster 520TFT (LXB530*)"
40b="Samsung Samtron 40B"
50e="Samsung Samtron 50(M)E"
50b="Samsung Samtron 50B"
70e="Samsung Samtron 70(M)E"
510b="Samsung SyncMaster 510b(CHB5707*)"
510s="Samsung SyncMaster 510(M)s (CHA5807*)"
410b="Samsung SyncMaster 410b(CHA4217*)"
710s="Samsung SyncMaster 710(M)s (CHB7707*)"
60b="Samsung Samtron 60(M)B"
610b="Samsung SyncMaster 610(M)b(CHB6107*)"
700ift="Samsung SyncMaster 700IFT (CSH780B*)"
40bn="Samsung Samtron 40Bn"
530TFT="Samsung SyncMaster 530/531TFT (LXB550*)"
330TFT="Samsung SyncMaster 330/331TFT (LXB350*)"
700bp="Samsung SyncMaster 700b Plus"
900ift="Samsung SyncMaster 900IFT"
900sl="Samsung SyncMaster 900SL (CSM92*)"
710b="Samsung SyncMaster 710(M)b (CHB7709*)"

STC="Sampo Technology Corp."
KM-711="AlphaScan 711"
KM-811="AlphaScan 811"
KM-712="AlphaScan 712"
KM-800S="AlphaScan 800S"

SMILE="Smile International Corp."
SMILE_CA6425="Smile/KFC CA6425DL/CB6425DL"
SMILE_CA6525="Smile/KFC CA6525DL/CB6525DL"
SMILE_CA6546="Smile/KFC CA6546SL/CB6546SL"
SMILE_CA6746="Smile/KFC CA6746SL/CB6746SL"
SMILE_CA6738="Smile/KFC, 85Khz Monitor"
SMILE_CA6748="Smile/KFC CA6748SL/CB6748SL"
SMILE_CA6719="Smile/KFC CA6719SL/CB6719SL"
SMILE_CA6919="Smile/KFC CA6919SL/CB6919SL"

Sony="Sony Corporation"
CPD-L150="Sony CPD-L150"
CPD-101VS_iGPE="Sony CPD-101VS iGPE"
CPD-520GS="Sony CPD-520GS/520GST/21GS2"
CPD-2003GT="Sony CPD-2003GT"
CPD-220GS="Sony CPD-220GS"
CPD-420GS="Sony CPD-420GS"
KL-W7000="KL-W7000"
CPD-L133="Sony CPD-L133"

Tatung="Tatung"
TATUNG_C9N="Tatung VDBU C9N 19'' Colour Monitor"

Taxan="Taxan (Europe) Ltd."
EV430="Ergovision 430LR"
EV550="Ergovision 550TCO95/TCO95-S"
EV730="Ergovision 730TCO95/TCO95-S"
EV740="Ergovision 740TCO95/TCO95-S"
EV750="Ergovision 750TCO95"
EV760="Ergovision 760TCO95/TCO95-S"
EV975="Ergovision 975TCO95"

TVM="TVM Monitor,Inc"
AS5S=" TVM AS5S Model"
TCO5S=" TVM TCO5S Model"
AS4Dp=" TVM AS4Dp/LR4Dp Model"
TCO6S=" TVM TCO6S Model"

Unisys ="Unisys Corp."
UNM_5002 ="Unisys EVG5000-P"
UNM_4002 ="Unisys EVG4000-P"
UNM_2101 ="Unisys EVG2100-E"
UNM_2102 ="Unisys EVG2100-P"

ViewSonic="ViewSonic"
P810-ER="ViewSonic P810-ER"
VCDTS21368-1="ViewSonic GA771"

CDTS21367-1="Optiquest V115"
VPRJ21408-1="ViewSonic PJL802"
VCDTS21356-2="ViewSonic E641-2"
VCDTS21386-1="ViewSonic E771"
VCDTS21349-1="ViewSonic EA771"
VCDTS21349-2="ViewSonic EA771B"
VCDTS21383-1="Optiquest V95"
VCDTS21353-1="ViewSonic G771"
G810-2="ViewSonic G810-2"
VCDTS21375-1="Optiquest Q51"
P810-3="ViewSonic P810-3"
VCDTS21406-1="ViewSonic GS771"
VCDTS21404-1="ViewSonic P655"
VCDTS21397-1="ViewSonic PT771"
VPRJ21402-1="ViewSonic PJ1000"
VPRJ21357-2="ViewSonic PJ820"
VLCDS21434-1="ViewSonic VP150"
VCDTS21403-1="ViewSonic GA655"
VCDTS21420-1="ViewSonic PS790"
VCDTS21431-1="Optiquest V75"
VCDTS21433-1="Optiquest V73"
VCDTS21399-1="Optiquest V55"
VCDTS21348-2="Optiquest Q71-2"

> But, if it is a .bin file-- no sense posting that. Just state its name.
>
> |> Open the .inf file that shows up in Notepad, & post it. If "ViewSonic
> |> VP930 Series" won't find it, then try "VSCE41B", no quotes necessary.
> |
> | ;Monitor.Inf for Windows(R) 95/98/Me/2000/XP/Server 2003/XP
> | x64/Vista/Vista x64
> |
> | ;Copyright 2008, ViewSonic Corporation
> |
> | [Version]
> | signature="$CHICAGO$"
> | Class=Monitor
> | ClassGuid={4D36E96E-E325-11CE-BFC1-08002BE10318}
> | Provider=%ViewSonic%
> | DriverVer=01/14/2008, 1.5.2.44
> |
> | [DestinationDirs]
> | DefaultDestDir= 11
> ...snip
> | VP930_Series.CopyFiles=23
> ...snip
> | [SourceDisksNames]
> | 1=%DiskLabel%,,
> |
> | [SourceDisksFiles]
> ...snip
> | VP930_Series.ICM=1
> ...snip
> | [Manufacturer]
> | %ViewSonic%=ViewSonic,NTia64,NTamd64
> |
> | [ControlFlags]
> | ExcludeFromSelect.nt=*
> |
> | [ViewSonic]
> ...snip
> | %VP930_Series%=VP930_Series.Install,Monitor\VSCE41B ;VP930_Series
> ...snip
> |
> | [ViewSonic.NTia64]
> ...snip
> | %VP930_Series%=VP930_Series.Install,Monitor\VSCE41B ;VP930_Series
> ...snip
> |
> | [ViewSonic.NTamd64]
> ...snip
> | %VP930_Series%=VP930_Series.Install,Monitor\VSCE41B ;VP930_Series
> ...snip
> |
> | [VP930_Series.Install] ;VP930_Series
> | DelReg=DEL_CURRENT_REG
> | AddReg=VP930_Series.AddReg,1280,DPMS
> | Copyfiles=VP930_Series.CopyFiles
> ...snip
> |
> | [DEL_CURRENT_REG]
> | HKR,MODES
> | HKR,,MaxResolution
> | HKR,,DPMS
> | HKR,,ICMProfile
> |
> | [1280]
> | HKR,,MaxResolution,,"1280,1024"
> | [1440]
> | HKR,,MaxResolution,,"1440,900"
> | [1680]
> | HKR,,MaxResolution,,"1680,1050"
> |
> | [DPMS]
> | HKR,,DPMS,,1
> ...snip
> |
> | [VP930_Series.AddReg] ;VP930_Series
> | HKR,"MODES\1280,1024",Mode1,,"30-82,50-75,+,+"
> | HKR,,ICMProfile,0,"VP930_Series.ICM"
> ...snip
> |
> | [VP930_Series.CopyFiles]
> | VP930_Series.ICM
> ...snip
> |
> | [Strings]
> | ViewSonic="ViewSonic"
> | DiskLabel="ViewSonic Wizard"
> |
> ...snip
> | VP930_Series="ViewSonic VP930 Series"
> ...snip
>
> Here is mine, unabridged-- & so much easier to look at...!...
>
> ; Copyright 2004 Envision Peripherals, Inc.
> ; This is a Setup information file for monitors with ICM file
>
> [Version]
> signature="$CHICAGO$"
> Class=Monitor
> ClassGuid={4D36E96E-E325-11CE-BFC1-08002BE10318}
> Provider=%EPI%
> ;Catalogfile=EN5400e.cat
> DriverVer=08/20/2004,1.0.0.0
>
> [ControlFlags]
> ExcludeFromSelect.nt=Monitor\EPIE564
>
> [ClassInstall32]
> AddReg=ClassAddReg32
>
> [ClassAddReg32]
> HKR,,,,%MonitorClassName%
> HKR,,Icon,,"-1"
> HKR,,NoInstallClass,,1
>
> [DestinationDirs]
> DefaultDestDir=11
> E564.CopyFiles=23
>
> [SourceDisksNames]
> 1=%DISK%,,,
>
> [SourceDisksFiles]
> EN5400e.ICM=1
>
> ; Manufacturer
> ;-------------------------------------------------
> [Manufacturer]
> %EPI%=EPI
>
> ; Manufacturer Sections
> ;-------------------------------------------------
> [EPI]
> %E564%=E564.Install, Monitor\EPIE564
>
> ; Install Sections
> ;-------------------------------------------------
> [E564.Install]
> DelReg=DEL_CURRENT_REG
> AddReg=E564.AddReg, 1024 ,DPMS
> Copyfiles=E564.CopyFiles
>
> ; Common AddReg/DelReg sections
> ;-------------------------------------------------
> [DEL_CURRENT_REG]
> HKR,MODES
> HKR,,MaxResolution
> HKR,,DPMS
> HKR,,ICMProfile
>
> [1024]
> HKR,,MaxResolution,,"1024,768"
>
> [DPMS]
> HKR,,DPMS,,1
>
> ; Model AddReg sections
> ;-------------------------------------------------
> [E564.AddReg]
> HKR,"MODES\640,480",Mode1,,"30.0-63.0,55.0-75.0,-,-"
> HKR,"MODES\800,600",Mode1,,"30.0-63.0,55.0-75.0,+,+"
> HKR,"MODES\1024,768",Mode1,,"30.0-63.0,55.0-75.0,+,+"
> HKR,,ICMProfile,0,"EN5400e.icm"
>
> [E564.CopyFiles]
> EN5400e.icm
>
> ;-------------------------------------------------
> ; User visible strings
>
> [Strings]
> DISK="EPI Monitor Installation Disk"
> MonitorClassName="Monitor"
> EPI="Envision Peripherals, Inc"
>
> E564="Envision EN5400e"
>
> |> | Default Monitor
> |> | Monitor
> |> | This device is disabled.
> |> | Registry Key:
> |> |
> |>
> HKEY_LOCAL_MACHINE\enum\MONITOR\DEFAULT_MONITOR\PCI_VEN_1002&DEV_5961&SU
> |> BSYS
> |> | _280117EE&REV_01_000800_1
> |> | Alloc resources: None
> |> | Forced resources: None
> |> | Boot resources: None
> |> | Filtered resources: None
> |> | Basic resources: None
> |> | Driver: Monitor\0002
> |> | Driver Date: 4-23-1999
> |>
> |> The above doesn't look especially bad-- except it is unwanted!
>
>
> ...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
>
>

Brian A. · Feb 23, 2008

Re: Trouble with new display and Device Manager

"PCR" <pcrrcp@netzero.net> wrote in message
news:%23IdnEpodIHA.2448@TK2MSFTNGP03.phx.gbl...
> Warren wrote:
> | !!!Please see comments below
> |
> | "PCR" <pcrrcp@netzero.net> wrote in message
> | news:u2ynvpDdIHA.2404@TK2MSFTNGP05.phx.gbl...
>
> Continue to work with Brian A. I hesitate to say you should R-Clk your
> .inf & select "Install". I'm just not sure that monster will itself know
> you are Win98 istead of the other OS it also will work for. There might
> be something else the full install process must do first-- I don't know.
>

Don't hesitate to say, if it's not the proper file for an installed device it will
not rear an ugly head or cause any harm to the OS or machine.

--

Brian A. Sesko { MS MVP_Windows Desktop User Experience }
Conflicts start where information lacks.
http://basconotw.mvps.org/

Suggested posting do's/don'ts: http://www.dts-l.org/goodpost.htm
How to ask a question: http://support.microsoft.com/kb/555375

Warren · Feb 24, 2008

Re: Trouble with new display and Device Manager

When I right click an ICM I get the option to "Install Profile", what does
this do and where does it get installed ?

When I right click an INF I get the option to "Open" or "Print"

Where does this "Install" menu for INF files become available and where do
they get installed ?

"Brian A." <gonefish'n@afarawaylake> wrote in message
news:%23o9CgDqdIHA.536@TK2MSFTNGP06.phx.gbl...
> "PCR" <pcrrcp@netzero.net> wrote in message
> news:%23IdnEpodIHA.2448@TK2MSFTNGP03.phx.gbl...
> > Warren wrote:
> > | !!!Please see comments below
> > |
> > | "PCR" <pcrrcp@netzero.net> wrote in message
> > | news:u2ynvpDdIHA.2404@TK2MSFTNGP05.phx.gbl...
> >
> > Continue to work with Brian A. I hesitate to say you should R-Clk your
> > .inf & select "Install". I'm just not sure that monster will itself know
> > you are Win98 istead of the other OS it also will work for. There might
> > be something else the full install process must do first-- I don't know.
> >
>
> Don't hesitate to say, if it's not the proper file for an installed
device it will
> not rear an ugly head or cause any harm to the OS or machine.
>
> --
>
>
> Brian A. Sesko { MS MVP_Windows Desktop User Experience }
> Conflicts start where information lacks.
> http://basconotw.mvps.org/
>
> Suggested posting do's/don'ts: http://www.dts-l.org/goodpost.htm
> How to ask a question: http://support.microsoft.com/kb/555375
>
>
>
>

Brian A. · Feb 24, 2008

Re: Trouble with new display and Device Manager

"Warren" <nospam@nospam.com> wrote in message
news:%23QUzUUqdIHA.6092@TK2MSFTNGP06.phx.gbl...
> When I right click an ICM I get the option to "Install Profile", what does
> this do and where does it get installed ?

An .icm file is for color management associated with imaging and printing devices
and is used as a standard file to allow the same color sets to be transported from
one system to another.

>
> When I right click an INF I get the option to "Open" or "Print"

Something is amiss if you do not get the full menu with a single right click.

>
> Where does this "Install" menu for INF files become available and where do
> they get installed ?

It's not an "Install" menu, install is one of the listed entries in the popup menu
when a user right clicks on a .inf file.

--

Brian A. Sesko { MS MVP_Windows Desktop User Experience }
Conflicts start where information lacks.
http://basconotw.mvps.org/

Suggested posting do's/don'ts: http://www.dts-l.org/goodpost.htm
How to ask a question: http://support.microsoft.com/kb/555375

>
> "Brian A." <gonefish'n@afarawaylake> wrote in message
> news:%23o9CgDqdIHA.536@TK2MSFTNGP06.phx.gbl...
>> "PCR" <pcrrcp@netzero.net> wrote in message
>> news:%23IdnEpodIHA.2448@TK2MSFTNGP03.phx.gbl...
>> > Warren wrote:
>> > | !!!Please see comments below
>> > |
>> > | "PCR" <pcrrcp@netzero.net> wrote in message
>> > | news:u2ynvpDdIHA.2404@TK2MSFTNGP05.phx.gbl...
>> >
>> > Continue to work with Brian A. I hesitate to say you should R-Clk your
>> > .inf & select "Install". I'm just not sure that monster will itself know
>> > you are Win98 istead of the other OS it also will work for. There might
>> > be something else the full install process must do first-- I don't know.
>> >
>>
>> Don't hesitate to say, if it's not the proper file for an installed
> device it will
>> not rear an ugly head or cause any harm to the OS or machine.
>>
>> --
>>
>>
>> Brian A. Sesko { MS MVP_Windows Desktop User Experience }
>> Conflicts start where information lacks.
>> http://basconotw.mvps.org/
>>
>> Suggested posting do's/don'ts: http://www.dts-l.org/goodpost.htm
>> How to ask a question: http://support.microsoft.com/kb/555375
>>
>>
>>
>>
>
>

Franc Zabkar · Feb 24, 2008

Re: Trouble with new display and Device Manager

On Sat, 23 Feb 2008 21:08:18 -0500, "Warren" <nospam@nospam.com> put
finger to keyboard and composed:

>Unfortunately part of my problem is I can't figure out where to point
>Windows. I can point to the VP930_Series.inf on the CD-ROM and it seems
>happy until it looks for the VP930_Series.icm file.

Try deleting any Viewsonic INF file in the C:\Windows\INF\OTHER
directory, or rename it to some_name.in_.

>I have this file on the
>CD-ROM, C:\Windows\Inf directory and yet the installer won't accept either
>version of this file. Very strange

On my machine the .ICM file is copied to the C:\Windows\System\Color
directory.

This file is used for Image Color Management but I'm not sure how you
would fare without it.

See http://www.microsoft.com/whdc/device/display/color/icmwp.mspx

- Franc Zabkar
--
Please remove one 'i' from my address when replying by email.

PCR · Feb 25, 2008

Re: Trouble with new display and Device Manager

Warren wrote:
| ***See responses below
|
| "PCR" <pcrrcp@netzero.net> wrote in message
| news:%23917VgcdIHA.4164@TK2MSFTNGP05.phx.gbl...
|> Warren wrote:
|> | !!!Please see comments below

....snip
|> | !!!Yes I have "Viewsonic" in the left window and "%VCDTS21367-1%"
|> | in the right window. Unfortunately when I select the VP930 Series
|> | entry in the right window, it wants the CD_ROM but can't find the
|> | files it wants (even though I know they are there). This is the
|> | scenario that caused the creation of the Default Monitor in the
|> | first place, the machine couldn't get the drivers off the CD-ROM
|> | for some silly reason.
|> |
|> | !!!I've sent an e-mail to Viewsonic asking if this driver
|> | "%VCDTS21367-1%" is appropriate, and if not how to change it. I'm
|> | also not sure where the driver installer placed all the drivers.
|>
|> That is a mess! But there is no such driver as "%VCDTS21367-1%". It
|> looks to me like it is a variable that should have changed to a model
|> name. You did also get the correct model -- ViewSonic VP930 Series
|> -- in the right pane, though. However, "%VCDTS21367-1%" is the one
|> highlighted in the R-Pane. When you try to switch to VP930, a disk
|> is requested & the drivers won't be found. Yucky!

....snip
|> | !!!VS080114_I19.inf found searching for text "ViewSonic VP930
|> | Series".
|>
|> Good. My .inf is much, much smaller, & I've deleted what I consider
|> to be extraneous lines in yours below. I do not see that your .inf
|> actually creates the Registry entries for that Default Monitor--
|> something else is doing it! Your .inf DOES properly create the
|> Registry entries for the "ViewSonic VP930 Series". And your MSInfo
|> data looks also quite good to me.
|>
|> Comparing your abridged .inf to mine, I see nothing startlingly bad.
|> Although I'm not a perfect expert, my impression seems corroborated
|> in that your Registry & MSInfo32 stuff look fine for the VP930.
|>
|> (a) You do actually have a... VP930_Series.ICM?
|> (My own EN5400e.icm is located in...
|> C:\WINDOWS\SYSTEM\COLOR.)
|
|>*** YES

OK. That is good. I'll have to agree with Brian A. on what it actually
does, whether it is the entire driver for the monitor or just a part of
it. It is the only file I can detect our .inf's are actually installing
for our particular monitor model.

Mine says...
[E564.CopyFiles]
EN5400e.icm

Yours says...
[VP930_Series.CopyFiles]
VP930_Series.ICM

I wonder... did your monster .inf install any of the other .icm files?
Look, for instance, for... VA902-2_SERIES.ICM & VA912-5_SERIES.ICM...
which are the ones before & after the correct one in your .inf.

|> (b) In that Update Driver requestor, when "ViewSonic" is
|> selected in the left (Manufacturers) pane, do you
|> have a trillion entries in the right (Models) pane?
|> (I have just "Envision EN5400e" there.)
|
|> *** Well it depends on whether or not you ask the list to be "all
| hardware" or "only compatible hardware"

I meant, after bolting "Show all hardware" in that Update Driver
requestor. And I see your answer is yes, that a trillion names will
showup in the Models pane. But I bundle of them too.

|> (c) In that requestor, what are a few Models immediately
|> before & after "%VCDTS21367-1%"?
|> (I might be able to spot a syntax error in your .inf, but
|> oddly I can't spot "%VCDTS21367-1%" itself in there.)

You didn't answer, but no matter-- I see what caused that in the
MONITR11.INF you posted below. I happen to have the very same
MONITR11.INF in this machine-- with the same error in it! I should have
thought of this earlier. I went into that Update Driver requestor-- & I
too have a "%VCDTS21367-1%" on top of the list of models when ViewSonic
is selected in the manufacturer's pane! Also, it is the highlighted one,
probably because it is on top.

|> (d) I'm not sure where the Manufacturers & Models that show
|> up in the Update Drivers requestor come from. There does
|> not seem to be a list of them in my Registry. I'm thinking
|> they may be built on the fly from the .inf's in
|> C:\Windows\Inf. Therefore...
|>
|> Look through that folder & subfolders for something unusal,
|> &...
|>
|> (1) "START button, Find, F/F"
|> (2) Leave "Named" empty.
|> (3) In "Containing text", enter... %VCDTS21367-1%
|> (4) In "Look in", browse to... "C:\WINDOWS\INF".
|> (5) If it is found, post the .inf.
|>
|
| *** Monitr11.inf, Drvidx.bin

I see the problem in this MONITR11.INF, which is setting up (or is part
of what sets up) that Update Driver requestor.

| ; MONITR11.INF
| ;
| ; This is a Setup information file for monitors P-Z
|
| [Version]
| LayoutFile= Layout.inf, Layout1.inf, Layout2.inf
| signature="$CHICAGO$"
| Class=Monitor
| ClassGuid={4D36E96E-E325-11CE-BFC1-08002BE10318}
| Provider=%MS%
| SetupClass=BASE
| CatalogFile=monitr11.cat
|

....snip of most of the .inf...
| ViewSonic="ViewSonic"
| P810-ER="ViewSonic P810-ER"
| VCDTS21368-1="ViewSonic GA771"
|
| CDTS21367-1="Optiquest V115"

The above line is wrong in yours & in mine. It should have a "V" in
front, thus...

VCDTS21367-1="Optiquest V115"

After that is done, likely we will end up with "Optiquest V115" in the
Models pane, instead of the gobbledygook. WELL-- bravely, I've done it!
A reboot wasn't even necessary...

(a) Open MONITR11.INF in Notepad.
(b) Change that line to have a "V" in front,
& save the file.
(c) R-Clk the MONITR11.inf in Explorer or a "Find" box,
& select "Install".

NOTE: There is no feedback that the install happens;
however, it does-- though InCtrl5 (my tracker)
shows precious little to have happened.

(d) Open the Update Driver requestor, get to & bolt
"Show all hardware".

NOTE: At that point (IIRC) Windows will quickly update
its "driver information database". Afterwards,
looks like 2 files are updated...
DRVDATA.bin & DRVIDX.bin.

(e) Click "ViewSonic" in the left (Manufacturers) pane.

You will see the gobbledygook "%VCDTS21367-1%"
is gone, & "Optiquest V115" is there instead, though
not on top.

I don't know whether it solves anything else, though. I'm thinking it is
unlikely that this fix will enable you to switch to "ViewSonic VP930
Series" at that screen. I guess its worth a try, though.

NOTE: If you lose "ViewSonic VP930 Series" as a choice, do a reboot. I
don't get that choice-- its a different .inf that installs it. Likely,
the process of rebuilding the driver information database gets it back
for you, though, without a reboot.

I'm still thinking, because I doubt that does more than rid you of the
gobbledygook. Soon, I must go watch Terminator. I'll get back to the
other post after that or tomorrow.

....snip of more of the .inf...
....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 · Feb 25, 2008

Re: Trouble with new display and Device Manager

Brian A. wrote:
| "Warren" <nospam@nospam.com> wrote in message
| news:%23QUzUUqdIHA.6092@TK2MSFTNGP06.phx.gbl...
|> When I right click an ICM I get the option to "Install Profile",
|> what does this do and where does it get installed ?
|
| An .icm file is for color management associated with imaging and
| printing devices and is used as a standard file to allow the same
| color sets to be transported from one system to another.
|
|>
|> When I right click an INF I get the option to "Open" or "Print"
|
| Something is amiss if you do not get the full menu with a single
| right click.

Absolutely-- something seems to be wrong! I copied Warren's posted
VS080114_I19.inf into a file of my own....
news:%235fmYYEdIHA.4144@TK2MSFTNGP05.phx.gbl

I R-Clkd it-- & "Install" is an option, right under Open & Print.

Warren... you don't you get "Install" for any .inf? What do you see at
this Registry key...?...

REGEDIT4

[HKEY_CLASSES_ROOT\.inf]
@="inffile"

....& this one...?...

REGEDIT4

[HKEY_CLASSES_ROOT\inffile]
@="Setup Information"

[HKEY_CLASSES_ROOT\inffile\DefaultIcon]
@="shell32.dll,-151"

[HKEY_CLASSES_ROOT\inffile\shell]

[HKEY_CLASSES_ROOT\inffile\shell\open]

[HKEY_CLASSES_ROOT\inffile\shell\open\command]
@="c:\\windows\\NOTEPAD.EXE %1"

[HKEY_CLASSES_ROOT\inffile\shell\print]

[HKEY_CLASSES_ROOT\inffile\shell\print\command]
@="c:\\windows\\NOTEPAD.EXE /p %1"

[HKEY_CLASSES_ROOT\inffile\shell\install]
@="&Install"

[HKEY_CLASSES_ROOT\inffile\shell\install\command]
@="c:\\windows\\rundll.exe setupx.dll,InstallHinfSection DefaultInstall
132 %1"

If they don't look like mine, then try...

http://home.satx.rr.com/badour/assets/images/InfInstall.zip
Repairs missing Install entry on right-click context menu.

That will come in as a .zip. Unzip it, then click the .reg file that was
inside. It should fix both Registry keys to look like mine.

|>
|> Where does this "Install" menu for INF files become available and
|> where do they get installed ?
|
| It's not an "Install" menu, install is one of the listed entries in
| the popup menu when a user right clicks on a .inf file.
|
|
| --
|
|
| Brian A. Sesko { MS MVP_Windows Desktop User Experience }
| Conflicts start where information lacks.
| http://basconotw.mvps.org/
|
| Suggested posting do's/don'ts: http://www.dts-l.org/goodpost.htm
| How to ask a question: http://support.microsoft.com/kb/555375
|
|
|
|>
|> "Brian A." <gonefish'n@afarawaylake> wrote in message
|> news:%23o9CgDqdIHA.536@TK2MSFTNGP06.phx.gbl...
|>> "PCR" <pcrrcp@netzero.net> wrote in message
|>> news:%23IdnEpodIHA.2448@TK2MSFTNGP03.phx.gbl...
|>> > Warren wrote:
|>> > | !!!Please see comments below
|>> > |
|>> > | "PCR" <pcrrcp@netzero.net> wrote in message
|>> > | news:u2ynvpDdIHA.2404@TK2MSFTNGP05.phx.gbl...
|>> >
|>> > Continue to work with Brian A. I hesitate to say you should R-Clk
|>> > your .inf & select "Install". I'm just not sure that monster will
|>> > itself know you are Win98 istead of the other OS it also will
|>> > work for. There might be something else the full install process
|>> > must do first-- I don't know.
|>> >
|>>
|>> Don't hesitate to say, if it's not the proper file for an
|>> installed
|> device it will
|>> not rear an ugly head or cause any harm to the OS or machine.
|>>
|>> --
|>>
|>>
|>> Brian A. Sesko { MS MVP_Windows Desktop User Experience }
|>> Conflicts start where information lacks.
|>> http://basconotw.mvps.org/
|>>
|>> Suggested posting do's/don'ts: http://www.dts-l.org/goodpost.htm
|>> How to ask a question: http://support.microsoft.com/kb/555375

--
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 · Feb 25, 2008

Re: Trouble with new display and Device Manager

Thanks PCR,that solved the problem perfectly. Good fix.

"PCR" <pcrrcp@netzero.net> wrote in message
news:O$5VlXCeIHA.288@TK2MSFTNGP02.phx.gbl...
> Brian A. wrote:
> | "Warren" <nospam@nospam.com> wrote in message
> | news:%23QUzUUqdIHA.6092@TK2MSFTNGP06.phx.gbl...
> |> When I right click an ICM I get the option to "Install Profile",
> |> what does this do and where does it get installed ?
> |
> | An .icm file is for color management associated with imaging and
> | printing devices and is used as a standard file to allow the same
> | color sets to be transported from one system to another.
> |
> |>
> |> When I right click an INF I get the option to "Open" or "Print"
> |
> | Something is amiss if you do not get the full menu with a single
> | right click.
>
> Absolutely-- something seems to be wrong! I copied Warren's posted
> VS080114_I19.inf into a file of my own....
> news:%235fmYYEdIHA.4144@TK2MSFTNGP05.phx.gbl
>
> I R-Clkd it-- & "Install" is an option, right under Open & Print.
>
> Warren... you don't you get "Install" for any .inf? What do you see at
> this Registry key...?...
>
> REGEDIT4
>
> [HKEY_CLASSES_ROOT\.inf]
> @="inffile"
>
> ...& this one...?...
>
> REGEDIT4
>
> [HKEY_CLASSES_ROOT\inffile]
> @="Setup Information"
>
> [HKEY_CLASSES_ROOT\inffile\DefaultIcon]
> @="shell32.dll,-151"
>
> [HKEY_CLASSES_ROOT\inffile\shell]
>
> [HKEY_CLASSES_ROOT\inffile\shell\open]
>
> [HKEY_CLASSES_ROOT\inffile\shell\open\command]
> @="c:\\windows\\NOTEPAD.EXE %1"
>
> [HKEY_CLASSES_ROOT\inffile\shell\print]
>
> [HKEY_CLASSES_ROOT\inffile\shell\print\command]
> @="c:\\windows\\NOTEPAD.EXE /p %1"
>
> [HKEY_CLASSES_ROOT\inffile\shell\install]
> @="&Install"
>
> [HKEY_CLASSES_ROOT\inffile\shell\install\command]
> @="c:\\windows\\rundll.exe setupx.dll,InstallHinfSection DefaultInstall
> 132 %1"
>
> If they don't look like mine, then try...
>
> http://home.satx.rr.com/badour/assets/images/InfInstall.zip
> Repairs missing Install entry on right-click context menu.
>
> That will come in as a .zip. Unzip it, then click the .reg file that was
> inside. It should fix both Registry keys to look like mine.
>
> |>
> |> Where does this "Install" menu for INF files become available and
> |> where do they get installed ?
> |
> | It's not an "Install" menu, install is one of the listed entries in
> | the popup menu when a user right clicks on a .inf file.
> |
> |
> | --
> |
> |
> | Brian A. Sesko { MS MVP_Windows Desktop User Experience }
> | Conflicts start where information lacks.
> | http://basconotw.mvps.org/
> |
> | Suggested posting do's/don'ts: http://www.dts-l.org/goodpost.htm
> | How to ask a question: http://support.microsoft.com/kb/555375
> |
> |
> |
> |>
> |> "Brian A." <gonefish'n@afarawaylake> wrote in message
> |> news:%23o9CgDqdIHA.536@TK2MSFTNGP06.phx.gbl...
> |>> "PCR" <pcrrcp@netzero.net> wrote in message
> |>> news:%23IdnEpodIHA.2448@TK2MSFTNGP03.phx.gbl...
> |>> > Warren wrote:
> |>> > | !!!Please see comments below
> |>> > |
> |>> > | "PCR" <pcrrcp@netzero.net> wrote in message
> |>> > | news:u2ynvpDdIHA.2404@TK2MSFTNGP05.phx.gbl...
> |>> >
> |>> > Continue to work with Brian A. I hesitate to say you should R-Clk
> |>> > your .inf & select "Install". I'm just not sure that monster will
> |>> > itself know you are Win98 istead of the other OS it also will
> |>> > work for. There might be something else the full install process
> |>> > must do first-- I don't know.
> |>> >
> |>>
> |>> Don't hesitate to say, if it's not the proper file for an
> |>> installed
> |> device it will
> |>> not rear an ugly head or cause any harm to the OS or machine.
> |>>
> |>> --
> |>>
> |>>
> |>> Brian A. Sesko { MS MVP_Windows Desktop User Experience }
> |>> Conflicts start where information lacks.
> |>> http://basconotw.mvps.org/
> |>>
> |>> Suggested posting do's/don'ts: http://www.dts-l.org/goodpost.htm
> |>> How to ask a question: http://support.microsoft.com/kb/555375
>
> --
> 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 · Feb 26, 2008

Re: Trouble with new display and Device Manager

See comments below +++

"PCR" <pcrrcp@netzero.net> wrote in message
news:%23AXVIyBeIHA.5984@TK2MSFTNGP06.phx.gbl...
> Warren wrote:
> | ***See responses below
> |
> | "PCR" <pcrrcp@netzero.net> wrote in message
> | news:%23917VgcdIHA.4164@TK2MSFTNGP05.phx.gbl...
> |> Warren wrote:
> |> | !!!Please see comments below
>
> ...snip
> |> | !!!Yes I have "Viewsonic" in the left window and "%VCDTS21367-1%"
> |> | in the right window. Unfortunately when I select the VP930 Series
> |> | entry in the right window, it wants the CD_ROM but can't find the
> |> | files it wants (even though I know they are there). This is the
> |> | scenario that caused the creation of the Default Monitor in the
> |> | first place, the machine couldn't get the drivers off the CD-ROM
> |> | for some silly reason.
> |> |
> |> | !!!I've sent an e-mail to Viewsonic asking if this driver
> |> | "%VCDTS21367-1%" is appropriate, and if not how to change it. I'm
> |> | also not sure where the driver installer placed all the drivers.
> |>
> |> That is a mess! But there is no such driver as "%VCDTS21367-1%". It
> |> looks to me like it is a variable that should have changed to a model
> |> name. You did also get the correct model -- ViewSonic VP930 Series
> |> -- in the right pane, though. However, "%VCDTS21367-1%" is the one
> |> highlighted in the R-Pane. When you try to switch to VP930, a disk
> |> is requested & the drivers won't be found. Yucky!
>
> ...snip
> |> | !!!VS080114_I19.inf found searching for text "ViewSonic VP930
> |> | Series".
> |>
> |> Good. My .inf is much, much smaller, & I've deleted what I consider
> |> to be extraneous lines in yours below. I do not see that your .inf
> |> actually creates the Registry entries for that Default Monitor--
> |> something else is doing it! Your .inf DOES properly create the
> |> Registry entries for the "ViewSonic VP930 Series". And your MSInfo
> |> data looks also quite good to me.
> |>
> |> Comparing your abridged .inf to mine, I see nothing startlingly bad.
> |> Although I'm not a perfect expert, my impression seems corroborated
> |> in that your Registry & MSInfo32 stuff look fine for the VP930.
> |>
> |> (a) You do actually have a... VP930_Series.ICM?
> |> (My own EN5400e.icm is located in...
> |> C:\WINDOWS\SYSTEM\COLOR.)
> |
> |>*** YES
>
> OK. That is good. I'll have to agree with Brian A. on what it actually
> does, whether it is the entire driver for the monitor or just a part of
> it. It is the only file I can detect our .inf's are actually installing
> for our particular monitor model.
>
> Mine says...
> [E564.CopyFiles]
> EN5400e.icm
>
> Yours says...
> [VP930_Series.CopyFiles]
> VP930_Series.ICM
>
> I wonder... did your monster .inf install any of the other .icm files?
> Look, for instance, for... VA902-2_SERIES.ICM & VA912-5_SERIES.ICM...
> which are the ones before & after the correct one in your .inf.

+++ VP920_Series.icm above
+++ VP950B.icm below

> |> (b) In that Update Driver requestor, when "ViewSonic" is
> |> selected in the left (Manufacturers) pane, do you
> |> have a trillion entries in the right (Models) pane?
> |> (I have just "Envision EN5400e" there.)
> |
> |> *** Well it depends on whether or not you ask the list to be "all
> | hardware" or "only compatible hardware"
>
> I meant, after bolting "Show all hardware" in that Update Driver
> requestor. And I see your answer is yes, that a trillion names will
> showup in the Models pane. But I bundle of them too.
>
> |> (c) In that requestor, what are a few Models immediately
> |> before & after "%VCDTS21367-1%"?
> |> (I might be able to spot a syntax error in your .inf, but
> |> oddly I can't spot "%VCDTS21367-1%" itself in there.)
>
> You didn't answer, but no matter-- I see what caused that in the
> MONITR11.INF you posted below. I happen to have the very same
> MONITR11.INF in this machine-- with the same error in it! I should have
> thought of this earlier. I went into that Update Driver requestor-- & I
> too have a "%VCDTS21367-1%" on top of the list of models when ViewSonic
> is selected in the manufacturer's pane! Also, it is the highlighted one,
> probably because it is on top.
>
> |> (d) I'm not sure where the Manufacturers & Models that show
> |> up in the Update Drivers requestor come from. There does
> |> not seem to be a list of them in my Registry. I'm thinking
> |> they may be built on the fly from the .inf's in
> |> C:\Windows\Inf. Therefore...
> |>
> |> Look through that folder & subfolders for something unusal,
> |> &...
> |>
> |> (1) "START button, Find, F/F"
> |> (2) Leave "Named" empty.
> |> (3) In "Containing text", enter... %VCDTS21367-1%
> |> (4) In "Look in", browse to... "C:\WINDOWS\INF".
> |> (5) If it is found, post the .inf.
> |>
> |
> | *** Monitr11.inf, Drvidx.bin
>
> I see the problem in this MONITR11.INF, which is setting up (or is part
> of what sets up) that Update Driver requestor.
>
> | ; MONITR11.INF
> | ;
> | ; This is a Setup information file for monitors P-Z
> |
> | [Version]
> | LayoutFile= Layout.inf, Layout1.inf, Layout2.inf
> | signature="$CHICAGO$"
> | Class=Monitor
> | ClassGuid={4D36E96E-E325-11CE-BFC1-08002BE10318}
> | Provider=%MS%
> | SetupClass=BASE
> | CatalogFile=monitr11.cat
> |
>
> ...snip of most of the .inf...
> | ViewSonic="ViewSonic"
> | P810-ER="ViewSonic P810-ER"
> | VCDTS21368-1="ViewSonic GA771"
> |
> | CDTS21367-1="Optiquest V115"
>
> The above line is wrong in yours & in mine. It should have a "V" in
> front, thus...
>
> VCDTS21367-1="Optiquest V115"
>
> After that is done, likely we will end up with "Optiquest V115" in the
> Models pane, instead of the gobbledygook. WELL-- bravely, I've done it!
> A reboot wasn't even necessary...
>
> (a) Open MONITR11.INF in Notepad.
> (b) Change that line to have a "V" in front,
> & save the file.
> (c) R-Clk the MONITR11.inf in Explorer or a "Find" box,
> & select "Install".
>
> NOTE: There is no feedback that the install happens;
> however, it does-- though InCtrl5 (my tracker)
> shows precious little to have happened.
>
> (d) Open the Update Driver requestor, get to & bolt
> "Show all hardware".
>
> NOTE: At that point (IIRC) Windows will quickly update
> its "driver information database". Afterwards,
> looks like 2 files are updated...
> DRVDATA.bin & DRVIDX.bin.
>
> (e) Click "ViewSonic" in the left (Manufacturers) pane.
>
> You will see the gobbledygook "%VCDTS21367-1%"
> is gone, & "Optiquest V115" is there instead, though
> not on top.
>
> I don't know whether it solves anything else, though. I'm thinking it is
> unlikely that this fix will enable you to switch to "ViewSonic VP930
> Series" at that screen. I guess its worth a try, though.
>
> NOTE: If you lose "ViewSonic VP930 Series" as a choice, do a reboot. I
> don't get that choice-- its a different .inf that installs it. Likely,
> the process of rebuilding the driver information database gets it back
> for you, though, without a reboot.
>
> I'm still thinking, because I doubt that does more than rid you of the
> gobbledygook. Soon, I must go watch Terminator. I'll get back to the
> other post after that or tomorrow.

+++ Good find, it certainly got rid of the garbage. Unfortunately it
doesn't solve the problem with not accepting the VP930_Series.icm

>
> ...snip of more of the .inf...
> ...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 · Feb 26, 2008

Re: Trouble with new display and Device Manager

Warren wrote:
| See comments below +++
|
| "PCR" <pcrrcp@netzero.net> wrote in message
| news:%23AXVIyBeIHA.5984@TK2MSFTNGP06.phx.gbl...

....snip
|> |> (a) You do actually have a... VP930_Series.ICM?
|> |> (My own EN5400e.icm is located in...
|> |> C:\WINDOWS\SYSTEM\COLOR.)
|> |
|> |>*** YES
|>
|> OK. That is good. I'll have to agree with Brian A. on what it
|> actually does, whether it is the entire driver for the monitor or
|> just a part of it. It is the only file I can detect our .inf's are
|> actually installing for our particular monitor model.
|>
|> Mine says...
|> [E564.CopyFiles]
|> EN5400e.icm
|>
|> Yours says...
|> [VP930_Series.CopyFiles]
|> VP930_Series.ICM
|>
|> I wonder... did your monster .inf install any of the other .icm
|> files? Look, for instance, for... VA902-2_SERIES.ICM &
|> VA912-5_SERIES.ICM... which are the ones before & after the correct
|> one in your .inf.
|
| +++ VP920_Series.icm above
| +++ VP950B.icm below

Hmm. Not bad-- I was just worried you might have gotten the full
trillion that appear in your VS080114_I19.inf. Did you ever have those
monitor models installed or switch temporarily to them in the Update
Driver requestor?

I think we should let it be, though, because, in my own...
C:\WINDOWS\SYSTEM\COLOR... I have 43 .icm in addition to EN5400E.ICM.
But all of mine came with the machine except for two. And they don't
appear to be just for monitors.

....snip
|> I see the problem in this MONITR11.INF, which is setting up (or is
|> part of what sets up) that Update Driver requestor.
|>
|> | ; MONITR11.INF
|> | ;
|> | ; This is a Setup information file for monitors P-Z
|> |
|> | [Version]
|> | LayoutFile= Layout.inf, Layout1.inf, Layout2.inf
|> | signature="$CHICAGO$"
|> | Class=Monitor
|> | ClassGuid={4D36E96E-E325-11CE-BFC1-08002BE10318}
|> | Provider=%MS%
|> | SetupClass=BASE
|> | CatalogFile=monitr11.cat
|> |
|>
|> ...snip of most of the .inf...
|> | ViewSonic="ViewSonic"
|> | P810-ER="ViewSonic P810-ER"
|> | VCDTS21368-1="ViewSonic GA771"
|> |
|> | CDTS21367-1="Optiquest V115"
|>
|> The above line is wrong in yours & in mine. It should have a "V" in
|> front, thus...
|>
|> VCDTS21367-1="Optiquest V115"
|>
|> After that is done, likely we will end up with "Optiquest V115" in
|> the Models pane, instead of the gobbledygook. WELL-- bravely, I've
|> done it! A reboot wasn't even necessary...
|>
|> (a) Open MONITR11.INF in Notepad.
|> (b) Change that line to have a "V" in front,
|> & save the file.
|> (c) R-Clk the MONITR11.inf in Explorer or a "Find" box,
|> & select "Install".
|>
|> NOTE: There is no feedback that the install happens;
|> however, it does-- though InCtrl5 (my tracker)
|> shows precious little to have happened.
|>
|> (d) Open the Update Driver requestor, get to & bolt
|> "Show all hardware".
|>
|> NOTE: At that point (IIRC) Windows will quickly update
|> its "driver information database". Afterwards,
|> looks like 2 files are updated...
|> DRVDATA.bin & DRVIDX.bin.
|>
|> (e) Click "ViewSonic" in the left (Manufacturers) pane.
|>
|> You will see the gobbledygook "%VCDTS21367-1%"
|> is gone, & "Optiquest V115" is there instead, though
|> not on top.
|>
|> I don't know whether it solves anything else, though. I'm thinking
|> it is unlikely that this fix will enable you to switch to "ViewSonic
|> VP930 Series" at that screen. I guess its worth a try, though.
|>
|> NOTE: If you lose "ViewSonic VP930 Series" as a choice, do a
|> reboot. I don't get that choice-- its a different .inf that installs
|> it. Likely, the process of rebuilding the driver information
|> database gets it back for you, though, without a reboot.
|>
|> I'm still thinking, because I doubt that does more than rid you of
|> the gobbledygook. Soon, I must go watch Terminator. I'll get back to
|> the other post after that or tomorrow.
|
| +++ Good find, it certainly got rid of the garbage. Unfortunately it
| doesn't solve the problem with not accepting the VP930_Series.icm

Alright. Very good. Yea, I'm still thinking on the rest. I will respond
elsewhere.

PCR · Feb 26, 2008

Re: Trouble with new display and Device Manager

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?

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

(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.)
(b) Click the Change button, & the Next button.
(c) Bolt "Display a list...", & click "Next".
Does ViewSonic VP930 Series show in the Models box?
(d) Bolt "Show all hardware".
Examine the two panes to see what is currently installed.

In the left (Manufacturers) pane, you should see ViewSonic, & in the
right (Models) pane, you should see ViewSonic VP930 Series selected &
highlighted.

| "PCR" <pcrrcp@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
pcrrcp@netzero.net

PCR · Feb 26, 2008

Re: Trouble with new display and Device Manager

Warren wrote:
| Wow!

Yep! You've got another monster here! Try reinstalling that
VS080114_I19.inf as posted elsewhere. If that fails to clean this up, we
may try to do it manually. We'll do the ENUM key & this one at the same
time, if necessary!

It looks like this could have been caused by trying to use that Update
Driver requestor when .inf processing was inhibited. Now that "Install"
is back in your context menu, all of this may actually clean up on its
own after VS080114_I19.inf is run.

| [HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor]
| @="Monitors"
| "Installer"="SetupX.Dll, Monitor_ClassInstaller"
| "Icon"="-1"
| "Link"="{4D36E96E-E325-11CE-BFC1-08002BE10318}"
|
|
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor\0001
]
| "InfPath"="MONITOR.INF"
| "InfSection"="Unknown.Install"
| "ProviderName"="Microsoft"
| "DriverDate"=" 4-23-1999"
| "DriverDesc"="Default Monitor"
| "MatchingDeviceId"="Monitor\\Default_Monitor"
|
|
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor\0001
\MOD
| ES]
|
|
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor\0001
\MOD
| ES\640,480]
| @=""
|
|
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor\0004
]
| "MaxResolution"="1600,1200"
| "DPMS"="1"
| "InfPath"="MONITOR.INF"
| "InfSection"="VESADDC.Install"
| "ProviderName"="Microsoft"
| "DriverDate"=" 4-23-1999"
| "DriverDesc"="Plug and Play Monitor"
| "MatchingDeviceId"="*PNP09FF"
|
|
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor\0004
\MOD
| ES]
|
|
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor\0004
\MOD
| ES\1600,1200]
| @=""
|
|
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor\0005
]
| "MaxResolution"="1600,1200"
| "DPMS"="1"
| "InfPath"="MONITOR.INF"
| "InfSection"="VESADDC.Install"
| "ProviderName"="Microsoft"
| "DriverDate"=" 4-23-1999"
| "DriverDesc"="Plug and Play Monitor"
| "MatchingDeviceId"="*PNP09FF"
|
|
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor\0005
\MOD
| ES]
|
|
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor\0005
\MOD
| ES\1600,1200]
| @=""
|
|
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor\0006
]
| "InfPath"="MONITOR.INF"
| "InfSection"="Unknown.Install"
| "ProviderName"="Microsoft"
| "DriverDate"=" 4-23-1999"
| "DriverDesc"="Default Monitor"
| "MatchingDeviceId"="Monitor\\Default_Monitor"
|
|
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor\0006
\MOD
| ES]
|
|
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor\0006
\MOD
| ES\640,480]
| @=""
|
|
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor\0007
]
| "InfPath"="MONITOR.INF"
| "InfSection"="Unknown.Install"
| "ProviderName"="Microsoft"
| "DriverDate"=" 4-23-1999"
| "DriverDesc"="Default Monitor"
| "MatchingDeviceId"="Monitor\\Default_Monitor"
|
|
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor\0007
\MOD
| ES]
|
|
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor\0007
\MOD
| ES\640,480]
| @=""
|
|
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor\0008
]
| "ICMProfile"=hex:56,50,39,33,30,5f,53,65,72,69,65,73,2e,49,43,4d,00,00
| "MaxResolution"="1280,1024"
| "DPMS"="1"
| "InfPath"="VIEWSO~1.INF"
| "InfSection"="VP930_Series.Install"
| "ProviderName"="ViewSonic"
| "DriverDate"=" 2-16-2008"
| "DriverDesc"="ViewSonic VP930 Series"
| "MatchingDeviceId"="Monitor\\VSCE41B"
|
|
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor\0008
\MOD
| ES]
|
|
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor\0008
\MOD
| ES\1280,1024]
| "Mode1"="30-82,50-75,+,+"
|
|
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor\0009
]
| "InfPath"="MONITOR.INF"
| "InfSection"="Unknown.Install"
| "ProviderName"="Microsoft"
| "DriverDate"=" 4-23-1999"
| "DriverDesc"="Default Monitor"
| "MatchingDeviceId"="Monitor\\Default_Monitor"
|
|
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor\0009
\MOD
| ES]
|
|
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor\0009
\MOD
| ES\640,480]
| @=""
|
|
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor\0010
]
| "ICMProfile"=hex:56,50,39,33,30,5f,53,65,72,69,65,73,2e,49,43,4d,00,00
| "MaxResolution"="1280,1024"
| "DPMS"="1"
| "InfPath"="VIEWSO~1.INF"
| "InfSection"="VP930_Series.Install"
| "ProviderName"="ViewSonic"
| "DriverDate"=" 2-16-2008"
| "DriverDesc"="ViewSonic VP930 Series"
| "MatchingDeviceId"="Monitor\\VSCE41B"
|
|
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor\0010
\MOD
| ES]
|
|
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor\0010
\MOD
| ES\1280,1024]
| "Mode1"="30-82,50-75,+,+"
|
|
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor\0011
]
| "InfPath"="MONITOR.INF"
| "InfSection"="Unknown.Install"
| "ProviderName"="Microsoft"
| "DriverDate"=" 4-23-1999"
| "DriverDesc"="Default Monitor"
| "MatchingDeviceId"="Monitor\\Default_Monitor"
|
|
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor\0011
\MOD
| ES]
|
|
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor\0011
\MOD
| ES\640,480]
| @=""
|
|
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor\0000
]
| "ICMProfile"=hex:56,50,39,33,30,5f,53,65,72,69,65,73,2e,49,43,4d,00,00
| "MaxResolution"="1280,1024"
| "DPMS"="1"
| "InfPath"="VIEWSO~1.INF"
| "InfSection"="VP930_Series.Install"
| "ProviderName"="ViewSonic"
| "DriverDate"=" 2-16-2008"
| "DriverDesc"="ViewSonic VP930 Series"
| "MatchingDeviceId"="Monitor\\VSCE41B"
|
|
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor\0000
\MOD
| ES]
|
|
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor\0000
\MOD
| ES\1280,1024]
| "Mode1"="30-82,50-75,+,+"
|
|
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor\0002
]
| "InfPath"="MONITOR.INF"
| "InfSection"="Unknown.Install"
| "ProviderName"="Microsoft"
| "DriverDate"=" 4-23-1999"
| "DriverDesc"="Default Monitor"
| "MatchingDeviceId"="Monitor\\Default_Monitor"
|
|
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor\0002
\MOD
| ES]
|
|
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor\0002
\MOD
| ES\640,480]
| @=""
|
|
[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"
|
|
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor\0003
\MOD
| ES]
|
|
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor\0003
\MOD
| ES\1600,1280]
| "Mode1"="30-95,50-160,+,+"
|
|
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor\0012
]
| "ICMProfile"=hex:56,50,39,33,30,5f,53,65,72,69,65,73,2e,49,43,4d,00,00
| "MaxResolution"="1280,1024"
| "DPMS"="1"
| "InfPath"="VIEWSO~1.INF"
| "InfSection"="VP930_Series.Install"
| "ProviderName"="ViewSonic"
| "DriverDate"=" 2-16-2008"
| "DriverDesc"="ViewSonic VP930 Series"
| "MatchingDeviceId"="Monitor\\VSCE41B"
|
|
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor\0012
\MOD
| ES]
|
|
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor\0012
\MOD
| ES\1280,1024]
| "Mode1"="30-82,50-75,+,+"
|
|
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor\0013
]
| "InfPath"="MONITOR.INF"
| "InfSection"="Unknown.Install"
| "ProviderName"="Microsoft"
| "DriverDate"=" 4-23-1999"
| "DriverDesc"="Default Monitor"
| "MatchingDeviceId"="Monitor\\Default_Monitor"
|
|
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor\0013
\MOD
| ES]
|
|
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor\0013
\MOD
| ES\640,480]
| @=""
|
|
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor\0014
]
| "ICMProfile"=hex:56,50,39,33,30,5f,53,65,72,69,65,73,2e,49,43,4d,00,00
| "MaxResolution"="1280,1024"
| "DPMS"="1"
| "InfPath"="VIEWSO~1.INF"
| "InfSection"="VP930_Series.Install"
| "ProviderName"="ViewSonic"
| "DriverDate"=" 2-16-2008"
| "DriverDesc"="ViewSonic VP930 Series"
| "MatchingDeviceId"="Monitor\\VSCE41B"
|
|
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor\0014
\MOD
| ES]
|
|
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor\0014
\MOD
| ES\1280,1024]
| "Mode1"="30-82,50-75,+,+"
|
|
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor\0015
]
| "InfPath"="MONITOR.INF"
| "InfSection"="Unknown.Install"
| "ProviderName"="Microsoft"
| "DriverDate"=" 4-23-1999"
| "DriverDesc"="Default Monitor"
| "MatchingDeviceId"="Monitor\\Default_Monitor"
|
|
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor\0015
\MOD
| ES]
|
|
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor\0015
\MOD
| ES\640,480]
| @=""
|
|
| "PCR" <pcrrcp@netzero.net> wrote in message
| news:%23IdnEpodIHA.2448@TK2MSFTNGP03.phx.gbl...
|> Warren wrote:
|> | !!!Please see comments below
|> |
|> | "PCR" <pcrrcp@netzero.net> wrote in message
|> | news:u2ynvpDdIHA.2404@TK2MSFTNGP05.phx.gbl...
|>
|> Continue to work with Brian A. I hesitate to say you should R-Clk
|> your .inf & select "Install". I'm just not sure that monster will
|> itself know you are Win98 istead of the other OS it also will work
|> for. There might be something else the full install process must do
|> first-- I don't know.
|>
|> You owe me a response to a nearby post. Also, I have found another
|> interesting Registry key. Post yours...
|>
|> [HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor]
|> @="Monitors"
|> "Installer"="SetupX.Dll, Monitor_ClassInstaller"
|> "Icon"="-1"
|> "Link"="{4d36e96e-e325-11ce-bfc1-08002be10318}"
|>
|>
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor\0000
|> ]
|> "ICMProfile"=hex:45,4e,35,34,30,30,65,2e,69,63,6d,00,00
|> "MaxResolution"="1024,768"
|> "DPMS"="1"
|> "InfPath"="ENVISI~1.INF"
|> "InfSection"="E564.Install"
|> "ProviderName"="Envision Peripherals, Inc"
|> "DriverDate"=" 8-20-2004"
|> "DriverDesc"="Envision EN5400e"
|> "MatchingDeviceId"="Monitor\\EPIE564"
|>
|>
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor\0000
|> \MODES]
|>
|>
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor\0000
|> \MODES\640,480]
|> "Mode1"="30.0-63.0,55.0-75.0,-,-"
|>
|>
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor\0000
|> \MODES\800,600]
|> "Mode1"="30.0-63.0,55.0-75.0,+,+"
|>
|>
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor\0000
|> \MODES\1024,768]
|> "Mode1"="30.0-63.0,55.0-75.0,+,+"
|>
|>
|> NOTE... "ICMProfile" actually says "EN5400e.icm". Yours hopefully
|> will say "VP930_Series.ICM"; R-Clk it in RegEdit & select "Modify"
|> to see.
|>
|>
|> --
|> 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

Warren · Feb 26, 2008

Re: Trouble with new display and Device Manager

See comments below: $$$

"PCR" <pcrrcp@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

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

> (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.)
> (b) Click the Change button, & the Next button.
> (c) Bolt "Display a list...", & click "Next".
> Does ViewSonic VP930 Series show in the Models box?
> (d) Bolt "Show all hardware".
> Examine the two panes to see what is currently installed.
>
> 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"

>
> | "PCR" <pcrrcp@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
> pcrrcp@netzero.net
>
>

Warren · Feb 27, 2008

Re: Trouble with new display and Device Manager

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 ?

"Warren" <nospam@nospam.com> wrote in message
news:eaekKAPeIHA.4464@TK2MSFTNGP02.phx.gbl...
> See comments below: $$$
>
> "PCR" <pcrrcp@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
>
> > (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
>
> > (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.)
> > (b) Click the Change button, & the Next button.
> > (c) Bolt "Display a list...", & click "Next".
> > Does ViewSonic VP930 Series show in the Models box?
> > (d) Bolt "Show all hardware".
> > Examine the two panes to see what is currently installed.
> >
> > 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"
>
> >
> > | "PCR" <pcrrcp@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
> > pcrrcp@netzero.net
> >
> >
>
>

PCR · Feb 27, 2008

Re: Trouble with new display and Device Manager

Warren wrote:
| Wow!

Alright. Let's try deleting most of this. First, do this again...

HKEY_LOCAL_MACHINE\Enum\MONITOR\DEFAULT_MONITOR

(a) "START button, Run, RegEdit".
(b) Click the plus sign to left of "HKEY_LOCAL_MACHINE".
(c) Click the plus sign left of "Enum".
(d) Click the plus sign left of "MONITOR"
(e) Click "DEFAULT_MONITOR" in the left pane.
(f) Select "Export Registry File" in the "Registry" menu.

Have it create a ".reg" file. It will contain all the information
of the Default Monitor. This can be used to restore it, if the
need may arise.

(g) R-Clk "DEFAULT_MONITOR" in the left pane, & select
to delete it.

(h) Get to this key, & maybe export it...

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor

After you have clicked "Monitor" in the left pane, you will see a
trillion nodes open under it. If "0000" is still one of them & still is
"ViewSonic VP930 Series", then keep that one-- but delete all the
others!

(g) Reboot-- are you rid of the Default Monitor?

You should end up with the following at that Registry key, looking a
lot, lot more like mine...

....snip
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor]
@="Monitors"
"Installer"="SetupX.Dll, Monitor_ClassInstaller"
"Icon"="-1"
"Link"="{4D36E96E-E325-11CE-BFC1-08002BE10318}"

....snip
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor\0000
]
"ICMProfile"=hex:56,50,39,33,30,5f,53,65,72,69,65,73,2e,49,43,4d,00,00
"MaxResolution"="1280,1024"
"DPMS"="1"
"InfPath"="VIEWSO~1.INF"
"InfSection"="VP930_Series.Install"
"ProviderName"="ViewSonic"
"DriverDate"=" 2-16-2008"
"DriverDesc"="ViewSonic VP930 Series"
"MatchingDeviceId"="Monitor\\VSCE41B"

[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor\0000
\MODES]

[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor\0000
\MODES\1280,1024]
"Mode1"="30-82,50-75,+,+"

....snip
| "PCR" <pcrrcp@netzero.net> wrote in message
| news:%23IdnEpodIHA.2448@TK2MSFTNGP03.phx.gbl...
|> Warren wrote:
|> | !!!Please see comments below
|> |
|> | "PCR" <pcrrcp@netzero.net> wrote in message
|> | news:u2ynvpDdIHA.2404@TK2MSFTNGP05.phx.gbl...
|>
|> Continue to work with Brian A. I hesitate to say you should R-Clk
|> your .inf & select "Install". I'm just not sure that monster will
|> itself know you are Win98 istead of the other OS it also will work
|> for. There might be something else the full install process must do
|> first-- I don't know.
|>
|> You owe me a response to a nearby post. Also, I have found another
|> interesting Registry key. Post yours...
|>
|> [HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor]
|> @="Monitors"
|> "Installer"="SetupX.Dll, Monitor_ClassInstaller"
|> "Icon"="-1"
|> "Link"="{4d36e96e-e325-11ce-bfc1-08002be10318}"
|>
|>
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor\0000
|> ]
|> "ICMProfile"=hex:45,4e,35,34,30,30,65,2e,69,63,6d,00,00
|> "MaxResolution"="1024,768"
|> "DPMS"="1"
|> "InfPath"="ENVISI~1.INF"
|> "InfSection"="E564.Install"
|> "ProviderName"="Envision Peripherals, Inc"
|> "DriverDate"=" 8-20-2004"
|> "DriverDesc"="Envision EN5400e"
|> "MatchingDeviceId"="Monitor\\EPIE564"
|>
|>
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor\0000
|> \MODES]
|>
|>
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor\0000
|> \MODES\640,480]
|> "Mode1"="30.0-63.0,55.0-75.0,-,-"
|>
|>
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor\0000
|> \MODES\800,600]
|> "Mode1"="30.0-63.0,55.0-75.0,+,+"
|>
|>
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor\0000
|> \MODES\1024,768]
|> "Mode1"="30.0-63.0,55.0-75.0,+,+"
|>
|>
|> NOTE... "ICMProfile" actually says "EN5400e.icm". Yours hopefully
|> will say "VP930_Series.ICM"; R-Clk it in RegEdit & select "Modify"
|> to see.
|>
|>
|> --
|> 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

Trouble with new display and Device Manager

Warren

Guest

Franc Zabkar

Guest

Warren

Guest

PCR

Guest

Warren

Guest

Warren

Guest

Brian A.

Guest

Warren

Guest

Brian A.

Guest

Franc Zabkar

Guest

PCR

Guest

PCR

Guest

Warren

Guest

Warren

Guest

PCR

Guest

PCR

Guest

PCR

Guest

Warren

Guest

Warren

Guest

PCR

Guest

Similar threads