For PCR, trying to get rid of DEFAULT_MONITOR

March 11, 2008

[HKEY_LOCAL_MACHINE\Enum\MONITOR]

[HKEY_LOCAL_MACHINE\Enum\MONITOR\VSCE41B]

[HKEY_LOCAL_MACHINE\Enum\MONITOR\VSCE41B\PCI_VEN_1002&DEV_5961&SUBSYS_280117

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,0e,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"

"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

[HKEY_LOCAL_MACHINE\Enum\MONITOR\DEFAULT_MONITOR]

[HKEY_LOCAL_MACHINE\Enum\MONITOR\DEFAULT_MONITOR\PCI_VEN_1002&DEV_5961&SUBSY

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\\0001"

"Mfg"="(Standard monitor types)"

"DeviceDesc"="Default Monitor"

"ConfigFlags"=hex:00,00,00,00

**************************************************************

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

"Link"="{4D36E96E-E325-11CE-BFC1-08002BE10318}"

[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\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]

@=""

********************************************************************

RADEON 9200 SERIES

Display

Registry Key:

HKEY_LOCAL_MACHINE\enum\PCI\VEN_1002&DEV_5961&SUBSYS_280117EE&REV_01\000800

Alloc resources: Logical Configuration 0

IRQ: 11 Mask: xFFFF

Forced resources: None

Boot resources: None

Filtered resources: Logical Configuration 0

IRQ: 11 Mask: xFFFF

Basic resources: Logical Configuration 0

IRQ: 0 Mask: xFFFF

HW Revision: 001

Driver: Display\0000

Driver Date: 2- 3-2006

Driver: vga.drv

File Size: 52080

(0xCB70)

File Date: 4/23/1999

10:22 AM

Company Name: Microsoft

Corporation

File Version: 4.10.1998

Driver: atricdxx.enu

File Size: 69632

(0x11000)

File Date: 1/24/2006

10:09 PM

Company Name: ATI

Technologies Inc.

File Version:

6.14.10.2045 (8.03.98.4.050725)

Driver: atiicdxx.sys

File Size: 5376 (0x1500)

File Date: 11/6/2002

2:48 PM

Company Name: ATI

Technologies Inc.

File Version:

6.13.10.1005

Driver: atiicdxx.vxd

File Size: 7849 (0x1EA9)

File Date: 4/14/2003

8:07 PM

Company Name: ATI

Technologies Inc.

File Version: 4.12.1003

Driver: atiicdxx.dll

File Size: 339968

(0x53000)

File Date: 1/24/2006

10:09 PM

Company Name: ATI

Technologies Inc.

File Version:

6.14.10.2087 (8.03.98.4.050725)

Driver: atiiiexx.dll

File Size: 294912

(0x48000)

File Date: 1/24/2006

10:13 PM

Company Name: ATI

Technologies Inc.

File Version:

6.14.10.4003

Driver: atiiisxx.exe

File Size: 13568

(0x3500)

File Date: 2/11/2002

9:09 PM

Driver: TI2DRAG.DRV

File Size: Driver Not

Installed

File Date: Driver Not

Installed

Driver: ati2edxx.dll

File Size: 30720

(0x7800)

File Date: 1/24/2006

9:42 PM

Company Name: ATI

Technologies, Inc.

File Version: 6, 14, 10,

2494

Driver: Oemdspif.dll

File Size: 102400

(0x19000)

File Date: 1/24/2006

9:42 PM

Company Name: ATI

Technologies, Inc.

File Version: 6.14.0010

Driver: atipdlxx.dll

File Size: 118784

(0x1D000)

File Date: 1/24/2006

9:42 PM

Company Name: ATI

Technologies, Inc.

File Version: 6, 14, 10,

2490

Driver: Ati2evxx.dll

File Size: 86016

(0x15000)

File Date: 1/24/2006

9:42 PM

Driver: Ati2evxx.exe

File Size: 376832

(0x5C000)

File Date: 1/24/2006

9:42 PM

Driver: atitvo32.dll

File Size: 17408

(0x4400)

File Date: 1/24/2006

9:31 PM

Company Name: ATI

Technologies Inc.

File Version:

6.14.10.4100

Driver: ATIDDC.DLL

File Size: 81920

(0x14000)

File Date: 1/24/2006

9:42 PM

Company Name: ATI

Technologies Inc.

File Version: 6.14.10.5

Driver: ATIO9XXX.DLL

File Size: 6582272

(0x647000)

File Date: 1/24/2006

10:02 PM

Company Name: ATI

Technologies Inc.

File Version:

4.14.10.4454

Driver: ATI3D2AG.DLL

File Size: 1294429

(0x13C05D)

File Date: 1/24/2006

9:38 PM

Company Name: ATI

Technologies Inc.

File Version:

4.14.01.4075

Driver: ATI3D1AG.DLL

File Size: 1081437

(0x10805D)

File Date: 1/24/2006

9:36 PM

Company Name: ATI

Technologies Inc.

File Version:

4.14.01.4075

Driver: ATIVVAXX.DLL

File Size: 589930

(0x9006A)

File Date: 1/24/2006

9:33 PM

Company Name: ATI

Technologies Inc.

File Version:

4.14.01.0511

Driver: ATIVVXXX.VXD

File Size: 127134

(0x1F09E)

File Date: 1/24/2006

9:30 PM

Company Name: ATI

Technologies Inc.

File Version: 4.14.7001

Driver: ATIVIFXX.DLL

File Size: 34816

(0x8800)

File Date: 1/24/2006

9:30 PM

Company Name: ATI

Technologies Inc.

File Version: 4.14.3001

Driver: ATIV16XX.DLL

File Size: 7552 (0x1D80)

File Date: 1/24/2006

9:30 PM

Company Name: ATI

Technologies Inc.

File Version: 4.14.3001

Driver: ATI3DUAG.DLL

File Size: 1773654

(0x1B1056)

File Date: 1/24/2006

9:41 PM

Company Name: ATI

Technologies Inc.

File Version:

4.14.01.0512

Driver: ATI2I9AG.DLL

File Size: 1175040

(0x11EE00)

File Date: 1/24/2006

9:43 PM

Company Name: ATI

Technologies Inc.

File Version:

4.15.1.9165

Driver: ati2cqag.DLL

File Size: 225372

(0x3705C)

File Date: 1/24/2006

9:29 PM

Company Name: ATI

Technologies Inc.

File Version:

4.15.1.9165.060124

Driver: ATI2VXAG.VXD

File Size: 465509

(0x71A65)

File Date: 1/24/2006

9:44 PM

Company Name: ATI

Technologies Inc.

File Version:

4.15.1.9165

Driver: ATI2DRAG.DRV

File Size: 86000

(0x14FF0)

File Date: 1/24/2006

9:42 PM

Company Name: ATI

Technologies Inc.

File Version:

4.15.1.9165

ViewSonic VP930 Series

Monitor

Registry Key:

HKEY_LOCAL_MACHINE\enum\MONITOR\VSCE41B\PCI_VEN_1002&DEV_5961&SUBSYS_280117E

E&REV_01_000800

Alloc resources: None

Forced resources: None

Boot resources: None

Filtered resources: None

Basic resources: None

Driver: Monitor\0000

Driver Date: 2-16-2008

Driver: VP930_Series.ICM

File Size: Driver Not

Installed

File Date: Driver Not

Installed

Default Monitor

Monitor

This device is disabled.

Registry Key:

HKEY_LOCAL_MACHINE\enum\MONITOR\DEFAULT_MONITOR\PCI_VEN_1002&DEV_5961&SUBSYS

_280117EE&REV_01_000800_1

Alloc resources: None

Forced resources: None

Boot resources: None

Filtered resources: None

Basic resources: None

Driver: Monitor\0001

Driver Date: 4-23-1999

**********************************************************************

Modified Dates for DRVDATA.bin & DRVIDX.bin : February 25, 2008

**********************************************************************

Post your Autoexec.bat file

SET PATH=%PATH%;C:\PROGRA~1\ATITEC~1\ATICON~1

Post your Config.sys

(Empty)

***********************************************************************

How many Registry keys contain the word "Default_Monitor"?

HKEY_CURRENT_CONFIG\Enum\MONITOR\DEFAULT_MONITOR\{KEY} : {KEY}

HKEY_CURRENT_CONFIG\Enum\MONITOR\DEFAULT_MONITOR\PCI_VEN_1002&DEV_5961&SUBSY

S_280117EE&REV_01_000800_1\{KEY} : {KEY}

HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\cfgmgr32\Phanto

m\3A\HardWareKey :

MONITOR\DEFAULT_MONITOR\PCI_VEN_1002&DEV_5961&SUBSYS_280117EE&REV_01_000800_

1

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

hingDeviceId : Monitor\Default_Monitor

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\ASD\Prob\{CF2524C0-29AE-

11CF-97EA-00AA0034319D}\MONITOR\DEFAULT_MONITOR\PCI_VEN_1002&DEV_5961&SUBSYS

_280117EE&REV_01_000800_1 : N/A

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\ASD\Prob\{9B4E7760-3196-

11CF-97EA-00AA0034319D}\MONITOR\DEFAULT_MONITOR\PCI_VEN_1002&DEV_5961&SUBSYS

_280117EE&REV_01_000800_1 : N/A

HKEY_LOCAL_MACHINE\Enum\MONITOR\DEFAULT_MONITOR\{KEY} : {KEY}

HKEY_LOCAL_MACHINE\Enum\MONITOR\DEFAULT_MONITOR\PCI_VEN_1002&DEV_5961&SUBSYS

_280117EE&REV_01_000800_1\{KEY} : {KEY}

HKEY_LOCAL_MACHINE\Enum\MONITOR\DEFAULT_MONITOR\PCI_VEN_1002&DEV_5961&SUBSYS

_280117EE&REV_01_000800_1\HardwareID : MONITOR\DEFAULT_MONITOR

HKEY_LOCAL_MACHINE\Config\0001\Enum\MONITOR\DEFAULT_MONITOR\{KEY} : {KEY}

HKEY_LOCAL_MACHINE\Config\0001\Enum\MONITOR\DEFAULT_MONITOR\PCI_VEN_1002&DEV

_5961&SUBSYS_280117EE&REV_01_000800_1\{KEY} : {KEY}

March 11, 2008

Re: For PCR, trying to get rid of DEFAULT_MONITOR

Warren wrote:

OK. I see it. I cannot begin to analyze this until tomorrow, though.

Ignore my earlier request for a reposting of this. A bit more is below.

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

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

|

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

| "Mfg"="(Standard monitor types)"

| "DeviceDesc"="Default Monitor"

| "ConfigFlags"=hex:00,00,00,00

|

| **************************************************************

|

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

| "Link"="{4D36E96E-E325-11CE-BFC1-08002BE10318}"

|

[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\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]

| @=""

|

| ********************************************************************

|

| RADEON 9200 SERIES

| Display

| Registry Key:

|

HKEY_LOCAL_MACHINE\enum\PCI\VEN_1002&DEV_5961&SUBSYS_280117EE&REV_01\000

800

....snip of adapter info, which looked fine...

|

| 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

|

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

| Driver Date: 4-23-1999

|

| **********************************************************************

|

| Modified Dates for DRVDATA.bin & DRVIDX.bin : February 25, 2008

|

| **********************************************************************

|

| Post your Autoexec.bat file

| SET PATH=%PATH%;C:\PROGRA~1\ATITEC~1\ATICON~1

|

| Post your Config.sys

| (Empty)

|

***********************************************************************

|

| How many Registry keys contain the word "Default_Monitor"?

|

| HKEY_CURRENT_CONFIG\Enum\MONITOR\DEFAULT_MONITOR\{KEY} : {KEY}

|

HKEY_CURRENT_CONFIG\Enum\MONITOR\DEFAULT_MONITOR\PCI_VEN_1002&DEV_5961&S

UBSY

| S_280117EE&REV_01_000800_1\{KEY} : {KEY}

|

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

|

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

Matc

| hingDeviceId : Monitor\Default_Monitor

|

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\ASD\Prob\{CF2524C0-2

9AE-

|

11CF-97EA-00AA0034319D}\MONITOR\DEFAULT_MONITOR\PCI_VEN_1002&DEV_5961&SU

BSYS

| _280117EE&REV_01_000800_1 : N/A

|

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\ASD\Prob\{9B4E7760-3

196-

|

11CF-97EA-00AA0034319D}\MONITOR\DEFAULT_MONITOR\PCI_VEN_1002&DEV_5961&SU

BSYS

| _280117EE&REV_01_000800_1 : N/A

|

| HKEY_LOCAL_MACHINE\Enum\MONITOR\DEFAULT_MONITOR\{KEY} : {KEY}

|

HKEY_LOCAL_MACHINE\Enum\MONITOR\DEFAULT_MONITOR\PCI_VEN_1002&DEV_5961&SU

BSYS

| _280117EE&REV_01_000800_1\{KEY} : {KEY}

|

HKEY_LOCAL_MACHINE\Enum\MONITOR\DEFAULT_MONITOR\PCI_VEN_1002&DEV_5961&SU

BSYS

| _280117EE&REV_01_000800_1\HardwareID : MONITOR\DEFAULT_MONITOR

|

| HKEY_LOCAL_MACHINE\Config\0001\Enum\MONITOR\DEFAULT_MONITOR\{KEY} :

| {KEY}

|

HKEY_LOCAL_MACHINE\Config\0001\Enum\MONITOR\DEFAULT_MONITOR\PCI_VEN_1002

&DEV

| _5961&SUBSYS_280117EE&REV_01_000800_1\{KEY} : {KEY}

I'll study this tomorrow. For now, I only note my own keys that mention

Default_Monitor are only these three...

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\{9B4E7760

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

MONITOR\DEFAULT_MONITOR\0001 00 <<Binary Value

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

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

MONITOR\DEFAULT_MONITOR\0001 00 <<Binary Value

--

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 11, 2008

Re: For PCR, trying to get rid of DEFAULT_MONITOR

Early in the original discussion, someone {Glen or Brian - indicating

nVidia as example} attempted to advise that some adapter cards and/or

monitor/panel installation files may require a default monitor installation.

OTHER FACTORS FOR CONCIDERATION

1. ENTRIES in win.ini or system.ini

2. These driver files MUST take over [replace] the function of the *default

monitor* in their INF or other during the installation process. Some

drivers/INF install both.

3. A PlugnPlay monitor/display may AUTOMATICALLY make two entries [hard set

in the actual chip - EEPROM via its DDC pins - EDID data], one for itself,

and one for its fallback DEFAULT when it *talks* to the OS during the

discovery process. Removing either entry generally causes them to re-install

as the function is performed at each boot, unless disabled {not

recommended}. When discovery is turned off, a corruption of the display

settings or driver, or a bad re-set call from an application or game or

other, may cause loss of functionality.

These issues were recently discussed in this group [by myself and

others]{nVidia adapter, panel display, other}. I suggest you review those

discussions

--

MEB

http://peoplescounsel.orgfree.com

_________

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

news:eBsIXbxgIHA.748@TK2MSFTNGP04.phx.gbl...

| [HKEY_LOCAL_MACHINE\Enum\MONITOR]

|

| [HKEY_LOCAL_MACHINE\Enum\MONITOR\VSCE41B]

|

[HKEY_LOCAL_MACHINE\Enum\MONITOR\VSCE41B\PCI_VEN_1002&DEV_5961&SUBSYS_280117

| 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,0e,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"

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

|

| [HKEY_LOCAL_MACHINE\Enum\MONITOR\DEFAULT_MONITOR]

|

[HKEY_LOCAL_MACHINE\Enum\MONITOR\DEFAULT_MONITOR\PCI_VEN_1002&DEV_5961&SUBSY

| 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\\0001"

| "Mfg"="(Standard monitor types)"

| "DeviceDesc"="Default Monitor"

| "ConfigFlags"=hex:00,00,00,00

|

| **************************************************************

|

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

| "Link"="{4D36E96E-E325-11CE-BFC1-08002BE10318}"

|

| [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\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]

| @=""

|

| ********************************************************************

|

| RADEON 9200 SERIES

| Display

| Registry Key:

|

HKEY_LOCAL_MACHINE\enum\PCI\VEN_1002&DEV_5961&SUBSYS_280117EE&REV_01\000800

| Alloc resources: Logical Configuration 0

| IRQ: 11 Mask: xFFFF

|

| Forced resources: None

| Boot resources: None

| Filtered resources: Logical Configuration 0

| IRQ: 11 Mask: xFFFF

|

| Basic resources: Logical Configuration 0

| IRQ: 0 Mask: xFFFF

|

| HW Revision: 001

| Driver: Display\0000

| Driver Date: 2- 3-2006

| Driver: vga.drv

| File Size: 52080

| (0xCB70)

| File Date: 4/23/1999

| 10:22 AM

| Company Name:

Microsoft

| Corporation

| File Version:

4.10.1998

| Driver: atricdxx.enu

| File Size: 69632

| (0x11000)

| File Date: 1/24/2006

| 10:09 PM

| Company Name: ATI

| Technologies Inc.

| File Version:

| 6.14.10.2045 (8.03.98.4.050725)

| Driver: atiicdxx.sys

| File Size: 5376

(0x1500)

| File Date: 11/6/2002

| 2:48 PM

| Company Name: ATI

| Technologies Inc.

| File Version:

| 6.13.10.1005

| Driver: atiicdxx.vxd

| File Size: 7849

(0x1EA9)

| File Date: 4/14/2003

| 8:07 PM

| Company Name: ATI

| Technologies Inc.

| File Version:

4.12.1003

| Driver: atiicdxx.dll

| File Size: 339968

| (0x53000)

| File Date: 1/24/2006

| 10:09 PM

| Company Name: ATI

| Technologies Inc.

| File Version:

| 6.14.10.2087 (8.03.98.4.050725)

| Driver: atiiiexx.dll

| File Size: 294912

| (0x48000)

| File Date: 1/24/2006

| 10:13 PM

| Company Name: ATI

| Technologies Inc.

| File Version:

| 6.14.10.4003

| Driver: atiiisxx.exe

| File Size: 13568

| (0x3500)

| File Date: 2/11/2002

| 9:09 PM

| Driver: TI2DRAG.DRV

| File Size: Driver Not

| Installed

| File Date: Driver Not

| Installed

| Driver: ati2edxx.dll

| File Size: 30720

| (0x7800)

| File Date: 1/24/2006

| 9:42 PM

| Company Name: ATI

| Technologies, Inc.

| File Version: 6, 14,

10,

| 2494

| Driver: Oemdspif.dll

| File Size: 102400

| (0x19000)

| File Date: 1/24/2006

| 9:42 PM

| Company Name: ATI

| Technologies, Inc.

| File Version:

6.14.0010

| Driver: atipdlxx.dll

| File Size: 118784

| (0x1D000)

| File Date: 1/24/2006

| 9:42 PM

| Company Name: ATI

| Technologies, Inc.

| File Version: 6, 14,

10,

| 2490

| Driver: Ati2evxx.dll

| File Size: 86016

| (0x15000)

| File Date: 1/24/2006

| 9:42 PM

| Driver: Ati2evxx.exe

| File Size: 376832

| (0x5C000)

| File Date: 1/24/2006

| 9:42 PM

| Driver: atitvo32.dll

| File Size: 17408

| (0x4400)

| File Date: 1/24/2006

| 9:31 PM

| Company Name: ATI

| Technologies Inc.

| File Version:

| 6.14.10.4100

| Driver: ATIDDC.DLL

| File Size: 81920

| (0x14000)

| File Date: 1/24/2006

| 9:42 PM

| Company Name: ATI

| Technologies Inc.

| File Version:

6.14.10.5

| Driver: ATIO9XXX.DLL

| File Size: 6582272

| (0x647000)

| File Date: 1/24/2006

| 10:02 PM

| Company Name: ATI

| Technologies Inc.

| File Version:

| 4.14.10.4454

| Driver: ATI3D2AG.DLL

| File Size: 1294429

| (0x13C05D)

| File Date: 1/24/2006

| 9:38 PM

| Company Name: ATI

| Technologies Inc.

| File Version:

| 4.14.01.4075

| Driver: ATI3D1AG.DLL

| File Size: 1081437

| (0x10805D)

| File Date: 1/24/2006

| 9:36 PM

| Company Name: ATI

| Technologies Inc.

| File Version:

| 4.14.01.4075

| Driver: ATIVVAXX.DLL

| File Size: 589930

| (0x9006A)

| File Date: 1/24/2006

| 9:33 PM

| Company Name: ATI

| Technologies Inc.

| File Version:

| 4.14.01.0511

| Driver: ATIVVXXX.VXD

| File Size: 127134

| (0x1F09E)

| File Date: 1/24/2006

| 9:30 PM

| Company Name: ATI

| Technologies Inc.

| File Version:

4.14.7001

| Driver: ATIVIFXX.DLL

| File Size: 34816

| (0x8800)

| File Date: 1/24/2006

| 9:30 PM

| Company Name: ATI

| Technologies Inc.

| File Version:

4.14.3001

| Driver: ATIV16XX.DLL

| File Size: 7552

(0x1D80)

| File Date: 1/24/2006

| 9:30 PM

| Company Name: ATI

| Technologies Inc.

| File Version:

4.14.3001

| Driver: ATI3DUAG.DLL

| File Size: 1773654

| (0x1B1056)

| File Date: 1/24/2006

| 9:41 PM

| Company Name: ATI

| Technologies Inc.

| File Version:

| 4.14.01.0512

| Driver: ATI2I9AG.DLL

| File Size: 1175040

| (0x11EE00)

| File Date: 1/24/2006

| 9:43 PM

| Company Name: ATI

| Technologies Inc.

| File Version:

| 4.15.1.9165

| Driver: ati2cqag.DLL

| File Size: 225372

| (0x3705C)

| File Date: 1/24/2006

| 9:29 PM

| Company Name: ATI

| Technologies Inc.

| File Version:

| 4.15.1.9165.060124

| Driver: ATI2VXAG.VXD

| File Size: 465509

| (0x71A65)

| File Date: 1/24/2006

| 9:44 PM

| Company Name: ATI

| Technologies Inc.

| File Version:

| 4.15.1.9165

| Driver: ATI2DRAG.DRV

| File Size: 86000

| (0x14FF0)

| File Date: 1/24/2006

| 9:42 PM

| Company Name: ATI

| Technologies Inc.

| File Version:

| 4.15.1.9165

|

| ViewSonic VP930 Series

| Monitor

| Registry Key:

|

HKEY_LOCAL_MACHINE\enum\MONITOR\VSCE41B\PCI_VEN_1002&DEV_5961&SUBSYS_280117E

| E&REV_01_000800

| Alloc resources: None

| Forced resources: None

| Boot resources: None

| Filtered resources: None

| Basic resources: None

| Driver: Monitor\0000

| Driver Date: 2-16-2008

| Driver: VP930_Series.ICM

| File Size: Driver Not

| Installed

| File Date: Driver Not

| Installed

|

| Default Monitor

| Monitor

| This device is disabled.

| Registry Key:

|

HKEY_LOCAL_MACHINE\enum\MONITOR\DEFAULT_MONITOR\PCI_VEN_1002&DEV_5961&SUBSYS

| _280117EE&REV_01_000800_1

| Alloc resources: None

| Forced resources: None

| Boot resources: None

| Filtered resources: None

| Basic resources: None

| Driver: Monitor\0001

| Driver Date: 4-23-1999

|

| **********************************************************************

|

| Modified Dates for DRVDATA.bin & DRVIDX.bin : February 25, 2008

|

| **********************************************************************

|

| Post your Autoexec.bat file

| SET PATH=%PATH%;C:\PROGRA~1\ATITEC~1\ATICON~1

|

| Post your Config.sys

| (Empty)

|

| ***********************************************************************

|

| How many Registry keys contain the word "Default_Monitor"?

|

| HKEY_CURRENT_CONFIG\Enum\MONITOR\DEFAULT_MONITOR\{KEY} : {KEY}

|

HKEY_CURRENT_CONFIG\Enum\MONITOR\DEFAULT_MONITOR\PCI_VEN_1002&DEV_5961&SUBSY

| S_280117EE&REV_01_000800_1\{KEY} : {KEY}

|

HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\cfgmgr32\Phanto

| m\3A\HardWareKey :

|

MONITOR\DEFAULT_MONITOR\PCI_VEN_1002&DEV_5961&SUBSYS_280117EE&REV_01_000800_

| 1

|

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

| hingDeviceId : Monitor\Default_Monitor

|

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\ASD\Prob\{CF2524C0-29AE-

|

11CF-97EA-00AA0034319D}\MONITOR\DEFAULT_MONITOR\PCI_VEN_1002&DEV_5961&SUBSYS

| _280117EE&REV_01_000800_1 : N/A

|

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\ASD\Prob\{9B4E7760-3196-

|

11CF-97EA-00AA0034319D}\MONITOR\DEFAULT_MONITOR\PCI_VEN_1002&DEV_5961&SUBSYS

| _280117EE&REV_01_000800_1 : N/A

|

| HKEY_LOCAL_MACHINE\Enum\MONITOR\DEFAULT_MONITOR\{KEY} : {KEY}

|

HKEY_LOCAL_MACHINE\Enum\MONITOR\DEFAULT_MONITOR\PCI_VEN_1002&DEV_5961&SUBSYS

| _280117EE&REV_01_000800_1\{KEY} : {KEY}

|

HKEY_LOCAL_MACHINE\Enum\MONITOR\DEFAULT_MONITOR\PCI_VEN_1002&DEV_5961&SUBSYS

| _280117EE&REV_01_000800_1\HardwareID : MONITOR\DEFAULT_MONITOR

|

| HKEY_LOCAL_MACHINE\Config\0001\Enum\MONITOR\DEFAULT_MONITOR\{KEY} : {KEY}

|

HKEY_LOCAL_MACHINE\Config\0001\Enum\MONITOR\DEFAULT_MONITOR\PCI_VEN_1002&DEV

| _5961&SUBSYS_280117EE&REV_01_000800_1\{KEY} : {KEY}

|

March 11, 2008

Re: For PCR, trying to get rid of DEFAULT_MONITOR

MEB wrote:

> Early in the original discussion, someone {Glen or Brian -

> indicating nVidia as example} attempted to advise that some adapter

> cards and/or monitor/panel installation files may require a default

> monitor installation.

ME, ME, it was me!

Wait. Attempted? I thought I was pretty clear :)

--

dadiOH

____________________________

dadiOH's dandies v3.06...

....a help file of info about MP3s, recording from

LP/cassette and tips & tricks on this and that.

Get it at http://mysite.verizon.net/xico

March 12, 2008

Re: For PCR, trying to get rid of DEFAULT_MONITOR

MEB wrote:

| Early in the original discussion, someone {Glen or Brian -

| indicating nVidia as example} attempted to advise that some adapter

| cards and/or monitor/panel installation files may require a default

| monitor installation.

I can't recall whether it was Glen or Brian A. or dadiOH who attempted

to explain that. But I'm reserving it for my own possible explanation on

the day I run out of ideas for a fix. On that day, I'll change the

spelling of some of the words to make it look more original.

HOWEVER, I did elicit the actual name of Warren's video adapter (RADEON

9200 SERIES) for a Google search, & here it is...

http://www.google.com/search?hl=en&q=RADEON+9200++Default_Monitor

Google found about 56 mentionings of that. I haven't yet found an answer

there after the first handful.

| OTHER FACTORS FOR CONCIDERATION

|

| 1. ENTRIES in win.ini or system.ini

I'll get to it, if necessary. "START button, Run, SysEdit" will show

those files.

My own WIN.INI & SYSTEM.INI do not contain the word "monitor". Here are

sections that have monitor-related info.

Warren, is anything in your own files that seems monitor-related

different from what I've got, or do you have another section that seems

monitor-related...?...

WIN.INI

[Devices]

Compaq IJ300=wwcij3,LPT1:

SYSTEM.INI

[boot]

*DisplayFallback=0

display.drv=pnpdrvr.drv

[boot.description]

display.drv=Trident Blade3D/MVP4 (63)

[386Enh]

display=*vdd,*vflatd

[DISPLAY]

BusThrottle=1

| 2. These driver files MUST take over [replace] the function of the

| *default monitor* in their INF or other during the installation

| process. Some drivers/INF install both.

No! I've looked at & even have a copy of Warren's VS080114_I19.inf on my

desktop. There is nothing in it (monster that it is!) that creates a

Default_Monitor!

| 3. A PlugnPlay monitor/display may AUTOMATICALLY make two entries

| [hard set in the actual chip - EEPROM via its DDC pins - EDID data],

| one for itself, and one for its fallback DEFAULT when it *talks* to

| the OS during the discovery process. Removing either entry generally

| causes them to re-install as the function is performed at each boot,

| unless disabled {not recommended}. When discovery is turned off, a

| corruption of the display settings or driver, or a bad re-set call

| from an application or game or other, may cause loss of functionality.

I'll change the spelling & reserve that as another possible

explanation-- if/when all else fails!

| These issues were recently discussed in this group [by myself and

| others]{nVidia adapter, panel display, other}. I suggest you review

| those discussions

|

| --

|

| MEB

| http://peoplescounsel.orgfree.com

| _________

|

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

| news:eBsIXbxgIHA.748@TK2MSFTNGP04.phx.gbl...

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

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

||

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

|| "Mfg"="(Standard monitor types)"

|| "DeviceDesc"="Default Monitor"

|| "ConfigFlags"=hex:00,00,00,00

||

|| **************************************************************

||

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

|| "Link"="{4D36E96E-E325-11CE-BFC1-08002BE10318}"

||

[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\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]

|| @=""

||

|| ********************************************************************

||

|| RADEON 9200 SERIES

|| Display

|| Registry Key:

||

|

HKEY_LOCAL_MACHINE\enum\PCI\VEN_1002&DEV_5961&SUBSYS_280117EE&REV_01\000

800

|| Alloc resources: Logical Configuration 0

|| IRQ: 11 Mask: xFFFF

||

|| Forced resources: None

|| Boot resources: None

|| Filtered resources: Logical Configuration 0

|| IRQ: 11 Mask: xFFFF

||

|| Basic resources: Logical Configuration 0

|| IRQ: 0 Mask: xFFFF

||

|| HW Revision: 001

|| Driver: Display\0000

|| Driver Date: 2- 3-2006

|| Driver: vga.drv

|| File Size: 52080

|| (0xCB70)

|| File Date:

|| 4/23/1999 10:22 AM

|| Company Name:

|| Microsoft Corporation

|| File Version:

|| 4.10.1998 Driver:

|| atricdxx.enu

|| File Size: 69632 (0x11000)

|| File Date:

|| 1/24/2006 10:09 PM

|| Company Name: ATI

|| Technologies Inc.

|| File Version:

|| 6.14.10.2045 (8.03.98.4.050725)

|| Driver: atiicdxx.sys

|| File Size: 5376

|| (0x1500) File

|| Date: 11/6/2002 2:48 PM

|| Company Name: ATI

|| Technologies Inc.

|| File Version:

|| 6.13.10.1005

|| Driver: atiicdxx.vxd

|| File Size: 7849

|| (0x1EA9) File

|| Date: 4/14/2003 8:07 PM

|| Company Name: ATI

|| Technologies Inc.

|| File Version:

|| 4.12.1003 Driver:

|| atiicdxx.dll

|| File Size: 339968 (0x53000)

|| File Date:

|| 1/24/2006 10:09 PM

|| Company Name: ATI

|| Technologies Inc.

|| File Version:

|| 6.14.10.2087 (8.03.98.4.050725)

|| Driver: atiiiexx.dll

|| File Size: 294912

|| (0x48000)

|| File Date:

|| 1/24/2006 10:13 PM

|| Company Name: ATI

|| Technologies Inc.

|| File Version:

|| 6.14.10.4003

|| Driver: atiiisxx.exe

|| File Size: 13568

|| (0x3500)

|| File Date:

|| 2/11/2002 9:09 PM

|| Driver: TI2DRAG.DRV

|| File Size:

|| Driver Not Installed

|| File Date:

|| Driver Not Installed

|| Driver: ati2edxx.dll

|| File Size: 30720

|| (0x7800)

|| File Date:

|| 1/24/2006 9:42 PM

|| Company Name: ATI

|| Technologies, Inc.

|| File Version: 6,

|| 14, 10, 2494

|| Driver: Oemdspif.dll

|| File Size: 102400

|| (0x19000)

|| File Date:

|| 1/24/2006 9:42 PM

|| Company Name: ATI

|| Technologies, Inc.

|| File Version:

|| 6.14.0010 Driver:

|| atipdlxx.dll

|| File Size: 118784 (0x1D000)

|| File Date:

|| 1/24/2006 9:42 PM

|| Company Name: ATI

|| Technologies, Inc.

|| File Version: 6,

|| 14, 10, 2490

|| Driver: Ati2evxx.dll

|| File Size: 86016

|| (0x15000)

|| File Date:

|| 1/24/2006 9:42 PM

|| Driver: Ati2evxx.exe

|| File Size: 376832

|| (0x5C000)

|| File Date:

|| 1/24/2006 9:42 PM

|| Driver: atitvo32.dll

|| File Size: 17408

|| (0x4400)

|| File Date:

|| 1/24/2006 9:31 PM

|| Company Name: ATI

|| Technologies Inc.

|| File Version:

|| 6.14.10.4100

|| Driver: ATIDDC.DLL

|| File Size: 81920

|| (0x14000)

|| File Date:

|| 1/24/2006 9:42 PM

|| Company Name:

|| ATI Technologies Inc.

|| File Version:

|| 6.14.10.5 Driver:

|| ATIO9XXX.DLL

|| File Size: 6582272 (0x647000)

|| File Date:

|| 1/24/2006 10:02 PM

|| Company Name: ATI

|| Technologies Inc.

|| File Version:

|| 4.14.10.4454

|| Driver: ATI3D2AG.DLL

|| File Size:

|| 1294429 (0x13C05D)

|| File Date:

|| 1/24/2006 9:38 PM

|| Company Name: ATI

|| Technologies Inc.

|| File Version:

|| 4.14.01.4075

|| Driver: ATI3D1AG.DLL

|| File Size:

|| 1081437 (0x10805D)

|| File Date:

|| 1/24/2006 9:36 PM

|| Company Name: ATI

|| Technologies Inc.

|| File Version:

|| 4.14.01.4075

|| Driver: ATIVVAXX.DLL

|| File Size: 589930

|| (0x9006A)

|| File Date:

|| 1/24/2006 9:33 PM

|| Company Name: ATI

|| Technologies Inc.

|| File Version:

|| 4.14.01.0511

|| Driver: ATIVVXXX.VXD

|| File Size: 127134

|| (0x1F09E)

|| File Date:

|| 1/24/2006 9:30 PM

|| Company Name: ATI

|| Technologies Inc.

|| File Version:

|| 4.14.7001 Driver:

|| ATIVIFXX.DLL

|| File Size: 34816 (0x8800)

|| File Date:

|| 1/24/2006 9:30 PM

|| Company Name: ATI

|| Technologies Inc.

|| File Version:

|| 4.14.3001 Driver:

|| ATIV16XX.DLL

|| File Size: 7552

|| (0x1D80) File Date: 1/24/2006 9:30 PM

|| Company Name: ATI

|| Technologies Inc.

|| File Version:

|| 4.14.3001 Driver:

|| ATI3DUAG.DLL

|| File Size: 1773654 (0x1B1056)

|| File Date:

|| 1/24/2006 9:41 PM

|| Company Name: ATI

|| Technologies Inc.

|| File Version:

|| 4.14.01.0512

|| Driver: ATI2I9AG.DLL

|| File Size:

|| 1175040 (0x11EE00)

|| File Date:

|| 1/24/2006 9:43 PM

|| Company Name: ATI

|| Technologies Inc.

|| File Version:

|| 4.15.1.9165

|| Driver: ati2cqag.DLL

|| File Size: 225372

|| (0x3705C)

|| File Date:

|| 1/24/2006 9:29 PM

|| Company Name: ATI

|| Technologies Inc.

|| File Version:

|| 4.15.1.9165.060124

|| Driver: ATI2VXAG.VXD

|| File Size: 465509

|| (0x71A65)

|| File Date:

|| 1/24/2006 9:44 PM

|| Company Name: ATI

|| Technologies Inc.

|| File Version:

|| 4.15.1.9165

|| Driver: ATI2DRAG.DRV

|| File Size: 86000

|| (0x14FF0)

|| File Date:

|| 1/24/2006 9:42 PM

|| Company Name: ATI

|| Technologies Inc.

|| File Version:

|| 4.15.1.9165

||

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

||

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

|| Driver Date: 4-23-1999

||

**********************************************************************

||

|| Modified Dates for DRVDATA.bin & DRVIDX.bin : February 25, 2008

||

**********************************************************************

||

|| Post your Autoexec.bat file

|| SET PATH=%PATH%;C:\PROGRA~1\ATITEC~1\ATICON~1

||

|| Post your Config.sys

|| (Empty)

||

***********************************************************************

||

|| How many Registry keys contain the word "Default_Monitor"?

||

|| HKEY_CURRENT_CONFIG\Enum\MONITOR\DEFAULT_MONITOR\{KEY} : {KEY}

||

|

HKEY_CURRENT_CONFIG\Enum\MONITOR\DEFAULT_MONITOR\PCI_VEN_1002&DEV_5961&S

UBSY

|| S_280117EE&REV_01_000800_1\{KEY} : {KEY}

||

|

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

||

|

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

Matc

|| hingDeviceId : Monitor\Default_Monitor

||

|

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\ASD\Prob\{CF2524C0-2

9AE-

||

|

11CF-97EA-00AA0034319D}\MONITOR\DEFAULT_MONITOR\PCI_VEN_1002&DEV_5961&SU

BSYS

|| _280117EE&REV_01_000800_1 : N/A

||

|

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\ASD\Prob\{9B4E7760-3

196-

||

|

11CF-97EA-00AA0034319D}\MONITOR\DEFAULT_MONITOR\PCI_VEN_1002&DEV_5961&SU

BSYS

|| _280117EE&REV_01_000800_1 : N/A

||

|| HKEY_LOCAL_MACHINE\Enum\MONITOR\DEFAULT_MONITOR\{KEY} : {KEY}

||

|

HKEY_LOCAL_MACHINE\Enum\MONITOR\DEFAULT_MONITOR\PCI_VEN_1002&DEV_5961&SU

BSYS

|| _280117EE&REV_01_000800_1\{KEY} : {KEY}

||

|

HKEY_LOCAL_MACHINE\Enum\MONITOR\DEFAULT_MONITOR\PCI_VEN_1002&DEV_5961&SU

BSYS

|| _280117EE&REV_01_000800_1\HardwareID : MONITOR\DEFAULT_MONITOR

||

|| HKEY_LOCAL_MACHINE\Config\0001\Enum\MONITOR\DEFAULT_MONITOR\{KEY} :

|| {KEY}

||

|

HKEY_LOCAL_MACHINE\Config\0001\Enum\MONITOR\DEFAULT_MONITOR\PCI_VEN_1002

&DEV

|| _5961&SUBSYS_280117EE&REV_01_000800_1\{KEY} : {KEY}

--

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 12, 2008

Re: For PCR, trying to get rid of DEFAULT_MONITOR

PCR wrote:

....snip

| HOWEVER, I did elicit the actual name of Warren's video adapter

| (RADEON 9200 SERIES) for a Google search, & here it is...

|

| http://www.google.com/search?hl=en&q=RADEON+9200++Default_Monitor

| Google found about 56 mentionings of that. I haven't yet found an

| answer there after the first handful.

Forget that. All of them that were in English were ours or otherwise

unhelpful.

March 12, 2008

Re: For PCR, trying to get rid of DEFAULT_MONITOR

Hi PCR,

I have even less monitor related information in my files than you have.

WIN INI has no reference to monitors under [Devices] or otherwise.

SYSTEM INI has the same entries as you except the [boot

description]display.drv = Radeon 9200 Series and I don't have a [DISPLAY]

heading

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

news:%23oLRqT9gIHA.2268@TK2MSFTNGP02.phx.gbl...

> MEB wrote:

> | Early in the original discussion, someone {Glen or Brian -

> | indicating nVidia as example} attempted to advise that some adapter

> | cards and/or monitor/panel installation files may require a default

> | monitor installation.

>

> I can't recall whether it was Glen or Brian A. or dadiOH who attempted

> to explain that. But I'm reserving it for my own possible explanation on

> the day I run out of ideas for a fix. On that day, I'll change the

> spelling of some of the words to make it look more original.

>

> HOWEVER, I did elicit the actual name of Warren's video adapter (RADEON

> 9200 SERIES) for a Google search, & here it is...

>

> http://www.google.com/search?hl=en&q=RADEON+9200++Default_Monitor

> Google found about 56 mentionings of that. I haven't yet found an answer

> there after the first handful.

>

> | OTHER FACTORS FOR CONCIDERATION

> |

> | 1. ENTRIES in win.ini or system.ini

>

> I'll get to it, if necessary. "START button, Run, SysEdit" will show

> those files.

>

> My own WIN.INI & SYSTEM.INI do not contain the word "monitor". Here are

> sections that have monitor-related info.

>

> Warren, is anything in your own files that seems monitor-related

> different from what I've got, or do you have another section that seems

> monitor-related...?...

>

> WIN.INI

>

> [Devices]

> Compaq IJ300=wwcij3,LPT1:

>

> SYSTEM.INI

>

> [boot]

> *DisplayFallback=0

> display.drv=pnpdrvr.drv

>

> [boot.description]

> display.drv=Trident Blade3D/MVP4 (63)

>

> [386Enh]

> display=*vdd,*vflatd

>

> [DISPLAY]

> BusThrottle=1

March 12, 2008

Re: For PCR, trying to get rid of DEFAULT_MONITOR

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

thoughts...

Warren wrote:

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

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

The above continues to look fine to me. It very closely matches my own,

though I have a different LCD monitor than yours. The only value up

there I don't have is...

"CompatibleIDs"="*PNP09FF"

...., but I have no reason to suspect that relates to the Default Monitor

problem. Does "PNP09FF" appear anywhere else in your Registry? It is

nowhere in mine.

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

| "Mfg"="(Standard monitor types)"

| "DeviceDesc"="Default Monitor"

| "ConfigFlags"=hex:00,00,00,00

The above continues to look fine to me-- except I don't have one & you

don't want yours! I'm not ready to give up yet!

| **************************************************************

|

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

| "Link"="{4D36E96E-E325-11CE-BFC1-08002BE10318}"

|

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

The above looks fine & matches mine very well.

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

| @=""

The above looks fine-- except you don't want it & I have none!

********************************************************************

|

| RADEON 9200 SERIES

| Display

| Registry Key:

|

HKEY_LOCAL_MACHINE\enum\PCI\VEN_1002&DEV_5961&SUBSYS_280117EE&REV_01\000

800

....snip of the Video Adapter info, but it looked a lot like mine...

| 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 continues to look just fine-- just like mine!

| Default Monitor

| Monitor

| This device is disabled.

You have disabled it again? Remember to enable it again, if we decide to

try another remove of the default monitor in Device Manager. And that

might be worth one last try-- now that your monster Registry key...

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Monitor

....has only two entries.

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

| Driver Date: 4-23-1999

The above looks fine-- except it is unwanted!

**********************************************************************

|

| Modified Dates for DRVDATA.bin & DRVIDX.bin : February 25, 2008

Those dates look good. They prove the monitor is not regenerating on its

own at every boot.

**********************************************************************

|

| Post your Autoexec.bat file

| SET PATH=%PATH%;C:\PROGRA~1\ATITEC~1\ATICON~1

|

| Post your Config.sys

| (Empty)

Fine. There is nothing in them possibly causing the generation of a

monitor before Windows is fully booted. Check your Win.ini & System.ini,

as I described in a response to MEB below.

***********************************************************************

|

| How many Registry keys contain the word "Default_Monitor"?

|

| HKEY_CURRENT_CONFIG\Enum\MONITOR\DEFAULT_MONITOR\{KEY} : {KEY}

|

HKEY_CURRENT_CONFIG\Enum\MONITOR\DEFAULT_MONITOR\PCI_VEN_1002&DEV_5961&S

UBSY

| S_280117EE&REV_01_000800_1\{KEY} : {KEY}

HKEY_CURRENT_CONFIG is a mirror key of HKEY_LOCAL_MACHINE, meaning they

are one & the same. But...

(a) My own HKEY_CURRENT_CONFIG\Enum has no MONITOR

(or much of anything) under it.

(b) I have read here that some keys won't go, unless they

are deleted from the mirror.

Therefore, open RegEdit to each in turn...

HKEY_CURRENT_CONFIG\Enum\MONITOR

HKEY_LOCAL_MACHINE\Enum\MONITOR

...., & delete just the Default_Monitor under each of them in the left

pane. Close RegEdit & reboot. Is it gone?

Note: After deleting one of them, you may discover the other is gone

too. But may as try anyhow.

|

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

Maybe try the above suggestion first, & consider the following, but

don't necessarily try it at the same time...

Well... my cfgmgr32 looks different from yours. Are you experienced

enough to get to that key & make it look like mine, after exporting what

you've got...?...

HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\cfgmgr32

\Phantom\C

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

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

Matc

| hingDeviceId : Monitor\Default_Monitor

That one we hope will go away on its own-- OR, maybe delete it with the

two ENUM Default_Monitors above.

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\ASD\Prob\{CF2524C0-2

9AE-

|

11CF-97EA-00AA0034319D}\MONITOR\DEFAULT_MONITOR\PCI_VEN_1002&DEV_5961&SU

BSYS

| _280117EE&REV_01_000800_1 : N/A

Again, that is different...

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

196-

|

11CF-97EA-00AA0034319D}\MONITOR\DEFAULT_MONITOR\PCI_VEN_1002&DEV_5961&SU

BSYS

| _280117EE&REV_01_000800_1 : N/A

That too...

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

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

MONITOR\DEFAULT_MONITOR\0001 00 <<Binary Value

| HKEY_LOCAL_MACHINE\Enum\MONITOR\DEFAULT_MONITOR\{KEY} : {KEY}

|

HKEY_LOCAL_MACHINE\Enum\MONITOR\DEFAULT_MONITOR\PCI_VEN_1002&DEV_5961&SU

BSYS

| _280117EE&REV_01_000800_1\{KEY} : {KEY}

|

HKEY_LOCAL_MACHINE\Enum\MONITOR\DEFAULT_MONITOR\PCI_VEN_1002&DEV_5961&SU

BSYS

| _280117EE&REV_01_000800_1\HardwareID : MONITOR\DEFAULT_MONITOR

Those two are covered above.

| HKEY_LOCAL_MACHINE\Config\0001\Enum\MONITOR\DEFAULT_MONITOR\{KEY} :

| {KEY}

|

HKEY_LOCAL_MACHINE\Config\0001\Enum\MONITOR\DEFAULT_MONITOR\PCI_VEN_1002

&DEV

| _5961&SUBSYS_280117EE&REV_01_000800_1\{KEY} : {KEY}

Under HKEY_LOCAL_MACHINE\Config\0001\Enum, all I have is ACPI. So,

delete this one as I suggested above.

REMEMBER... If things go horribly wrong, you can do that "ScanReg

/Restore" in DOS to get back your current Registry. Choose the one of

date you make the changes, because the Registry backups are done at

boot-- the 1st boot to Normal Mode of each day.

--

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 12, 2008

Re: For PCR, trying to get rid of DEFAULT_MONITOR

Warren wrote:

| Hi PCR,

|

| I have even less monitor related information in my files than you

| have.

|

| WIN INI has no reference to monitors under [Devices] or otherwise.

|

| SYSTEM INI has the same entries as you except the [boot

| description]display.drv = Radeon 9200 Series and I don't have a

| [DISPLAY] heading

OK. That sounds fine. No problem there I can detect. I've just posted

something else. Here again is how to do that /Restore-- if it should

prove to be necessary (i.e., we make a complete mess of your

Registry)...

I'm not a big proponent of a "/Restore", but sometimes it can do amazing

things. Maybe, before trying it, copy your current Registry backup files

to a new folder.

(a) Boot to DOS (hold CTRL as you boot for the Startup Menu, &

select "Command Prompt Only")

(b) DIR C:\Windows\Sysbckup\RB???.cab /od

Shows you the current backups sorted by date.

This makes a new folder named RegBckup.

(d) COPY C:\Windows\Sysbckup\RB???.cab C:\RegBckup

This copies your Registry backups to the new folder, because the

originals will change as you do the following...

(e) SCANREG /Restore

It will offer five, one for each of the last five separate days you

first booted successfully. Start with the one of the day the problem

began, as these backups of the entire Registry (& System.ini & Win.ini)

are done at boot, not at shut down.

CAVEAT: A /Restore restores settings only. If there was a file change

(other than to System.ini & Win.ini), those cannot be undone this way.

That could be a problem, especially if there was a hardware change or

large un/in-stall since the backup was made. Also, a large settings

change, such as adding/removing a User Profile, is likely best undone a

different way. Finally, some apps may keep a small database in the

Registry. I do believe Explorer itself may keep its list of blocked

sites there.

|

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

| news:%23oLRqT9gIHA.2268@TK2MSFTNGP02.phx.gbl...

|> MEB wrote:

|> | Early in the original discussion, someone {Glen or Brian -

|> | indicating nVidia as example} attempted to advise that some adapter

|> | cards and/or monitor/panel installation files may require a default

|> | monitor installation.

|>

|> I can't recall whether it was Glen or Brian A. or dadiOH who

|> attempted to explain that. But I'm reserving it for my own possible

|> explanation on the day I run out of ideas for a fix. On that day,

|> I'll change the spelling of some of the words to make it look more

|> original.

|>

|> HOWEVER, I did elicit the actual name of Warren's video adapter

|> (RADEON 9200 SERIES) for a Google search, & here it is...

|>

|> http://www.google.com/search?hl=en&q=RADEON+9200++Default_Monitor

|> Google found about 56 mentionings of that. I haven't yet found an

|> answer there after the first handful.

|>

|> | OTHER FACTORS FOR CONCIDERATION

|> |

|> | 1. ENTRIES in win.ini or system.ini

|>

|> I'll get to it, if necessary. "START button, Run, SysEdit" will show

|> those files.

|>

|> My own WIN.INI & SYSTEM.INI do not contain the word "monitor". Here

|> are sections that have monitor-related info.

|>

|> Warren, is anything in your own files that seems monitor-related

|> different from what I've got, or do you have another section that

|> seems monitor-related...?...

|>

|> WIN.INI

|>

|> [Devices]

|> Compaq IJ300=wwcij3,LPT1:

|>

|> SYSTEM.INI

|>

|> [boot]

|> *DisplayFallback=0

|> display.drv=pnpdrvr.drv

|>

|> [boot.description]

|> display.drv=Trident Blade3D/MVP4 (63)

|>

|> [386Enh]

|> display=*vdd,*vflatd

|>

|> [DISPLAY]

|> BusThrottle=1

--

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 12, 2008

Re: For PCR, trying to get rid of DEFAULT_MONITOR

This is probably a reply 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...

>

> Warren wrote:

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

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

>

> The above continues to look fine to me. It very closely matches my own,

> though I have a different LCD monitor than yours. The only value up

> there I don't have is...

>

> "CompatibleIDs"="*PNP09FF"

>

> ..., but I have no reason to suspect that relates to the Default Monitor

> problem. Does "PNP09FF" appear anywhere else in your Registry? It is

> nowhere in mine.

>

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

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

> | "DeviceDesc"="Default Monitor"

> | "ConfigFlags"=hex:00,00,00,00

>

> The above continues to look fine to me-- except I don't have one & you

> don't want yours! I'm not ready to give up yet!

>

> | **************************************************************

> |

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

> | "Link"="{4D36E96E-E325-11CE-BFC1-08002BE10318}"

> |

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

>

> The above looks fine & matches mine very well.

>

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

> | @=""

>

> The above looks fine-- except you don't want it & I have none!

>

> ********************************************************************

> |

> | RADEON 9200 SERIES

> | Display

> | Registry Key:

> |

> HKEY_LOCAL_MACHINE\enum\PCI\VEN_1002&DEV_5961&SUBSYS_280117EE&REV_01\000

> 800

>

> ...snip of the Video Adapter info, but it looked a lot like mine...

> | 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 continues to look just fine-- just like mine!

>

> | Default Monitor

> | Monitor

> | This device is disabled.

>

> You have disabled it again? Remember to enable it again, if we decide to

> try another remove of the default monitor in Device Manager. And that

> might be worth one last try-- now that your monster Registry key...

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

> ...has only two entries.

>

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

> | Driver Date: 4-23-1999

>

> The above looks fine-- except it is unwanted!

>

> **********************************************************************

> |

> | Modified Dates for DRVDATA.bin & DRVIDX.bin : February 25, 2008

>

> Those dates look good. They prove the monitor is not regenerating on its

> own at every boot.

>

> **********************************************************************

> |

> | Post your Autoexec.bat file

> | SET PATH=%PATH%;C:\PROGRA~1\ATITEC~1\ATICON~1

> |

> | Post your Config.sys

> | (Empty)

>

> Fine. There is nothing in them possibly causing the generation of a

> monitor before Windows is fully booted. Check your Win.ini & System.ini,

> as I described in a response to MEB below.

>

> ***********************************************************************

> |

> | How many Registry keys contain the word "Default_Monitor"?

> |

> | HKEY_CURRENT_CONFIG\Enum\MONITOR\DEFAULT_MONITOR\{KEY} : {KEY}

> |

> HKEY_CURRENT_CONFIG\Enum\MONITOR\DEFAULT_MONITOR\PCI_VEN_1002&DEV_5961&S

> UBSY

> | S_280117EE&REV_01_000800_1\{KEY} : {KEY}

>

> HKEY_CURRENT_CONFIG is a mirror key of HKEY_LOCAL_MACHINE, meaning they

> are one & the same. But...

>

> (a) My own HKEY_CURRENT_CONFIG\Enum has no MONITOR

> (or much of anything) under it.

> (b) I have read here that some keys won't go, unless they

> are deleted from the mirror.

>

> Therefore, open RegEdit to each in turn...

>

> HKEY_CURRENT_CONFIG\Enum\MONITOR

> HKEY_LOCAL_MACHINE\Enum\MONITOR

>

> ..., & delete just the Default_Monitor under each of them in the left

> pane. Close RegEdit & reboot. Is it gone?

>

> Note: After deleting one of them, you may discover the other is gone

> too. But may as try anyhow.

>

> |

> 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

>

> Maybe try the above suggestion first, & consider the following, but

> don't necessarily try it at the same time...

>

> Well... my cfgmgr32 looks different from yours. Are you experienced

> enough to get to that key & make it look like mine, after exporting what

> you've got...?...

>

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

> \Phantom\C

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

>

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

> Matc

> | hingDeviceId : Monitor\Default_Monitor

>

> That one we hope will go away on its own-- OR, maybe delete it with the

> two ENUM Default_Monitors above.

>

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

> 9AE-

> |

> 11CF-97EA-00AA0034319D}\MONITOR\DEFAULT_MONITOR\PCI_VEN_1002&DEV_5961&SU

