<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: &#8220;You Chose Poorly&#8221; says the dumb installer</title>
	<atom:link href="http://lonesysadmin.net/2006/09/14/you-chose-poorly-says-the-installer/feed" rel="self" type="application/rss+xml" />
	<link>http://lonesysadmin.net/2006/09/14/you-chose-poorly-says-the-installer/</link>
	<description>im in ur data centrz patchin ur serverz</description>
	<pubDate>Fri, 21 Nov 2008 22:01:21 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: The Lone Sysadmin &#187; Comment Roundup</title>
		<link>http://lonesysadmin.net/2006/09/14/you-chose-poorly-says-the-installer/#comment-18421</link>
		<dc:creator>The Lone Sysadmin &#187; Comment Roundup</dc:creator>
		<pubDate>Sat, 13 Jan 2007 22:12:04 +0000</pubDate>
		<guid isPermaLink="false">http://lonesysadmin.net/2006/09/14/you-chose-poorly-says-the-installer/#comment-18421</guid>
		<description>[...] - Some anonymous dude named z4k pointed out that I can use the Microsoft Installer SDK to alter installers that are refuse to install based on your Windows version. I started this by bitching about Adobe shipping installers that refused to work on Windows Server 2003. Turns out there is a workaround. I still contend that vendors should let you install wherever you want but just make it clear you aren&#8217;t supported in that configuration. [...]</description>
		<content:encoded><![CDATA[<p>[...] - Some anonymous dude named z4k pointed out that I can use the Microsoft Installer SDK to alter installers that are refuse to install based on your Windows version. I started this by bitching about Adobe shipping installers that refused to work on Windows Server 2003. Turns out there is a workaround. I still contend that vendors should let you install wherever you want but just make it clear you aren&#8217;t supported in that configuration. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: z4k</title>
		<link>http://lonesysadmin.net/2006/09/14/you-chose-poorly-says-the-installer/#comment-18410</link>
		<dc:creator>z4k</dc:creator>
		<pubDate>Sat, 13 Jan 2007 18:20:19 +0000</pubDate>
		<guid isPermaLink="false">http://lonesysadmin.net/2006/09/14/you-chose-poorly-says-the-installer/#comment-18410</guid>
		<description>Here's a quick workaround:

1. Download and install "Windows Installer 1.0 SDK (x86)":
http://www.microsoft.com/downloads/details.aspx?FamilyID=105dfc41-801e-4441-aa75-7696d794f109&#38;DisplayLang=en

2. Install the Orca tool from the SDK you just unpacked.

3. Make a &lt;b&gt;backup&lt;/b&gt; copy of "Adobe Premiere Pro 2.0.msi".

4. Run Orca and open Adobe Premiere Pro 2.0.msi, this will allow you to view the install parameters.

5. Find the "LaunchCondition" variable and look for the following condition:
((VersionNT&#62;500) AND (ServicePackLevel&#62;=2)) OR ((VersionNT64) AND (ServicePackLevel&#62;=1))

6. Add the following text, w/o the quotes, to the &lt;b&gt;beginning&lt;/b&gt; of the above condition:
"(1=1) OR "

7. It should now look like this:
(1=1) OR ((VersionNT&#62;500) AND (ServicePackLevel&#62;=2)) OR ((VersionNT64) AND (ServicePackLevel&#62;=1))

8. Save the modified msi file

9. Double click your new msi and enjoy Premiere on &lt;b&gt;any&lt;/b&gt; version of windows.

&lt;i&gt;
This document is provided as information only to show the inner workings of msi files.  This document should not be use to circumvent Adobe's installation restrictions, doing so may violate Adobe's copyright.
&lt;/i&gt;</description>
		<content:encoded><![CDATA[<p>Here&#8217;s a quick workaround:</p>
<p>1. Download and install &#8220;Windows Installer 1.0 SDK (x86)&#8221;:<br />
<a href="http://www.microsoft.com/downloads/details.aspx?FamilyID=105dfc41-801e-4441-aa75-7696d794f109&amp;DisplayLang=en" rel="nofollow">http://www.microsoft.com/downloads/details.aspx?FamilyID=105dfc41-801e-4441-aa75-7696d794f109&amp;DisplayLang=en</a></p>
<p>2. Install the Orca tool from the SDK you just unpacked.</p>
<p>3. Make a <b>backup</b> copy of &#8220;Adobe Premiere Pro 2.0.msi&#8221;.</p>
<p>4. Run Orca and open Adobe Premiere Pro 2.0.msi, this will allow you to view the install parameters.</p>
<p>5. Find the &#8220;LaunchCondition&#8221; variable and look for the following condition:<br />
((VersionNT&gt;500) AND (ServicePackLevel&gt;=2)) OR ((VersionNT64) AND (ServicePackLevel&gt;=1))</p>
<p>6. Add the following text, w/o the quotes, to the <b>beginning</b> of the above condition:<br />
&#8220;(1=1) OR &#8221;</p>
<p>7. It should now look like this:<br />
(1=1) OR ((VersionNT&gt;500) AND (ServicePackLevel&gt;=2)) OR ((VersionNT64) AND (ServicePackLevel&gt;=1))</p>
<p>8. Save the modified msi file</p>
<p>9. Double click your new msi and enjoy Premiere on <b>any</b> version of windows.</p>
<p><i><br />
This document is provided as information only to show the inner workings of msi files.  This document should not be use to circumvent Adobe&#8217;s installation restrictions, doing so may violate Adobe&#8217;s copyright.<br />
</i></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: The Lone Sysadmin &#187; What an Installer Should Do</title>
		<link>http://lonesysadmin.net/2006/09/14/you-chose-poorly-says-the-installer/#comment-11263</link>
		<dc:creator>The Lone Sysadmin &#187; What an Installer Should Do</dc:creator>
		<pubDate>Tue, 10 Oct 2006 18:30:55 +0000</pubDate>
		<guid isPermaLink="false">http://lonesysadmin.net/2006/09/14/you-chose-poorly-says-the-installer/#comment-11263</guid>
		<description>[...] Certainly many of you have seen my rants about installers that don&#8217;t do a very good job of installing. I must extend props to the EA/Dice guys for doing the right thing with the Battlefield 2142 installer when it encounters a version of Windows it doesn&#8217;t know about: [...]</description>
		<content:encoded><![CDATA[<p>[...] Certainly many of you have seen my rants about installers that don&#8217;t do a very good job of installing. I must extend props to the EA/Dice guys for doing the right thing with the Battlefield 2142 installer when it encounters a version of Windows it doesn&#8217;t know about: [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: just jon</title>
		<link>http://lonesysadmin.net/2006/09/14/you-chose-poorly-says-the-installer/#comment-9580</link>
		<dc:creator>just jon</dc:creator>
		<pubDate>Fri, 15 Sep 2006 18:39:10 +0000</pubDate>
		<guid isPermaLink="false">http://lonesysadmin.net/2006/09/14/you-chose-poorly-says-the-installer/#comment-9580</guid>
		<description>Well, it imports with no problem on the Mac, but iMovie, IMHO, leaves a bit to be desired (but, then again, it's "free" with the OS..)  At least, it's tough if you have no idea what you're doing... And I don't.</description>
		<content:encoded><![CDATA[<p>Well, it imports with no problem on the Mac, but iMovie, IMHO, leaves a bit to be desired (but, then again, it&#8217;s &#8220;free&#8221; with the OS..)  At least, it&#8217;s tough if you have no idea what you&#8217;re doing&#8230; And I don&#8217;t.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
