<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Blog - PonticStar.com &#187; Windows Programming</title>
	<atom:link href="http://www.ponticstar.com/blog/category/win-dev/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.ponticstar.com/blog</link>
	<description>Blog about various aspects of programming and web design</description>
	<lastBuildDate>Mon, 28 Jun 2010 19:53:52 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>How to install Microsoft Visual Studio 6.0 on Windows 2000/XP</title>
		<link>http://www.ponticstar.com/blog/2009/07/13/how-to-install-msvs-on-windows/</link>
		<comments>http://www.ponticstar.com/blog/2009/07/13/how-to-install-msvs-on-windows/#comments</comments>
		<pubDate>Mon, 13 Jul 2009 15:20:40 +0000</pubDate>
		<dc:creator>Michael Ryvkin</dc:creator>
				<category><![CDATA[Windows Programming]]></category>
		<category><![CDATA[Microsoft Visual Studio]]></category>

		<guid isPermaLink="false">http://www.ponticstar.com/blog/?p=93</guid>
		<description><![CDATA[If you ever tried to install Microsoft Visual Studio 6.0 or a standalone Visual Studio product on Windows 2000 or XP, you already know that setup fails. But luckily there is a workaround. At the command prompt, type the following command: E:\SETUP\acmsetup.exe /T E:\SETUP\PRODUCT.STF /s E:\ /n "NAME" /o "ORGANIZATION" /k 1234567890 where: E: &#8211; [...]]]></description>
			<content:encoded><![CDATA[<p>If you ever tried to install Microsoft Visual Studio 6.0 or a standalone Visual Studio product on Windows 2000 or XP, you already know that setup fails. But luckily there is a workaround. At the command prompt, type the following command:</p>
<pre class="brush:shell;light:true">E:\SETUP\acmsetup.exe /T E:\SETUP\PRODUCT.STF /s E:\ /n "NAME" /o "ORGANIZATION" /k 1234567890</pre>
<p><span id="more-93"></span>where:</p>
<ul>
<li><code>E:</code> &#8211; your CD-ROM or DVD-ROM drive letter. Also you can replace <code>E:\</code> with path to the folder where you have your installation files.</li>
<li><code>PRODUCT</code> &#8211; File name of the product you are installing with <code>.stf</code> extension. The specific <code>.stf</code> file that is required for the manual command line will vary depending on the specific product you are installing. Search the <code>\SETUP</code> folder on the CD-ROM of the product you are installing for the <code>.stf</code> to use. For example, for Visual Basic 6.0 Professional, use <code>vb98pro.stf</code>; for Visual C++ 6.0 Professional, use <code>vc98pro.stf</code>.</li>
<li><code>NAME</code> &#8211; your name</li>
<li><code>ORGANIZATION</code> &#8211; your organization</li>
<li><code>1234567890</code> &#8211; your CD key</li>
</ul>
<p>If you get the message &#8220;You must first run the Installation Wizard before running this setup&#8221;, run the following command and repeat.</p>
<pre class="brush:shell;light:true">regedit /s E:\key.dat</pre>
<p>In the same way you should install service packs.</p>
<p>Service Pack 5:</p>
<pre class="brush:shell;light:true">C:\SP5\acmsetup.exe /T C:\SP5\sp598ent.stf /s C:\SP5 /n "NAME" /o "ORGANIZATION"</pre>
<p>Service Pack 6:</p>
<pre class="brush:shell;light:true">C:\SP6\acmsetup.exe /T C:\SP6\sp698ent.stf /s C:\SP6 /n "NAME" /o "ORGANIZATION"</pre>
<p>where:</p>
<ul>
<li><code>C:\SP5</code> and <code>C:\SP6</code> &#8211; folders where you have extracted service pack files.</li>
</ul>
<p>Microsoft published an article regarding this problem at <a class="target-blank" href="http://support.microsoft.com/kb/250343">http://support.microsoft.com/kb/250343</a>. However they suggest to use <code>/B1</code> (or <code>/B 1</code>) command line argument, which in my case resulted in product options dialog being skipped. </p>
]]></content:encoded>
			<wfw:commentRss>http://www.ponticstar.com/blog/2009/07/13/how-to-install-msvs-on-windows/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
	</channel>
</rss>