> BSYS

> | _280117EE&REV_01_000800_1 : N/A

>

> Again, that is different...

>

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

> 196-

> |

> 11CF-97EA-00AA0034319D}\MONITOR\DEFAULT_MONITOR\PCI_VEN_1002&DEV_5961&SU

> BSYS

> | _280117EE&REV_01_000800_1 : N/A

>

> That too...

>

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

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

> MONITOR\DEFAULT_MONITOR\0001 00 <<Binary Value

>

> | HKEY_LOCAL_MACHINE\Enum\MONITOR\DEFAULT_MONITOR\{KEY} : {KEY}

> |

> HKEY_LOCAL_MACHINE\Enum\MONITOR\DEFAULT_MONITOR\PCI_VEN_1002&DEV_5961&SU

> BSYS

> | _280117EE&REV_01_000800_1\{KEY} : {KEY}

> |

> HKEY_LOCAL_MACHINE\Enum\MONITOR\DEFAULT_MONITOR\PCI_VEN_1002&DEV_5961&SU

> BSYS

> | _280117EE&REV_01_000800_1\HardwareID : MONITOR\DEFAULT_MONITOR

>

> Those two are covered above.

>

> | HKEY_LOCAL_MACHINE\Config\0001\Enum\MONITOR\DEFAULT_MONITOR\{KEY} :

