Guest PCR Posted March 19, 2008 Posted March 19, 2008 Re: For PCR, trying to get rid of DEFAULT_MONITOR PCR wrote: | Warren wrote: || I think there was one prior to installing the new Viewsonic monitor. || I wasn't sure when we first started this exercise but I found a || little program that reads backup registry files. There was still a || copy that predated the new Viewsonic monitor installation at the || time, so I looked inside and sure enough there was a Default_Monitor || present when I was operating with a Samsung CRT monitor. || || So to my surprise I believe there was a Default_Monitor present, I || just wasn't aware of it until I installed the Viewsonic. | | OK. Then... it could be as MEB & Zabcar have suggested, that it has to | do with certain newer Intel chips (& maybe others) demanding a Default | Monitor-- but I have not yet had the time to spend at the MS | Library... http://msdn2.microsoft.com/en-us/library/ | ... for me to totally give up hope. Only should I discover there are | no more articles about it there will I begin to give up! | | I still tend to think that... Monitor.inf gave you that Default | Monitor when it could find no other possibility. That's how it | started, but even before you got the VP930 Series. Once installed, it | appears to be impossible to be rid of it. I also think it is not | installing each & every boot, because the dates on your .bin files do | not change & also you are not noticing a "driver database" getting | built on each boot. | | Tomorrow I'll get back into that library! | I've spent time at that highly XP/Vista infected library... http://msdn2.microsoft.com/en-us/library/ I am unable to discover how to get rid of that Default Monitor. I found nothing new to try, & I've run out of my own thoughts &/or they've been irradiated out of my head. I think you are OK with it as is. Who knows-- you may even be better off with it than I am without! We did get a few things cleaned up in your Registry relating to it. And you've always had the Viewsonic VP930 Serious monitor also installed & working, anyhow. You should be fine. ....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
Guest Warren Posted March 19, 2008 Posted March 19, 2008 Re: For PCR, trying to get rid of DEFAULT_MONITOR Thanks very much for your time & effort PCR. I learned a lot about the Registry and how it works. I appreciate your patience and incredible attention to detail and the great care you took in helping me work safely with the Registry. It was a great pleasure doing business with you. Again, best regards wnd thank you very much for your time and attention. "PCR" <pcrrcp@netzero.net> wrote in message news:eos$BYYiIHA.4868@TK2MSFTNGP03.phx.gbl... > PCR wrote: > | Warren wrote: > || I think there was one prior to installing the new Viewsonic monitor. > || I wasn't sure when we first started this exercise but I found a > || little program that reads backup registry files. There was still a > || copy that predated the new Viewsonic monitor installation at the > || time, so I looked inside and sure enough there was a Default_Monitor > || present when I was operating with a Samsung CRT monitor. > || > || So to my surprise I believe there was a Default_Monitor present, I > || just wasn't aware of it until I installed the Viewsonic. > | > | OK. Then... it could be as MEB & Zabcar have suggested, that it has to > | do with certain newer Intel chips (& maybe others) demanding a Default > | Monitor-- but I have not yet had the time to spend at the MS > | Library... http://msdn2.microsoft.com/en-us/library/ > | ... for me to totally give up hope. Only should I discover there are > | no more articles about it there will I begin to give up! > | > | I still tend to think that... Monitor.inf gave you that Default > | Monitor when it could find no other possibility. That's how it > | started, but even before you got the VP930 Series. Once installed, it > | appears to be impossible to be rid of it. I also think it is not > | installing each & every boot, because the dates on your .bin files do > | not change & also you are not noticing a "driver database" getting > | built on each boot. > | > | Tomorrow I'll get back into that library! > | > > I've spent time at that highly XP/Vista infected library... > http://msdn2.microsoft.com/en-us/library/ > > I am unable to discover how to get rid of that Default Monitor. I found > nothing new to try, & I've run out of my own thoughts &/or they've been > irradiated out of my head. I think you are OK with it as is. Who knows-- > you may even be better off with it than I am without! We did get a few > things cleaned up in your Registry relating to it. And you've always had > the Viewsonic VP930 Serious monitor also installed & working, anyhow. > You should be fine. > > > ...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 > >
Guest PCR Posted March 20, 2008 Posted March 20, 2008 Re: For PCR, trying to get rid of DEFAULT_MONITOR Warren wrote: | Thanks very much for your time & effort PCR. I learned a lot about | the Registry and how it works. I appreciate your patience and | incredible attention to detail and the great care you took in helping | me work safely with the Registry. It was a great pleasure doing | business with you. | | Again, best regards wnd thank you very much for your time and | attention. You are welcome. We tried all the normal things & even some that were abnormal. It was so much, I wouldn't know where to begin a synopsis of it. We went into Safe Mode & removed both the good Viewsonic VP930 Series monitor & the Default Monitor using Device Manager-- but they both came back! We went & deleted them both from the Registry ENUM key & from that other Registry Monitor key I found-- to no avail! We made a certain 3 Registry keys of yours that mentioned Default_Monitor to look a lot like mine, & we even deleted that "CompatibleIDs=*PNP09FF" from your ENUM key-- again the Default Monitor would not go! And I had big, big hopes for that last one! On the plus side, we cleaned up that gobledygook in the Update Driver requestor for both of us, & we did manage to clean up a ton of junk in that other Monitor key. Also, you've become familiar with the use of RegEdit-- but be careful with that! I studied your .inf & mine & even Monitor.inf, & I took a ton of XP/Vista-irradiation at the MSDN2 Library in an attempt to find a cure, but there is none I can find or divine-- and a monitor has begun to grow on my pinky toe! Anyhow, I'm sure you will live at least 6 years just the way you are. Keep us informed if anything further develops. I think Monitor.inf gave you that Default Monitor when no driver could initially be found for the VP930 Series. Subsequently, you got the right driver in-- but the Default Monitor won't go. It is fine to leave it as suggested by Jeff Richards long, long ago-- disabled in the hardware profile using Device Manager. | "PCR" <pcrrcp@netzero.net> wrote in message | news:eos$BYYiIHA.4868@TK2MSFTNGP03.phx.gbl... |> PCR wrote: |> | Warren wrote: |> || I think there was one prior to installing the new Viewsonic |> || monitor. I wasn't sure when we first started this exercise but I |> || found a little program that reads backup registry files. There |> || was still a copy that predated the new Viewsonic monitor |> || installation at the time, so I looked inside and sure enough |> || there was a Default_Monitor present when I was operating with a |> || Samsung CRT monitor. |> || |> || So to my surprise I believe there was a Default_Monitor present, I |> || just wasn't aware of it until I installed the Viewsonic. |> | |> | OK. Then... it could be as MEB & Zabcar have suggested, that it |> | has to do with certain newer Intel chips (& maybe others) |> | demanding a Default Monitor-- but I have not yet had the time to |> | spend at the MS Library... |> | http://msdn2.microsoft.com/en-us/library/ ... for me to totally |> | give up hope. Only should I discover there are no more articles |> | about it there will I begin to give up! |> | |> | I still tend to think that... Monitor.inf gave you that Default |> | Monitor when it could find no other possibility. That's how it |> | started, but even before you got the VP930 Series. Once installed, |> | it appears to be impossible to be rid of it. I also think it is not |> | installing each & every boot, because the dates on your .bin files |> | do not change & also you are not noticing a "driver database" |> | getting built on each boot. |> | |> | Tomorrow I'll get back into that library! |> | |> |> I've spent time at that highly XP/Vista infected library... |> http://msdn2.microsoft.com/en-us/library/ |> |> I am unable to discover how to get rid of that Default Monitor. I |> found nothing new to try, & I've run out of my own thoughts &/or |> they've been irradiated out of my head. I think you are OK with it |> as is. Who knows-- you may even be better off with it than I am |> without! We did get a few things cleaned up in your Registry |> relating to it. And you've always had the Viewsonic VP930 Serious |> monitor also installed & working, anyhow. You should be fine. ....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
Recommended Posts