Breakthru Software
Translation
"Breaking down barriers to your innovation."

DirectX Information

Verify DirectX Level

Follow these instructions to check you level of DirectX. Our products use the DirectSound components (dsound.dll and Microsoft.DirectX.DirectSound.dll) of DirectX 9.0c.

Instructions

  1.  To check for DirectX 9.0c, go to Start -- Run, type "DXDIAG" and click OK. This will pop up DirectX Diagnostic Tool (Figure 1.).
  2.  On the DirectX Diagnostic Tool -- System tab (Figure 1.), look for DirectX Version 9.0c. If it shows an earlier version you will need to upgrade. If you are running Vista or Windows 7, see the Tech Note below.
  3.  On the DirectX Diagnostic Tool -- Files tab (Figure 2.), look for dsound.dll. It should be dated March 2008 or later. Or check the date on the dsound.dll file in the C:\WINDOWS\SYSTEM32\ folder (or where ever you have Windows installed). Also, look for Microsoft.DirectX.DirectSound.dll. It should be dated February 2007 or later.

Tech Note for Windows 7 and Vista: Windows 7 and Vista are different from XP regarding DirectX. Windows 7 and Vista come with Microsoft XNA technology (a.k.a. DirectX-10). DirectX-10 and DirectX 9.0c (a.k.a. DirectX 9.0Ex) are two distinctly different technologies. They can co-exist on the same computer. But your computer manufacturer may or may not have pre-installed DirectX 9.0c so you need to check for it. Yes, it is confusing. Microsoft admits using the name DirectX 10 for XNA is, and I quote, "misleading" for customers (so what were they thinking?). DirectX Diagnostic Tool System tab (Figure 1.) on Windows 7 and Vista, it will show the DirectX Version 10, not DirectX 9.0c. So you will need to check the date of dsound.dll as described in step 3 to determine if you have the right level. If the the dsound.dll file is missing, then DirectX 9.0c was probably not installed.

Figure 1. DirectX Diagnostic Tool - System tab
Figure 1. DirectX Diagnostic Tool - System tab
Figure 2.  DirectX Diagnostic Tool - Files tab
Figure 2. DirectX Diagnostic Tool - Files tab

Install DirectX

If you have found that your system is back level for DirectX, you will need to upgrade the level. Look for the latest DirectX End-User Runtime (NOT the software developers kit SDK which has extra files you don't need ). Installation typically takes 20 to 40 minutes to complete. The download is approximately 90-100 Megabytes. Important: Note: Microsoft often releases updates to DirectX without updating the version number or letter so be sure to install the latest release even if your version is technically the same.

Instructions: If you need to install BOTH DirectX and the .NET Framework, then install the .NET Framework FIRST. Otherwise, the DirectX install may skip some .Net related dlls and you will have to reinstall DirectX again. It's highly recommended that you create a Windows Restore Point before installing new .NET Framework versions in case you need to back out of an install.

  1.  Install the Download latest DirectX End-User Runtime (FREE download).
  2.  After installing and rebooting, double check the level using the instructions above.

Test DirectX Sound

Try testing the sound devices directly in the DirectX Diagnostic Tool. Note however, even if this diagnostic indicates your sound is working properly, there still may be a problem. Our products use the "Managed DirectX" components which are not tested with this tool. But this test may find a more generic sound problem.

Instructions

  1.  Go to Start -- Run, type "DXDIAG" and click OK. This will pop up DirectX Diagnostic Tool (Figure 1.).
  2.  On the DirectX Diagnostic Tool -- Files tab (Figure 2.), does the Notes field at the bottom say, "No Problems"?
  3.  On the DirectX Diagnostic Tool -- Sound tab, press the "Test DirectSound" button. This will ensure your sound hardware and drivers are working with DirectX.
  4.  If you have found problems with any of the above, there are Troubleshooter functions on the More Help tab.

Always Set a Windows Restore Point

Caution!Optional but Smart! DirectX and the .Net Framework should be considered as service packs to your system. As such, it is always a safe practice to set a Windows Restore Point before installing them. It only takes a few seconds. And it is the ONLY way to back out of either of these types of installs (in rare cases where it is necessary). Here are instructions if you are not familiar. [ How to set a Restore Point for Windows 7, Vista], or [XP]