> | {KEY}

> |

> HKEY_LOCAL_MACHINE\Config\0001\Enum\MONITOR\DEFAULT_MONITOR\PCI_VEN_1002

> &DEV

> | _5961&SUBSYS_280117EE&REV_01_000800_1\{KEY} : {KEY}

>

> Under HKEY_LOCAL_MACHINE\Config\0001\Enum, all I have is ACPI. So,

> delete this one as I suggested above.

>

> REMEMBER... If things go horribly wrong, you can do that "ScanReg

> /Restore" in DOS to get back your current Registry. Choose the one of

> date you make the changes, because the Registry backups are done at

> boot-- the 1st boot to Normal Mode of each day.

>

> --

> 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 12, 2008

Re: For PCR, trying to get rid of DEFAULT_MONITOR

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

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

March 12, 2008

Re: For PCR, trying to get rid of DEFAULT_MONITOR

"dadiOH" <dadiOH@guesswhere.com> wrote in message

news:%23$VU8x7gIHA.1996@TK2MSFTNGP03.phx.gbl...

| MEB wrote:

| > Early in the original discussion, someone {Glen or Brian -

| > indicating nVidia as example} attempted to advise that some adapter

| > cards and/or monitor/panel installation files may require a default

| > monitor installation.

|

| ME, ME, it was me!

