For PCR, trying to get rid of DEFAULT_MONITOR

March 13, 2008

Re: For PCR, trying to get rid of DEFAULT_MONITOR

PCR wrote:

| Warren wrote:

|| Yes the whole key

||

|

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor\0001

|| is gone and stays away until I remove

|| HKEY_LOCAL_MACHINE\Enum\MONITOR\DEFAULT_MONITOR & reboot.

||

|| In fact every time I remove

|| HKEY_LOCAL_MACHINE\Enum\MONITOR\DEFAULT_MONITOR or

|| HKEY_LOCAL_MACHINE\Enum\MONITOR\VSCE41B the registry in

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

|| starts to bloat with extra monitors. They are easy to clean out,

|| however, and stay away once cleaned out.

|

| Hmm. This was my 2nd-best hope to be rid of your Default Monitor! At

| least the junk that accumulates in that last key can now be

| eliminated. And you really did have a pile of junk in there to start!

| Mine has only the stuff of my EN5400e-- though this is my 3rd monitor

| & I've never deleted stuff in that key! And I've never seen a Default

| Monitor in there!

|

| I'm still thinking, but losing hope.

I have begun an intensive study at...

http://msdn2.microsoft.com/en-us/library/

Here is the first article I've found...

http://msdn2.microsoft.com/en-us/library/aa939135.aspx

But I must go now. Back tomorrow.

....snip

--

Thanks or Good Luck,

There may be humor in this post, and,

Naturally, you will not sue,

Should things get worse after this,

PCR

pcrrcp@netzero.net

March 14, 2008

Re: For PCR, trying to get rid of DEFAULT_MONITOR

The only thing that isn't like yours is that my machine provides the

DEFAULT_MONITOR information in key Phantom\3A, while your's is in

Phantom\key C. As I said before, my key C is occupied by information about

an old and still working hard drive that is not currently installed. I

don't know if there's any difference between using key C or key 3C for

storing this information, as long as it is stored ?

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

news:O5mvBdVhIHA.4740@TK2MSFTNGP05.phx.gbl...

> Warren wrote:

> | Sorry PCR, missed them.

> |

> | Applied the name change from

> | "PCI_VEN_1002&DEV_5961&SUBSYS_280117EE&REV_01_000800_1"

> | to "0001'' to match your registry entries but no effect on

> | Default_Monitor. Still reappears after deleting

> | HKEY_LOCAL_MACHINE\Enum\MONITOR\DEFAULT_MONITOR and rebooting.

>

> OK. Provided you did all three at once to look like mine & rebooted,...

>

> HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\cfgmgr32

> \Phantom\C

> HardWareKey "MONITOR\DEFAULT_MONITOR\0001" <<String value

>

> HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\ASD\Prob\{CF2524C0

> -29AE-11CF-97EA-00AA0034319D}

> MONITOR\DEFAULT_MONITOR\0001 00 <<Binary Value

>

> HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\ASD\Prob\{9B4E7760

> -3196-11CF-97EA-00AA0034319D}

> MONITOR\DEFAULT_MONITOR\0001 00 <<Binary Value

>

> ...that pretty well proves those keys were not responsible.

>

> I wonder, though-- did they change back to the original data on their

> own after you rebooted? If not, let them alone for now -- until we give

> up hope entirely -- because they may be a contributing factor. But, if

> they've gone back to your original data-- fine, let that alone too.

> These keys probably are a dead end.

>

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

> | news:eNZMaGLhIHA.1208@TK2MSFTNGP05.phx.gbl...

> |> Warren wrote:

> |> | I think I also figured out what you meant about modifying

> |> |

> |>

> HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\cfgmgr32\Ph

> |> anto

> |> | m\3A\HardWareKey :

> |> |

> |>

> MONITOR\DEFAULT_MONITOR\PCI_VEN_1002&DEV_5961&SUBSYS_280117EE&REV_01_000

> |> 800_

> |> | 1

> |> |

> |> | It is now the same as yours,

> |> |

> |>

> HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\cfgmgr32\Ph

> |> anto

> |> | m\3A\, HardWareKey, MONITOR\DEFAULT_MONITOR\0001

> |> |

> |> | Unfortunately the change had no effect

> |>

> |> OK, but there were two others...

> |>

> HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\ASD\Prob\{CF2524C0

> |> -29AE-11CF-97EA-00AA0034319D}

> |> MONITOR\DEFAULT_MONITOR\0001 00 <<Binary Value

> |>

> HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\ASD\Prob\{9B4E7760

> |> -3196-11CF-97EA-00AA0034319D}

> |> MONITOR\DEFAULT_MONITOR\0001 00 <<Binary Value

> |>

> |> I must go now. Back tomorrow.

> |>

>

> ...snip

> --

> Thanks or Good Luck,

> There may be humor in this post, and,

> Naturally, you will not sue,

> Should things get worse after this,

> PCR

> pcrrcp@netzero.net

>

March 14, 2008

Re: For PCR, trying to get rid of DEFAULT_MONITOR

See comments below:

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

news:%23UIOKuVhIHA.3788@TK2MSFTNGP04.phx.gbl...

> Warren wrote:

> | Well the CompableIDs line in

> |

> HKEY_LOCAL_MACHINE\Enum\MONITOR\VSCE41B\PCI_VEN_1002&DEV_5961&SUBSYS_28

> |> 0117EE&REV_01_000800 stays away when you delete it & reboot but the

> | Default_Monitor still comes back after it is removed and the computer

> | rebooted.

>

> Interesting. I was really leaning to that as the cause. Hmm. Suddenly I

> begin to get a feeling of frustration & ultimate failure. I wonder--

>

> (1) Is "CompableIDs" mentioned in any .inf...?...

>

> (a) "START button, Find, F/F"

> (b) Leave "Named" empty.

> © In "Containing text", enter... "CompableIDs".

> (d) In "Look in", browse to........ "C:\WINDOWS\INF".

Nothing shows up

> Open the .inf file (if any shows up) in Notepad, & post it. None of mine

> have that term. Probably, none of yours have it, either, though, or the

> term would have come back on its own.

>

> (2) Does "CompatibleIDs" or "*PNP09FF" show up in EDID...?...

>

> (a) Open RegEdit, get to & click...

>

> HKEY_LOCAL_MACHINE\Enum\MONITOR\VSCE41B\PCI_VEN_1002&DEV_5961&SUBSYS_28

> 0117EE&REV_01_000800

>

> © R-Clk "EDID" in the R-Pane, & select Modify.

> Do not click Delete-- click Modify.

>

> (d) Examine the requestor that opens. Do you see

> "CompatibleIDs" or "*PNP09FF" anywhere in there?

>

> © CANCEL the requestor, & close RegEdit.

No it is not present

> I'm trying to discover where that line is coming from, though it seems

> it doesn't matter. Still, if you haven't done so already, do not put the

> "CompableIDs" line back into your Registry-- at least not until we give

> up all hope, as it may be a contributing factor. If you've already put

> it back, let it be.

>

> I'm still thinking, (but losing hope. Those excuses of MEB & Zabcar &

> glee & Terhune for why this is doomed to failure begins to make sense).

You certainly do a lot of thinking and I appreciate your efforts. It sure

seems that the Default_Monitor has to be there but why is still a question

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

> | news:uzaNPgKhIHA.4152@TK2MSFTNGP02.phx.gbl...

> |> Warren wrote:

> |> | I forgot to mention that PNP09FF shows up nowhere else in my

> |> | Registry

> |>

> |> Hmm, (just like mine). NOW, I'm looking inside Monitor.inf mentioned

> |> in your...

> |>

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

> |>

> |> ..., & I detect a connection to *PNP09FF...

> |>

> |> .....Quote Monitor.inf............

> |> [Generic]

> |> %Unknown.DeviceDesc%=Unknown.Install,Monitor\Default_Monitor ; for

> |> auto-install

> |> %Unknown.DeviceDesc%=Unknown.Install ; for pick list

> |> %*PNP09FF.DeviceDesc%=VESADDC.Install,*PNP09FF

> |> .....EOQ Monitor.inf..............

> |>

> |> It looks like they are strongly connected! Therefore, it could

> |> indeed be that line...

> |>

> |> "CompatibleIDs"="*PNP09FF"

> |>

> |> ...of your...

> |>

> [HKEY_LOCAL_MACHINE\Enum\MONITOR\VSCE41B\PCI_VEN_1002&DEV_5961&SUBSYS_28

> |> 0117EE&REV_01_000800]

> |> "Capabilities"=hex:14,00,00,00

> |> "InitMonitorPowerState"="0f"

> |> ...snip of EDID, but it looked fine...

> |> "HardwareID"="MONITOR\\VSCE41B"

> |> "CompatibleIDs"="*PNP09FF"

> |> "Class"="Monitor"

> |> "SerialNum"="Q8H062001250"

> |> "DeviceDesc"="ViewSonic VP930 Series"

> |> "FriendlyName"="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

> |>

> |> ...that may be causing the Default Monitor to generate. If so, it

> |> may be best to let it be-- there may be a reason for it! (Can it be

> |> your is right & mine is wrong? But yours was such a mess!) Note that

> |> Zabcar has definitively proven that certain new Intel chips may

> |> cause a monitor to enumerate twice...

> |> ftp://download.intel.com/design/chipsets/applnots/30969401.pdf

> |> Mine is an AMD chip.

> |>

> |> I'm not sure where that "CompatibleIDs" line is coming from in your

> |> ENUM key. If you delete it & reboot, it may well come back on its

> |> own. No part of the line is mentioned in your VS080114_I19.inf.

> |>

> |> (a) Decide whether you want to pursue this.

> |> (I really se no big problem with Default_Monitor;

> |> although I don't have one, it is mentioned in 3

> |> of my Registry keys & in my Monitor.inf.)

> |>

> |> (b) If so, open RegEdit, get to & click...

> |>

> HKEY_LOCAL_MACHINE\Enum\MONITOR\VSCE41B\PCI_VEN_1002&DEV_5961&SUBSYS_28

> |> 0117EE&REV_01_000800

> |>

> |> © R-Clk "CompatibleIDs" in the R-Pane, & select delete.

> |> (Maybe use the Edit menu to export that key first.)

> |>

> |> Close up, & reboot-- did it go away?

> |> I see your other response & will get to it shortly.

> |>

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

> |> | news:O4qJ1R$gIHA.748@TK2MSFTNGP04.phx.gbl...

> |> |> This is probably a replay of the last removal exercise. You've

> |> |> got all the right moves, but it matters more in what order they

> |> |> are performed. Will printout your sugestions and think about

> |> |> various ways of performing the same operations until I come up

> |> |> with a winner, or not.

> |> |>

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

> |> |> news:eLhiGz%23gIHA.4196@TK2MSFTNGP04.phx.gbl...

