<?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>Scottie’s Tech.Info &#187; x64</title>
	<atom:link href="http://scottiestech.info/tag/x64/feed/" rel="self" type="application/rss+xml" />
	<link>http://scottiestech.info</link>
	<description>A chimpanzee and two trainees could run her!</description>
	<lastBuildDate>Tue, 24 Jan 2012 18:03:47 +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>How to fix &#8220;Windows cannot connect to printer&#8221; Errors in Windows 7</title>
		<link>http://scottiestech.info/2010/09/21/how-to-fix-windows-cannot-connect-to-printer-errors-in-windows-7/</link>
		<comments>http://scottiestech.info/2010/09/21/how-to-fix-windows-cannot-connect-to-printer-errors-in-windows-7/#comments</comments>
		<pubDate>Tue, 21 Sep 2010 12:58:27 +0000</pubDate>
		<dc:creator>Scottie</dc:creator>
				<category><![CDATA[Computers]]></category>
		<category><![CDATA[hotfix]]></category>
		<category><![CDATA[printer]]></category>
		<category><![CDATA[windows]]></category>
		<category><![CDATA[x64]]></category>

		<guid isPermaLink="false">http://scottiestech.info/?p=443</guid>
		<description><![CDATA[Let's say you're running Windows 7 on a computer connected to a local network. There is a shared printer running on a different machine on the network. The drivers for the printer are installed on the remote machine, and the printer is shared. You think that you'll just sit down at your puter, use the Add Printer feature, connect to the remote printer, the driver will be copied over to your machine automagically, and you'll be off and running. But then you see this: Windows cannot connect to the printer. Operation could not be completed (error 0x0000007e). The solution to your problem is very simple, and is even available as a Hotfix from Microsoft that will be incorporated into Windows 7 SP1.]]></description>
		<wfw:commentRss>http://scottiestech.info/2010/09/21/how-to-fix-windows-cannot-connect-to-printer-errors-in-windows-7/feed/</wfw:commentRss>
		<slash:comments>10</slash:comments>
		</item>
		<item>
		<title>64-bit Printing Using a Driver for a Similar Model</title>
		<link>http://scottiestech.info/2010/04/15/64-bit-printing-using-a-driver-for-a-similar-model/</link>
		<comments>http://scottiestech.info/2010/04/15/64-bit-printing-using-a-driver-for-a-similar-model/#comments</comments>
		<pubDate>Thu, 15 Apr 2010 07:03:24 +0000</pubDate>
		<dc:creator>Scottie</dc:creator>
				<category><![CDATA[Computers]]></category>
		<category><![CDATA[printer]]></category>
		<category><![CDATA[windows]]></category>
		<category><![CDATA[x64]]></category>

		<guid isPermaLink="false">http://scottiestech.info/?p=377</guid>
		<description><![CDATA[Printing with 64-bit Windows can be a lot of fun if you don't have a 64-bit driver.

As I mentioned in Windows x64: How to Print to Any Printer Even Without a 64-bit Driver, there are ways to make your printer talk, even if they are a bit involved.

There is one other trick in particular that you might want to try first, though: use a similar 64-bit driver from the same manufacturer and fool Windows into thinking that everything is working fine!]]></description>
		<wfw:commentRss>http://scottiestech.info/2010/04/15/64-bit-printing-using-a-driver-for-a-similar-model/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Save Time and Preserve Your Sanity with Windows Easy Transfer</title>
		<link>http://scottiestech.info/2009/09/12/save-time-and-preserve-your-sanity-with-windows-easy-transfer/</link>
		<comments>http://scottiestech.info/2009/09/12/save-time-and-preserve-your-sanity-with-windows-easy-transfer/#comments</comments>
		<pubDate>Sat, 12 Sep 2009 10:00:14 +0000</pubDate>
		<dc:creator>Scottie</dc:creator>
				<category><![CDATA[Computers]]></category>
		<category><![CDATA[upgrade]]></category>
		<category><![CDATA[windows]]></category>
		<category><![CDATA[x64]]></category>

		<guid isPermaLink="false">http://scottiestech.info/?p=269</guid>
		<description><![CDATA[If you're like me, when it comes time to upgrade Windows or the hardware inside a computer, you do things the old fashioned way: you manually copy all the user's desktop, settings, and data onto a backup drive, and then restore it all after the upgrade. Recently I have discovered a much, much easier and faster way to do the same thing. It's called Windows Easy Transfer, and it's present in Vista, Windows 7, and you can even install it on an old XP box.]]></description>
		<wfw:commentRss>http://scottiestech.info/2009/09/12/save-time-and-preserve-your-sanity-with-windows-easy-transfer/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Calling a 32-bit System Command from a Script in x64 Windows</title>
		<link>http://scottiestech.info/2009/06/20/calling-a-32-bit-system-command-from-a-script-in-x64-windows/</link>
		<comments>http://scottiestech.info/2009/06/20/calling-a-32-bit-system-command-from-a-script-in-x64-windows/#comments</comments>
		<pubDate>Sat, 20 Jun 2009 09:58:28 +0000</pubDate>
		<dc:creator>Scottie</dc:creator>
				<category><![CDATA[Programming]]></category>
		<category><![CDATA[ruby]]></category>
		<category><![CDATA[windows]]></category>
		<category><![CDATA[x64]]></category>

		<guid isPermaLink="false">http://scottiestech.info/?p=221</guid>
		<description><![CDATA[Let's say you've written a little script that calls a Windows command such as nbtstat. When you try to run the script in x64 Windows, you get an annoying "File not found" error - even though you can see the command sitting in the \Windows\system32 folder. What's going on here?]]></description>
		<wfw:commentRss>http://scottiestech.info/2009/06/20/calling-a-32-bit-system-command-from-a-script-in-x64-windows/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<item>
		<title>Windows x64: How to Print to Any Printer Even Without a 64-bit Driver</title>
		<link>http://scottiestech.info/2009/06/06/windows-x64-how-to-print-to-any-printer-even-without-a-64-bit-driver/</link>
		<comments>http://scottiestech.info/2009/06/06/windows-x64-how-to-print-to-any-printer-even-without-a-64-bit-driver/#comments</comments>
		<pubDate>Sat, 06 Jun 2009 21:49:34 +0000</pubDate>
		<dc:creator>Scottie</dc:creator>
				<category><![CDATA[Computers]]></category>
		<category><![CDATA[printer]]></category>
		<category><![CDATA[windows]]></category>
		<category><![CDATA[x64]]></category>

		<guid isPermaLink="false">http://scottiestech.info/?p=206</guid>
		<description><![CDATA[So, let's say you've taken the plunge and installed 64-bit Windows XP, Vista, or Windows 7. All is going well, until you try to install your printers. It's at that point that you discover that Windows doesn't have a 64-bit driver for your printer. Worse yet, the manufacturer may not provide one, either! What the heck are you supposed to do now? Fortunately, there IS a way. And, strangely enough, you have Mac OS X to thank for this solution!]]></description>
		<wfw:commentRss>http://scottiestech.info/2009/06/06/windows-x64-how-to-print-to-any-printer-even-without-a-64-bit-driver/feed/</wfw:commentRss>
		<slash:comments>7</slash:comments>
		</item>
		<item>
		<title>The 3GB Barrier: Why you want a 64-bit OS</title>
		<link>http://scottiestech.info/2009/05/02/the-3gb-barrier-why-you-want-a-64-bit-os/</link>
		<comments>http://scottiestech.info/2009/05/02/the-3gb-barrier-why-you-want-a-64-bit-os/#comments</comments>
		<pubDate>Sat, 02 May 2009 13:12:14 +0000</pubDate>
		<dc:creator>Scottie</dc:creator>
				<category><![CDATA[Computers]]></category>
		<category><![CDATA[linux]]></category>
		<category><![CDATA[OSX]]></category>
		<category><![CDATA[processor]]></category>
		<category><![CDATA[RAM]]></category>
		<category><![CDATA[windows]]></category>
		<category><![CDATA[x64]]></category>

		<guid isPermaLink="false">http://scottiestech.info/?p=166</guid>
		<description><![CDATA[I'm sure you've all heard some hype about 64-bit this and 64-bit that. The thing I read the most is that a 64-bit operating system or piece of software is automagically twice as fast as a 32-bit one. Not so. In any case, most people today are using a 32-bit operating system, but a surprising number have already switched to a 64-bit OS. Or in some cases, a quasi-64-bit OS... There is one true reason though why you will actually want to switch to a 64-bit OS in the near future: the infamous 3GB barrier. Just what the heck is this mystical barrier, and why should you care?]]></description>
		<wfw:commentRss>http://scottiestech.info/2009/05/02/the-3gb-barrier-why-you-want-a-64-bit-os/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