|

| Wait. Attempted? I thought I was pretty clear :)

|

OOPS, sorry about that.. knew it had been presented

|

| --

|

| dadiOH

| ____________________________

|

| dadiOH's dandies v3.06...

| ...a help file of info about MP3s, recording from

| LP/cassette and tips & tricks on this and that.

| Get it at http://mysite.verizon.net/xico

|

March 12, 2008

Re: For PCR, trying to get rid of DEFAULT_MONITOR

On Tue, 11 Mar 2008 17:11:16 -0400, "dadiOH" <dadiOH@guesswhere.com>

put finger to keyboard and composed:

>MEB wrote:

>> Early in the original discussion, someone {Glen or Brian -

>> indicating nVidia as example} attempted to advise that some adapter

>> cards and/or monitor/panel installation files may require a default

>> monitor installation.

>

>ME, ME, it was me!

>

>Wait. Attempted? I thought I was pretty clear :)

Intel's chipsets can have up to 5 default monitors for the one real

monitor.

New Device Enumeration for Intel® UMA White Paper:

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

"A new enumeration scheme was introduced in the Device Manager with

the release of the 14.0 Intel® Graphics Media Accelerator Driver.

Prior to 14.0, there was a one to one correlation between the number

of physically attached monitors and the displays enumerated. With the