> |> |> > I've been studying this at least an hour now. Here are

> |> |> > preliminary thoughts...

>

> --

> Thanks or Good Luck,

> There may be humor in this post, and,

> Naturally, you will not sue,

> Should things get worse after this,

> PCR

> pcrrcp@netzero.net

>

March 14, 2008

Re: For PCR, trying to get rid of DEFAULT_MONITOR

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

news:%23UIOKuVhIHA.3788@TK2MSFTNGP04.phx.gbl...

| Warren wrote:

| | Well the CompableIDs line in

| |

| HKEY_LOCAL_MACHINE\Enum\MONITOR\VSCE41B\PCI_VEN_1002&DEV_5961&SUBSYS_28

| |> 0117EE&REV_01_000800 stays away when you delete it & reboot but the

| | Default_Monitor still comes back after it is removed and the computer

| | rebooted.

|

| Interesting. I was really leaning to that as the cause. Hmm. Suddenly I

| begin to get a feeling of frustration & ultimate failure. I wonder--

|

| (1) Is "CompableIDs" mentioned in any .inf...?...

|

| (a) "START button, Find, F/F"

| (b) Leave "Named" empty.

| © In "Containing text", enter... "CompableIDs".

| (d) In "Look in", browse to........ "C:\WINDOWS\INF".

|

| Open the .inf file (if any shows up) in Notepad, & post it. None of mine

| have that term. Probably, none of yours have it, either, though, or the

| term would have come back on its own.

|

| (2) Does "CompatibleIDs" or "*PNP09FF" show up in EDID...?...

|

| (a) Open RegEdit, get to & click...

|

| HKEY_LOCAL_MACHINE\Enum\MONITOR\VSCE41B\PCI_VEN_1002&DEV_5961&SUBSYS_28

| 0117EE&REV_01_000800

|

| © R-Clk "EDID" in the R-Pane, & select Modify.

| Do not click Delete-- click Modify.

|

| (d) Examine the requestor that opens. Do you see

| "CompatibleIDs" or "*PNP09FF" anywhere in there?

|

| © CANCEL the requestor, & close RegEdit.

|

| I'm trying to discover where that line is coming from, though it seems

| it doesn't matter. Still, if you haven't done so already, do not put the

| "CompableIDs" line back into your Registry-- at least not until we give

| up all hope, as it may be a contributing factor. If you've already put

| it back, let it be.

|

| I'm still thinking, (but losing hope. Those excuses of MEB & Zabcar &

| glee & Terhune for why this is doomed to failure begins to make sense).

Those weren't excuses, but attempts to explain the physical/chip related

aspects. For XP and VISTA these are crutial to the original setup in those

environments.

IF you intend to try to over-ride this in 9X then you MUST disable PnP/auto

detection in the system AND if possible, the video adaptor, AND ensure the

INF does not contain any references to a default, OR that it REPLACES the

default [original video driver], OR that it isn't added BY the driver itself

once it is installed and first rebooted.

NOTE though, that the video device must have the ALL the OLD 9X

installation and system/registry settings in its installation routine, as if

it was NOT PnP [9X term - XP/Vista uses different routines in its HAL and

other]..

--

MEB

http://peoplescounsel.orgfree.com

_________

March 15, 2008

Re: For PCR, trying to get rid of DEFAULT_MONITOR

Warren wrote:

| See comments below:

|

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

| news:%23UIOKuVhIHA.3788@TK2MSFTNGP04.phx.gbl...

|> Warren wrote:

|> | Well the CompableIDs line in

|> |

|>

HKEY_LOCAL_MACHINE\Enum\MONITOR\VSCE41B\PCI_VEN_1002&DEV_5961&SUBSYS_28

|> |> 0117EE&REV_01_000800 stays away when you delete it & reboot but

|> |> the

|> | Default_Monitor still comes back after it is removed and the

|> | computer rebooted.

|>

|> Interesting. I was really leaning to that as the cause. Hmm.

|> Suddenly I begin to get a feeling of frustration & ultimate failure.

|> I wonder--

|>

|> (1) Is "CompableIDs" mentioned in any .inf...?...

|>

....snip

| Nothing shows up

Alright. I thought it might not.

....snip

|> (2) Does "CompatibleIDs" or "*PNP09FF" show up in EDID...?...

....snip

| No it is not present

Alright. Maybe there'll be something about it at the MS Library.

....snip

|> I'm still thinking, (but losing hope. Those excuses of MEB & Zabcar &

|> glee & Terhune for why this is doomed to failure begins to make

|> sense).

|

| You certainly do a lot of thinking and I appreciate your efforts. It

| sure seems that the Default_Monitor has to be there but why is still

| a question

The first & only article I've read so far at the MS Library mentions

Win95...

http://msdn2.microsoft.com/en-us/library/aa939135.aspx

......Quote.................

Default Monitor

The Default Monitor component provides support for a generic monitor

device. This component supplies the monitor.inf file, which is a

system-supplied INF (information) file for a generic monitor. The

monitor.inf file is associated with Windows 95.

Services

There are no services associated with this component.

Associated Components

No other components interact with this component.

Settings

There are no configurable settings for this component.

......EOQ...................

Is your machine an upgrade from Win95?

....snip

--

Thanks or Good Luck,

There may be humor in this post, and,

Naturally, you will not sue,

Should things get worse after this,

PCR

pcrrcp@netzero.net

March 15, 2008

Re: For PCR, trying to get rid of DEFAULT_MONITOR

Warren wrote:

| The only thing that isn't like yours is that my machine provides the

| DEFAULT_MONITOR information in key Phantom\3A, while your's is in

| Phantom\key C. As I said before, my key C is occupied by information

| about an old and still working hard drive that is not currently

| installed. I don't know if there's any difference between using key

| C or key 3C for storing this information, as long as it is stored ?

Alright. That sounds like an irrelevant configuration difference. It was

good that you spotted the key difference (I never did) & altered the

right one.

Sounds like this was a dead end, & you may as well change all 3 keys

back, if you haven't already done so. And also (I guess) return that

CompatibleIDs line to your Registry...

HKEY_LOCAL_MACHINE\Enum\MONITOR\VSCE41B\

PCI_VEN_1002&DEV_5961&SUBSYS_280117EE&REV_01_000800

CompatibleIDs *PNP09FF <<String value

That one was so promising, though!

I'm going to read MEBs post thrice & spend time at the MS Library...

http://msdn2.microsoft.com/en-us/library/

...., before giving up the ghost, though.

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

| news:O5mvBdVhIHA.4740@TK2MSFTNGP05.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

March 15, 2008

Re: For PCR, trying to get rid of DEFAULT_MONITOR

MEB wrote:

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

| news:%23UIOKuVhIHA.3788@TK2MSFTNGP04.phx.gbl...

|| Warren wrote:

|| | Well the CompableIDs line in

|| |

||

HKEY_LOCAL_MACHINE\Enum\MONITOR\VSCE41B\PCI_VEN_1002&DEV_5961&SUBSYS_28

|| |> 0117EE&REV_01_000800 stays away when you delete it & reboot but

|| |> the

|| | Default_Monitor still comes back after it is removed and the

|| | computer rebooted.

||

|| Interesting. I was really leaning to that as the cause. Hmm.

|| Suddenly I begin to get a feeling of frustration & ultimate failure.

....snip

||

|| I'm still thinking, (but losing hope. Those excuses of MEB & Zabcar &

|| glee & Terhune for why this is doomed to failure begins to make

|| sense).

|

| Those weren't excuses, but attempts to explain the physical/chip

| related aspects. For XP and VISTA these are crutial to the original

| setup in those environments.

I couldn't spell explication-- that's why I said excuses! No reason to

throw XP/Vista irradiation at me-- & just when my tinfoil hat fell off!

| IF you intend to try to over-ride this in 9X then you MUST disable

| PnP/auto detection in the system AND if possible, the video adaptor,

| AND ensure the INF does not contain any references to a default, OR

| that it REPLACES the default [original video driver], OR that it

| isn't added BY the driver itself once it is installed and first

| rebooted. NOTE though, that the video device must have the ALL the

| OLD 9X installation and system/registry settings in its installation

| routine, as if it was NOT PnP [9X term - XP/Vista uses different

| routines in its HAL and other]..

That seems like a little too much to do! I'm at the MS Library, &, if I

can't find something simpler, I'll resort to one of your explications.

What do you make of this...?...

http://msdn2.microsoft.com/en-us/library/aa939135.aspx

......Quote.................

Default Monitor

The Default Monitor component provides support for a generic monitor

device. This component supplies the monitor.inf file, which is a

system-supplied INF (information) file for a generic monitor. The

monitor.inf file is associated with Windows 95.

Services

There are no services associated with this component.

Associated Components

No other components interact with this component.

Settings

There are no configurable settings for this component.

......EOQ...................

| --

| MEB

| http://peoplescounsel.orgfree.com

| _________

--

Thanks or Good Luck,

There may be humor in this post, and,

Naturally, you will not sue,

Should things get worse after this,

PCR

pcrrcp@netzero.net

March 15, 2008

Re: For PCR, trying to get rid of DEFAULT_MONITOR

No it was a fresh install of Winows 98SE

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

news:uAYn$mjhIHA.4740@TK2MSFTNGP05.phx.gbl...

> Warren wrote:

> | See comments below:

> |

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

> | news:%23UIOKuVhIHA.3788@TK2MSFTNGP04.phx.gbl...

> |> Warren wrote:

> |> | Well the CompableIDs line in

> |> |

> |>

> HKEY_LOCAL_MACHINE\Enum\MONITOR\VSCE41B\PCI_VEN_1002&DEV_5961&SUBSYS_28

> |> |> 0117EE&REV_01_000800 stays away when you delete it & reboot but

> |> |> the

> |> | Default_Monitor still comes back after it is removed and the

> |> | computer rebooted.

> |>

> |> Interesting. I was really leaning to that as the cause. Hmm.

> |> Suddenly I begin to get a feeling of frustration & ultimate failure.

> |> I wonder--

> |>

> |> (1) Is "CompableIDs" mentioned in any .inf...?...

> |>

>

> ...snip

> | Nothing shows up

>

> Alright. I thought it might not.

>

> ...snip

> |> (2) Does "CompatibleIDs" or "*PNP09FF" show up in EDID...?...

>

> ...snip

> | No it is not present

>

> Alright. Maybe there'll be something about it at the MS Library.

>

> ...snip

> |> I'm still thinking, (but losing hope. Those excuses of MEB & Zabcar &

> |> glee & Terhune for why this is doomed to failure begins to make

> |> sense).

> |

> | You certainly do a lot of thinking and I appreciate your efforts. It

> | sure seems that the Default_Monitor has to be there but why is still

> | a question

>

> The first & only article I've read so far at the MS Library mentions

> Win95...

