Comments on: Backbuffer on the Touch Diamond ??? http://www.livingroomfun.info/blog/20090404/backbuffer-on-the-touch-diamond/ Dedicated to any technical stuff Mon, 06 Feb 2012 18:17:25 +0000 http://wordpress.org/?v=2.7.1 hourly 1 By: Yannick http://www.livingroomfun.info/blog/20090404/backbuffer-on-the-touch-diamond/comment-page-1/#comment-6959 Yannick Fri, 17 Apr 2009 06:26:00 +0000 http://www.livingroomfun.info/blog/?p=20#comment-6959 Hi Robert ! I've been looking around for some more information about GWES. Here's something I found : "It is the Graphics, Windowing, and Events Subsystem, but it does not load the drivers. That is actually handled by another app called device.exe. Gwes.exe is purely for the user interface components and doesn't deal with the hardware layer." If you check this post http://www.livingroomfun.info/blog/20090416/hardware-page-flip-or-not/ you see that I do not have the problem on the diamond anymore. Receiving an E_OUT_OF_MEMORY error, when creating a primary surface with backbuffer, but not getting any error when creating TWO of these backbuffers manually ( and blitting to the primary surface instead of page flipping ) seems to indicate that we have plenty of memory and that the fault is on the driver. However, I must admit that I was targetting system memory for these backbuffers, so maybe it's something else. Hi Robert !

I’ve been looking around for some more information about GWES. Here’s something I found : “It is the Graphics, Windowing, and Events Subsystem, but it does not load the drivers. That is actually handled by another app called device.exe. Gwes.exe is purely for the user interface components and doesn’t deal with the hardware layer.”

If you check this post http://www.livingroomfun.info/blog/20090416/hardware-page-flip-or-not/ you see that I do not have the problem on the diamond anymore.

Receiving an E_OUT_OF_MEMORY error, when creating a primary surface with backbuffer, but not getting any error when creating TWO of these backbuffers manually ( and blitting to the primary surface instead of page flipping ) seems to indicate that we have plenty of memory and that the fault is on the driver. However, I must admit that I was targetting system memory for these backbuffers, so maybe it’s something else.

]]> By: Robert van Hoose http://www.livingroomfun.info/blog/20090404/backbuffer-on-the-touch-diamond/comment-page-1/#comment-6958 Robert van Hoose Fri, 17 Apr 2009 03:36:05 +0000 http://www.livingroomfun.info/blog/?p=20#comment-6958 I'm experiencing the same problem with my HTC Touch HD (800x480 @ 192dpi, definitely good looking!). After I rebuilt and modified MS's dumpmem code to work on my Touch HD, I've been profiling the memory on the device. The only possible culprit I saw was: gwes.exe. I don't know as much as I'd like to about it yet, but although my program has a LOT of space right now between the low DLL load point (currently 0x00FA0000!), gwes.exe's heap seems to extend above this point. I realize that it's part of the graphics, windows, and event system. What I don't know is whether or not DirectDraw surface creation does anything that would cause gwes to try to allocate more heap, etc? I’m experiencing the same problem with my HTC Touch HD (800×480 @ 192dpi, definitely good looking!). After I rebuilt and modified MS’s dumpmem code to work on my Touch HD, I’ve been profiling the memory on the device. The only possible culprit I saw was: gwes.exe. I don’t know as much as I’d like to about it yet, but although my program has a LOT of space right now between the low DLL load point (currently 0×00FA0000!), gwes.exe’s heap seems to extend above this point. I realize that it’s part of the graphics, windows, and event system. What I don’t know is whether or not DirectDraw surface creation does anything that would cause gwes to try to allocate more heap, etc?

]]>