new enumeration scheme, the number of devices listed is greater than

what is connected to the platform. Users will see between two and five

monitors (Default or Plug and Play*) displayed under the Monitors tab

...."

- Franc Zabkar

--

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

March 12, 2008

Re: For PCR, trying to get rid of DEFAULT_MONITOR

"Franc Zabkar" <fzabkar@iinternode.on.net> wrote in message

news:2n0ft3dq6glq8km340ci2qjm3558k683ki@4ax.com...

| On Tue, 11 Mar 2008 17:11:16 -0400, "dadiOH" <dadiOH@guesswhere.com>

| put finger to keyboard and composed:

|

| >MEB wrote:

| >> Early in the original discussion, someone {Glen or Brian -

| >> indicating nVidia as example} attempted to advise that some adapter

| >> cards and/or monitor/panel installation files may require a default

| >> monitor installation.

| >

| >ME, ME, it was me!

| >

| >Wait. Attempted? I thought I was pretty clear :)

|

| Intel's chipsets can have up to 5 default monitors for the one real

| monitor.

|

| New Device Enumeration for Intel® UMA White Paper:

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

|

| "A new enumeration scheme was introduced in the Device Manager with

| the release of the 14.0 Intel® Graphics Media Accelerator Driver.

| Prior to 14.0, there was a one to one correlation between the number

| of physically attached monitors and the displays enumerated. With the

| new enumeration scheme, the number of devices listed is greater than

| what is connected to the platform. Users will see between two and five

| monitors (Default or Plug and Play*) displayed under the Monitors tab

| ..."

|

| - Franc Zabkar

| --

| Please remove one 'i' from my address when replying by email.

Thanks Franc, knew {hoped} we could count on you. I had noticed the same

type of issues being presented in other white papers or technical

journals/specification sheets, or being discussed in other forums.

I suppose I can see why these might be necessary, however, these are a good

indication of how far and how much is now designed around the new NT

environment.

--

MEB

http://peoplescounsel.orgfree.com

_________

March 12, 2008

Re: For PCR, trying to get rid of DEFAULT_MONITOR

Okay I managed to clean up a few occurrences of DEFAULT_MONITOR. I still

have the following:

HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\cfgmgr32\Phanto

m\3A\HardWareKey :

MONITOR\DEFAULT_MONITOR\PCI_VEN_1002&DEV_5961&SUBSYS_280117EE&REV_01_000800_

1

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\ASD\Prob\{CF2524C0-29AE-

11CF-97EA-00AA0034319D}\MONITOR\DEFAULT_MONITOR\PCI_VEN_1002&DEV_5961&SUBSYS

_280117EE&REV_01_000800_1 : N/A

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\ASD\Prob\{9B4E7760-3196-

11CF-97EA-00AA0034319D}\MONITOR\DEFAULT_MONITOR\PCI_VEN_1002&DEV_5961&SUBSYS

_280117EE&REV_01_000800_1 : N/A

HKEY_LOCAL_MACHINE\Enum\MONITOR\DEFAULT_MONITOR\{KEY} : {KEY}

HKEY_LOCAL_MACHINE\Enum\MONITOR\DEFAULT_MONITOR\PCI_VEN_1002&DEV_5961&SUBSYS

_280117EE&REV_01_000800_1\{KEY} : {KEY}

HKEY_LOCAL_MACHINE\Enum\MONITOR\DEFAULT_MONITOR\PCI_VEN_1002&DEV_5961&SUBSYS

_280117EE&REV_01_000800_1\HardwareID : MONITOR\DEFAULT_MONITOR

Getting pretty close to yours, the real culprit seemingly being

HKEY_LOCAL_MACHINE\Enum\MONITOR\DEFAULT_MONITOR. I'll be damned if it will

go away. I din't choose to edit

HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\cfgmgr32\Phanto

m\C because it is referencing has an old but still very usable hard drive.

Also I don't know what I'm doing.

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

>

> Warren wrote:

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

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

>

> The above continues to look fine to me. It very closely matches my own,

> though I have a different LCD monitor than yours. The only value up

> there I don't have is...

>

> "CompatibleIDs"="*PNP09FF"

>

> ..., but I have no reason to suspect that relates to the Default Monitor

> problem. Does "PNP09FF" appear anywhere else in your Registry? It is

> nowhere in mine.

>

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

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

> | "DeviceDesc"="Default Monitor"

> | "ConfigFlags"=hex:00,00,00,00

>

> The above continues to look fine to me-- except I don't have one & you

> don't want yours! I'm not ready to give up yet!

>

> | **************************************************************

> |

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

> | "Link"="{4D36E96E-E325-11CE-BFC1-08002BE10318}"

> |

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

>

> The above looks fine & matches mine very well.

>

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

> | @=""

>

> The above looks fine-- except you don't want it & I have none!

>

> ********************************************************************

> |

> | RADEON 9200 SERIES

> | Display

> | Registry Key:

> |

> HKEY_LOCAL_MACHINE\enum\PCI\VEN_1002&DEV_5961&SUBSYS_280117EE&REV_01\000

> 800

>

> ...snip of the Video Adapter info, but it looked a lot like mine...

> | 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 continues to look just fine-- just like mine!

>

> | Default Monitor

> | Monitor

> | This device is disabled.

>

> You have disabled it again? Remember to enable it again, if we decide to

> try another remove of the default monitor in Device Manager. And that

> might be worth one last try-- now that your monster Registry key...

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

> ...has only two entries.

>

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

> | Driver Date: 4-23-1999

>

> The above looks fine-- except it is unwanted!

>

> **********************************************************************

> |

> | Modified Dates for DRVDATA.bin & DRVIDX.bin : February 25, 2008

>

> Those dates look good. They prove the monitor is not regenerating on its

> own at every boot.

>

> **********************************************************************

> |

> | Post your Autoexec.bat file

> | SET PATH=%PATH%;C:\PROGRA~1\ATITEC~1\ATICON~1

> |

> | Post your Config.sys

> | (Empty)

>

> Fine. There is nothing in them possibly causing the generation of a

> monitor before Windows is fully booted. Check your Win.ini & System.ini,

> as I described in a response to MEB below.

>

> ***********************************************************************

> |

> | How many Registry keys contain the word "Default_Monitor"?

> |

> | HKEY_CURRENT_CONFIG\Enum\MONITOR\DEFAULT_MONITOR\{KEY} : {KEY}

> |

> HKEY_CURRENT_CONFIG\Enum\MONITOR\DEFAULT_MONITOR\PCI_VEN_1002&DEV_5961&S

> UBSY

> | S_280117EE&REV_01_000800_1\{KEY} : {KEY}

>

> HKEY_CURRENT_CONFIG is a mirror key of HKEY_LOCAL_MACHINE, meaning they

> are one & the same. But...

>

> (a) My own HKEY_CURRENT_CONFIG\Enum has no MONITOR

> (or much of anything) under it.

> (b) I have read here that some keys won't go, unless they

> are deleted from the mirror.

>

> Therefore, open RegEdit to each in turn...

>

> HKEY_CURRENT_CONFIG\Enum\MONITOR

> HKEY_LOCAL_MACHINE\Enum\MONITOR

>

> ..., & delete just the Default_Monitor under each of them in the left

> pane. Close RegEdit & reboot. Is it gone?

>

> Note: After deleting one of them, you may discover the other is gone

> too. But may as try anyhow.

>

> |

> 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

>

> Maybe try the above suggestion first, & consider the following, but

> don't necessarily try it at the same time...

>

> Well... my cfgmgr32 looks different from yours. Are you experienced

> enough to get to that key & make it look like mine, after exporting what

> you've got...?...

>

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

> \Phantom\C

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

>

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

> Matc

> | hingDeviceId : Monitor\Default_Monitor

>

> That one we hope will go away on its own-- OR, maybe delete it with the

> two ENUM Default_Monitors above.

>

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

> 9AE-

> |

> 11CF-97EA-00AA0034319D}\MONITOR\DEFAULT_MONITOR\PCI_VEN_1002&DEV_5961&SU

> BSYS

> | _280117EE&REV_01_000800_1 : N/A

>

> Again, that is different...

>

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

> 196-

> |

> 11CF-97EA-00AA0034319D}\MONITOR\DEFAULT_MONITOR\PCI_VEN_1002&DEV_5961&SU

> BSYS

> | _280117EE&REV_01_000800_1 : N/A

>

> That too...

>

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

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

> MONITOR\DEFAULT_MONITOR\0001 00 <<Binary Value

>

> | HKEY_LOCAL_MACHINE\Enum\MONITOR\DEFAULT_MONITOR\{KEY} : {KEY}

> |

> HKEY_LOCAL_MACHINE\Enum\MONITOR\DEFAULT_MONITOR\PCI_VEN_1002&DEV_5961&SU

> BSYS

> | _280117EE&REV_01_000800_1\{KEY} : {KEY}

> |

> HKEY_LOCAL_MACHINE\Enum\MONITOR\DEFAULT_MONITOR\PCI_VEN_1002&DEV_5961&SU

> BSYS

> | _280117EE&REV_01_000800_1\HardwareID : MONITOR\DEFAULT_MONITOR

>

> Those two are covered above.

>

> | HKEY_LOCAL_MACHINE\Config\0001\Enum\MONITOR\DEFAULT_MONITOR\{KEY} :

> | {KEY}

> |

> HKEY_LOCAL_MACHINE\Config\0001\Enum\MONITOR\DEFAULT_MONITOR\PCI_VEN_1002

> &DEV

> | _5961&SUBSYS_280117EE&REV_01_000800_1\{KEY} : {KEY}

>

> Under HKEY_LOCAL_MACHINE\Config\0001\Enum, all I have is ACPI. So,

> delete this one as I suggested above.

>

> REMEMBER... If things go horribly wrong, you can do that "ScanReg

> /Restore" in DOS to get back your current Registry. Choose the one of

> date you make the changes, because the Registry backups are done at

> boot-- the 1st boot to Normal Mode of each day.

>

> --

> 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 13, 2008

Re: For PCR, trying to get rid of DEFAULT_MONITOR

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

(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 13, 2008

Re: For PCR, trying to get rid of DEFAULT_MONITOR

I think I also figured out what you meant about modifying

HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\cfgmgr32\Phanto

m\3A\HardWareKey :

MONITOR\DEFAULT_MONITOR\PCI_VEN_1002&DEV_5961&SUBSYS_280117EE&REV_01_000800_

1

It is now the same as yours,

HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\cfgmgr32\Phanto

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

Unfortunately the change had no effect

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

news:eIU4HeIhIHA.5752@TK2MSFTNGP03.phx.gbl...

> Okay I managed to clean up a few occurrences of DEFAULT_MONITOR. I still

> have the following:

>

HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\cfgmgr32\Phanto

> m\3A\HardWareKey :

>

MONITOR\DEFAULT_MONITOR\PCI_VEN_1002&DEV_5961&SUBSYS_280117EE&REV_01_000800_

> 1

>

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\ASD\Prob\{CF2524C0-29AE-

>

11CF-97EA-00AA0034319D}\MONITOR\DEFAULT_MONITOR\PCI_VEN_1002&DEV_5961&SUBSYS

> _280117EE&REV_01_000800_1 : N/A

>

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\ASD\Prob\{9B4E7760-3196-

>

11CF-97EA-00AA0034319D}\MONITOR\DEFAULT_MONITOR\PCI_VEN_1002&DEV_5961&SUBSYS

> _280117EE&REV_01_000800_1 : N/A

>

> HKEY_LOCAL_MACHINE\Enum\MONITOR\DEFAULT_MONITOR\{KEY} : {KEY}

>

HKEY_LOCAL_MACHINE\Enum\MONITOR\DEFAULT_MONITOR\PCI_VEN_1002&DEV_5961&SUBSYS

> _280117EE&REV_01_000800_1\{KEY} : {KEY}

>

HKEY_LOCAL_MACHINE\Enum\MONITOR\DEFAULT_MONITOR\PCI_VEN_1002&DEV_5961&SUBSYS

> _280117EE&REV_01_000800_1\HardwareID : MONITOR\DEFAULT_MONITOR

>

> Getting pretty close to yours, the real culprit seemingly being

> HKEY_LOCAL_MACHINE\Enum\MONITOR\DEFAULT_MONITOR. I'll be damned if it

will

> go away. I din't choose to edit

>

HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\cfgmgr32\Phanto

> m\C because it is referencing has an old but still very usable hard drive.

> Also I don't know what I'm doing.

>

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

> >

> > Warren wrote:

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

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

> >

> > The above continues to look fine to me. It very closely matches my own,

> > though I have a different LCD monitor than yours. The only value up

> > there I don't have is...

> >

> > "CompatibleIDs"="*PNP09FF"

> >

> > ..., but I have no reason to suspect that relates to the Default Monitor

> > problem. Does "PNP09FF" appear anywhere else in your Registry? It is

> > nowhere in mine.

> >

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

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

> > | "DeviceDesc"="Default Monitor"

> > | "ConfigFlags"=hex:00,00,00,00

> >

> > The above continues to look fine to me-- except I don't have one & you

> > don't want yours! I'm not ready to give up yet!

> >

> > | **************************************************************

> > |

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

> > | "Link"="{4D36E96E-E325-11CE-BFC1-08002BE10318}"

> > |

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

> >

> > The above looks fine & matches mine very well.

> >

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

> > | @=""

> >

> > The above looks fine-- except you don't want it & I have none!

> >

> > ********************************************************************

> > |

> > | RADEON 9200 SERIES

> > | Display

> > | Registry Key:

> > |

> > HKEY_LOCAL_MACHINE\enum\PCI\VEN_1002&DEV_5961&SUBSYS_280117EE&REV_01\000

> > 800

> >

> > ...snip of the Video Adapter info, but it looked a lot like mine...

> > | 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 continues to look just fine-- just like mine!

> >

> > | Default Monitor

> > | Monitor

> > | This device is disabled.

> >

> > You have disabled it again? Remember to enable it again, if we decide to

> > try another remove of the default monitor in Device Manager. And that

> > might be worth one last try-- now that your monster Registry key...

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

> > ...has only two entries.

> >

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

> > | Driver Date: 4-23-1999

> >

> > The above looks fine-- except it is unwanted!

> >

> > **********************************************************************

> > |

> > | Modified Dates for DRVDATA.bin & DRVIDX.bin : February 25, 2008

> >

> > Those dates look good. They prove the monitor is not regenerating on its

> > own at every boot.

> >

> > **********************************************************************

> > |

> > | Post your Autoexec.bat file

> > | SET PATH=%PATH%;C:\PROGRA~1\ATITEC~1\ATICON~1

> > |

> > | Post your Config.sys

> > | (Empty)

> >

> > Fine. There is nothing in them possibly causing the generation of a

> > monitor before Windows is fully booted. Check your Win.ini & System.ini,

> > as I described in a response to MEB below.

> >

> > ***********************************************************************

> > |

> > | How many Registry keys contain the word "Default_Monitor"?

> > |

> > | HKEY_CURRENT_CONFIG\Enum\MONITOR\DEFAULT_MONITOR\{KEY} : {KEY}

> > |

> > HKEY_CURRENT_CONFIG\Enum\MONITOR\DEFAULT_MONITOR\PCI_VEN_1002&DEV_5961&S

> > UBSY

> > | S_280117EE&REV_01_000800_1\{KEY} : {KEY}

> >

> > HKEY_CURRENT_CONFIG is a mirror key of HKEY_LOCAL_MACHINE, meaning they

> > are one & the same. But...

> >

> > (a) My own HKEY_CURRENT_CONFIG\Enum has no MONITOR

> > (or much of anything) under it.

> > (b) I have read here that some keys won't go, unless they

> > are deleted from the mirror.

> >

> > Therefore, open RegEdit to each in turn...

> >

> > HKEY_CURRENT_CONFIG\Enum\MONITOR

> > HKEY_LOCAL_MACHINE\Enum\MONITOR

> >

> > ..., & delete just the Default_Monitor under each of them in the left

> > pane. Close RegEdit & reboot. Is it gone?

> >

> > Note: After deleting one of them, you may discover the other is gone

> > too. But may as try anyhow.

> >

> > |

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

> >

> > Maybe try the above suggestion first, & consider the following, but

> > don't necessarily try it at the same time...

> >

> > Well... my cfgmgr32 looks different from yours. Are you experienced

> > enough to get to that key & make it look like mine, after exporting what

> > you've got...?...

> >

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

> > \Phantom\C

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

> >

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

> > Matc

> > | hingDeviceId : Monitor\Default_Monitor

> >

> > That one we hope will go away on its own-- OR, maybe delete it with the

> > two ENUM Default_Monitors above.

> >

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

> > 9AE-

> > |

> > 11CF-97EA-00AA0034319D}\MONITOR\DEFAULT_MONITOR\PCI_VEN_1002&DEV_5961&SU

