Jump to content
  • Advertisement

Archived

This topic is now archived and is closed to further replies.

elaine_fyl

Slow response in Win2K

This topic is 5274 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

Hi, I have a program with Direct3D and DirectDraw. I developed it in WinXP. However, when I run it in Win2K, the program has extraordinary slow response. Up till now, I can run it in one win2K machine only. The following errors are obtained from other Win2K pc. ------- "Direct3D8: (ERROR) :Unsupported Interface identifier passed to QueryInterface for IDirect3DDevice8" ... .. "Direct3D9: (ERROR) :Driver failed command batch. Attempting to reset device state. The device may now be in an unstable state and the application may experience an access violation." ------ I searched from web that should be the problem in vertexbuffer, or wrong type of vertex selected. Also, it may be the bad display driver to be blame. Did anyone of you encounter similar errors before? How do you work it around? Thanks!

Share this post


Link to post
Share on other sites
Advertisement
Those errors do sound like some form of driver problem...what driver and version are you using?

IIRC, win2k is not fast to begin with. It was built for the professional workplace, for servers and stability. It was not made for high-performance in graphics and gaming situations.

However, when I had win2k, stuff still ran OK on it, but just not great. Everything is a lot faster on winXP.


Dustin Franklin
Mircrosoft DirectX MVP

Share this post


Link to post
Share on other sites
Hi CircleSoft,

Let me clarify my problem. I can run my program in only one Win2K up till now, with comparative performance as winXP, everything runs smooth there. It has DirectX 8.1 and driver of nv4_disp.dll.

However, when it is run at other win2K pc. It seems totally hang. I have to use TaskManager to break it out. And a invalid procedure call error was thrown. I wondered how come it can run smooth in one Win2K so far, but not the others.

Sorry that I can''t tell you the driver version now. Tell you once I back home

Share this post


Link to post
Share on other sites
Guest Anonymous Poster
The following are the error codes I obtained from a win2K with Pentium II 330M Hz, 256M RAM, DirectX 9.0 with driver of s3mtrio.dll(5.11.01.0133). I agree that this is not a fast and powerful processor, but I can''t deny that some of my clients may have such kind of machine. Thus, plz help me in settling the error like "Driver won''t let surface be created, rc=8876017c (380)" and "Unsupported Interface identifier passed to QueryInterface for IDirect3DDevice8". Thanks!


1600: Direct3D8: :====> ENTER: DLLMAIN(02d6c640): Process Attach: 00000640, tid=
00000580
1600: Direct3D8: (WARN) :Executing processor detection code (benign first-chance
exception possible)
1600:
1600: Direct3D8: (INFO) :MMX detected
1600:
1600: Direct3D8: (INFO) entium Pro CPU features (fcomi, cmov) detected
1600:
1600: Direct3D8: (INFO) :dwCPUFamily = 6, dwCPUFeatures = 3
1600:
1600: Direct3D8: (INFO) :szCPUString = GenuineIntel
1600:
1600: Direct3D8: (INFO) :Win2K SP1 or above detected - enabling VB swap workarou
nd
1600:
1600: Direct3D8: :====> EXIT: DLLMAIN(02d6c640): Process Attach: 00000640
1600: Direct3D8: (INFO) :Direct3D8 Debug Runtime selected.
1600: Direct3D8: :Device doesn''t support mip-maps
1600: Direct3D8: :Device doesn''t support mip-maps
1600: Direct3D8: :Device doesn''t support mip-maps
1600: Direct3D8: (INFO) :======================= Hal SWVP device selected
1600:
1600: Direct3D8: (INFO) :HalDevice Driver Style 4
1600:
1600: Direct3D8: :DoneExclusiveMode
1600: D3DX: (INFO) Using x87 Instructions
1600: Direct3D9: :====> ENTER: DLLMAIN(5104c35f): Process Attach: 00000640, tid=
00000580
1600: Direct3D9: :====> EXIT: DLLMAIN(5104c35f): Process Attach: 00000640
1600: Direct3D9: :Reading App Compatiblity Information
1600: Direct3D9: :Reading Registry
1600: Direct3D9: (INFO) : ModeXOnly: 0
1600: Direct3D9: (INFO) : EmulationOnly: 0
1600: Direct3D9: (INFO) : ShowFrameRate: 0
1600: Direct3D9: (INFO) : EnablePrintScreen: 0
1600: Direct3D9: (INFO) : DisableAGPSupport: 0
1600: Direct3D9: (INFO) : DisableMMX: 0
1600: Direct3D9: (INFO) : DisableWiderSurfaces:0
1600: Direct3D9: (INFO) : DisableNoSysLock:0
1600: Direct3D9: (INFO) : ForceNoSysLock:0
1600: Direct3D9: (INFO) : DisableInactivate:0
1600: Direct3D9: :DirectDrawObjectCreate: oldpdd == 0x00000000, reset = 0
1600: Direct3D9: :oldpdd == 0x00000000, reset = 0
1600: Direct3D9: :oldpdd == NULL || reset
1600: Direct3D9: (INFO) :NOT Setting DDCAPS_BANKSWITCHED
1600: Direct3D9: (WARN) :Checking Processor for MMX support (Benign first-chance
exception possible)
1600: Direct3D9: (INFO) :This is an MMX machine.
1600: Direct3D9: :HELInit for GDI Driver: Reference Count = 1
1600: Direct3D9: (INFO) :*********** NOT!! ALLOWING MODE X AND VGA MODES
1600: Direct3D9: :Calling HAL for create surface, emulation == 0
1600: Direct3D9: :*** Structs Surface 0 ***
1600: Direct3D9: :**************************
1600: Direct3D9: :Calling driver to see if it wants to say something about creat
e surface
1600: Direct3D9: : CreateSurface returns 00000000 (0)
1600: Direct3D9: :Calling HAL for create surface, emulation == 0
1600: Direct3D9: :*** Structs Surface 0 ***
1600: Direct3D9: :**************************
1600: Direct3D9: :Calling driver to see if it wants to say something about creat
e surface
1600: Direct3D9: (WARN) :Driver won''t let surface be created, rc=8876017c (380)
1600: Direct3D9: :Calling HAL for create surface, emulation == 1
1600: Direct3D9: :*** Structs Surface 0 ***
1600: Direct3D9: :**************************
1600: Direct3D9: :Calling driver to see if it wants to say something about creat
e surface
1600: Direct3D9: :#### Using GDI screen bpp = 16
1600: Direct3D9: :*** allocating a surface 610x512x16
1600: Direct3D9: : CreateSurface returns 00000000 (0)
1600: Direct3D8: (ERROR) :Unsupported Interface identifier passed to QueryInterf
ace for IDirect3DDevice8

Share this post


Link to post
Share on other sites

  • Advertisement
×

Important Information

By using GameDev.net, you agree to our community Guidelines, Terms of Use, and Privacy Policy.

We are the game development community.

Whether you are an indie, hobbyist, AAA developer, or just trying to learn, GameDev.net is the place for you to learn, share, and connect with the games industry. Learn more About Us or sign up!

Sign me up!