Unsolved
This post is more than 5 years old
2 Posts
0
13380
June 22nd, 2008 08:00
DirectX Error Message (Driver Problem?)
Thanks to anyone who can help me out with this:
When I got a pop-up having something to do about my DirectX, I went ahead and decided to test the DirectDraw and 3D, but when I opened the Diagnostics Tool I saw that not only was I unable to test the 3D but the DirectDraw, 3D AND texture Accelerations were unavailable as well! I can't remember having changed anything recently but I don't use this computer for gaming, just surfing the net and my husband's music. Anyways, I couldn't find the driver updates from the Dell website, but I downloaded several updates to be sure I got the one I needed, but it is possible I didn't get the right one. Anyways, its 5 in the AM and I can't deal with trying to fix this anymore, so any help is much apreciated.
Thanks
~CherubicWindigo
My Information:
Operating System: Windows XP Professional (5.1, Build 2600) Service Pack 2 (2600.xpsp_sp2_qfe.070227-2300)
System Manufacturer: Dell Inc.
System Model: Inspiron 2200
BIOS: Phoenix ROM BIOS PLUS Version 1.10 A03
Processor: Intel(R) Celeron(R) M processor 1.40GHz
DirectX Version: DirectX 9.0c (4.09.0000.0904)
DxDiag Version: 5.03.2600.2180 32bit Unicode
Display Devices Card: Intel Mobile Intel(R) 915GM/GMS,910GML Express Chipset Family
Chip type: Intel(R) 915GM/GMS,910GML Express Chipset
Current Mode: 1024 x 768 (32 bit) (60Hz)
Driver Name: ialmrnt5.dll
Driver Version: 6.14.0010.4609 (English)
ejn63
9 Legend
•
87.5K Posts
0
June 22nd, 2008 13:00
If this is the Inspiron 2200, it doesn't support T&L, so some of the diagnostics won't run.
cherubicwindigo
2 Posts
0
June 22nd, 2008 15:00
I'm sorry, T & L? I'm not sure what that means. Um, my DirectX used to work and I do have an Inspiron 2200.
gigiipse
82 Posts
0
June 23rd, 2008 08:00
http://en.wikipedia.org/wiki/Transform_and_lighting
Even if your hardware doesn't suport t&l there's no reason why those test won't run. The pc should still be able to emulate it so with the right setings it should only run slower than 'normal' so to say. Thry updateing you driver to the last version (not only from dell, check intel's site) and run a hardware diagnostic.
podfish
2 Posts
0
August 11th, 2008 18:00
I have the same problem on a D830 with NVS 135M - which is supposed to be DX10 - capable, I think. And I'm sure it's DX9 capable! I do have the June2008 DX redistributables freshly installed, and the (only) driver off the Dell site freshly reinstalled. The 'chat' support tech didn't have anything for me to try besides a restore-PC which would take huge amounts of time - there's a lot of data and other installs I don't want to lose, especially without a guarantee that it's the real fix.
When I run DXDiag I get the same message about "no hardware support" along with a message that I need to get a new driver from the manufacturer! NVidia won't support the drivers (I bet they don't want to spend money that they can get Dell to spend on support). Has anyone else had success with using DX on this chip? What driver/DX-DLL combo works for you?
byerre1
2 Posts
0
September 23rd, 2008 02:00
I had the same problem, but mine is a desktop. My son had bought this game World of Warcraft, and would not leave me alone until I had this working for him. My dianogstics showed Not Available on all. I kept getting error messages saying install Directx9.0 or missing video driver. I checked Intel, (your graphics are Intel) I followed a six step process with a reboot after each item. And by the time I was done, my dianogstics showed the Directx and the 3d Accelerator both were enabled.
Don't download everything like I did, try activating what you already have.
podfish
2 Posts
0
October 2nd, 2008 22:00
If you have a similar problem, don't forget to recheck the display-properties settings each time you do one of the reinstallation steps.
In the end, I had to turn the hardware acceleration setting back on to get D3D running. It was one of the first things I checked at the beginning of the process of debugging, so I don't think it was the the original cause of the problem I had - but somewhere during the other changes I made it was reset.