Install directx 9.0b install#
You might decide to leave it out if you don’t care about video capturing, or to install it with everything else.
Install directx 9.0b driver#
ManagedDx.cab – Managed DirectX extensions (for any Windows family)īDA stands for Broadcast Driver Architecture and is related to video capture.dxnt.cab – DirectX for Windows NT, including XP.BDANT.cab – BDA for Windows NT, excluding XP.So we will try installing 9.0c another way. Still, the warning is there, and this kinda makes me uneasy. I did not investigate this and my guess is that you can safely ignore this message because it’s probably caused not by files being outdated, but by dxdiag thinking wrong about which version they should be. Well, it turns out, not so happily, because dxdiag will report some files being of older version than needed. Delete the registry data as described in this post earlier, then run 9.0b setup and it’ll happily install 9.0c. Then, delete all the *.cab files from the 9.0b redist and replace them with *.cab files from the 9.0c redist. Ensure that what you have is indeed 9.0b and not 9.0c since some web pages tend to replace the underlying file with a new version without modifying the link description.
Install directx 9.0b download#
For that, download DirectX 9.0b redistributable from the internet (you’ll have to google for it a bit, since Microsoft does not seem to host it anymore). I’ll describe both.įirst, you can use DirectX 9.0b setup to install DirectX 9.0c files. One is more straightforward, but the other is cleaner and has better results. What to do? Well, there are two ways of installing DirectX 9.0c if the installer is acting weird. In some, if not in the majority of cases, neither procmon nor depwalker help, as the setup process seems to be going perfectly normal judging from their data. The above steps might help, but the chances are low. Run depwalker and inspect dxsetup.exe to check if there are any unresolved dynamic dependencies (for one, you need advpack.dll to unpack cabs, though this dependency is explicit and you’ll simply see an error when you run dxsetup.exe). Usually setup just loads dxsetup32.dll, which then enumerates audio devices, makes a few requests to ntkrnlpa.exe and user.exe, if they’re present, writes several messages into log, and that’s all. Fire procmon and protocol the whole setup procedure to see if there’s any suspicious activity going on. Inspect it to see if there’s anything of help (usually not the case). DirectX setup writes a log to “WinDir\DirectX.log”. Next come the obvious steps you would (be supposed to) do in such case.
Theoretically these two are not explicitly required, but in practice you can try putting them in the setup folder and see if that helps.
So you most likely don’t have neither user.exe nor ntkrnlpa.exe (most of XP distros don’t have the latter either). User.exe is from “Dos Windows on Windows Support” component, which provides “Core architecture that is required to run 16-bit applications”. If you’re working on your own XPE build, you have probably cut them down. These files are the redistributable I’m talking about).Īnother thing to remember is that DirectX 9.0c setup has an implicit dependency upon user.exe and ntkrnlpa.exe. If you have a single-file setup, run it, type in a path and it’ll extract a bunch of files there. Web setup is another story which I’m not inclined to discuss since rarely anybody uses web setup on embedded systems, anyway. (When talking about DirectX redistributable, obviously I mean an unpacked local distributable. For example, “E:\redist\dx9” is a simple path, and “E:\Application Installation Redistributables\Microsoft ® Windows © DiræctX 9.0c ” is a bad idea. “Simple” means no spaces, no unicode symbols, preferably 8.3 folder and file names (yeah, this is most likely NOT required in any way, but making them 8.3 costs you nothing, so what’s the difference). If it doesn’t, next thing to make sure of is that your DirectX redistributable is accessible by a simple file path. Actually, it’s enough to delete just subkeys “Version” and “InstalledVersion”, but if this is XPE image you probably have nothing else there anyway. To trick setup into thinking you don’t have DirectX yet, delete the following registry key: HKLM\Software\Microsoft\DirectX. The simplest case is where you already have this or later DirectX version installed (you might have accidentally included “DirectX Registry Data” component in your configuration). No general solution exists for this kind of problem because it might be caused by a different reasons. Installer window blinks for a moment, then displays “Installation complete. The setup tool runs just fine, but when you click “Next” nothing happens.
/nC6HLJdjwt-7afb729b3715416d9bddee55a73578c5.png "install directx 9.0b")
There’s a relatively well-known problem with DirectX 9.0c installer that manifests itself on some XP installations, including, maybe, your XPE image.
0 kommentar(er)
