Eric12341

dell needs to fix it, somebody report it to them

Eric12341

Originally Posted by Mokubai

The 2700g doesn't need the processor in order to draw things, the processor simply says, "draw this rectangle, copy data from this block of memory to the screen" and the 2700g gets on with it. The problem seems to be that there is an API to allow programs direct access to graphics memory and programs that are badly written don't know how to deal with things when exceptions occur. I've seen this with a few programs that don't like being put into standby (games mainly) and when brought out of standby they "loose" whatever information they have regarding the screen memory, some error occurs that they don't catch and so they end up writing garbage thus corrupting graphics memory and a restart is required. I know IE does this sometimes and it seems to be a similar exception, mainly on graphics intensive pages, it encounters some problems it can't handle and writes garbage to the display buffers. This may be exacerbated by the processor scaling feature, as protochu suggests. Thinking about it, in the process of scaling the processor it changes the bus, memory *and* LCD bus speeds, it could be that this (done at a bad moment) causes the graphics system to respond with an LCD error which the software completely fails to catch and so does the computing equivalent of a major hissy fit.

not it I don't think cuz when I have the axim on ac power,the procesor doesn't scale it jus stays @ 624 and I have had this on ac power, purely disgusting problem as it is the #1 reason y I hafta soft reset.