<?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>Tardis Technologies &#187; Windows</title>
	<atom:link href="http://www.tardistech.com/wp/category/windows/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.tardistech.com/wp</link>
	<description>Advanced Software for Microsoft Windows and the Web</description>
	<lastBuildDate>Fri, 13 Jan 2012 15:21:35 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Where is the MSDN File Transfer Manager installed?</title>
		<link>http://www.tardistech.com/wp/2010/10/06/where-is-the-msdn-file-transfer-manager-installed/</link>
		<comments>http://www.tardistech.com/wp/2010/10/06/where-is-the-msdn-file-transfer-manager-installed/#comments</comments>
		<pubDate>Wed, 06 Oct 2010 19:29:48 +0000</pubDate>
		<dc:creator>Rob</dc:creator>
				<category><![CDATA[Windows]]></category>

		<guid isPermaLink="false">http://www.tardistech.com/wp/?p=53</guid>
		<description><![CDATA[02/25/2011 Update: On my Windows 7 x64 (SP1) machine, I found it located in: C:\Program Files (x86)\Microsoft File Transfer Manager\TransferMgr.exe Of course, if you&#8217;re running 32-bit, then drop the &#8221; (x86)&#8221;. &#8212;&#8212;&#8212;&#8212;&#8212;&#8212; File Transfer Manager for MSDN can be found in the following location: %SystemRoot%\Downloaded Program Files\TransferMgr.exe See http://bit.ly/bMhDVj]]></description>
			<content:encoded><![CDATA[<p>02/25/2011 Update: On my Windows 7 x64 (SP1) machine, I found it located in:</p>
<p style="padding-left: 30px;">C:\Program Files (x86)\Microsoft File Transfer Manager\TransferMgr.exe</p>
<p>Of course, if you&#8217;re running 32-bit, then drop the &#8221; (x86)&#8221;.</p>
<p>&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;</p>
<p>File Transfer Manager for MSDN can be found in the following location:</p>
<p style="padding-left: 30px;">%SystemRoot%\Downloaded Program Files\TransferMgr.exe</p>
<p>See <a title="http://bit.ly/bMhDVj" rel="nofollow" href="http://bit.ly/bMhDVj" target="_blank">http://bit.ly/bMhDVj</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.tardistech.com/wp/2010/10/06/where-is-the-msdn-file-transfer-manager-installed/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Ping, Windows 7, and the Windows Firewall</title>
		<link>http://www.tardistech.com/wp/2010/09/30/ping-windows-7-and-the-windows-firewall/</link>
		<comments>http://www.tardistech.com/wp/2010/09/30/ping-windows-7-and-the-windows-firewall/#comments</comments>
		<pubDate>Thu, 30 Sep 2010 21:16:34 +0000</pubDate>
		<dc:creator>Rob</dc:creator>
				<category><![CDATA[Windows]]></category>

		<guid isPermaLink="false">http://www.tardistech.com/wp/?p=55</guid>
		<description><![CDATA[If you cannot ping a Windows 7 box, don&#8217;t just disable the Windows Firewall.  See the following page describing how to enable the included ICMP Echo rule in the Windows Firewall: http://www.fixya.com/support/r5359816-allow_ping_icmp_echo_request_windows_7 Note that I shut down the Windows Firewall service (net stop mpssvc) and this did not &#8220;re-enable&#8221; ping.  I had to add the [...]]]></description>
			<content:encoded><![CDATA[<p>If you cannot ping a Windows 7 box, don&#8217;t just disable the Windows  Firewall.  See the following page describing how to enable the included  ICMP Echo rule in the Windows Firewall:</p>
<p><a href="http://www.fixya.com/support/r5359816-allow_ping_icmp_echo_request_windows_7" target="_blank">http://www.fixya.com/support/r5359816-allow_ping_icmp_echo_request_windows_7</a></p>
<p>Note that I shut down the Windows Firewall service (net stop mpssvc)  and this did not &#8220;re-enable&#8221; ping.  I had to add the firewall rule.   There may be another solution, but this solved my problem.</p>
<p>Rob</p>
]]></content:encoded>
			<wfw:commentRss>http://www.tardistech.com/wp/2010/09/30/ping-windows-7-and-the-windows-firewall/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>(Re)installing the iTunes COM API in Windows</title>
		<link>http://www.tardistech.com/wp/2006/04/10/reinstalling-the-itunes-com-api-in-windows/</link>
		<comments>http://www.tardistech.com/wp/2006/04/10/reinstalling-the-itunes-com-api-in-windows/#comments</comments>
		<pubDate>Tue, 11 Apr 2006 00:07:49 +0000</pubDate>
		<dc:creator>Rob</dc:creator>
				<category><![CDATA[iTunes]]></category>
		<category><![CDATA[Windows]]></category>

		<guid isPermaLink="false">http://www.tardistech.com/wp/?p=7</guid>
		<description><![CDATA[I ran into a problem recently where a third-party application could not launch iTunes and the Apple iTunes COM SDK also could not launch iTunes.  I have the 64-bit version of Windows XP Professional (x64 Edition) installed on my Athlon 64 computer and initially thought that perhaps MarkAble (an excellent tool for converting audio files [...]]]></description>
			<content:encoded><![CDATA[<p>I ran into a problem recently where a <a target="_blank" href="http://www.ipodsoft.com/index.php?/software/markable">third-party application</a> could not launch iTunes and the <a target="_blank" href="http://developer.apple.com/sdk/itunescomsdk.html">Apple iTunes COM SDK</a> also could not launch iTunes.  I have the 64-bit version of Windows XP Professional (x64 Edition) installed on my Athlon 64 computer and initially thought that perhaps <a target="_blank" href="http://www.ipodsoft.com/index.php?/software/markable">MarkAble</a> (an excellent tool for converting audio files into iTunes/iPod Audiobooks) was not working correctly on my 64-bit OS.   However, its problem was with launching iTunes, not calling any of iTunes&#8217; functionality.</p>
<p><strong>Technical Explanation</strong></p>
<p>It was not a 64-bit issue at all.  For some reason, my iTunes  COM type library (TLB) was never registered on the system.   So, values  like &#8220;HKEY_LOCAL_MACHINE\SOFTWARE\Classes\iTunes.Application&#8221; and  &#8220;HKEY_LOCAL_MACHINE\SOFTWARE\Classes\iTunes.Application.1&#8243; were not  registered on my system.  Neither the ITunes.Application GUID  (DC0C2640-1415-4644-875C-6F4D769839BA) nor the iTunes TypeLib for all of  the COM interfaces (9E93C96F-CF0D-43f6-8BA8-B807A3370712) showed up  anywhere in my registry.</p>
<p><strong>Possible Explanations</strong></p>
<p>What caused this?   This may happen when iTunes does not complete its  installation process or when the type libraries do not get registered  correctly.  Either situation could occur on a 32-bit or a 64-bit version  of Windows.</p>
<p><strong>Solution</strong></p>
<p>How did I fix it?  I just dropped to a command-prompt, changed to the  &#8220;C:\Program Files (x86)\iTunes&#8221; directory, and issued the following command:</p>
<blockquote><p>itunes /regserver</p></blockquote>
<p>That did the trick!   Now MarkAble works like a charm.   The iTunes COM  SDK should also work fine now.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.tardistech.com/wp/2006/04/10/reinstalling-the-itunes-com-api-in-windows/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

