<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Updated version of DUAScriptGen (v1.1.0004) is now available</title><link>http://blogs.msdn.com/b/astebner/archive/2006/04/06/570484.aspx</link><description>A customer posted a bug report on my blog indicating that DUAScriptGen was incorrectly marking registry values that should be under HKEY_CLASSES_ROOT as HKEY_LOCAL_MACHINE. After investigating this scenario, I found that recent Windows XP Embedded hotfix</description><dc:language>en-US</dc:language><generator>Telligent Evolution Platform Developer Build (Build: 5.6.50428.7875)</generator><item><title>re: Updated version of DUAScriptGen (v1.1.0004) is now available</title><link>http://blogs.msdn.com/b/astebner/archive/2006/04/06/570484.aspx#593511</link><pubDate>Tue, 09 May 2006 13:28:04 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:593511</guid><dc:creator>Yves Bourguet</dc:creator><description>Very useful tool. Thanks! I had the same problem with HKEY_CLASSES_ROOT and HKEY_LOCAL_MACHINE, and I was just writing you, when I found you have already solved.&lt;br&gt;&lt;br&gt;Yves Bourguet&lt;br&gt;FIDA S.p.A.&lt;br&gt;Rome, Italy&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=593511" width="1" height="1"&gt;</description></item></channel></rss>