 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
Pocket PC Forum / Developers / Test Tools / August 2008Failed on Direct3D mobile Test
Dear all, When I tested Direct3D Mobile relative test items, it was failed and the failed message was like this: *** vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv *** TEST STARTING *** *** Test Name: (ProcessVerticesTest) World/View Matrix Mult Test *** Test ID: 1 *** Library Path: \d3dm_driververif.dll *** Command Line: *** Kernel Mode: No *** Random Seed: 30074 *** Thread Count: 1 *** vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv D3DMQA: ShellProc(SPM_BEGIN_TEST, ...) called BEGIN TEST: "(ProcessVerticesTest) World/View Matrix Mult Test", Threads=1, Seed=30074 D3DMQA: Creating D3DM object. D3DMQA: Getting adapter display mode D3DMQA: Unable to determine current display mode. hr = 0x8d3d086b D3DMQA: File: C:\yzqa\private\test\Multimedia\DirectX\d3d\mobile \libs\initializer\.\initializer.cpp : 388 D3DMQA: Aborting initialization, due to prior initialization failure. (hr = 0x8d3d086b) D3DMQA: File: C:\yzqa\private\test\Multimedia\DirectX\d3d\mobile \tests\functional\DriverVerif\.\DriverVerif.cpp : 78 D3DMQA: Test object initialization failed. (hr = 0x8d3d086b) Skipping. D3DMQA: File: C:\yzqa\private\test\Multimedia\DirectX\d3d\mobile \tests\functional\DriverVerif\.\test.cpp : 379 D3DMQA: ShellProc(SPM_END_TEST, ...) called END TEST: "(ProcessVerticesTest) World/View Matrix Mult Test", SKIPPED, Time=0.658 or *** vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv *** TEST STARTING *** *** Test Name: (CullTest) D3DMCULL_NONE Test; X-Axis Rotation Step #1 *** Test ID: 0 *** Library Path: \d3dm_drivercomp.dll *** Command Line: *** Kernel Mode: No *** Random Seed: 3857 *** Thread Count: 1 *** vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv D3DMQA: ShellProc(SPM_BEGIN_TEST, ...) called BEGIN TEST: "(CullTest) D3DMCULL_NONE Test; X-Axis Rotation Step #1", Threads=1, Seed=3857 D3DMQA: Creating D3DM object. D3DMQA: Getting adapter display mode D3DMQA: Unable to determine current display mode. hr = 0x8d3d086b D3DMQA: File: C:\yzqa\private\test\Multimedia\DirectX\d3d\mobile \libs\initializer\.\initializer.cpp : 490 D3DMQA: Aborting initialization, due to prior initialization failure. D3DMQA: File: C:\yzqa\private\test\Multimedia\DirectX\d3d\mobile \tests\functional\DriverComp\.\DriverComp.cpp : 74 D3DMQA: Test object initialization failed. (hr = 0x80004005) Skipping. D3DMQA: File: C:\yzqa\private\test\Multimedia\DirectX\d3d\mobile \tests\functional\DriverComp\.\test.cpp : 744 D3DMQA: ShellProc(SPM_END_TEST, ...) called Why unable to determine current display mode?? Do you have some suggestion about it? Thanks a lots! Do you have a D3DM driver installed and registered on your device? That error typically shows up when you attempt to call a D3DM API and the OS image wasn't built to include Direct3D Mobile. Don Crouch Microsoft > Dear all, > When I tested Direct3D Mobile relative test items, it was failed [quoted text clipped - 20 lines] > D3DMQA: Unable to determine current display mode. hr = > 0x8d3d086b Hi Don Crouch, Thanks for your reply. I have been make sure the OS image has built to include Direct3D Mobile(SYSGEN_D3DM). How to installed and registered a D3DM driver on my device?? Have only OS built in Direct3D Mobile(SYSGEN_D3DM)? Thanks a lots! The SYSGEN_D3DM flag ensures that the D3DM runtime (d3dm.dll) and the remote hook portion of D3DM in GWES is included in the OS. It does not include a D3DM driver. Providing this driver is the responsiblity of the OEM. Microsoft provides a D3DM driver that is optimized for XScale platforms (SYSGEN_D3DMXSCALE). It also includes a D3DM Reference driver that is used by the CETK for driver verification tests (SYSGEN_D3DMREF). Microsoft recently added an optimized D3DM software driver for WM6.1 (SYSGEN_D3DM_MSDRV). You cannot redistribute the D3DM Reference driver on your platform - it is for testing purposes only. More details on D3DM drivers can be found here: http://msdn.microsoft.com/en-us/library/aa910477.aspx > Hi Don Crouch, > [quoted text clipped - 6 lines] > > Thanks a lots! > Microsoft provides a D3DM driver that is optimized for XScale platforms > (SYSGEN_D3DMXSCALE). It also includes a D3DM Reference driver that is used > by the CETK for driver verification tests (SYSGEN_D3DMREF). Microsoft > recently added an optimized D3DM software driver for WM6.1 > (SYSGEN_D3DM_MSDRV). You cannot redistribute the D3DM Reference driver on > your platform - it is for testing purposes only. Hi, are you sure the D3DM reference driver cannot be redistributed, and is not redistributed as the standard driver? HTC has been shipping on their recent HTC TyTN II/AT&T Tilt WinMob device with a htc_d3dm.dll (in LocalHook) that LoadLibary()s a default_d3dm.dll. Running the lights.exe from the SDK and some dumping of driver identification: Desc: Microsoft Direct3D Mobile Reference Driver Id: 0 Ident: 9c59509a-39bd-11d1-824c-01c04ad90dc8 Name: d3dmref.dll Vendor: 0 Is this not the reference driver you said cannot be redistributed? It's been quite debated over at http://www.htcclassaction.org/ about OEMs are now shipping WM6.0 and 6.1 only with reference drivers, unlike WM5.x. There is no XSCALE/Qualcomm optimized version available anywhere for these devices. Is this the state of how Windows Mobile is supposed to be in this post iPhone world? |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2008 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.