> > BSYS

> > | _280117EE&REV_01_000800_1 : N/A

> >

> > Again, that is different...

> >

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

> > 196-

> > |

> > 11CF-97EA-00AA0034319D}\MONITOR\DEFAULT_MONITOR\PCI_VEN_1002&DEV_5961&SU

> > BSYS

> > | _280117EE&REV_01_000800_1 : N/A

> >

> > That too...

> >

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

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

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

> >

> > | HKEY_LOCAL_MACHINE\Enum\MONITOR\DEFAULT_MONITOR\{KEY} : {KEY}

> > |

> > HKEY_LOCAL_MACHINE\Enum\MONITOR\DEFAULT_MONITOR\PCI_VEN_1002&DEV_5961&SU

> > BSYS

> > | _280117EE&REV_01_000800_1\{KEY} : {KEY}

> > |

> > HKEY_LOCAL_MACHINE\Enum\MONITOR\DEFAULT_MONITOR\PCI_VEN_1002&DEV_5961&SU

> > BSYS

> > | _280117EE&REV_01_000800_1\HardwareID : MONITOR\DEFAULT_MONITOR

> >

> > Those two are covered above.

> >

> > | HKEY_LOCAL_MACHINE\Config\0001\Enum\MONITOR\DEFAULT_MONITOR\{KEY} :

> > | {KEY}

> > |

> > HKEY_LOCAL_MACHINE\Config\0001\Enum\MONITOR\DEFAULT_MONITOR\PCI_VEN_1002

> > &DEV

> > | _5961&SUBSYS_280117EE&REV_01_000800_1\{KEY} : {KEY}

> >

> > Under HKEY_LOCAL_MACHINE\Config\0001\Enum, all I have is ACPI. So,

> > delete this one as I suggested above.

> >

> > REMEMBER... If things go horribly wrong, you can do that "ScanReg

> > /Restore" in DOS to get back your current Registry. Choose the one of

> > date you make the changes, because the Registry backups are done at

> > boot-- the 1st boot to Normal Mode of each day.

> >

> > --

> > 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 13, 2008

Re: For PCR, trying to get rid of DEFAULT_MONITOR

Warren wrote:

| Okay I managed to clean up a few occurrences of DEFAULT_MONITOR. I

| still have the following:

Well, looks like you got rid of the Default_Monitor entries that were in

the mirror key, HKEY_CURRENT_CONFIG\Enum. (Under that one, all I've got

is a puny ACPI sub-key.) And you got rid of the one under...?...

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

Is that whole key gone? But Default Monitor still shows in Devive

manager?

But-- too bad your other Default_Monitors in HKEY_LOCAL_MACHINE wouldn't

also go.

(a) Consider my other post about that "CompatibleIDs" line.

(b) Go into Device Manager & enable the Default Monitor.

(I don't know-- it may need to be for delete to work.)

they may go now that the others are gone...

HKEY_LOCAL_MACHINE\Enum\MONITOR\DEFAULT_MONITOR

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

|

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

|

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\ASD\Prob\{CF2524C0-2

9AE-

|

11CF-97EA-00AA0034319D}\MONITOR\DEFAULT_MONITOR\PCI_VEN_1002&DEV_5961&SU

BSYS

| _280117EE&REV_01_000800_1 : N/A

|

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\ASD\Prob\{9B4E7760-3

196-

|

11CF-97EA-00AA0034319D}\MONITOR\DEFAULT_MONITOR\PCI_VEN_1002&DEV_5961&SU

BSYS

| _280117EE&REV_01_000800_1 : N/A

|

| HKEY_LOCAL_MACHINE\Enum\MONITOR\DEFAULT_MONITOR\{KEY} : {KEY}

|

HKEY_LOCAL_MACHINE\Enum\MONITOR\DEFAULT_MONITOR\PCI_VEN_1002&DEV_5961&SU

BSYS

| _280117EE&REV_01_000800_1\{KEY} : {KEY}

|

HKEY_LOCAL_MACHINE\Enum\MONITOR\DEFAULT_MONITOR\PCI_VEN_1002&DEV_5961&SU

BSYS

| _280117EE&REV_01_000800_1\HardwareID : MONITOR\DEFAULT_MONITOR

|

| Getting pretty close to yours, the real culprit seemingly being

| HKEY_LOCAL_MACHINE\Enum\MONITOR\DEFAULT_MONITOR. I'll be damned if

| it will go away. I din't choose to edit

|

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

anto

| m\C because it is referencing has an old but still very usable hard

| drive.

Post that key. Here is mine...

[HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\cfgmgr32\P

hantom\C]

"HardWareKey"="MONITOR\\DEFAULT_MONITOR\\0001"

"DevNode"=dword:0000000c

| Also I don't know what I'm doing.

I have an occasional doubt, myself!

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

|>

|> Warren wrote:

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

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

|>

|> The above continues to look fine to me. It very closely matches my

|> own, though I have a different LCD monitor than yours. The only

|> value up there I don't have is...

|>

|> "CompatibleIDs"="*PNP09FF"

|>

|> ..., but I have no reason to suspect that relates to the Default

|> Monitor problem. Does "PNP09FF" appear anywhere else in your

|> Registry? It is nowhere in mine.

|>

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

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

|> | "DeviceDesc"="Default Monitor"

|> | "ConfigFlags"=hex:00,00,00,00

|>

|> The above continues to look fine to me-- except I don't have one &

|> you don't want yours! I'm not ready to give up yet!

|>

|> | **************************************************************

|> |

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

|> | "Link"="{4D36E96E-E325-11CE-BFC1-08002BE10318}"

|> |

|>

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

|>

|> The above looks fine & matches mine very well.

|>

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

|> | @=""

|>

|> The above looks fine-- except you don't want it & I have none!

|>

|> ********************************************************************

|> |

|> | RADEON 9200 SERIES

|> | Display

|> | Registry Key:

|> |

|>

HKEY_LOCAL_MACHINE\enum\PCI\VEN_1002&DEV_5961&SUBSYS_280117EE&REV_01\000

|> 800

|>

|> ...snip of the Video Adapter info, but it looked a lot like mine...

|> | 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 continues to look just fine-- just like mine!

|>

|> | Default Monitor

|> | Monitor

|> | This device is disabled.

|>

|> You have disabled it again? Remember to enable it again, if we

|> decide to try another remove of the default monitor in Device

|> Manager. And that might be worth one last try-- now that your

|> monster Registry key...

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

|> ...has only two entries.

|>

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

|> | Driver Date: 4-23-1999

|>

|> The above looks fine-- except it is unwanted!

|>

**********************************************************************

|> |

|> | Modified Dates for DRVDATA.bin & DRVIDX.bin : February 25, 2008

|>

|> Those dates look good. They prove the monitor is not regenerating on

|> its own at every boot.

|>

**********************************************************************

|> |

|> | Post your Autoexec.bat file

|> | SET PATH=%PATH%;C:\PROGRA~1\ATITEC~1\ATICON~1

|> |

|> | Post your Config.sys

|> | (Empty)

|>

|> Fine. There is nothing in them possibly causing the generation of a

|> monitor before Windows is fully booted. Check your Win.ini &

|> System.ini, as I described in a response to MEB below.

|>

***********************************************************************

|> |

|> | How many Registry keys contain the word "Default_Monitor"?

|> |

|> | HKEY_CURRENT_CONFIG\Enum\MONITOR\DEFAULT_MONITOR\{KEY} : {KEY}

|> |

|>

HKEY_CURRENT_CONFIG\Enum\MONITOR\DEFAULT_MONITOR\PCI_VEN_1002&DEV_5961&S

|> UBSY

|> | S_280117EE&REV_01_000800_1\{KEY} : {KEY}

|>

|> HKEY_CURRENT_CONFIG is a mirror key of HKEY_LOCAL_MACHINE, meaning

|> they are one & the same. But...

|>

|> (a) My own HKEY_CURRENT_CONFIG\Enum has no MONITOR

|> (or much of anything) under it.

|> (b) I have read here that some keys won't go, unless they

|> are deleted from the mirror.

|>

|> Therefore, open RegEdit to each in turn...

|>

|> HKEY_CURRENT_CONFIG\Enum\MONITOR

|> HKEY_LOCAL_MACHINE\Enum\MONITOR

|>

|> ..., & delete just the Default_Monitor under each of them in the left

|> pane. Close RegEdit & reboot. Is it gone?

|>

|> Note: After deleting one of them, you may discover the other is gone

|> too. But may as try anyhow.

|>

|> |

|>

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

|>

|> Maybe try the above suggestion first, & consider the following, but

|> don't necessarily try it at the same time...

|>

|> Well... my cfgmgr32 looks different from yours. Are you experienced

|> enough to get to that key & make it look like mine, after exporting

|> what you've got...?...

|>

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

|> \Phantom\C

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

|>

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

|> Matc

|> | hingDeviceId : Monitor\Default_Monitor

|>

|> That one we hope will go away on its own-- OR, maybe delete it with

|> the two ENUM Default_Monitors above.

|>

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\ASD\Prob\{CF2524C0-2

|> 9AE-

|> |

|>

11CF-97EA-00AA0034319D}\MONITOR\DEFAULT_MONITOR\PCI_VEN_1002&DEV_5961&SU

|> BSYS

|> | _280117EE&REV_01_000800_1 : N/A

|>

|> Again, that is different...

|>

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

|> 196-

|> |

|>

11CF-97EA-00AA0034319D}\MONITOR\DEFAULT_MONITOR\PCI_VEN_1002&DEV_5961&SU

|> BSYS

|> | _280117EE&REV_01_000800_1 : N/A

|>

|> That too...

|>

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

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

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

|>

|> | HKEY_LOCAL_MACHINE\Enum\MONITOR\DEFAULT_MONITOR\{KEY} : {KEY}

|> |

|>

HKEY_LOCAL_MACHINE\Enum\MONITOR\DEFAULT_MONITOR\PCI_VEN_1002&DEV_5961&SU

|> BSYS

|> | _280117EE&REV_01_000800_1\{KEY} : {KEY}

|> |

|>

HKEY_LOCAL_MACHINE\Enum\MONITOR\DEFAULT_MONITOR\PCI_VEN_1002&DEV_5961&SU

|> BSYS

|> | _280117EE&REV_01_000800_1\HardwareID : MONITOR\DEFAULT_MONITOR

|>

|> Those two are covered above.

|>

|> | HKEY_LOCAL_MACHINE\Config\0001\Enum\MONITOR\DEFAULT_MONITOR\{KEY} :

|> | {KEY}

|> |

|>

HKEY_LOCAL_MACHINE\Config\0001\Enum\MONITOR\DEFAULT_MONITOR\PCI_VEN_1002

|> &DEV

|> | _5961&SUBSYS_280117EE&REV_01_000800_1\{KEY} : {KEY}

|>

|> Under HKEY_LOCAL_MACHINE\Config\0001\Enum, all I have is ACPI. So,

|> delete this one as I suggested above.

Actually, it is under the mirror key, HKEY_CURRENT_CONFIG\Enum, that all

I have is a puny ACPI sub-key.

|> REMEMBER... If things go horribly wrong, you can do that "ScanReg

|> /Restore" in DOS to get back your current Registry. Choose the one of

|> date you make the changes, because the Registry backups are done at

|> boot-- the 1st boot to Normal Mode of each day.

|>

|> --

|> 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 13, 2008

Re: For PCR, trying to get rid of DEFAULT_MONITOR

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.

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

| news:eIU4HeIhIHA.5752@TK2MSFTNGP03.phx.gbl...

|> Okay I managed to clean up a few occurrences of DEFAULT_MONITOR. I

|> still have the following:

|>

|

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

|>

|

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\ASD\Prob\{CF2524C0-2

9AE-

|>

|

11CF-97EA-00AA0034319D}\MONITOR\DEFAULT_MONITOR\PCI_VEN_1002&DEV_5961&SU

BSYS

|> _280117EE&REV_01_000800_1 : N/A

|>

|

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\ASD\Prob\{9B4E7760-3

196-

|>

|

11CF-97EA-00AA0034319D}\MONITOR\DEFAULT_MONITOR\PCI_VEN_1002&DEV_5961&SU

