<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/1.5.1-alpha" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: DirectX problem, how I loathe thee</title>
	<link>http://dansdata.blogsome.com/2007/08/07/directx-problem-how-i-loathe-thee/</link>
	<description>the blog that is not dansdata.com</description>
	<pubDate>Mon, 13 Oct 2008 06:44:54 +0000</pubDate>
	<generator>http://wordpress.org/?v=1.5.1-alpha</generator>

	<item>
		<title>by: directionless</title>
		<link>http://dansdata.blogsome.com/2007/08/07/directx-problem-how-i-loathe-thee/#comment-1951</link>
		<pubDate>Sat, 26 Jan 2008 11:30:41 +0000</pubDate>
		<guid>http://dansdata.blogsome.com/2007/08/07/directx-problem-how-i-loathe-thee/#comment-1951</guid>
					<description>Now that you have no doubt fixed your issue, I found that removing extra subkeys from the following registry key fixed this issue on my PC.
HKLM\SYSTEM\CurrentControlSet\Control\Video

There are several keys listed there which seem to list all the video drivers you have ever loaded on your PC.

I recommend uninstalling your video drivers, deleting all the keys except for the VgaSave key {23A77BF7-ED96-40EC-AF06-9B1F4867732A} and rebooting.

After reloading the latest Nvidia drivers DirectX worked on my PC.
</description>
		<content:encoded><![CDATA[	<p>Now that you have no doubt fixed your issue, I found that removing extra subkeys from the following registry key fixed this issue on my PC.<br />
HKLM\SYSTEM\CurrentControlSet\Control\Video</p>
	<p>There are several keys listed there which seem to list all the video drivers you have ever loaded on your PC.</p>
	<p>I recommend uninstalling your video drivers, deleting all the keys except for the VgaSave key {23A77BF7-ED96-40EC-AF06-9B1F4867732A} and rebooting.</p>
	<p>After reloading the latest Nvidia drivers DirectX worked on my PC.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Thrillhouse</title>
		<link>http://dansdata.blogsome.com/2007/08/07/directx-problem-how-i-loathe-thee/#comment-1270</link>
		<pubDate>Wed, 15 Aug 2007 08:58:33 +0100</pubDate>
		<guid>http://dansdata.blogsome.com/2007/08/07/directx-problem-how-i-loathe-thee/#comment-1270</guid>
					<description>This sounds like the sort of thing Dial-a-fix can take care of.  It solves a lot of windows dll weirdness.  Just run the exe, click the green checkmark, and go.

http://wiki.djlizard.net/Dial-a-fix</description>
		<content:encoded><![CDATA[	<p>This sounds like the sort of thing Dial-a-fix can take care of.  It solves a lot of windows dll weirdness.  Just run the exe, click the green checkmark, and go.</p>
	<p><a href='http://wiki.djlizard.net/Dial-a-fix' rel='nofollow'>http://wiki.djlizard.net/Dial-a-fix</a>
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: BTU</title>
		<link>http://dansdata.blogsome.com/2007/08/07/directx-problem-how-i-loathe-thee/#comment-1260</link>
		<pubDate>Fri, 10 Aug 2007 22:01:16 +0100</pubDate>
		<guid>http://dansdata.blogsome.com/2007/08/07/directx-problem-how-i-loathe-thee/#comment-1260</guid>
					<description>Thirty minutes wasted installing Windows?  You should try nLite, OK it takes maybe 30 minutes to set it up at first but then you can do unattended installs of Windows, with all your personal tweaks, to your heart's content.  (Warning: setting up the 'perfect' nLite configuration can become a time-consuming obsession in itself.)

I would pull out the hard drive in this machine, slot in a shiny new one, and do a clean install of Windows and the graphics driver.  At least that way you will know whether it is a hardware/BIOS issue or Windows.</description>
		<content:encoded><![CDATA[	<p>Thirty minutes wasted installing Windows?  You should try nLite, OK it takes maybe 30 minutes to set it up at first but then you can do unattended installs of Windows, with all your personal tweaks, to your heart&#8217;s content.  (Warning: setting up the &#8216;perfect&#8217; nLite configuration can become a time-consuming obsession in itself.)</p>
	<p>I would pull out the hard drive in this machine, slot in a shiny new one, and do a clean install of Windows and the graphics driver.  At least that way you will know whether it is a hardware/BIOS issue or Windows.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Condemned</title>
		<link>http://dansdata.blogsome.com/2007/08/07/directx-problem-how-i-loathe-thee/#comment-1254</link>
		<pubDate>Thu, 09 Aug 2007 19:02:56 +0100</pubDate>
		<guid>http://dansdata.blogsome.com/2007/08/07/directx-problem-how-i-loathe-thee/#comment-1254</guid>
					<description>I too have been troubled by the failure to install windows updates. In my case it was 74 failures following a (repair) install of XP pro. Entering the following runes into a cmd window saved me: (b.t.w. I like the sound of wups.dll - I'd like to think that this is where all 'whoops' code from MS is put, but alas, it's only 36Kb)

net stop wuauserv
regsvr32 wuapi.dll
regsvr32 wups.dll
regsvr32 wuaueng.dll
regsvr32 wuaueng1.dll
regsvr32 wucltui.dll
regsvr32 wuweb.dll
regsvr32 qmgr.dll
regsvr32 qmgrprxy.dll
net start wuauserv
</description>
		<content:encoded><![CDATA[	<p>I too have been troubled by the failure to install windows updates. In my case it was 74 failures following a (repair) install of XP pro. Entering the following runes into a cmd window saved me: (b.t.w. I like the sound of wups.dll - I&#8217;d like to think that this is where all &#8216;whoops&#8217; code from MS is put, but alas, it&#8217;s only 36Kb)</p>
	<p>net stop wuauserv<br />
regsvr32 wuapi.dll<br />
regsvr32 wups.dll<br />
regsvr32 wuaueng.dll<br />
regsvr32 wuaueng1.dll<br />
regsvr32 wucltui.dll<br />
regsvr32 wuweb.dll<br />
regsvr32 qmgr.dll<br />
regsvr32 qmgrprxy.dll<br />
net start wuauserv
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Bedlam</title>
		<link>http://dansdata.blogsome.com/2007/08/07/directx-problem-how-i-loathe-thee/#comment-1246</link>
		<pubDate>Wed, 08 Aug 2007 18:38:14 +0100</pubDate>
		<guid>http://dansdata.blogsome.com/2007/08/07/directx-problem-how-i-loathe-thee/#comment-1246</guid>
					<description>I re-second the motion to have System Restore enabled.  I too duly killed it back in the glory days of 2002 when we were all still trying to turn XP back into Win2k.  But bugger it, the thing does what it says on the tin and it's not like modern computers don't have the resources to handle it.
I ordinarily run a pretty tight ship, but SR saved my bacon a couple of weeks ago when I somehow got infected with some very persistent spyware from an official Skype update of all things.  Restored to the day before and boom, back up and running.</description>
		<content:encoded><![CDATA[	<p>I re-second the motion to have System Restore enabled.  I too duly killed it back in the glory days of 2002 when we were all still trying to turn XP back into Win2k.  But bugger it, the thing does what it says on the tin and it&#8217;s not like modern computers don&#8217;t have the resources to handle it.<br />
I ordinarily run a pretty tight ship, but SR saved my bacon a couple of weeks ago when I somehow got infected with some very persistent spyware from an official Skype update of all things.  Restored to the day before and boom, back up and running.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: mstromb</title>
		<link>http://dansdata.blogsome.com/2007/08/07/directx-problem-how-i-loathe-thee/#comment-1245</link>
		<pubDate>Wed, 08 Aug 2007 17:01:59 +0100</pubDate>
		<guid>http://dansdata.blogsome.com/2007/08/07/directx-problem-how-i-loathe-thee/#comment-1245</guid>
					<description>I guess your video card problem is solved-ish at this point, but there's one thing you might try to weed out some of that generic weirdness left hanging around: System File Checker. It's a little command line utility that came about around SP2 if I recall. It does just what it says, and will check your current system files against a known good catalog. You'll need your XP CD.

Run the command: sfc /scannow

It'll do it's thing for a bit, and probably tell you to reboot. No guarantees it'll fix your problem of course, but it can't really hurt.

It won't work if you used n-lite to make yourself a custom install image and disabled digital signatures or something like that... But I don't think you've ever mentioned n-lite so that probably won't be a problem.</description>
		<content:encoded><![CDATA[	<p>I guess your video card problem is solved-ish at this point, but there&#8217;s one thing you might try to weed out some of that generic weirdness left hanging around: System File Checker. It&#8217;s a little command line utility that came about around SP2 if I recall. It does just what it says, and will check your current system files against a known good catalog. You&#8217;ll need your XP CD.</p>
	<p>Run the command: sfc /scannow</p>
	<p>It&#8217;ll do it&#8217;s thing for a bit, and probably tell you to reboot. No guarantees it&#8217;ll fix your problem of course, but it can&#8217;t really hurt.</p>
	<p>It won&#8217;t work if you used n-lite to make yourself a custom install image and disabled digital signatures or something like that&#8230; But I don&#8217;t think you&#8217;ve ever mentioned n-lite so that probably won&#8217;t be a problem.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Daniel Rutter</title>
		<link>http://dansdata.blogsome.com/2007/08/07/directx-problem-how-i-loathe-thee/#comment-1244</link>
		<pubDate>Wed, 08 Aug 2007 16:12:09 +0100</pubDate>
		<guid>http://dansdata.blogsome.com/2007/08/07/directx-problem-how-i-loathe-thee/#comment-1244</guid>
					<description>&lt;i&gt;I have a Windows XP install that has not been reinstalled since early 2006&lt;/i&gt;

Same here, until now. Making disk images is all very well if you expect to have to reinstall on the same hardware, but I normally only go back to a fresh install when I get a whole new computer, on which an image of the last one would be useless.</description>
		<content:encoded><![CDATA[	<p><i>I have a Windows XP install that has not been reinstalled since early 2006</i></p>
	<p>Same here, until now. Making disk images is all very well if you expect to have to reinstall on the same hardware, but I normally only go back to a fresh install when I get a whole new computer, on which an image of the last one would be useless.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Anthony Hersey</title>
		<link>http://dansdata.blogsome.com/2007/08/07/directx-problem-how-i-loathe-thee/#comment-1243</link>
		<pubDate>Wed, 08 Aug 2007 15:10:26 +0100</pubDate>
		<guid>http://dansdata.blogsome.com/2007/08/07/directx-problem-how-i-loathe-thee/#comment-1243</guid>
					<description>Balentius,

I used to be all about finding out what happened. The fifth or sixth time, though, I just said screw it. My Windows box is used for games, porn, and BitTorrent (ok, non-porn BT). Reinstalling the OS when it fails to do those things takes less time than troubleshooting whatever arcane DLL conflict has arisen from the latest security patch. I keep my data and most apps on another partition, as mentioned above. I even have registry patches for the most frequently played games so I can &quot;reinstall&quot; those in seconds.</description>
		<content:encoded><![CDATA[	<p>Balentius,</p>
	<p>I used to be all about finding out what happened. The fifth or sixth time, though, I just said screw it. My Windows box is used for games, porn, and BitTorrent (ok, non-porn BT). Reinstalling the OS when it fails to do those things takes less time than troubleshooting whatever arcane DLL conflict has arisen from the latest security patch. I keep my data and most apps on another partition, as mentioned above. I even have registry patches for the most frequently played games so I can &#8220;reinstall&#8221; those in seconds.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: alphacheez</title>
		<link>http://dansdata.blogsome.com/2007/08/07/directx-problem-how-i-loathe-thee/#comment-1242</link>
		<pubDate>Wed, 08 Aug 2007 13:10:57 +0100</pubDate>
		<guid>http://dansdata.blogsome.com/2007/08/07/directx-problem-how-i-loathe-thee/#comment-1242</guid>
					<description>This sounds like the kind of issue that makes a good case for running Windows as a virtual machine inside some flavor of more stable OS (such as linux I guess).  I think some of the newer versions of virtualization software support 3D acceleration.</description>
		<content:encoded><![CDATA[	<p>This sounds like the kind of issue that makes a good case for running Windows as a virtual machine inside some flavor of more stable OS (such as linux I guess).  I think some of the newer versions of virtualization software support 3D acceleration.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: GeeJay</title>
		<link>http://dansdata.blogsome.com/2007/08/07/directx-problem-how-i-loathe-thee/#comment-1241</link>
		<pubDate>Wed, 08 Aug 2007 11:43:12 +0100</pubDate>
		<guid>http://dansdata.blogsome.com/2007/08/07/directx-problem-how-i-loathe-thee/#comment-1241</guid>
					<description>bugger, bugger, bugger.....just reading all of this implies I will find a similar problem on my PC when I get home....and the missus is using it for her Uni stuff ....damn, damn, damn...
I'd be tempted to disable the vid card in dev manager and let XP find it again....although I guess you've tried that already.</description>
		<content:encoded><![CDATA[	<p>bugger, bugger, bugger&#8230;..just reading all of this implies I will find a similar problem on my PC when I get home&#8230;.and the missus is using it for her Uni stuff &#8230;.damn, damn, damn&#8230;<br />
I&#8217;d be tempted to disable the vid card in dev manager and let XP find it again&#8230;.although I guess you&#8217;ve tried that already.
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
