DDEX1 (DirectDraw App) failing in DirectDrawCreate

Hi,

While running the DDEX1.exe (DirectDraw sample application) on WinCE
6.0 on CEPC the DirectDrawCreate() fails with the return code
E_OutOfMemory (0x800700E) and following error comes in PB's debug
window.

Error:

4294847715 PID:32e0002 TID:32f0002 GWES Hook fails device creation.
DirectDrawCreate fails.
4294847731 PID:32e0002 TID:32f0002 DDEX1: DirectDrawCreate FAILED
4294847798 PID:400002 TID:32f0002 DeleteFromProcessInputLocaleTable:
Deleted process from ProcessInputLocale table, hProcess: 0x032E0002
4294847798 PID:32e0002 TID:32f0002 OSAXST1: <<< Unloading Module
'ddraw.dll' (0x8845D8A8) at address 0x404B0000-0x404C6000 in Process
'ddex1.exe' (0x8841E000)

The function call sequence i am seeing here is

DDEX1.EXE --> GetDriverInfo --> CanCreateSurface --> CreateSurface -->
HALLock --> HALUnlock --> HALDestroySurfcace

I dont know whether the above sequence of calls correct or this is
happening because of some error.

Can anyone tell me is this sequence correct or something going wrong?
What may be the possible reasons of above errors? or How can I debug
this as there is no middleware code available?

Thnaking you in Advance and hoping for reply.


Vikas Patil

Louis
Mon Jun 02 18:31:48 PDT 2008

This looks like it is caused by the driver reporting an incorrect amount of
video memory available. The DirectDraw middleware is creating a primary
surface and locking it to determine the base pointer for the video memory to
be mapped into the application's memory space. The size of memory availabe
should be returned from HALInit when it calls buildddhalinfo.

--
Louis Clausen
Software Design Engineer in Test
Windows Devices Core Multimedia

This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use.
"Vikas" <vikasmpatil@gmail.com> wrote in message
news:cac86d60-d223-400d-94b0-3ad7c4dc264e@p39g2000prm.googlegroups.com...
> Hi,
>
> While running the DDEX1.exe (DirectDraw sample application) on WinCE
> 6.0 on CEPC the DirectDrawCreate() fails with the return code
> E_OutOfMemory (0x800700E) and following error comes in PB's debug
> window.
>
> Error:
>
> 4294847715 PID:32e0002 TID:32f0002 GWES Hook fails device creation.
> DirectDrawCreate fails.
> 4294847731 PID:32e0002 TID:32f0002 DDEX1: DirectDrawCreate FAILED
> 4294847798 PID:400002 TID:32f0002 DeleteFromProcessInputLocaleTable:
> Deleted process from ProcessInputLocale table, hProcess: 0x032E0002
> 4294847798 PID:32e0002 TID:32f0002 OSAXST1: <<< Unloading Module
> 'ddraw.dll' (0x8845D8A8) at address 0x404B0000-0x404C6000 in Process
> 'ddex1.exe' (0x8841E000)
>
> The function call sequence i am seeing here is
>
> DDEX1.EXE --> GetDriverInfo --> CanCreateSurface --> CreateSurface -->
> HALLock --> HALUnlock --> HALDestroySurfcace
>
> I dont know whether the above sequence of calls correct or this is
> happening because of some error.
>
> Can anyone tell me is this sequence correct or something going wrong?
> What may be the possible reasons of above errors? or How can I debug
> this as there is no middleware code available?
>
> Thnaking you in Advance and hoping for reply.
>
>
> Vikas Patil

Vikas
Mon Jun 02 23:46:53 PDT 2008

On Jun 3, 6:31 am, "Louis Clausen" <loui...@online.microsoft.com>
wrote:
> This looks like it is caused by the driver reporting an incorrect amount of
> video memory available. The DirectDraw middleware is creating a primary
> surface and locking it to determine the base pointer for the video memory to
> be mapped into the application's memory space. The size of memory availabe
> should be returned from HALInit when it calls buildddhalinfo.
>
> --
> Louis Clausen
> Software Design Engineer in Test
> Windows Devices Core Multimedia
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
> You assume all risk for your use."Vikas" <vikasmpa...@gmail.com> wrote in message
>
> news:cac86d60-d223-400d-94b0-3ad7c4dc264e@p39g2000prm.googlegroups.com...
>
> > Hi,
>
> > While running the DDEX1.exe (DirectDraw sample application) on WinCE
> > 6.0 on CEPC the DirectDrawCreate() fails with the return code
> > E_OutOfMemory (0x800700E) and following error comes in PB's debug
> > window.
>
> > Error:
>
> > 4294847715 PID:32e0002 TID:32f0002 GWES Hook fails device creation.
> > DirectDrawCreate fails.
> > 4294847731 PID:32e0002 TID:32f0002 DDEX1: DirectDrawCreate FAILED
> > 4294847798 PID:400002 TID:32f0002 DeleteFromProcessInputLocaleTable:
> > Deleted process from ProcessInputLocale table, hProcess: 0x032E0002
> > 4294847798 PID:32e0002 TID:32f0002 OSAXST1: <<< Unloading Module
> > 'ddraw.dll' (0x8845D8A8) at address 0x404B0000-0x404C6000 in Process
> > 'ddex1.exe' (0x8841E000)
>
> > The function call sequence i am seeing here is
>
> > DDEX1.EXE --> GetDriverInfo --> CanCreateSurface --> CreateSurface -->
> > HALLock --> HALUnlock --> HALDestroySurfcace
>
> > I dont know whether the above sequence of calls correct or this is
> > happening because of some error.
>
> > Can anyone tell me is this sequence correct or something going wrong?
> > What may be the possible reasons of above errors? or How can I debug
> > this as there is no middleware code available?
>
> > Thnaking you in Advance and hoping for reply.
>
> > Vikas Patil

Hi Louis,

But my DirectDraw driver is based on DDHAL not DDGPE?
Is it must to have DDRAW driver based on the DDGPE for WinCE 6.0?
Thanking you!

Vikas