5 Posts

September 21st, 2006 09:00

I really do not understand what D E L L has in mind. 700m is not a product they sold 10,20 years ago. D E L L should support their valuable customers for this issue.   With all these experience when I buy a new computer next time I will probably hesitate to choose DELL again. and what I see from thisl will definitely spread out to the people around me.

6 Posts

September 22nd, 2006 05:00

I completely agree. This is getting ridiculous. My "solution" that i have posted before has ceased to work, and now its all by luck that i get the native res. working at 1290x768 is not the reason why i bought a 20inch monitor for. At least im glad that someone has been investigating the matter (i.e. Alvin) and can demonstrate that it is possible. What solutions do we have? have everyone here called dell about this problem? maybe if enough people would call, they may investigate? Maybe its just wishful thinking. But regardless, i am not satisfied by how they are addressing this issue. I even have over a year of warranty left on this laptop too!
 
ridiculous 
 
*sigh*

25 Posts

September 23rd, 2006 01:00

I was told that the Dell team had sent a 700m to the monitor manufacturing factory in China for testing purposes during the first week of August.
 
Still waiting on an update.
 
 

20 Posts

September 23rd, 2006 03:00

Any way we can get Dell's attention to this thread?

6 Posts

September 29th, 2006 05:00

Exact same thing my friend.
 
Operating under extended desktop, I see the same thing. Except, since im using a viewsonic vx2025 (another 20inch ws monitor), i am getting 3 instances of this instead of your dell 2007WFP. My laptop lcd is indeed the plug and play.
 
 

September 29th, 2006 05:00

I want your help to identify more about this problem. Can you guys and girls go to your device manager, expand the Monitors section, right click on each of the entries go to properties->details and respond with the term following "DISPLAY\" under Device Instance ID.

For instance if I expand my Monitors section I see:

Dell 2007WFP (Analog)
Dell 2007WFP (Analog)
Dell 2007WFP (Analog)
Plug and Play Monitor
Plug and Play Monitor

The Device Instance ID of
Dell 2007WFP (Analog) is DISPLAY\DEFAULT_MONITOR\4&1587A340&0&80872100&00&22
and of Plug and Play Monitor is
DISPLAY\AUO2114\4&1587A340&0&80871400&00&22

I think this is weird because my default monitor should be the one on my laptop (not the dell) and it should be operating off the "generic monitor" driver not the "plug and play" monitor driver. So not only is the native resolution not being recognized, my whole monitor/driver correspondence is mismanaged.

Am I alone on this phenomenon? Please check your device instance ID's and respond.

25 Posts

September 30th, 2006 02:00

As far as I know, older (non-PnP) monitors used the Default Monitor (i.e. generic monitor) driver. I believe our problem lies in the fact that the 700m is not seeing the LCD as a PnP monitor, thereby assigning the old Default Monitor driver, and thus not recognizing the display capabilities and allowing only those written into the Video-BIOS (of which, obviously, 1680x1050 is not one - hence why DELL NEEDS TO ISSUE A BIOS/VBIOS REVISION).
 
I have forced the installation of the PnP driver for the monitor, but this did nothing - no surprise there, as the computer still sees the display as non-PnP, but uses the PnP driver anyway.

Community Manager

 • 

56.9K Posts

October 2nd, 2006 13:00

All,

No updates. I can say this with certainty, if a possible fix were to include a monitor firmware update, it will never happen. Any fix will have to come from the Intel Video driver.

6 Posts

October 27th, 2006 03:00

So what does this mean?

Is Dell going to find a solution? Are they going to contact intel? Do we contact intel?

October 27th, 2006 04:00

That means it up. No updates. Ever. We will never see a fix for 700m. Indeed, for some of us, the 2007 WFP is not compatible. In short, just don't buy dell.

Contacting intel is unlikely to help us as this problem is exclusive to the Dell 700m.

Message Edited by DCustomer06 on 10-27-2006 12:47 AM

3 Posts

November 3rd, 2006 00:00

Hi all, I also have this problem and was struggling for a week now, from drivers to vbios and sort of programs. non has worked. After all now i am sure this has to do with vbios not defining such a resolution for system.
Chris said no update for monitor. Actually we need an update for VBios or graphics driver.
People using linux have come up with program 855resolution to fix it.
As Dell 700m is on compatibility list it is unfair and unacceptable that we don't get driver update for our DELL system and brand new monitor.
 
Don't disappoint me pls,
Cheers

7 Posts

January 10th, 2007 10:00

AGGGH. I just want to use my laptop with the montior I bought for it!! Instead, this monitor is sitting there on my desktop where the wide and ids use it.

Extremely disappointed.

5 Posts

February 20th, 2007 17:00

Aaargh--I messed with this for a whole entire weekend! Should have checked here first. How unbelievable is this really--Dell refusing to fix a known compatibility problem between two of their products, and NOT posting it anywhere in the equipment FAQ, nor correcting their marketing materials.

Fortunately, I still have a 2005fpw that works fine at native resolution with my 700m. But the position from Dell is not very customer friendly. I suppose it's buyer beware.

5 Posts

January 13th, 2008 19:00

Hi,
I guess this thread is kind of dead, but I just bought a 1680 X1050 monitor and can't get it to work with my 700m.  I guess there's no new good news on getting this to work? It's kind of annoying that Dell support still says the 700m can support this monitor when it can't!  I have the most current video card driver update (6.14.10.4396) and still no go.
 
Thanks
 
Nancy

2 Intern

 • 

1.5K Posts

January 15th, 2008 14:00

NParanka
 
 The 700M supports that monitor fine. If you are using a KVM switch or something similar that's the problem, if you are using a monitor cable other then the one that came with the 2007 that could also cause this.
No Events found!

Top