> http://msdn2.microsoft.com/en-us/library/aa939135.aspx

> .....Quote.................

> Default Monitor

>

> The Default Monitor component provides support for a generic monitor

> device. This component supplies the monitor.inf file, which is a

> system-supplied INF (information) file for a generic monitor. The

> monitor.inf file is associated with Windows 95.

>

> Services

> There are no services associated with this component.

>

> Associated Components

> No other components interact with this component.

>

> Settings

> There are no configurable settings for this component.

> .....EOQ...................

>

> Is your machine an upgrade from Win95?

>

> ...snip

> --

> Thanks or Good Luck,

> There may be humor in this post, and,

> Naturally, you will not sue,

> Should things get worse after this,

> PCR

> pcrrcp@netzero.net

>

March 15, 2008

Re: For PCR, trying to get rid of DEFAULT_MONITOR

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

news:ORjn80jhIHA.6092@TK2MSFTNGP06.phx.gbl...

| MEB wrote:

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

| | news:%23UIOKuVhIHA.3788@TK2MSFTNGP04.phx.gbl...

| || Warren wrote:

| || | Well the CompableIDs line in

| || |

| ||

| HKEY_LOCAL_MACHINE\Enum\MONITOR\VSCE41B\PCI_VEN_1002&DEV_5961&SUBSYS_28

| || |> 0117EE&REV_01_000800 stays away when you delete it & reboot but

| || |> the

| || | Default_Monitor still comes back after it is removed and the

| || | computer rebooted.

| ||

| || Interesting. I was really leaning to that as the cause. Hmm.

| || Suddenly I begin to get a feeling of frustration & ultimate failure.

|

| ...snip

| ||

| || I'm still thinking, (but losing hope. Those excuses of MEB & Zabcar &

| || glee & Terhune for why this is doomed to failure begins to make

| || sense).

| |

| | Those weren't excuses, but attempts to explain the physical/chip

| | related aspects. For XP and VISTA these are crutial to the original

| | setup in those environments.

|

| I couldn't spell explication-- that's why I said excuses! No reason to

| throw XP/Vista irradiation at me-- & just when my tinfoil hat fell off!

|

| | IF you intend to try to over-ride this in 9X then you MUST disable

| | PnP/auto detection in the system AND if possible, the video adaptor,

| | AND ensure the INF does not contain any references to a default, OR

| | that it REPLACES the default [original video driver], OR that it

| | isn't added BY the driver itself once it is installed and first

| | rebooted. NOTE though, that the video device must have the ALL the

| | OLD 9X installation and system/registry settings in its installation

| | routine, as if it was NOT PnP [9X term - XP/Vista uses different

| | routines in its HAL and other]..

|

| That seems like a little too much to do! I'm at the MS Library, &, if I

| can't find something simpler, I'll resort to one of your explications.

| What do you make of this...?...

|

| http://msdn2.microsoft.com/en-us/library/aa939135.aspx

| .....Quote.................

| Default Monitor

|

| The Default Monitor component provides support for a generic monitor

| device. This component supplies the monitor.inf file, which is a

| system-supplied INF (information) file for a generic monitor. The

| monitor.inf file is associated with Windows 95.

|

| Services

| There are no services associated with this component.

|

| Associated Components

| No other components interact with this component.

|

| Settings

| There are no configurable settings for this component.

| .....EOQ...................

|

Okay, you found the XPSR2 file to briefly explain why a default was

included..

As I see it:

Well, let me put that on my own website [rather than letting someone else

re-write it and put it on their site].

http://peoplescounsel.orgfree.com/ref/gen/windows/default_monitor.htm

- Windows Default Monitor in the registry and Device Manager

The short is, its the chips baby, its all in the chips...

|

| | MEB

| | _________

| PCR

|

--

MEB

http://peoplescounsel.orgfree.com

_________

March 16, 2008

Re: For PCR, trying to get rid of DEFAULT_MONITOR

Warren wrote:

| No it was a fresh install of Winows 98SE

Alright. Then, it isn't that; I thought maybe Win95 was responsible.

I'm beginning to think... maybe... depending on what monitor is attached

when Windows first boots with a new monitor... Windows will install the

Default Monitor, if it doesn't find another possibility in Monitor.inf.

(I might have always been lucky that my three were in there. Anyhow, I

can't recall I ever had a Default Monitor showing. I DID do a Registry

delete last time -- probably from the ENUM key -- but I THINK it might

have the prior monitor that I deleted.) After you did install the right

one to go with your ViewSonic VP930 Series monitor, for some reason it

is impossible to be rid of the Default Monitor-- even with a Registry

delete!

HOWEVER... I haven't done scouring that MS Library. But I must go-- no

time today. I've still only read that one article.

Did you get your Registry back to what it was?

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

| news:uAYn$mjhIHA.4740@TK2MSFTNGP05.phx.gbl...

|> Warren wrote:

|> | See comments below:

|> |

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

|> | news:%23UIOKuVhIHA.3788@TK2MSFTNGP04.phx.gbl...

|> |> Warren wrote:

|> |> | Well the CompableIDs line in

|> |> |

|> |>

|>

HKEY_LOCAL_MACHINE\Enum\MONITOR\VSCE41B\PCI_VEN_1002&DEV_5961&SUBSYS_28

|> |> |> 0117EE&REV_01_000800 stays away when you delete it & reboot but

|> |> |> the

|> |> | Default_Monitor still comes back after it is removed and the

|> |> | computer rebooted.

|> |>

|> |> Interesting. I was really leaning to that as the cause. Hmm.

|> |> Suddenly I begin to get a feeling of frustration & ultimate

|> |> failure. I wonder--

|> |>

|> |> (1) Is "CompableIDs" mentioned in any .inf...?...

|> |>

|>

|> ...snip

|> | Nothing shows up

|>

|> Alright. I thought it might not.

|>

|> ...snip

|> |> (2) Does "CompatibleIDs" or "*PNP09FF" show up in EDID...?...

|>

|> ...snip

|> | No it is not present

|>

|> Alright. Maybe there'll be something about it at the MS Library.

|>

|> ...snip

|> |> I'm still thinking, (but losing hope. Those excuses of MEB &

|> |> Zabcar & glee & Terhune for why this is doomed to failure begins

|> |> to make sense).

|> |

|> | You certainly do a lot of thinking and I appreciate your efforts.

|> | It sure seems that the Default_Monitor has to be there but why is

|> | still a question

|>

|> The first & only article I've read so far at the MS Library mentions

|> Win95...

|> http://msdn2.microsoft.com/en-us/library/aa939135.aspx

|> .....Quote.................

|> Default Monitor

|>

|> The Default Monitor component provides support for a generic monitor

|> device. This component supplies the monitor.inf file, which is a

|> system-supplied INF (information) file for a generic monitor. The

|> monitor.inf file is associated with Windows 95.

|>

|> Services

|> There are no services associated with this component.

|>

|> Associated Components

|> No other components interact with this component.

|>

|> Settings

|> There are no configurable settings for this component.

|> .....EOQ...................

|>

|> Is your machine an upgrade from Win95?

|>

|> ...snip

|> --

|> Thanks or Good Luck,

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

|> Naturally, you will not sue,

|> Should things get worse after this,

|> PCR

|> pcrrcp@netzero.net

--

Thanks or Good Luck,

There may be humor in this post, and,

Naturally, you will not sue,

Should things get worse after this,

PCR

pcrrcp@netzero.net

March 16, 2008

Re: For PCR, trying to get rid of DEFAULT_MONITOR

MEB wrote:

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

| news:ORjn80jhIHA.6092@TK2MSFTNGP06.phx.gbl...

|| MEB wrote:

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

|| | news:%23UIOKuVhIHA.3788@TK2MSFTNGP04.phx.gbl...

....snip

|| That seems like a little too much to do! I'm at the MS Library, &,

|| if I can't find something simpler, I'll resort to one of your

|| explications. What do you make of this...?...

||

|| http://msdn2.microsoft.com/en-us/library/aa939135.aspx

|| .....Quote.................

|| Default Monitor

||

|| The Default Monitor component provides support for a generic monitor

|| device. This component supplies the monitor.inf file, which is a

|| system-supplied INF (information) file for a generic monitor. The

|| monitor.inf file is associated with Windows 95.

||

|| Services

|| There are no services associated with this component.

||

|| Associated Components

|| No other components interact with this component.

||

|| Settings

|| There are no configurable settings for this component.

|| .....EOQ...................

||

|

| Okay, you found the XPSR2 file to briefly explain why a default was

| included..

|

| As I see it:

|

| Well, let me put that on my own website [rather than letting someone

| else re-write it and put it on their site].

| http://peoplescounsel.orgfree.com/ref/gen/windows/default_monitor.htm

| - Windows Default Monitor in the registry and Device Manager

|

| The short is, its the chips baby, its all in the chips...

Because you've trebled the size of your explication, it will take longer

to read it thrice. I also want to scour that MS Library-- & I haven't

got the time tonight! Will get back to this tomorrow.

||

|| | MEB

|| | _________

|| PCR

||

| --

|

| MEB

| http://peoplescounsel.orgfree.com

| _________

--

Thanks or Good Luck,

There may be humor in this post, and,

Naturally, you will not sue,

Should things get worse after this,

PCR

pcrrcp@netzero.net

March 16, 2008

Re: For PCR, trying to get rid of DEFAULT_MONITOR

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

news:%23HA86uxhIHA.1944@TK2MSFTNGP02.phx.gbl...

| MEB wrote:

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

| | news:ORjn80jhIHA.6092@TK2MSFTNGP06.phx.gbl...

| || MEB wrote:

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

| || | news:%23UIOKuVhIHA.3788@TK2MSFTNGP04.phx.gbl...

|

| ...snip

| || That seems like a little too much to do! I'm at the MS Library, &,

| || if I can't find something simpler, I'll resort to one of your

| || explications. What do you make of this...?...

| ||

| || http://msdn2.microsoft.com/en-us/library/aa939135.aspx

| || .....Quote.................

| || Default Monitor

| ||

| || The Default Monitor component provides support for a generic monitor

| || device. This component supplies the monitor.inf file, which is a

| || system-supplied INF (information) file for a generic monitor. The

| || monitor.inf file is associated with Windows 95.

| ||

| || Services

| || There are no services associated with this component.

| ||

| || Associated Components

| || No other components interact with this component.

| ||

| || Settings

| || There are no configurable settings for this component.

| || .....EOQ...................

| ||

| |

| | Okay, you found the XPSR2 file to briefly explain why a default was

| | included..

| |

| | As I see it:

| |

| | Well, let me put that on my own website [rather than letting someone

| | else re-write it and put it on their site].

| | http://peoplescounsel.orgfree.com/ref/gen/windows/default_monitor.htm

| | - Windows Default Monitor in the registry and Device Manager