BSYS

|> _280117EE&REV_01_000800_1 : N/A

|>

|> HKEY_LOCAL_MACHINE\Enum\MONITOR\DEFAULT_MONITOR\{KEY} : {KEY}

|>

|

HKEY_LOCAL_MACHINE\Enum\MONITOR\DEFAULT_MONITOR\PCI_VEN_1002&DEV_5961&SU

BSYS

|> _280117EE&REV_01_000800_1\{KEY} : {KEY}

|>

|

HKEY_LOCAL_MACHINE\Enum\MONITOR\DEFAULT_MONITOR\PCI_VEN_1002&DEV_5961&SU

BSYS

|> _280117EE&REV_01_000800_1\HardwareID : MONITOR\DEFAULT_MONITOR

|>

|> Getting pretty close to yours, the real culprit seemingly being

|> HKEY_LOCAL_MACHINE\Enum\MONITOR\DEFAULT_MONITOR. I'll be damned if

|> it will go away. I din't choose to edit

|>

|

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

anto

|> m\C because it is referencing has an old but still very usable hard

|> drive. Also I don't know what I'm doing.

|>

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

|> >

|> > Warren wrote:

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

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

|> >

|> > The above continues to look fine to me. It very closely matches my

|> > own, though I have a different LCD monitor than yours. The only

|> > value up there I don't have is...

|> >

|> > "CompatibleIDs"="*PNP09FF"

|> >

|> > ..., but I have no reason to suspect that relates to the Default

|> > Monitor problem. Does "PNP09FF" appear anywhere else in your

|> > Registry? It is nowhere in mine.

|> >

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

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

|> > | "DeviceDesc"="Default Monitor"

|> > | "ConfigFlags"=hex:00,00,00,00

|> >

|> > The above continues to look fine to me-- except I don't have one &

|> > you don't want yours! I'm not ready to give up yet!

|> >

|> > | **************************************************************

|> > |

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

|> > | "Link"="{4D36E96E-E325-11CE-BFC1-08002BE10318}"

|> > |

|> >

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

|> >

|> > The above looks fine & matches mine very well.

|> >

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

|> > | @=""

|> >

|> > The above looks fine-- except you don't want it & I have none!

|> >

********************************************************************

|> > |

|> > | RADEON 9200 SERIES

|> > | Display

|> > | Registry Key:

|> > |

|> >

HKEY_LOCAL_MACHINE\enum\PCI\VEN_1002&DEV_5961&SUBSYS_280117EE&REV_01\000

|> > 800

|> >

|> > ...snip of the Video Adapter info, but it looked a lot like mine...

|> > | 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 continues to look just fine-- just like mine!

|> >

|> > | Default Monitor

|> > | Monitor

|> > | This device is disabled.

|> >

|> > You have disabled it again? Remember to enable it again, if we

|> > decide to try another remove of the default monitor in Device

|> > Manager. And that might be worth one last try-- now that your

|> > monster Registry key...

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

|> > ...has only two entries.

|> >

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

|> > | Driver Date: 4-23-1999

|> >

|> > The above looks fine-- except it is unwanted!

|> >

**********************************************************************

|> > |

|> > | Modified Dates for DRVDATA.bin & DRVIDX.bin : February 25, 2008

|> >

|> > Those dates look good. They prove the monitor is not regenerating

|> > on its own at every boot.

|> >

**********************************************************************

|> > |

|> > | Post your Autoexec.bat file

|> > | SET PATH=%PATH%;C:\PROGRA~1\ATITEC~1\ATICON~1

|> > |

|> > | Post your Config.sys

|> > | (Empty)

|> >

|> > Fine. There is nothing in them possibly causing the generation of a

|> > monitor before Windows is fully booted. Check your Win.ini &

|> > System.ini, as I described in a response to MEB below.

|> >

***********************************************************************

|> > |

|> > | How many Registry keys contain the word "Default_Monitor"?

|> > |

|> > | HKEY_CURRENT_CONFIG\Enum\MONITOR\DEFAULT_MONITOR\{KEY} : {KEY}

|> > |

|> >

HKEY_CURRENT_CONFIG\Enum\MONITOR\DEFAULT_MONITOR\PCI_VEN_1002&DEV_5961&S

|> > UBSY

|> > | S_280117EE&REV_01_000800_1\{KEY} : {KEY}

|> >

|> > HKEY_CURRENT_CONFIG is a mirror key of HKEY_LOCAL_MACHINE, meaning

|> > they are one & the same. But...

|> >

|> > (a) My own HKEY_CURRENT_CONFIG\Enum has no MONITOR

|> > (or much of anything) under it.

|> > (b) I have read here that some keys won't go, unless they

|> > are deleted from the mirror.

|> >

|> > Therefore, open RegEdit to each in turn...

|> >

|> > HKEY_CURRENT_CONFIG\Enum\MONITOR

|> > HKEY_LOCAL_MACHINE\Enum\MONITOR

|> >

|> > ..., & delete just the Default_Monitor under each of them in the

|> > left pane. Close RegEdit & reboot. Is it gone?

|> >

|> > Note: After deleting one of them, you may discover the other is

|> > gone too. But may as try anyhow.

|> >

|> > |

|> >

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

|> >

|> > Maybe try the above suggestion first, & consider the following, but

|> > don't necessarily try it at the same time...

|> >

|> > Well... my cfgmgr32 looks different from yours. Are you experienced

|> > enough to get to that key & make it look like mine, after

|> > exporting what you've got...?...

|> >

HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\cfgmgr32

|> > \Phantom\C

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

|> >

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

|> > Matc

|> > | hingDeviceId : Monitor\Default_Monitor

|> >

|> > That one we hope will go away on its own-- OR, maybe delete it

|> > with the two ENUM Default_Monitors above.

|> >

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\ASD\Prob\{CF2524C0-2

|> > 9AE-

|> > |

|> >

11CF-97EA-00AA0034319D}\MONITOR\DEFAULT_MONITOR\PCI_VEN_1002&DEV_5961&SU

|> > BSYS

|> > | _280117EE&REV_01_000800_1 : N/A

|> >

|> > Again, that is different...

|> >

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

|> > 196-

|> > |

|> >

11CF-97EA-00AA0034319D}\MONITOR\DEFAULT_MONITOR\PCI_VEN_1002&DEV_5961&SU

|> > BSYS

|> > | _280117EE&REV_01_000800_1 : N/A

|> >

|> > That too...

|> >

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

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

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

|> >

|> > | HKEY_LOCAL_MACHINE\Enum\MONITOR\DEFAULT_MONITOR\{KEY} : {KEY}

|> > |

|> >

HKEY_LOCAL_MACHINE\Enum\MONITOR\DEFAULT_MONITOR\PCI_VEN_1002&DEV_5961&SU

|> > BSYS

|> > | _280117EE&REV_01_000800_1\{KEY} : {KEY}

|> > |

|> >

HKEY_LOCAL_MACHINE\Enum\MONITOR\DEFAULT_MONITOR\PCI_VEN_1002&DEV_5961&SU

|> > BSYS

|> > | _280117EE&REV_01_000800_1\HardwareID : MONITOR\DEFAULT_MONITOR

|> >

|> > Those two are covered above.

|> >

|> > | HKEY_LOCAL_MACHINE\Config\0001\Enum\MONITOR\DEFAULT_MONITOR\{KEY}

|> > | : {KEY}

|> > |

|> >

HKEY_LOCAL_MACHINE\Config\0001\Enum\MONITOR\DEFAULT_MONITOR\PCI_VEN_1002

|> > &DEV

|> > | _5961&SUBSYS_280117EE&REV_01_000800_1\{KEY} : {KEY}

|> >

|> > Under HKEY_LOCAL_MACHINE\Config\0001\Enum, all I have is ACPI. So,

|> > delete this one as I suggested above.

|> >

|> > REMEMBER... If things go horribly wrong, you can do that "ScanReg

|> > /Restore" in DOS to get back your current Registry. Choose the one

|> > of date you make the changes, because the Registry backups are

|> > done at boot-- the 1st boot to Normal Mode of each day.

|> >

|> > --

|> > 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 13, 2008

Re: For PCR, trying to get rid of DEFAULT_MONITOR

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.

"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

>

> (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 13, 2008

Re: For PCR, trying to get rid of DEFAULT_MONITOR

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.

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

news:uMn9jCLhIHA.3400@TK2MSFTNGP03.phx.gbl...

> Warren wrote:

> | Okay I managed to clean up a few occurrences of DEFAULT_MONITOR. I

> | still have the following:

>

> Well, looks like you got rid of the Default_Monitor entries that were in

> the mirror key, HKEY_CURRENT_CONFIG\Enum. (Under that one, all I've got

> is a puny ACPI sub-key.) And you got rid of the one under...?...

>

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

>

> Is that whole key gone? But Default Monitor still shows in Devive

> manager?

>

> But-- too bad your other Default_Monitors in HKEY_LOCAL_MACHINE wouldn't

> also go.

>

> (a) Consider my other post about that "CompatibleIDs" line.

> (b) Go into Device Manager & enable the Default Monitor.

> (I don't know-- it may need to be for delete to work.)

> they may go now that the others are gone...

>

> HKEY_LOCAL_MACHINE\Enum\MONITOR\DEFAULT_MONITOR

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

>

> |

> 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

> |

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

> 9AE-

> |

> 11CF-97EA-00AA0034319D}\MONITOR\DEFAULT_MONITOR\PCI_VEN_1002&DEV_5961&SU

> BSYS

> | _280117EE&REV_01_000800_1 : N/A

> |

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

> 196-

> |

> 11CF-97EA-00AA0034319D}\MONITOR\DEFAULT_MONITOR\PCI_VEN_1002&DEV_5961&SU

> BSYS

> | _280117EE&REV_01_000800_1 : N/A

> |

> | HKEY_LOCAL_MACHINE\Enum\MONITOR\DEFAULT_MONITOR\{KEY} : {KEY}

> |

> HKEY_LOCAL_MACHINE\Enum\MONITOR\DEFAULT_MONITOR\PCI_VEN_1002&DEV_5961&SU

> BSYS

> | _280117EE&REV_01_000800_1\{KEY} : {KEY}

> |

> HKEY_LOCAL_MACHINE\Enum\MONITOR\DEFAULT_MONITOR\PCI_VEN_1002&DEV_5961&SU

> BSYS

> | _280117EE&REV_01_000800_1\HardwareID : MONITOR\DEFAULT_MONITOR

> |

> | Getting pretty close to yours, the real culprit seemingly being

> | HKEY_LOCAL_MACHINE\Enum\MONITOR\DEFAULT_MONITOR. I'll be damned if

> | it will go away. I din't choose to edit

> |

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

> anto

> | m\C because it is referencing has an old but still very usable hard

> | drive.

>

> Post that key. Here is mine...

>

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

> hantom\C]

> "HardWareKey"="MONITOR\\DEFAULT_MONITOR\\0001"

> "DevNode"=dword:0000000c

>

> | Also I don't know what I'm doing.

>

> I have an occasional doubt, myself!

>

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

> |>

> |> Warren wrote:

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

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

> |>

> |> The above continues to look fine to me. It very closely matches my

> |> own, though I have a different LCD monitor than yours. The only

> |> value up there I don't have is...

> |>

> |> "CompatibleIDs"="*PNP09FF"

> |>

> |> ..., but I have no reason to suspect that relates to the Default

> |> Monitor problem. Does "PNP09FF" appear anywhere else in your

> |> Registry? It is nowhere in mine.

> |>

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

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

> |> | "DeviceDesc"="Default Monitor"

> |> | "ConfigFlags"=hex:00,00,00,00

> |>

> |> The above continues to look fine to me-- except I don't have one &

> |> you don't want yours! I'm not ready to give up yet!

> |>

> |> | **************************************************************

> |> |

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

> |> | "Link"="{4D36E96E-E325-11CE-BFC1-08002BE10318}"

> |> |

> |>

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

> |>

> |> The above looks fine & matches mine very well.

> |>

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

> |> | @=""

> |>

> |> The above looks fine-- except you don't want it & I have none!

> |>

> |> ********************************************************************

> |> |

> |> | RADEON 9200 SERIES

> |> | Display

> |> | Registry Key:

> |> |

> |>

> HKEY_LOCAL_MACHINE\enum\PCI\VEN_1002&DEV_5961&SUBSYS_280117EE&REV_01\000

> |> 800

> |>

> |> ...snip of the Video Adapter info, but it looked a lot like mine...

> |> | 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 continues to look just fine-- just like mine!

> |>

> |> | Default Monitor

> |> | Monitor

> |> | This device is disabled.

> |>

> |> You have disabled it again? Remember to enable it again, if we

> |> decide to try another remove of the default monitor in Device

> |> Manager. And that might be worth one last try-- now that your

> |> monster Registry key...

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

> |> ...has only two entries.

> |>

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

> |> | Driver Date: 4-23-1999

> |>

> |> The above looks fine-- except it is unwanted!

> |>

> **********************************************************************

> |> |

> |> | Modified Dates for DRVDATA.bin & DRVIDX.bin : February 25, 2008

> |>

> |> Those dates look good. They prove the monitor is not regenerating on

> |> its own at every boot.

> |>

> **********************************************************************

> |> |

> |> | Post your Autoexec.bat file

> |> | SET PATH=%PATH%;C:\PROGRA~1\ATITEC~1\ATICON~1

> |> |

> |> | Post your Config.sys

> |> | (Empty)

> |>

> |> Fine. There is nothing in them possibly causing the generation of a

> |> monitor before Windows is fully booted. Check your Win.ini &

> |> System.ini, as I described in a response to MEB below.

> |>

> ***********************************************************************

> |> |

> |> | How many Registry keys contain the word "Default_Monitor"?

> |> |

> |> | HKEY_CURRENT_CONFIG\Enum\MONITOR\DEFAULT_MONITOR\{KEY} : {KEY}

> |> |

> |>

> HKEY_CURRENT_CONFIG\Enum\MONITOR\DEFAULT_MONITOR\PCI_VEN_1002&DEV_5961&S

> |> UBSY

> |> | S_280117EE&REV_01_000800_1\{KEY} : {KEY}

> |>

> |> HKEY_CURRENT_CONFIG is a mirror key of HKEY_LOCAL_MACHINE, meaning

> |> they are one & the same. But...

> |>

> |> (a) My own HKEY_CURRENT_CONFIG\Enum has no MONITOR

> |> (or much of anything) under it.

> |> (b) I have read here that some keys won't go, unless they

> |> are deleted from the mirror.

> |>

> |> Therefore, open RegEdit to each in turn...

> |>

> |> HKEY_CURRENT_CONFIG\Enum\MONITOR

> |> HKEY_LOCAL_MACHINE\Enum\MONITOR

