<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
	<title type="html"><![CDATA[DriverPacks.net Forum - Quick question: How is the PhysX installer launched?]]></title>
	<link rel="self" href="http://forum.driverpacks.net/extern.php?action=feed&amp;tid=4273&amp;type=atom"/>
	<updated>2010-01-13T19:27:18Z</updated>
	<generator>PunBB</generator>
	<id>http://forum.driverpacks.net/viewtopic.php?id=4273</id>
		<entry>
			<title type="html"><![CDATA[Re: Quick question: How is the PhysX installer launched?]]></title>
			<link rel="alternate" href="http://forum.driverpacks.net/viewtopic.php?pid=36036#p36036"/>
			<content type="html"><![CDATA[<p>I still squeeze everything onto a 700MB disc. I like to keep it old school.</p><br /><p>Anyway, thanks for testing and helping me out. If you guys change your mind, you&#039;re more than welcome to use the pack however you please.</p>]]></content>
			<author>
				<name><![CDATA[dumpydooby]]></name>
				<uri>http://forum.driverpacks.net/profile.php?id=13</uri>
			</author>
			<updated>2010-01-13T19:27:18Z</updated>
			<id>http://forum.driverpacks.net/viewtopic.php?pid=36036#p36036</id>
		</entry>
		<entry>
			<title type="html"><![CDATA[Re: Quick question: How is the PhysX installer launched?]]></title>
			<link rel="alternate" href="http://forum.driverpacks.net/viewtopic.php?pid=36022#p36022"/>
			<content type="html"><![CDATA[<p>- Does my modification break the signature of the driver?<br />NO.&nbsp; Running sigverif.exe confirms all the nvidia crap is still signed. <img src="http://forum.driverpacks.net/img/smilies/smile.png" width="15" height="15" alt="smile" /></p><p>- Do you want me to change anything about <em>PhysX_9.09.1112_SystemSoftware.exe</em>?<br />Nope.&nbsp; It&#039;s fine the way it is.&nbsp; If you want to tinker with it to add more checks/failsafes, go for it if you&#039;ve got time to waste.</p><p>Although, we&#039;ll probably still maintain the original PhysX installers for those nitpicky types who only want original (untouched) installers.<br />But it&#039;s nice to have alternatives for space-conscious folks like yourself.</p>]]></content>
			<author>
				<name><![CDATA[mr_smartepants]]></name>
				<uri>http://forum.driverpacks.net/profile.php?id=1602</uri>
			</author>
			<updated>2010-01-11T09:27:42Z</updated>
			<id>http://forum.driverpacks.net/viewtopic.php?pid=36022#p36022</id>
		</entry>
		<entry>
			<title type="html"><![CDATA[Re: Quick question: How is the PhysX installer launched?]]></title>
			<link rel="alternate" href="http://forum.driverpacks.net/viewtopic.php?pid=36020#p36020"/>
			<content type="html"><![CDATA[<p>Having the file repeated three times in a single archive doesn&#039;t noticeably increase the size of the archive. The problem is that the Nvidia installer uses <em>terrible compression</em>, and it can&#039;t be compressed down much more due to the <a href="http://en.wikipedia.org/wiki/Shannon_limit">Shannon limit</a> (I think you guys have it going from 35MB down to 30MB or something). By decompressing everything, I am able to then compress it <em>the right way</em> down to 8-9MB (down from a whopping 100MB or so). I made it into a &quot;multimode&quot; application because those are what I prefer.</p><br /><br /><p>Anyway, a couple of questions/ideas:</p><p>- Does my modification break the signature of the driver?</p><p>- Do you want me to change anything about <em>PhysX_9.09.1112_SystemSoftware.exe</em>? I can make it look for PhysX.exe, or I can make it do stuff with command-line paramters, check the registry, or whatever. As of right now, it&#039;s literally one line of code with zero fail-safe. If PhysX.exe isn&#039;t present, then it will return an error alert. While this isn&#039;t a problem on a fresh install, it might cause problems with KTD if a person deletes physx.exe, but the &quot;dummy&quot; file remains in tact.</p>]]></content>
			<author>
				<name><![CDATA[dumpydooby]]></name>
				<uri>http://forum.driverpacks.net/profile.php?id=13</uri>
			</author>
			<updated>2010-01-11T02:53:10Z</updated>
			<id>http://forum.driverpacks.net/viewtopic.php?pid=36020#p36020</id>
		</entry>
		<entry>
			<title type="html"><![CDATA[Re: Quick question: How is the PhysX installer launched?]]></title>
			<link rel="alternate" href="http://forum.driverpacks.net/viewtopic.php?pid=36013#p36013"/>
			<content type="html"><![CDATA[<p>We could just as easily add an .ini discriminator and let DriverPacks Finisher handle the install.&nbsp; But I prefer to leave everything alone and have the drivers digitally signed whenever possible.<br />But having three instances of the identical software in the same Third Party DriverPack bothers me.&nbsp; I wish we could have a single installer and have un7zip extract the one to the three directories.</p><p>I&#039;ll have to play around with your idea.&nbsp; I&#039;ll test and report back.</p><p>*Edit<br />Works perfectly.&nbsp; Great job!</p>]]></content>
			<author>
				<name><![CDATA[mr_smartepants]]></name>
				<uri>http://forum.driverpacks.net/profile.php?id=1602</uri>
			</author>
			<updated>2010-01-10T15:49:14Z</updated>
			<id>http://forum.driverpacks.net/viewtopic.php?pid=36013#p36013</id>
		</entry>
		<entry>
			<title type="html"><![CDATA[Re: Quick question: How is the PhysX installer launched?]]></title>
			<link rel="alternate" href="http://forum.driverpacks.net/viewtopic.php?pid=36011#p36011"/>
			<content type="html"><![CDATA[<p>I don&#039;t have an Nvidia card. </p><br /><p>Anyone want to give it a shot?</p><p>Download: <a href="http://xp.xpdnc.org/temp/DP_Graphics_PhysX_wnt5_x86-32_1001dd1a.7z">http://xp.xpdnc.org/temp/DP_Graphics_Ph … 001dd1a.7z</a><br />md5: 0746926668f9c9cf0e6fe23544447318<br />compressed: 9.2MB | decompressed: 10.6MB</p><br /><p>What&#039;s in it:<br /></p><div class="codebox"><pre><code>%SystemDrive%\D\
%SystemDrive%\D\G\
%SystemDrive%\D\G\PhysX.exe
%SystemDrive%\D\G\N1\
%SystemDrive%\D\G\N1\PhysX_9.09.1112_SystemSoftware.exe
%SystemDrive%\D\G\N3\
%SystemDrive%\D\G\N3\PhysX_9.09.1112_SystemSoftware.exe
%SystemDrive%\D\G\NM\
%SystemDrive%\D\G\NM\PhysX_9.09.1112_SystemSoftware.exe</code></pre></div><p><em>PhysX_9.09.1112_SystemSoftware.exe</em> will execute the following:<br /></p><div class="codebox"><pre><code>..\PhysX.exe -ai</code></pre></div>]]></content>
			<author>
				<name><![CDATA[dumpydooby]]></name>
				<uri>http://forum.driverpacks.net/profile.php?id=13</uri>
			</author>
			<updated>2010-01-10T00:42:17Z</updated>
			<id>http://forum.driverpacks.net/viewtopic.php?pid=36011#p36011</id>
		</entry>
		<entry>
			<title type="html"><![CDATA[Re: Quick question: How is the PhysX installer launched?]]></title>
			<link rel="alternate" href="http://forum.driverpacks.net/viewtopic.php?pid=36008#p36008"/>
			<content type="html"><![CDATA[<p>Gah! No wonder nothing was turning up.</p><br /><p>Do you know if there is an easy way to change the command line that&#039;s actually passed to launch the installer? (the one above simply tells it to instantiate the installer, but it doesn&#039;t lead to the command line that&#039;s executed) </p><br /><p>Basically, what I&#039;m doing is pulling the MSI out of the installer EXE, then doing an admin install of the MSI,&nbsp; and repackaging it. This should significantly reduce the size of my PhysX DriverPack. But in order to do it, I need to change the command-line to execute my MSI instead of Nvidia&#039;s EXE.</p><br /><p>Any ideas?</p><br /><br /><p>edit--</p><p>On second thought, I could actually do what you guys do with SETUP.EXE, and just create an EXE file that tells it to execute my MSI file at a specified time or upon a specified trigger. That would probably be better anyway because it would significantly reduce the amount of space that&#039;s taken up when the files are extracted (since the MSI would only have to appear once in the DriverPack).</p><p>I&#039;ll toy around with it and see what I can come up with.</p>]]></content>
			<author>
				<name><![CDATA[dumpydooby]]></name>
				<uri>http://forum.driverpacks.net/profile.php?id=13</uri>
			</author>
			<updated>2010-01-09T23:00:08Z</updated>
			<id>http://forum.driverpacks.net/viewtopic.php?pid=36008#p36008</id>
		</entry>
		<entry>
			<title type="html"><![CDATA[Re: Quick question: How is the PhysX installer launched?]]></title>
			<link rel="alternate" href="http://forum.driverpacks.net/viewtopic.php?pid=36006#p36006"/>
			<content type="html"><![CDATA[<p>LOL, nvidia calls the physx installer from within their .inf (same with their HDaudio installer).&nbsp; The installation happens around T-34.<br /></p><div class="codebox"><pre><code>[nv_commonBase_addreg__03]
HKLM,&quot;Software\NVIDIA Corporation\Installer&quot;,HDAudioInstall,%REG_DWORD%,1
HKLM,&quot;Software\NVIDIA Corporation\Installer&quot;,PhysXInstall,%REG_DWORD%,1
[Strings]
REG_DWORD = 0x00010001</code></pre></div><p>It&#039;s magic! <img src="http://forum.driverpacks.net/img/smilies/big_smile.png" width="15" height="15" alt="big_smile" /></p>]]></content>
			<author>
				<name><![CDATA[mr_smartepants]]></name>
				<uri>http://forum.driverpacks.net/profile.php?id=1602</uri>
			</author>
			<updated>2010-01-09T22:47:24Z</updated>
			<id>http://forum.driverpacks.net/viewtopic.php?pid=36006#p36006</id>
		</entry>
		<entry>
			<title type="html"><![CDATA[Quick question: How is the PhysX installer launched?]]></title>
			<link rel="alternate" href="http://forum.driverpacks.net/viewtopic.php?pid=36005#p36005"/>
			<content type="html"><![CDATA[<p>I can&#039;t figure out where you actually have the command set to launch PhysX, and what sets that command. I&#039;d imagine that it would all start at BASE or DPsFnshr because PhysX doesn&#039;t have an INI file with it, so something has to detect that it&#039;s there. What is it?</p>]]></content>
			<author>
				<name><![CDATA[dumpydooby]]></name>
				<uri>http://forum.driverpacks.net/profile.php?id=13</uri>
			</author>
			<updated>2010-01-09T22:38:36Z</updated>
			<id>http://forum.driverpacks.net/viewtopic.php?pid=36005#p36005</id>
		</entry>
</feed>