| |

| | The short is, its the chips baby, its all in the chips...

|

| Because you've trebled the size of your explication, it will take longer

| to read it thrice. I also want to scour that MS Library-- & I haven't

| got the time tonight! Will get back to this tomorrow.

Actually, I just collected the presentations from this thread, and a small

part from what I put into another monitor/adapter discussion.

Anyway, will see hat you come up with...

|

| ||

| || | MEB

| || PCR

| | MEB

| | _________

| PCR

--

MEB

http://peoplescounsel.orgfree.com

_________

March 17, 2008

Re: For PCR, trying to get rid of DEFAULT_MONITOR

MEB wrote:

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

| news:%23HA86uxhIHA.1944@TK2MSFTNGP02.phx.gbl...

|| MEB wrote:

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

|| | news:ORjn80jhIHA.6092@TK2MSFTNGP06.phx.gbl...

|| || MEB wrote:

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

|| || | news:%23UIOKuVhIHA.3788@TK2MSFTNGP04.phx.gbl...

||

|| ...snip

|| || That seems like a little too much to do! I'm at the MS Library, &,

|| || if I can't find something simpler, I'll resort to one of your

|| || explications. What do you make of this...?...

|| ||

|| || http://msdn2.microsoft.com/en-us/library/aa939135.aspx

|| || .....Quote.................

|| || Default Monitor

|| ||

|| || The Default Monitor component provides support for a generic

|| || monitor device. This component supplies the monitor.inf file,

|| || which is a system-supplied INF (information) file for a generic

|| || monitor. The monitor.inf file is associated with Windows 95.

|| ||

|| || Services

|| || There are no services associated with this component.

|| ||

|| || Associated Components

|| || No other components interact with this component.

|| ||

|| || Settings

|| || There are no configurable settings for this component.

|| || .....EOQ...................

|| ||

|| |

|| | Okay, you found the XPSR2 file to briefly explain why a default

|| | was included..

|| |

|| | As I see it:

|| |

|| | Well, let me put that on my own website [rather than letting

|| | someone else re-write it and put it on their site].

|| |

http://peoplescounsel.orgfree.com/ref/gen/windows/default_monitor.htm

|| | - Windows Default Monitor in the registry and Device Manager

|| |

|| | The short is, its the chips baby, its all in the chips...

||

|| Because you've trebled the size of your explication, it will take

|| longer to read it thrice. I also want to scour that MS Library-- & I

|| haven't got the time tonight! Will get back to this tomorrow.

|

| Actually, I just collected the presentations from this thread, and a

| small part from what I put into another monitor/adapter discussion.

| Anyway, will see hat you come up with...

OK. And I continue to promise it is coming... but again I've run out of

time. (I did post to Lee in the other thread.) I'll get back tomorrow.

My first few additional clicks at the MS Library came up empty-- but I

remain guardedly hopeful. As I posted to Lee, here are the lines in

Warren's VS080114_I19.inf that mention the VP930...

[DestinationDirs]

VP930_Series.CopyFiles=23

[sourceDisksFiles]

VP930_Series.ICM=1

[ViewSonic]

%VP930_Series%=VP930_Series.Install,Monitor\VSCE41B ;VP930_Series

[ViewSonic.NTia64]

%VP930_Series%=VP930_Series.Install,Monitor\VSCE41B ;VP930_Series

[ViewSonic.NTamd64]

%VP930_Series%=VP930_Series.Install,Monitor\VSCE41B ;VP930_Series

[VP930_Series.Install] ;VP930_Series

DelReg=DEL_CURRENT_REG

AddReg=VP930_Series.AddReg,1280,DPMS

Copyfiles=VP930_Series.CopyFiles

[VP930_Series.AddReg] ;VP930_Series

HKR,"MODES\1280,1024",Mode1,,"30-82,50-75,+,+"

HKR,,ICMProfile,0,"VP930_Series.ICM"

[VP930_Series.CopyFiles]

VP930_Series.ICM

[strings]

VP930_Series="ViewSonic VP930 Series"

Also, that Default_Monitor is not mentioned in his .inf. It is mentioned

in Monitor.inf that we all have. I show only the lines that mention

it (but I must go)...

[sysCfgClasses]

Monitor, %Unknown.DeviceDesc%,MONITOR,4,%MonitorClassName% ; Default

to "Unknown Monitor"

; Monitors to hide from pick list

;-------------------------------------------------

[ControlFlags]

ExcludeFromSelect=Monitor\Default_Monitor

[Generic]

%Unknown.DeviceDesc%=Unknown.Install,Monitor\Default_Monitor ; for

auto-install

%Unknown.DeviceDesc%=Unknown.Install ; for pick list

%*PNP09FF.DeviceDesc%=VESADDC.Install,*PNP09FF

[strings]

MonitorClassName="Monitors"

MS="Microsoft"

Generic="(Standard monitor types)"

Unknown.DeviceDesc="Default Monitor"

*PNP09FF.DeviceDesc = "Plug and Play Monitor"

||

|| ||

|| || | MEB

|| || PCR

|| | MEB

|| | _________

|| PCR

| --

|

| MEB

| http://peoplescounsel.orgfree.com

| _________

--

Thanks or Good Luck,

There may be humor in this post, and,

Naturally, you will not sue,

Should things get worse after this,

PCR

pcrrcp@netzero.net

March 17, 2008

Re: For PCR, trying to get rid of DEFAULT_MONITOR

[Generic]

%Unknown.DeviceDesc%=Unknown.Install,Monitor\Default_Monitor ; for

auto-install

%Unknown.DeviceDesc%=Unknown.Install ; for pick list

%*PNP09FF.DeviceDesc%=VESADDC.Install,*PNP09FF

*VESADDC*?

http://pinouts.ru/Video/VGAVesaDdc_pinout.shtml

http://www.laptopvideo2go.com/forum/index.php?act=attach&type=post&id=1820 -

note the multiple default monitors

For the NT users, a tool to dig out information:

http://www.laptopvideo2go.com/forum/index.php?showtopic=756&mode=threaded

| AddReg=VP930_Series.AddReg,1280,DPMS

http://webpages.charter.net/dperr/dpms.htm

http://www.versiontracker.com/dyn/moreinfo/win/37027

Did you ask him to use the DDC test tool I posted?

IF its talkin, we be walkin...

* MEB

http://peoplescounsel.orgfree.com

--

_________

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

news:ueXIxj9hIHA.944@TK2MSFTNGP05.phx.gbl...

| MEB wrote:

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

| | news:%23HA86uxhIHA.1944@TK2MSFTNGP02.phx.gbl...

| || MEB wrote:

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

| || | news:ORjn80jhIHA.6092@TK2MSFTNGP06.phx.gbl...

| || || MEB wrote:

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

| || || | news:%23UIOKuVhIHA.3788@TK2MSFTNGP04.phx.gbl...

| ||

| || ...snip

| || || That seems like a little too much to do! I'm at the MS Library, &,

| || || if I can't find something simpler, I'll resort to one of your

| || || explications. What do you make of this...?...

| || ||

| || || http://msdn2.microsoft.com/en-us/library/aa939135.aspx

| || || .....Quote.................

| || || Default Monitor

| || ||

| || || The Default Monitor component provides support for a generic

| || || monitor device. This component supplies the monitor.inf file,

| || || which is a system-supplied INF (information) file for a generic

| || || monitor. The monitor.inf file is associated with Windows 95.

| || ||

| || || Services

| || || There are no services associated with this component.

| || ||

| || || Associated Components

| || || No other components interact with this component.

| || ||

| || || Settings

| || || There are no configurable settings for this component.

| || || .....EOQ...................

| || ||

| || |

| || | Okay, you found the XPSR2 file to briefly explain why a default

| || | was included..

| || |

| || | As I see it:

| || |

| || | Well, let me put that on my own website [rather than letting

| || | someone else re-write it and put it on their site].

| || |

| http://peoplescounsel.orgfree.com/ref/gen/windows/default_monitor.htm

| || | - Windows Default Monitor in the registry and Device Manager

| || |

| || | The short is, its the chips baby, its all in the chips...

| ||

| || Because you've trebled the size of your explication, it will take

| || longer to read it thrice. I also want to scour that MS Library-- & I

| || haven't got the time tonight! Will get back to this tomorrow.

| |

| | Actually, I just collected the presentations from this thread, and a

| | small part from what I put into another monitor/adapter discussion.

| | Anyway, will see hat you come up with...

|

| OK. And I continue to promise it is coming... but again I've run out of

| time. (I did post to Lee in the other thread.) I'll get back tomorrow.

| My first few additional clicks at the MS Library came up empty-- but I

| remain guardedly hopeful. As I posted to Lee, here are the lines in

| Warren's VS080114_I19.inf that mention the VP930...

|

| [DestinationDirs]

| VP930_Series.CopyFiles=23

|

| [sourceDisksFiles]

| VP930_Series.ICM=1

|

| [ViewSonic]

| %VP930_Series%=VP930_Series.Install,Monitor\VSCE41B ;VP930_Series

|

| [ViewSonic.NTia64]

| %VP930_Series%=VP930_Series.Install,Monitor\VSCE41B ;VP930_Series

|

| [ViewSonic.NTamd64]

| %VP930_Series%=VP930_Series.Install,Monitor\VSCE41B ;VP930_Series

|

| [VP930_Series.Install] ;VP930_Series

| DelReg=DEL_CURRENT_REG

| AddReg=VP930_Series.AddReg,1280,DPMS

| Copyfiles=VP930_Series.CopyFiles

|

| [VP930_Series.AddReg] ;VP930_Series

| HKR,"MODES\1280,1024",Mode1,,"30-82,50-75,+,+"

| HKR,,ICMProfile,0,"VP930_Series.ICM"

|

| [VP930_Series.CopyFiles]

| VP930_Series.ICM

|

| [strings]

| VP930_Series="ViewSonic VP930 Series"

|

| Also, that Default_Monitor is not mentioned in his .inf. It is mentioned

| in Monitor.inf that we all have. I show only the lines that mention

| it (but I must go)...

|

| [sysCfgClasses]

| Monitor, %Unknown.DeviceDesc%,MONITOR,4,%MonitorClassName% ; Default

| to "Unknown Monitor"

|

| ; Monitors to hide from pick list

| ;-------------------------------------------------

| [ControlFlags]

| ExcludeFromSelect=Monitor\Default_Monitor

|

| [Generic]

| %Unknown.DeviceDesc%=Unknown.Install,Monitor\Default_Monitor ; for

| auto-install

| %Unknown.DeviceDesc%=Unknown.Install ; for pick list

| %*PNP09FF.DeviceDesc%=VESADDC.Install,*PNP09FF

|

| [strings]

| MonitorClassName="Monitors"

| MS="Microsoft"

|