> |>

> |> ..., & delete just the Default_Monitor under each of them in the left

> |> pane. Close RegEdit & reboot. Is it gone?

> |>

> |> Note: After deleting one of them, you may discover the other is gone

> |> too. But may as try anyhow.

> |>

> |> |

> |>

> 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

> |>

> |> Maybe try the above suggestion first, & consider the following, but

> |> don't necessarily try it at the same time...

> |>

> |> Well... my cfgmgr32 looks different from yours. Are you experienced

> |> enough to get to that key & make it look like mine, after exporting

> |> what you've got...?...

> |>

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

> |> \Phantom\C

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

> |>

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

> |> Matc

> |> | hingDeviceId : Monitor\Default_Monitor

> |>

> |> That one we hope will go away on its own-- OR, maybe delete it with

> |> the two ENUM Default_Monitors above.

> |>

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

> |> 9AE-

> |> |

> |>

> 11CF-97EA-00AA0034319D}\MONITOR\DEFAULT_MONITOR\PCI_VEN_1002&DEV_5961&SU

> |> BSYS

> |> | _280117EE&REV_01_000800_1 : N/A

> |>

> |> Again, that is different...

> |>

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

> |> 196-

> |> |

> |>

> 11CF-97EA-00AA0034319D}\MONITOR\DEFAULT_MONITOR\PCI_VEN_1002&DEV_5961&SU

> |> BSYS

> |> | _280117EE&REV_01_000800_1 : N/A

> |>

> |> That too...

> |>

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

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

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

> |>

> |> | HKEY_LOCAL_MACHINE\Enum\MONITOR\DEFAULT_MONITOR\{KEY} : {KEY}

> |> |

> |>

> HKEY_LOCAL_MACHINE\Enum\MONITOR\DEFAULT_MONITOR\PCI_VEN_1002&DEV_5961&SU

> |> BSYS

> |> | _280117EE&REV_01_000800_1\{KEY} : {KEY}

> |> |

> |>

> HKEY_LOCAL_MACHINE\Enum\MONITOR\DEFAULT_MONITOR\PCI_VEN_1002&DEV_5961&SU

> |> BSYS

> |> | _280117EE&REV_01_000800_1\HardwareID : MONITOR\DEFAULT_MONITOR

> |>

> |> Those two are covered above.

> |>

> |> | HKEY_LOCAL_MACHINE\Config\0001\Enum\MONITOR\DEFAULT_MONITOR\{KEY} :

> |> | {KEY}

> |> |

> |>

> HKEY_LOCAL_MACHINE\Config\0001\Enum\MONITOR\DEFAULT_MONITOR\PCI_VEN_1002

> |> &DEV

> |> | _5961&SUBSYS_280117EE&REV_01_000800_1\{KEY} : {KEY}

> |>

> |> Under HKEY_LOCAL_MACHINE\Config\0001\Enum, all I have is ACPI. So,

> |> delete this one as I suggested above.

>

> Actually, it is under the mirror key, HKEY_CURRENT_CONFIG\Enum, that all

> I have is a puny ACPI sub-key.

>

> |> REMEMBER... If things go horribly wrong, you can do that "ScanReg

> |> /Restore" in DOS to get back your current Registry. Choose the one of

> |> date you make the changes, because the Registry backups are done at

> |> boot-- the 1st boot to Normal Mode of each day.

> |>

> |> --

> |> 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 13, 2008

Re: For PCR, trying to get rid of DEFAULT_MONITOR

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.

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

>

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

> | news:eIU4HeIhIHA.5752@TK2MSFTNGP03.phx.gbl...

> |> Okay I managed to clean up a few occurrences of DEFAULT_MONITOR. I

> |> still have the following:

> |>

> |

> 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

> |>

> |

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

> 9AE-

> |>

> |

> 11CF-97EA-00AA0034319D}\MONITOR\DEFAULT_MONITOR\PCI_VEN_1002&DEV_5961&SU

> BSYS

> |> _280117EE&REV_01_000800_1 : N/A

> |>

> |

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

> 196-

> |>

> |

> 11CF-97EA-00AA0034319D}\MONITOR\DEFAULT_MONITOR\PCI_VEN_1002&DEV_5961&SU

> BSYS

> |> _280117EE&REV_01_000800_1 : N/A

> |>

> |> HKEY_LOCAL_MACHINE\Enum\MONITOR\DEFAULT_MONITOR\{KEY} : {KEY}

> |>

> |

> HKEY_LOCAL_MACHINE\Enum\MONITOR\DEFAULT_MONITOR\PCI_VEN_1002&DEV_5961&SU

> BSYS

> |> _280117EE&REV_01_000800_1\{KEY} : {KEY}

> |>

> |

> HKEY_LOCAL_MACHINE\Enum\MONITOR\DEFAULT_MONITOR\PCI_VEN_1002&DEV_5961&SU

> BSYS

> |> _280117EE&REV_01_000800_1\HardwareID : MONITOR\DEFAULT_MONITOR

> |>

> |> Getting pretty close to yours, the real culprit seemingly being

> |> HKEY_LOCAL_MACHINE\Enum\MONITOR\DEFAULT_MONITOR. I'll be damned if

> |> it will go away. I din't choose to edit

> |>

> |

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

> anto

> |> m\C because it is referencing has an old but still very usable hard

> |> drive. Also I don't know what I'm doing.

> |>

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

> |> >

> |> > Warren wrote:

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

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

> |> >

> |> > The above continues to look fine to me. It very closely matches my

> |> > own, though I have a different LCD monitor than yours. The only

> |> > value up there I don't have is...

> |> >

> |> > "CompatibleIDs"="*PNP09FF"

> |> >

> |> > ..., but I have no reason to suspect that relates to the Default

> |> > Monitor problem. Does "PNP09FF" appear anywhere else in your

> |> > Registry? It is nowhere in mine.

> |> >

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

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

> |> > | "DeviceDesc"="Default Monitor"

> |> > | "ConfigFlags"=hex:00,00,00,00

> |> >

> |> > The above continues to look fine to me-- except I don't have one &

> |> > you don't want yours! I'm not ready to give up yet!

> |> >

> |> > | **************************************************************

> |> > |

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

> |> > | "Link"="{4D36E96E-E325-11CE-BFC1-08002BE10318}"

> |> > |

> |> >

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

> |> >

> |> > The above looks fine & matches mine very well.

> |> >

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

> |> > | @=""

> |> >

> |> > The above looks fine-- except you don't want it & I have none!

> |> >

> ********************************************************************

> |> > |

> |> > | RADEON 9200 SERIES

> |> > | Display

> |> > | Registry Key:

> |> > |

> |> >

> HKEY_LOCAL_MACHINE\enum\PCI\VEN_1002&DEV_5961&SUBSYS_280117EE&REV_01\000

> |> > 800

> |> >

> |> > ...snip of the Video Adapter info, but it looked a lot like mine...

> |> > | 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 continues to look just fine-- just like mine!

> |> >

> |> > | Default Monitor

> |> > | Monitor

> |> > | This device is disabled.

> |> >

> |> > You have disabled it again? Remember to enable it again, if we

> |> > decide to try another remove of the default monitor in Device

> |> > Manager. And that might be worth one last try-- now that your

> |> > monster Registry key...

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

> |> > ...has only two entries.

> |> >

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

> |> > | Driver Date: 4-23-1999

> |> >

> |> > The above looks fine-- except it is unwanted!

> |> >

> **********************************************************************

> |> > |

> |> > | Modified Dates for DRVDATA.bin & DRVIDX.bin : February 25, 2008

> |> >

> |> > Those dates look good. They prove the monitor is not regenerating

> |> > on its own at every boot.

> |> >

> **********************************************************************

> |> > |

> |> > | Post your Autoexec.bat file

> |> > | SET PATH=%PATH%;C:\PROGRA~1\ATITEC~1\ATICON~1

> |> > |

> |> > | Post your Config.sys

> |> > | (Empty)

> |> >

> |> > Fine. There is nothing in them possibly causing the generation of a

> |> > monitor before Windows is fully booted. Check your Win.ini &

> |> > System.ini, as I described in a response to MEB below.

> |> >

> ***********************************************************************

> |> > |

> |> > | How many Registry keys contain the word "Default_Monitor"?

> |> > |

> |> > | HKEY_CURRENT_CONFIG\Enum\MONITOR\DEFAULT_MONITOR\{KEY} : {KEY}

> |> > |

> |> >

> HKEY_CURRENT_CONFIG\Enum\MONITOR\DEFAULT_MONITOR\PCI_VEN_1002&DEV_5961&S

> |> > UBSY

> |> > | S_280117EE&REV_01_000800_1\{KEY} : {KEY}

> |> >

> |> > HKEY_CURRENT_CONFIG is a mirror key of HKEY_LOCAL_MACHINE, meaning

> |> > they are one & the same. But...

> |> >

> |> > (a) My own HKEY_CURRENT_CONFIG\Enum has no MONITOR

> |> > (or much of anything) under it.

> |> > (b) I have read here that some keys won't go, unless they

> |> > are deleted from the mirror.

> |> >

> |> > Therefore, open RegEdit to each in turn...

> |> >

> |> > HKEY_CURRENT_CONFIG\Enum\MONITOR

> |> > HKEY_LOCAL_MACHINE\Enum\MONITOR

> |> >

> |> > ..., & delete just the Default_Monitor under each of them in the

> |> > left pane. Close RegEdit & reboot. Is it gone?

> |> >

> |> > Note: After deleting one of them, you may discover the other is

> |> > gone too. But may as try anyhow.

> |> >

> |> > |

> |> >

> 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

> |> >

> |> > Maybe try the above suggestion first, & consider the following, but

> |> > don't necessarily try it at the same time...

> |> >

> |> > Well... my cfgmgr32 looks different from yours. Are you experienced

> |> > enough to get to that key & make it look like mine, after

> |> > exporting what you've got...?...

> |> >

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

> |> > \Phantom\C

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

> |> >

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

> |> > Matc

> |> > | hingDeviceId : Monitor\Default_Monitor

> |> >

> |> > That one we hope will go away on its own-- OR, maybe delete it

> |> > with the two ENUM Default_Monitors above.

> |> >

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

> |> > 9AE-

> |> > |

> |> >

> 11CF-97EA-00AA0034319D}\MONITOR\DEFAULT_MONITOR\PCI_VEN_1002&DEV_5961&SU

> |> > BSYS

> |> > | _280117EE&REV_01_000800_1 : N/A

> |> >

> |> > Again, that is different...

> |> >

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

> |> > 196-

> |> > |

> |> >

> 11CF-97EA-00AA0034319D}\MONITOR\DEFAULT_MONITOR\PCI_VEN_1002&DEV_5961&SU

> |> > BSYS

> |> > | _280117EE&REV_01_000800_1 : N/A

> |> >

> |> > That too...

> |> >

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

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

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

> |> >

> |> > | HKEY_LOCAL_MACHINE\Enum\MONITOR\DEFAULT_MONITOR\{KEY} : {KEY}

> |> > |

> |> >

> HKEY_LOCAL_MACHINE\Enum\MONITOR\DEFAULT_MONITOR\PCI_VEN_1002&DEV_5961&SU

> |> > BSYS

> |> > | _280117EE&REV_01_000800_1\{KEY} : {KEY}

> |> > |

> |> >

> HKEY_LOCAL_MACHINE\Enum\MONITOR\DEFAULT_MONITOR\PCI_VEN_1002&DEV_5961&SU

> |> > BSYS

> |> > | _280117EE&REV_01_000800_1\HardwareID : MONITOR\DEFAULT_MONITOR

> |> >

> |> > Those two are covered above.

> |> >

> |> > | HKEY_LOCAL_MACHINE\Config\0001\Enum\MONITOR\DEFAULT_MONITOR\{KEY}

> |> > | : {KEY}

> |> > |

> |> >

> HKEY_LOCAL_MACHINE\Config\0001\Enum\MONITOR\DEFAULT_MONITOR\PCI_VEN_1002

> |> > &DEV

> |> > | _5961&SUBSYS_280117EE&REV_01_000800_1\{KEY} : {KEY}

> |> >

> |> > Under HKEY_LOCAL_MACHINE\Config\0001\Enum, all I have is ACPI. So,

> |> > delete this one as I suggested above.

> |> >

> |> > REMEMBER... If things go horribly wrong, you can do that "ScanReg

> |> > /Restore" in DOS to get back your current Registry. Choose the one

> |> > of date you make the changes, because the Registry backups are

> |> > done at boot-- the 1st boot to Normal Mode of each day.

> |> >

> |> > --

> |> > 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 13, 2008

Re: For PCR, trying to get rid of DEFAULT_MONITOR

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 13, 2008

Re: For PCR, trying to get rid of DEFAULT_MONITOR

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.

(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

Do not click Delete-- click Modify.

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

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

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

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

|>

|> (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 13, 2008

Re: For PCR, trying to get rid of DEFAULT_MONITOR

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.

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

| news:uMn9jCLhIHA.3400@TK2MSFTNGP03.phx.gbl...

|> Warren wrote:

|> | Okay I managed to clean up a few occurrences of DEFAULT_MONITOR. I

|> | still have the following:

|>

|> Well, looks like you got rid of the Default_Monitor entries that

|> were in the mirror key, HKEY_CURRENT_CONFIG\Enum. (Under that one,

|> all I've got is a puny ACPI sub-key.) And you got rid of the one

|> under...?...

|>

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

|>

|> Is that whole key gone? But Default Monitor still shows in Devive

|> manager?

|>

|> But-- too bad your other Default_Monitors in HKEY_LOCAL_MACHINE

|> wouldn't also go.

|>

|> (a) Consider my other post about that "CompatibleIDs" line.

|> (b) Go into Device Manager & enable the Default Monitor.

|> (I don't know-- it may need to be for delete to work.)

|> they may go now that the others are gone...

|>

|> HKEY_LOCAL_MACHINE\Enum\MONITOR\DEFAULT_MONITOR

|>

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

|>

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

Sign In

For PCR, trying to get rid of DEFAULT_MONITOR

Recommended Posts

Guest Warren

Popular Days

Popular Days

Guest PCR

Guest MEB

Guest dadiOH

Guest PCR

Guest PCR

Guest Warren

Guest PCR

Guest PCR

Guest Warren

Guest Warren

Guest MEB

Guest Franc Zabkar

Guest MEB

Guest Warren

Guest PCR

Guest Warren

Guest PCR

Guest PCR

Guest Warren

Guest Warren

Guest Warren

Guest PCR

Guest PCR

Guest PCR

Similar Content

Can't get rid of the defaultuser0

How to get rid of Windows Installation?

Fully get rid of MS gaming overlay

How do I get rid of this?

I try to download windows 11 and i get this error

Browse

Activity

Site Info