| Generic="(Standard monitor types)"

| Unknown.DeviceDesc="Default Monitor"

|

| *PNP09FF.DeviceDesc = "Plug and Play Monitor"

|

| ||

| || ||

| || || | MEB

| || || PCR

| || | MEB

| || | _________

| || PCR

| | --

| |

| | MEB

| | http://peoplescounsel.orgfree.com

| | _________

|

| --

| Thanks or Good Luck,

| There may be humor in this post, and,

| Naturally, you will not sue,

| Should things get worse after this,

| PCR

| pcrrcp@netzero.net

|

March 17, 2008

Re: For PCR, trying to get rid of DEFAULT_MONITOR

Yes he did run it, but I'm not sure what it told him:

[EDID]

ID=VSCE41B

SN=xx16843009

Manufactured=Week 20, 2006

Type=Analog (0.7V)

Size=380 x 310 mm (20")

MaxHfreq=75 kHz (est.)

MaxVfreq=at least 85 Hz

MaxRes=2048 x 1200 (est.)

Gamma=2.20

GTF=n/a

DPMS=No

"MEB" <meb@not here@hotmail.com> wrote in message

news:u3wzss$hIHA.1184@TK2MSFTNGP04.phx.gbl...

> [Generic]

> %Unknown.DeviceDesc%=Unknown.Install,Monitor\Default_Monitor ; for

> auto-install

> %Unknown.DeviceDesc%=Unknown.Install ; for pick list

> %*PNP09FF.DeviceDesc%=VESADDC.Install,*PNP09FF

>

> *VESADDC*?

> http://pinouts.ru/Video/VGAVesaDdc_pinout.shtml

>

http://www.laptopvideo2go.com/forum/index.php?act=attach&type=post&id=1820 -

> note the multiple default monitors

>

> For the NT users, a tool to dig out information:

> http://www.laptopvideo2go.com/forum/index.php?showtopic=756&mode=threaded

>

> | AddReg=VP930_Series.AddReg,1280,DPMS

> http://webpages.charter.net/dperr/dpms.htm

> http://www.versiontracker.com/dyn/moreinfo/win/37027

>

> Did you ask him to use the DDC test tool I posted?

>

> IF its talkin, we be walkin...

>

> * MEB

> http://peoplescounsel.orgfree.com

> --

> _________

>

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

> news:ueXIxj9hIHA.944@TK2MSFTNGP05.phx.gbl...

> | MEB wrote:

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

> | | news:%23HA86uxhIHA.1944@TK2MSFTNGP02.phx.gbl...

> | || MEB wrote:

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

> | || | news:ORjn80jhIHA.6092@TK2MSFTNGP06.phx.gbl...

> | || || MEB wrote:

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

> | || || | news:%23UIOKuVhIHA.3788@TK2MSFTNGP04.phx.gbl...

> | ||

> | || ...snip

> | || || That seems like a little too much to do! I'm at the MS Library, &,

> | || || if I can't find something simpler, I'll resort to one of your

> | || || explications. What do you make of this...?...

> | || ||

> | || || http://msdn2.microsoft.com/en-us/library/aa939135.aspx

> | || || .....Quote.................

> | || || Default Monitor

> | || ||

> | || || The Default Monitor component provides support for a generic

> | || || monitor device. This component supplies the monitor.inf file,

> | || || which is a system-supplied INF (information) file for a generic

> | || || monitor. The monitor.inf file is associated with Windows 95.

> | || ||

> | || || Services

> | || || There are no services associated with this component.

> | || ||

> | || || Associated Components

> | || || No other components interact with this component.

> | || ||

> | || || Settings

> | || || There are no configurable settings for this component.

> | || || .....EOQ...................

> | || ||

> | || |

> | || | Okay, you found the XPSR2 file to briefly explain why a default

> | || | was included..

> | || |

> | || | As I see it:

> | || |

> | || | Well, let me put that on my own website [rather than letting

> | || | someone else re-write it and put it on their site].

> | || |

> | http://peoplescounsel.orgfree.com/ref/gen/windows/default_monitor.htm

> | || | - Windows Default Monitor in the registry and Device Manager

> | || |

> | || | The short is, its the chips baby, its all in the chips...

> | ||

> | || Because you've trebled the size of your explication, it will take

> | || longer to read it thrice. I also want to scour that MS Library-- & I

> | || haven't got the time tonight! Will get back to this tomorrow.

> | |

> | | Actually, I just collected the presentations from this thread, and a

> | | small part from what I put into another monitor/adapter discussion.

> | | Anyway, will see hat you come up with...

> |

> | OK. And I continue to promise it is coming... but again I've run out of

> | time. (I did post to Lee in the other thread.) I'll get back tomorrow.

> | My first few additional clicks at the MS Library came up empty-- but I

> | remain guardedly hopeful. As I posted to Lee, here are the lines in

> | Warren's VS080114_I19.inf that mention the VP930...

> |

> | [DestinationDirs]

> | VP930_Series.CopyFiles=23

> |

> | [sourceDisksFiles]

> | VP930_Series.ICM=1

> |

> | [ViewSonic]

> | %VP930_Series%=VP930_Series.Install,Monitor\VSCE41B ;VP930_Series

> |

> | [ViewSonic.NTia64]

> | %VP930_Series%=VP930_Series.Install,Monitor\VSCE41B ;VP930_Series

> |

> | [ViewSonic.NTamd64]

> | %VP930_Series%=VP930_Series.Install,Monitor\VSCE41B ;VP930_Series

> |

> | [VP930_Series.Install] ;VP930_Series

> | DelReg=DEL_CURRENT_REG

> | AddReg=VP930_Series.AddReg,1280,DPMS

> | Copyfiles=VP930_Series.CopyFiles

> |

> | [VP930_Series.AddReg] ;VP930_Series

> | HKR,"MODES\1280,1024",Mode1,,"30-82,50-75,+,+"

> | HKR,,ICMProfile,0,"VP930_Series.ICM"

> |

> | [VP930_Series.CopyFiles]

> | VP930_Series.ICM

> |

> | [strings]

> | VP930_Series="ViewSonic VP930 Series"

> |

> | Also, that Default_Monitor is not mentioned in his .inf. It is mentioned

> | in Monitor.inf that we all have. I show only the lines that mention

> | it (but I must go)...

> |

> | [sysCfgClasses]

> | Monitor, %Unknown.DeviceDesc%,MONITOR,4,%MonitorClassName% ; Default

> | to "Unknown Monitor"

> |

> | ; Monitors to hide from pick list

> | ;-------------------------------------------------

> | [ControlFlags]

> | ExcludeFromSelect=Monitor\Default_Monitor

> |

> | [Generic]

> | %Unknown.DeviceDesc%=Unknown.Install,Monitor\Default_Monitor ; for

> | auto-install

> | %Unknown.DeviceDesc%=Unknown.Install ; for pick list

> | %*PNP09FF.DeviceDesc%=VESADDC.Install,*PNP09FF

> |

> | [strings]

> | MonitorClassName="Monitors"

> | MS="Microsoft"

> |

> | Generic="(Standard monitor types)"

> | Unknown.DeviceDesc="Default Monitor"

> |

> | *PNP09FF.DeviceDesc = "Plug and Play Monitor"

> |

> | ||

> | || ||

> | || || | MEB

> | || || PCR

> | || | MEB

> | || | _________

> | || PCR

> | | --

> | |

> | | MEB

> | | http://peoplescounsel.orgfree.com

> | | _________

> |

> | --

> | Thanks or Good Luck,

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

> | Naturally, you will not sue,

> | Should things get worse after this,

> | PCR

> | pcrrcp@netzero.net

> |

>

March 17, 2008

Re: For PCR, trying to get rid of DEFAULT_MONITOR

On Mar 17, 4:45 am, "Warren" <nos...@nospam.com> wrote:

> Yes he did run it, but I'm not sure what it told him:

>

> [EDID]

> ID=VSCE41B

> SN=xx16843009

> Manufactured=Week 20, 2006

> Type=Analog (0.7V)

> Size=380 x 310 mm (20")

> MaxHfreq=75 kHz (est.)

> MaxVfreq=at least 85 Hz

> MaxRes=2048 x 1200 (est.)

> Gamma=2.20

> GTF=n/a

> DPMS=No

>

> "MEB" <meb@not h...@hotmail.com> wrote in message

>

> news:u3wzss$hIHA.1184@TK2MSFTNGP04.phx.gbl...> [Generic]

> > %Unknown.DeviceDesc%=Unknown.Install,Monitor\Default_Monitor ; for

> > auto-install

> > %Unknown.DeviceDesc%=Unknown.Install ; for pick list

> > %*PNP09FF.DeviceDesc%=VESADDC.Install,*PNP09FF

>

> > *VESADDC*?

> >http://pinouts.ru/Video/VGAVesaDdc_pinout.shtml

>

> http://www.laptopvideo2go.com/forum/index.php?act=attach&type=post&id....-

>

> > note the multiple default monitors

>

> > For the NT users, a tool to dig out information:

> >http://www.laptopvideo2go.com/forum/index.php?showtopic=756&mode=thre....

>

> > | AddReg=VP930_Series.AddReg,1280,DPMS

> >http://webpages.charter.net/dperr/dpms.htm

> >http://www.versiontracker.com/dyn/moreinfo/win/37027

>

> > Did you ask him to use the DDC test tool I posted?

>

> > IF its talkin, we be walkin...

>

> > * MEB

> >http://peoplescounsel.orgfree.com

> > --

> > _________

>

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

> >news:ueXIxj9hIHA.944@TK2MSFTNGP05.phx.gbl...

> > | MEB wrote:

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

> > | |news:%23HA86uxhIHA.1944@TK2MSFTNGP02.phx.gbl...

> > | || MEB wrote:

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

> > | || |news:ORjn80jhIHA.6092@TK2MSFTNGP06.phx.gbl...

> > | || || MEB wrote:

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

> > | || || |news:%23UIOKuVhIHA.3788@TK2MSFTNGP04.phx.gbl...

> > | ||

> > | || ...snip

> > | || || That seems like a little too much to do! I'm at the MS Library, &,

> > | || || if I can't find something simpler, I'll resort to one of your

> > | || || explications. What do you make of this...?...

> > | || ||

> > | || ||http://msdn2.microsoft.com/en-us/library/aa939135.aspx

> > | || || .....Quote.................

> > | || || Default Monitor

> > | || ||

> > | || || The Default Monitor component provides support for a generic

> > | || || monitor device. This component supplies the monitor.inf file,

> > | || || which is a system-supplied INF (information) file for a generic

> > | || || monitor. The monitor.inf file is associated with Windows 95.

> > | || ||

> > | || || Services

> > | || || There are no services associated with this component.

> > | || ||

> > | || || Associated Components

> > | || || No other components interact with this component.

> > | || ||

> > | || || Settings

> > | || || There are no configurable settings for this component.

> > | || || .....EOQ...................

> > | || ||

> > | || |

> > | || | Okay, you found the XPSR2 file to briefly explain why a default

> > | || | was included..

> > | || |

> > | || | As I see it:

> > | || |

> > | || | Well, let me put that on my own website [rather than letting

> > | || | someone else re-write it and put it on their site].

> > | || |

> > |http://peoplescounsel.orgfree.com/ref/gen/windows/default_monitor.htm

> > | || | - Windows Default Monitor in the registry and Device Manager

> > | || |

> > | || | The short is, its the chips baby, its all in the chips...

> > | ||

> > | || Because you've trebled the size of your explication, it will take

> > | || longer to read it thrice. I also want to scour that MS Library-- & I

> > | || haven't got the time tonight! Will get back to this tomorrow.

> > | |

> > | | Actually, I just collected the presentations from this thread, and a

> > | | small part from what I put into another monitor/adapter discussion.

> > | | Anyway, will see hat you come up with...

> > |

> > | OK. And I continue to promise it is coming... but again I've run out of

> > | time. (I did post to Lee in the other thread.) I'll get back tomorrow.

> > | My first few additional clicks at the MS Library came up empty-- but I

> > | remain guardedly hopeful. As I posted to Lee, here are the lines in

> > | Warren's VS080114_I19.inf that mention the VP930...

> > |

> > | [DestinationDirs]

> > | VP930_Series.CopyFiles=23

> > |

> > | [sourceDisksFiles]

> > | VP930_Series.ICM=1

> > |

> > | [ViewSonic]

> > | %VP930_Series%=VP930_Series.Install,Monitor\VSCE41B ;VP930_Series

> > |

> > | [ViewSonic.NTia64]

> > | %VP930_Series%=VP930_Series.Install,Monitor\VSCE41B ;VP930_Series

> > |

> > | [ViewSonic.NTamd64]

> > | %VP930_Series%=VP930_Series.Install,Monitor\VSCE41B ;VP930_Series

> > |

> > | [VP930_Series.Install] ;VP930_Series

> > | DelReg=DEL_CURRENT_REG

> > | AddReg=VP930_Series.AddReg,1280,DPMS

> > | Copyfiles=VP930_Series.CopyFiles

> > |

> > | [VP930_Series.AddReg] ;VP930_Series

> > | HKR,"MODES\1280,1024",Mode1,,"30-82,50-75,+,+"

> > | HKR,,ICMProfile,0,"VP930_Series.ICM"

> > |

> > | [VP930_Series.CopyFiles]

> > | VP930_Series.ICM

> > |

> > | [strings]

> > | VP930_Series="ViewSonic VP930 Series"

> > |

> > | Also, that Default_Monitor is not mentioned in his .inf. It is mentioned

> > | in Monitor.inf that we all have. I show only the lines that mention

> > | it (but I must go)...

> > |

> > | [sysCfgClasses]

> > | Monitor, %Unknown.DeviceDesc%,MONITOR,4,%MonitorClassName% ; Default

> > | to "Unknown Monitor"

> > |

> > | ; Monitors to hide from pick list

> > | ;-------------------------------------------------

> > | [ControlFlags]

> > | ExcludeFromSelect=Monitor\Default_Monitor

> > |

> > | [Generic]

> > | %Unknown.DeviceDesc%=Unknown.Install,Monitor\Default_Monitor ; for

> > | auto-install

> > | %Unknown.DeviceDesc%=Unknown.Install ; for pick list

> > | %*PNP09FF.DeviceDesc%=VESADDC.Install,*PNP09FF

> > |

> > | [strings]

> > | MonitorClassName="Monitors"

> > | MS="Microsoft"

> > |

> > | Generic="(Standard monitor types)"

> > | Unknown.DeviceDesc="Default Monitor"

> > |

> > | *PNP09FF.DeviceDesc = "Plug and Play Monitor"

> > |

> > | ||

> > | || ||

> > | || || | MEB

> > | || || PCR

> > | || | MEB

> > | || | _________

> > | || PCR

> > | | --

> > | |

> > | | MEB

> > | |http://peoplescounsel.orgfree.com

> > | | _________

> > |

> > | --

> > | Thanks or Good Luck,

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

> > | Naturally, you will not sue,

> > | Should things get worse after this,

> > | PCR

> > | pcr...@netzero.net

> > |

> > |- Hide quoted text -

>

> - Show quoted text -

It told the ID number VSCE41B which is used by Windows to identify the

monitor such as to match it with an inf file and then from the inf

file to an ICM file to drive it with. The ID number does match the

latest VS080314_l19.inf file so there is hope it will work. When

Windows queries the monitor as to "who are you?", it answers with the

ID number which is how Windows knows which inf to install the drivers

for it with.

So as soon as PCR mentioned the inf file was a large one, I flinched

because 9x inf files can not be 60k or larger or they fail to work

properly and that would explain why the unknown monitor gets installed

as the Default Monitor all day long. The inf file can not be used to

ID the monitor properly because it is too big. I see even in the

latest driver package ViewSonic has a 63k inf for 9x systems which is

a big fat no-no all the way around (nobody told them?). Thankfully it

doesn't have your monitor info in it so maybe it doesn't matter.

So I set about to download my own copy of this dadgummed driver

critter, lift the hood and take a peek at it myself. What I find is

that as of 3 days ago ViewSonic posted a new driver for your monitor -

how is that for a co-inkeedink? 3/14/2008, so go get the new one and

see if they cleaned it up just for you. This thread and the other one

is replicating itself beyond belief, but amidst all the echos I did

find these that seem to be of some interest.

http://forums.windrivers.com/showthread.php?t=81436

http://www.tomshardware.com/forum/50591-3-calibrating-viewsonic-vp930

http://www.viewsonic.com/support/drivers/drivers.cfm?category=1&formName=monitor

I thought boy howdy, I'm going to get Warren the low down skinny on

just what is going on, look at all these vp930 Google hits with

"Default Monitor" in them only to find out that the author is Warren

himself. Hopefully the new release will fix it up right - let us know

as per usual.

March 17, 2008

Re: For PCR, trying to get rid of DEFAULT_MONITOR

Both Warren and Lee are responded to here.

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

news:faf8f27e-cbcb-42ee-bf4b-1d851d4dc420@v3g2000hsc.googlegroups.com...

On Mar 17, 4:45 am, "Warren" <nos...@nospam.com> wrote:

> Yes he did run it, but I'm not sure what it told him:

>

> [EDID]

> ID=VSCE41B

> SN=xx16843009

> Manufactured=Week 20, 2006

> Type=Analog (0.7V)

> Size=380 x 310 mm (20")

> MaxHfreq=75 kHz (est.)

> MaxVfreq=at least 85 Hz

> MaxRes=2048 x 1200 (est.)

> Gamma=2.20

> GTF=n/a

> DPMS=No

Sorry Warren, thought you had dropped back to the older discussion.

Oft'times, when discussions revolve between two people, such as myself and

PCR, others tend to stop monitoring the discussion, or at least it seems

that way.

For a display to be able to use DDC, DPMS, GTF, and other; the adaptor/chip

MUST also supply that ability or pass it through.

>

> "MEB" <meb@not h...@hotmail.com> wrote in message

>

> news:u3wzss$hIHA.1184@TK2MSFTNGP04.phx.gbl...> [Generic]

> > %Unknown.DeviceDesc%=Unknown.Install,Monitor\Default_Monitor ; for

> > auto-install

> > %Unknown.DeviceDesc%=Unknown.Install ; for pick list

> > %*PNP09FF.DeviceDesc%=VESADDC.Install,*PNP09FF

>

> > *VESADDC*?

> >http://pinouts.ru/Video/VGAVesaDdc_pinout.shtml

>

> http://www.laptopvideo2go.com/forum/index.php?act=attach&type=post&id...-

> > note the multiple default monitors

>

> > For the NT users, a tool to dig out information:

> >http://www.laptopvideo2go.com/forum/index.php?showtopic=756&mode=thre...

>

> > | AddReg=VP930_Series.AddReg,1280,DPMS

> >http://webpages.charter.net/dperr/dpms.htm

> >http://www.versiontracker.com/dyn/moreinfo/win/37027

>

> > Did you ask him to use the DDC test tool I posted?

>

> > IF its talkin, we be walkin...

>

> > * MEB

> >http://peoplescounsel.orgfree.com

> > --

> > _________

>

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

> >news:ueXIxj9hIHA.944@TK2MSFTNGP05.phx.gbl...

> > | MEB wrote:

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

> > | |news:%23HA86uxhIHA.1944@TK2MSFTNGP02.phx.gbl...

> > | || MEB wrote:

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

> > | || |news:ORjn80jhIHA.6092@TK2MSFTNGP06.phx.gbl...

> > | || || MEB wrote:

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

> > | || || |news:%23UIOKuVhIHA.3788@TK2MSFTNGP04.phx.gbl...

> > | ||

> > | || ...snip

> > | || || That seems like a little too much to do! I'm at the MS Library,

&,

> > | || || if I can't find something simpler, I'll resort to one of your

> > | || || explications. What do you make of this...?...

> > | || ||

> > | || ||http://msdn2.microsoft.com/en-us/library/aa939135.aspx

> > | || || .....Quote.................

> > | || || Default Monitor

> > | || ||

> > | || || The Default Monitor component provides support for a generic

> > | || || monitor device. This component supplies the monitor.inf file,

> > | || || which is a system-supplied INF (information) file for a generic

> > | || || monitor. The monitor.inf file is associated with Windows 95.

> > | || ||

> > | || || Services

> > | || || There are no services associated with this component.

> > | || ||

> > | || || Associated Components

> > | || || No other components interact with this component.

> > | || ||

> > | || || Settings

> > | || || There are no configurable settings for this component.

> > | || || .....EOQ...................

> > | || ||

> > | || |

> > | || | Okay, you found the XPSR2 file to briefly explain why a default

> > | || | was included..

> > | || |

> > | || | As I see it:

> > | || |

> > | || | Well, let me put that on my own website [rather than letting

> > | || | someone else re-write it and put it on their site].

> > | || |

> > |http://peoplescounsel.orgfree.com/ref/gen/windows/default_monitor.htm

> > | || | - Windows Default Monitor in the registry and Device Manager

> > | || |

> > | || | The short is, its the chips baby, its all in the chips...

> > | ||

> > | || Because you've trebled the size of your explication, it will take

> > | || longer to read it thrice. I also want to scour that MS Library-- &

I

> > | || haven't got the time tonight! Will get back to this tomorrow.

> > | |

> > | | Actually, I just collected the presentations from this thread, and a

> > | | small part from what I put into another monitor/adapter discussion.

> > | | Anyway, will see hat you come up with...

> > |

> > | OK. And I continue to promise it is coming... but again I've run out

of

> > | time. (I did post to Lee in the other thread.) I'll get back tomorrow.

> > | My first few additional clicks at the MS Library came up empty-- but I

> > | remain guardedly hopeful. As I posted to Lee, here are the lines in

> > | Warren's VS080114_I19.inf that mention the VP930...

> > |

> > | [DestinationDirs]

> > | VP930_Series.CopyFiles=23

> > |

> > | [sourceDisksFiles]

> > | VP930_Series.ICM=1

> > |

> > | [ViewSonic]

> > | %VP930_Series%=VP930_Series.Install,Monitor\VSCE41B ;VP930_Series

> > |

> > | [ViewSonic.NTia64]

> > | %VP930_Series%=VP930_Series.Install,Monitor\VSCE41B ;VP930_Series

> > |

> > | [ViewSonic.NTamd64]

> > | %VP930_Series%=VP930_Series.Install,Monitor\VSCE41B ;VP930_Series

> > |

> > | [VP930_Series.Install] ;VP930_Series

> > | DelReg=DEL_CURRENT_REG

> > | AddReg=VP930_Series.AddReg,1280,DPMS

> > | Copyfiles=VP930_Series.CopyFiles

> > |

> > | [VP930_Series.AddReg] ;VP930_Series

> > | HKR,"MODES\1280,1024",Mode1,,"30-82,50-75,+,+"

> > | HKR,,ICMProfile,0,"VP930_Series.ICM"

> > |

> > | [VP930_Series.CopyFiles]

> > | VP930_Series.ICM

> > |

> > | [strings]

> > | VP930_Series="ViewSonic VP930 Series"

> > |

> > | Also, that Default_Monitor is not mentioned in his .inf. It is

mentioned

> > | in Monitor.inf that we all have. I show only the lines that mention

> > | it (but I must go)...

> > |

> > | [sysCfgClasses]

> > | Monitor, %Unknown.DeviceDesc%,MONITOR,4,%MonitorClassName% ; Default

> > | to "Unknown Monitor"

> > |

> > | ; Monitors to hide from pick list

> > | ;-------------------------------------------------

> > | [ControlFlags]

> > | ExcludeFromSelect=Monitor\Default_Monitor

> > |

> > | [Generic]

> > | %Unknown.DeviceDesc%=Unknown.Install,Monitor\Default_Monitor ; for

> > | auto-install

> > | %Unknown.DeviceDesc%=Unknown.Install ; for pick list

> > | %*PNP09FF.DeviceDesc%=VESADDC.Install,*PNP09FF

> > |

> > | [strings]

> > | MonitorClassName="Monitors"

> > | MS="Microsoft"

> > |

> > | Generic="(Standard monitor types)"

> > | Unknown.DeviceDesc="Default Monitor"

> > |

> > | *PNP09FF.DeviceDesc = "Plug and Play Monitor"

> > |

> > | ||

> > | || ||

> > | || || | MEB

> > | || || PCR

> > | || | MEB

> > | || | _________

> > | || PCR

> > | | --

> > | |

> > | | MEB

> > | |http://peoplescounsel.orgfree.com

> > | | _________

> > |

> > | --

> > | PCR

> > |

| It told the ID number VSCE41B which is used by Windows to identify the

| monitor such as to match it with an inf file and then from the inf

| file to an ICM file to drive it with. The ID number does match the

| latest VS080314_l19.inf file so there is hope it will work. When

| Windows queries the monitor as to "who are you?", it answers with the

| ID number which is how Windows knows which inf to install the drivers

| for it with.

|

| So as soon as PCR mentioned the inf file was a large one, I flinched

| because 9x inf files can not be 60k or larger or they fail to work

| properly and that would explain why the unknown monitor gets installed

| as the Default Monitor all day long. The inf file can not be used to

| ID the monitor properly because it is too big. I see even in the

| latest driver package ViewSonic has a 63k inf for 9x systems which is

| a big fat no-no all the way around (nobody told them?). Thankfully it

| doesn't have your monitor info in it so maybe it doesn't matter.

I didn't download the driver, glad you did. Had PCR or Warren mentioned the

actual size, this discussion might have been much shorter.

That's also, in part, what I was attempting to indicate previously [in the

work-around]:

| MEB wrote:

| IF you intend to try to over-ride this in 9X then you MUST disable

| PnP/auto detection in the system AND if possible, the video adaptor,

| AND ensure the INF does not contain any references to a default, OR

| that it REPLACES the default [original video driver], OR that it

| isn't added BY the driver itself once it is installed and first

| rebooted. NOTE though, that the video device **must have the ALL the

| OLD 9X installation and system/registry settings in its installation

| routine**, as if it was NOT PnP [9X term - XP/Vista uses different

| routines in its HAL and other]..

Interestingly, you say it doesn't contain information for Warren's monitor.

IF so, Win9X is going to use the standards [PnP INFs] it has for the

monitor.

DDC, DPMS, and VESA. Part of that information comes from monitor.inf, hence

the default.

It shouldn't be difficult to create an actual INF for the display. Its

settings for XP/NT would be basicly the same in 9X without all the

redundency necessary in those NT environments. Anything beyond the limit, or

which can not be handled otherwise, CAN be addressed via *.bin or *.pnf. 9X

IS, after all, a conglomeration of DOS-9X-NT code. Since its no longer

necessary to ensure the code produces no errors [after Microsoft breaking

its own requirements with IE6 files], staying within those limits

[non-fatal] seems to be the applicable standard.

This brings to light, in my mind, a question to these device manufacturers:

Why would you [the manufacturers] cowtow to Microsoft's demand [recently

confirmed in Tech News, coming from "leaked" Microsoft internal and other

memos] you remove support for unsupported systems, merely to obtain WHQL

certification for VISTA?

To limit yourself [and your investors] to Microsoft demands, seems to be

counter-productive and economically unsound. Most of your devices WILL work

in 9X. Will users use non-certified drivers from you, well DUH, !YEAH!, they

will as long as they work.

| So I set about to download my own copy of this dadgummed driver

| critter, lift the hood and take a peek at it myself. What I find is

| that as of 3 days ago ViewSonic posted a new driver for your monitor -

| how is that for a co-inkeedink? 3/14/2008, so go get the new one and

| see if they cleaned it up just for you. This thread and the other one

| is replicating itself beyond belief, but amidst all the echos I did

| find these that seem to be of some interest.

| http://forums.windrivers.com/showthread.php?t=81436

| http://www.tomshardware.com/forum/50591-3-calibrating-viewsonic-vp930

|

http://www.viewsonic.com/support/drivers/drivers.cfm?category=1&formName=monitor

|

| I thought boy howdy, I'm going to get Warren the low down skinny on

| just what is going on, look at all these vp930 Google hits with

| "Default Monitor" in them only to find out that the author is Warren

| himself. Hopefully the new release will fix it up right - let us know

| as per usual.

Right.

This is a pretty good indication of the power of the NET... if we can some

how manage to get the world's people to look at REAL discussions and

information rather than watching videos and getting caught up in "glitz and

glamour" {ah, okay, I do realize this is NOT going to happen}...

* MEB

http://peoplescounsel.orgfree.com

--

_________

March 18, 2008

Re: For PCR, trying to get rid of DEFAULT_MONITOR

We are close to firing on all cylinders soon? What I should have done

was list all the files in the driver package but I might rival PCR's

master post in doing so. There are at least 11 inf files ranging from

31k thru 63k with the one inf file dealing with the VP930 monitor

(VS080314_l19.inf) being 48k in length. There is a large number of

ICM files added to the System\Color folder as well. The count went up

from a one page display in Windows Explorer to now 873 files. So it's

a pretty heathy driver package.

VS080314_l19.inf file does have a 3/14/2008 date on it now so it was

modifed a few days ago which is the only hope I have for a real

solution here. I of course can't know what size the previous inf file

was since it is no longer available from ViewSonic, and it seems all

driver sites link back to ViewSonic as well so there is no archived

version readily available? I kinda doubt it was too big to work, but

I do suspect strongly that it was still written wrong which may or may

not be fixed now - it's obvious the inf writers at ViewSonic need a

lesson or two in proper inf file construction, not that I could teach

the course mind you.

I'm thinking it's pure circumstance that a new driver would be

available as of a few days ago. ViewSonic has remained totally

oblivious to it's Device Mangler's double doppleganger for five or

more years now, I'm sure they are happy doing so too. So odds are

that it's not fixed even yet...

On Mar 17, 2:38 pm, "MEB" <meb@not h...@hotmail.com> wrote:

> Both Warren and Lee are responded to here.

>

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

>

> news:faf8f27e-cbcb-42ee-bf4b-1d851d4dc420@v3g2000hsc.googlegroups.com...

> On Mar 17, 4:45 am, "Warren" <nos...@nospam.com> wrote:

>

> > Yes he did run it, but I'm not sure what it told him:

>

> > [EDID]

> > ID=VSCE41B

> > SN=xx16843009

> > Manufactured=Week 20, 2006

> > Type=Analog (0.7V)

> > Size=380 x 310 mm (20")

> > MaxHfreq=75 kHz (est.)

> > MaxVfreq=at least 85 Hz

> > MaxRes=2048 x 1200 (est.)

> > Gamma=2.20

> > GTF=n/a

> > DPMS=No

>

> Sorry Warren, thought you had dropped back to the older discussion.

> Oft'times, when discussions revolve between two people, such as myself and

> PCR, others tend to stop monitoring the discussion, or at least it seems

> that way.

>

> For a display to be able to use DDC, DPMS, GTF, and other; the adaptor/chip

> MUST also supply that ability or pass it through.

>

> > "MEB" <meb@not h...@hotmail.com> wrote in message

>

> >news:u3wzss$hIHA.1184@TK2MSFTNGP04.phx.gbl...> [Generic]

> > > %Unknown.DeviceDesc%=Unknown.Install,Monitor\Default_Monitor ; for

> > > auto-install

> > > %Unknown.DeviceDesc%=Unknown.Install ; for pick list

> > > %*PNP09FF.DeviceDesc%=VESADDC.Install,*PNP09FF

>

> > > *VESADDC*?

> > >http://pinouts.ru/Video/VGAVesaDdc_pinout.shtml

>

> >http://www.laptopvideo2go.com/forum/index.php?act=attach&type=post&id....

> > > note the multiple default monitors

>

> > > For the NT users, a tool to dig out information:

> > >http://www.laptopvideo2go.com/forum/index.php?showtopic=756&mode=thre...

>

> > > | AddReg=VP930_Series.AddReg,1280,DPMS

> > >http://webpages.charter.net/dperr/dpms.htm

> > >http://www.versiontracker.com/dyn/moreinfo/win/37027

>

> > > Did you ask him to use the DDC test tool I posted?

>

> > > IF its talkin, we be walkin...

>

> > > * MEB

> > >http://peoplescounsel.orgfree.com

> > > --

> > > _________

>

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

> > >news:ueXIxj9hIHA.944@TK2MSFTNGP05.phx.gbl...

> > > | MEB wrote:

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

> > > | |news:%23HA86uxhIHA.1944@TK2MSFTNGP02.phx.gbl...

> > > | || MEB wrote:

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

> > > | || |news:ORjn80jhIHA.6092@TK2MSFTNGP06.phx.gbl...

> > > | || || MEB wrote:

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

> > > | || || |news:%23UIOKuVhIHA.3788@TK2MSFTNGP04.phx.gbl...

> > > | ||

> > > | || ...snip

> > > | || || That seems like a little too much to do! I'm at the MS Library,

> &,

> > > | || || if I can't find something simpler, I'll resort to one of your

> > > | || || explications. What do you make of this...?...

> > > | || ||

> > > | || ||http://msdn2.microsoft.com/en-us/library/aa939135.aspx

> > > | || || .....Quote.................

> > > | || || Default Monitor

> > > | || ||

> > > | || || The Default Monitor component provides support for a generic

> > > | || || monitor device. This component supplies the monitor.inf file,

> > > | || || which is a system-supplied INF (information) file for a generic

> > > | || || monitor. The monitor.inf file is associated with Windows 95.

> > > | || ||

> > > | || || Services

> > > | || || There are no services associated with this component.

> > > | || ||

> > > | || || Associated Components

> > > | || || No other components interact with this component.

> > > | || ||

> > > | || || Settings

> > > | || || There are no configurable settings for this component.

> > > | || || .....EOQ...................

> > > | || ||

> > > | || |

> > > | || | Okay, you found the XPSR2 file to briefly explain why a default

> > > | || | was included..

> > > | || |

> > > | || | As I see it:

> > > | || |

> > > | || | Well, let me put that on my own website [rather than letting

> > > | || | someone else re-write it and put it on their site].

> > > | || |

> > > |http://peoplescounsel.orgfree.com/ref/gen/windows/default_monitor.htm

> > > | || | - Windows Default Monitor in the registry and Device Manager

> > > | || |

> > > | || | The short is, its the chips baby, its all in the chips...

> > > | ||

> > > | || Because you've trebled the size of your explication, it will take

> > > | || longer to read it thrice. I also want to scour that MS Library-- &

> I

> > > | || haven't got the time tonight! Will get back to this tomorrow.

> > > | |

> > > | | Actually, I just collected the presentations from this thread, and a

> > > | | small part from what I put into another monitor/adapter discussion..

> > > | | Anyway, will see hat you come up with...

> > > |

> > > | OK. And I continue to promise it is coming... but again I've run out

> of

> > > | time. (I did post to Lee in the other thread.) I'll get back tomorrow.

> > > | My first few additional clicks at the MS Library came up empty-- but I

> > > | remain guardedly hopeful. As I posted to Lee, here are the lines in

> > > | Warren's VS080114_I19.inf that mention the VP930...

> > > |

> > > | [DestinationDirs]

> > > | VP930_Series.CopyFiles=23

> > > |

> > > | [sourceDisksFiles]

> > > | VP930_Series.ICM=1

> > > |

> > > | [ViewSonic]

> > > | %VP930_Series%=VP930_Series.Install,Monitor\VSCE41B ;VP930_Series

> > > |

> > > | [ViewSonic.NTia64]

> > > | %VP930_Series%=VP930_Series.Install,Monitor\VSCE41B ;VP930_Series

> > > |

> > > | [ViewSonic.NTamd64]

> > > | %VP930_Series%=VP930_Series.Install,Monitor\VSCE41B ;VP930_Series

> > > |

> > > | [VP930_Series.Install] ;VP930_Series

> > > | DelReg=DEL_CURRENT_REG

> > > | AddReg=VP930_Series.AddReg,1280,DPMS

> > > | Copyfiles=VP930_Series.CopyFiles

> > > |

> > > | [VP930_Series.AddReg] ;VP930_Series

> > > | HKR,"MODES\1280,1024",Mode1,,"30-82,50-75,+,+"

> > > | HKR,,ICMProfile,0,"VP930_Series.ICM"

> > > |

> > > | [VP930_Series.CopyFiles]

> > > | VP930_Series.ICM

> > > |

> > > | [strings]

> > > | VP930_Series="ViewSonic VP930 Series"

> > > |

> > > | Also, that Default_Monitor is not mentioned in his .inf. It is

> mentioned

> > > | in Monitor.inf that we all have. I show only the lines that mention

> > > | it (but I must go)...

> > > |

> > > | [sysCfgClasses]

> > > | Monitor, %Unknown.DeviceDesc%,MONITOR,4,%MonitorClassName% ; Default

> > > | to "Unknown Monitor"

> > > |

> > > | ; Monitors to hide from pick list

> > > | ;-------------------------------------------------

> > > | [ControlFlags]

> > > | ExcludeFromSelect=Monitor\Default_Monitor

> > > |

> > > | [Generic]

> > > | %Unknown.DeviceDesc%=Unknown.Install,Monitor\Default_Monitor ; for

> > > | auto-install

> > > | %Unknown.DeviceDesc%=Unknown.Install ; for pick list

> > > | %*PNP09FF.DeviceDesc%=VESADDC.Install,*PNP09FF

> > > |

> > > | [strings]

> > > | MonitorClassName="Monitors"

> > > | MS="Microsoft"

> > > |

> > > | Generic="(Standard monitor types)"

> > > | Unknown.DeviceDesc="Default Monitor"

> > > |

> > > | *PNP09FF.DeviceDesc = "Plug and Play Monitor"

> > > |

> > > | ||

> > > | || ||

> > > | || || | MEB

> > > | || || PCR

> > > | || | MEB

> > > | || | _________

> > > | || PCR

> > > | | --

> > > | |

> > > | | MEB

> > > | |http://peoplescounsel.orgfree.com

> > > | | _________

> > > |

> > > | --

> > > | PCR

> > > |

>

> | It told the ID number VSCE41B which is used by Windows to identify the

> | monitor such as to match it with an inf file and then from the inf

> | file to an ICM file to drive it with. The ID number does match the

> | latest VS080314_l19.inf file so there is hope it will work. When

> | Windows queries the monitor as to "who are you?", it answers with the

> | ID number which is how Windows knows which inf to install the drivers

> | for it with.

> |

> | So as soon as PCR mentioned the inf file was a large one, I flinched

> | because 9x inf files can not be 60k or larger or they fail to work

> | properly and that would explain why the unknown monitor gets installed

> | as the Default Monitor all day long. The inf file can not be used to

> | ID the monitor properly because it is too big. I see even in the

> | latest driver package ViewSonic has a 63k inf for 9x systems which is

> | a big fat no-no all the way around (nobody told them?). Thankfully it

> | doesn't have your monitor info in it so maybe it doesn't matter.

>

> I didn't download the driver, glad you did. Had PCR or Warren mentioned the

> actual size, this discussion might have been much shorter.

> That's also, in part, what I was attempting to indicate previously [in the

> work-around]:| MEB wrote:

>

> | IF you intend to try to over-ride this in 9X then you MUST disable

> | PnP/auto detection in the system AND if possible, the video adaptor,

> | AND ensure the INF does not contain any references to a default, OR

> | that it REPLACES the default [original video driver], OR that it

> | isn't added BY the driver itself once it is installed and first

> | rebooted. NOTE though, that the video device **must have the ALL the

> | OLD 9X installation and system/registry settings in its installation

> | routine**, as if it was NOT PnP [9X term - XP/Vista uses different

> | routines in its HAL and other]..

>

> Interestingly, you say it doesn't contain information for Warren's monitor.

> IF so, Win9X is going to use the standards [PnP INFs] it has for the

> monitor.

> DDC, DPMS, and VESA. Part of that information comes from monitor.inf, hence

> the default.

> It shouldn't be difficult to create an actual INF for the display. Its

> settings for XP/NT would be basicly the same in 9X without all the

> redundency necessary in those NT environments. Anything beyond the limit, or

> which can not be handled otherwise, CAN be addressed via *.bin or *.pnf. 9X

> IS, after all, a conglomeration of DOS-9X-NT code. Since its no longer

> necessary to ensure the code produces no errors [after Microsoft breaking

> its own requirements with IE6 files], staying within those limits

> [non-fatal] seems to be the applicable standard.

>

> This brings to light, in my mind, a question to these device manufacturers:

> Why would you [the manufacturers] cowtow to Microsoft's demand [recently

> confirmed in Tech News, coming from "leaked" Microsoft internal and other

> memos] you remove support for unsupported systems, merely to obtain WHQL

> certification for VISTA?

> To limit yourself [and your investors] to Microsoft demands, seems to be

> counter-productive and economically unsound. Most of your devices WILL work

> in 9X. Will users use non-certified drivers from you, well DUH, !YEAH!, they

> will as long as they work.

>

> | So I set about to download my own copy of this dadgummed driver

> | critter, lift the hood and take a peek at it myself. What I find is

> | that as of 3 days ago ViewSonic posted a new driver for your monitor -

> | how is that for a co-inkeedink? 3/14/2008, so go get the new one and

> | see if they cleaned it up just for you. This thread and the other one

> | is replicating itself beyond belief, but amidst all the echos I did

> | find these that seem to be of some interest.

> |http://forums.windrivers.com/showthread.php?t=81436

> |http://www.tomshardware.com/forum/50591-3-calibrating-viewsonic-vp930

> |http://www.viewsonic.com/support/drivers/drivers.cfm?category=1&formN....

> |

> | I thought boy howdy, I'm going to get Warren the low down skinny on

> | just what is going on, look at all these vp930 Google hits with

> | "Default Monitor" in them only to find out that the author is Warren

> | himself. Hopefully the new release will fix it up right - let us know

> | as per usual.

>

> Right.

>

> This is a pretty good indication of the power of the NET... if we can some

> how manage to get the world's people to look at REAL discussions and

> information rather than watching videos and getting caught up in "glitz and

> glamour" {ah, okay, I do realize this is NOT going to happen}...

>

> * MEBhttp://peoplescounsel.orgfree.com

> --

> _________

March 18, 2008

Re: For PCR, trying to get rid of DEFAULT_MONITOR

Well, I downloaded & installed the latest driver package from Viewsonic

(thanks for the tip), deleted all occurences of Default_Monitor & VSCE41B in

the Registry and rebooted. Windows picked up the new driver dated March 14,

2008 for my VP930b. But unfortunately the Default_Monitor also reappeared.

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

news:aa6737dc-803d-49e6-97b9-479339391f05@u72g2000hsf.googlegroups.com...