<?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>TechPaladin Printing &#187; IT</title>
	<atom:link href="http://techpaladin.com/category/it/feed/" rel="self" type="application/rss+xml" />
	<link>http://techpaladin.com</link>
	<description></description>
	<lastBuildDate>Wed, 28 Mar 2012 23:25:27 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
		<item>
		<title>The Standard Mac IT Rant</title>
		<link>http://techpaladin.com/2008/06/20/the-standard-mac-it-rant/</link>
		<comments>http://techpaladin.com/2008/06/20/the-standard-mac-it-rant/#comments</comments>
		<pubDate>Fri, 20 Jun 2008 04:12:50 +0000</pubDate>
		<dc:creator>Nathaniel</dc:creator>
				<category><![CDATA[IT]]></category>
		<category><![CDATA[Mac OS X]]></category>
		<category><![CDATA[Windows]]></category>

		<guid isPermaLink="false">http://techpaladin.com/?p=139</guid>
		<description><![CDATA[Are you an IT person? No? Well, pretend that was a yes for a moment. I&#8217;d like to take a few moments to talk about Microsoft Windows as it relates to IT. The particular issue I&#8217;ve been having at the moment that out of the box, WIndows XP, well, just can&#8217;t do anything. You have [...]]]></description>
			<content:encoded><![CDATA[<p>Are you an IT person?  No?  Well, pretend that was a yes for a moment.  I&#8217;d like to take a few moments to talk about Microsoft Windows as it relates to IT.  The particular issue I&#8217;ve been having at the moment that out of the box, WIndows XP, well, just can&#8217;t <em>do</em> anything.  You have to install some crufty third-party software to do extremely basic things, such as:</p>
<ul>
<li>Disk image creation</li>
<li>Disk image mounting and management</li>
<li>Hard disk cloning</li>
<li>PDF reading</li>
<li>PDF creation</li>
<li>PDF editing (watermarking, rotation, etc)</li>
<li>The capacity to install the operating system on a USB-connected external hard drive</li>
</ul>
<p>I actually lied a little on that last one.  You see, that last one simply isn&#8217;t possible at all!  The situation was this: I had a <a href="http://en.wikipedia.org/wiki/Small_form_factor">small form-factor</a> PC that needed a 2.5&#8243; IDE hard drive.  So I figured, with my Mac-accustomed brain, &#8220;I&#8217;ll stick its blank hard drive into an external enclosure, plug that into a PC, then run Windows setup from there, setting the external hard drive as the target of the install.&#8221;</p>
<p>No dice.  Now first of all, the procedure that I just illustrated works in the Mac world.  It <em>works.</em>  I can install OS X on any sort of connected hard drive; via USB, via Firewire, from one Mac directly to another&#8217;s hard drive over Firewire, over the network via netboot—any way I like with whatever infrastructure I have available.  So it was somewhat frustrating when Windows stubbornly refused to install.  It would see the drive; I could even partition and format the drive, but install Windows?  Nope, nada.  Sadly, I&#8217;m pretty used to this sort of cantankerous hocus-pocus, so I started thinking about how I could actually get around the problem to accomplish the goal.
<p>I had a mad combination of external enclosures that supported different drive standards and some of which didn&#8217;t work on some computers, and I also had several types of drives; 2 SATA and 1 IDE.  Here&#8217;s what I wound up doing: connecting one of the 2.5&#8243; SATA drives to some PC&#8217;s internal SATA connector, thus temporarily making it an internal drive.  I then installed Windows on it.  When I was done, I removed the drive, reconnected the PC&#8217;s original 3.5&#8243; internal drive, and booted it up.  Then I put the 2.5&#8243; SATA drive into an external enclosure and attached that to the PC, and then did the same with a 2.5&#8243; IDE drive.  Now, as luck would refuse to have it, the IDE drive was being used for backup, so couldn&#8217;t just clone the SATA drive onto the IDE one unless I didn&#8217;t care much about that backup.  So I copied its backup onto the SATA drive, giving me a SATA drive with a Windows install on it sitting alongside a copy of the backup, and an IDE drive with the original backup.  The next step was to clone the SATA drive with everything on it onto the IDE drive, whereupon I deleted the backup from the IDE drive (didn&#8217;t need it there) and deleted Windows from the SATA drive (don&#8217;t need Windows on a backup disk).  Finally <em>(finally!)</em>, I put the IDE drive into the computer and…</p>
<p><strong>DISK BOOT FAILURE</strong></p>
<p>…and so on and so on and so on.  The nightmare continued throughout the whole day, and in the end, I still didn&#8217;t manage to get the PC up and running.  In the end, I ended up attaching an internal optical drive to the motherboard&#8217;s ATA connector ((Also, for some reason, this motherboard ATA connector actually used pin 20, so I had to poke a hole in my ATA cable to get the damn thing to fit, go figure.)) and an AC to <a href="http://en.wikipedia.org/wiki/Molex_connector">molex</a> adapter, and then I installed Windows from there finally I went through the refreshingly <strong>usual</strong> nonsense of hunting down drivers, and even then it took about 3 hours to get the LAN drivers working for some still unknown reason.  Thank goodness it was <em>only two days</em> of lost time.</p>
<p>By contrast, here&#8217;s what the process would look like if this situation had involved Macs:</p>
<ol>
<li>Boot the Mac into Firewire Target Mode and connect it to another Mac.</li>
<li>Pop an install DVD into the connected Mac and use it to install Mac OS X on the Firewire Target Mode computer.</li>
</ol>
<p>It takes about an hour.  I&#8217;m serious; deadly serious.  I&#8217;ve done this process literally dozens of times, and it&#8217;s alarming how much more time-efficient is is than swapping drives, cracking open cases, modifying ATA cables to fit, or fiddling and diddling with Windows.  Even the installation of Mac OS X takes about half the time that installing Windows does; the copy of Windows I installed just this morning took an hour and 22 minutes, and that&#8217;s before I installed the drivers.  By contrast, The version of OS X I installed about a week ago that needed no such post-install mumbo-jumbo completed in more like 40 minutes.</p>
<p>This is not my first IT job.  Based on my experiences here at <a href="http://www.cliqk.com/">CLIQK Digital</a> as well as those as my previous job, I can confidently say that Macs running Mac OS X are significantly more robust than either Windows PCs, or even those very same Macs when they&#8217;re running Windows.  The Macs in my last workplace were a dream to support compared to the Dell PCs we had which routinely fell over and died as a matter of course.  I can&#8217;t even begin to express how many times I spent a whole morning attacking a Windows problem so unique in its randomness that it surprised the entire department.</p>
<p>As an IT person, my primary goal is to make the machines I supports as robust and fault-tolerant as possible, for the simple and selfish reason that it makes my job easier.  When PCs get overrun with malware or <a href="http://techpaladin.com/2007/08/27/fun-in-pc-land-or-why-macs-are-faster/">confused by floppy disks</a>, it wastes my time fixing problems that don&#8217;t ever happen in Mac-land and prevents me from accomplishing other tasks, which often consist of far more meaningful things like updating important websites, creating policies for new computer use trends, training staff in new software, or transitioning to more efficient back-end systems.  Having to install Acrobat Reader for the zillionth time or re-re-explain that opening random email attachments will result in lost time for everyone just adds to my already-full plate of technical tasks.</p>
<p>The intertubes are filled with stories of organizations that overcame their institutional inertia and <a href="http://linux.slashdot.org/article.pl?sid=07/09/07/2147256&#038;from=rss">saved trucktons of cash</a> by switching to Macs or Linux.  I believe it.  Microsoft&#8217;s IT-centric technologies like <a href="http://en.wikipedia.org/wiki/Microsoft_Exchange_Server">Exchange</a> and <a href="http://en.wikipedia.org/wiki/Active_directory">Active Directory</a> are hellishly complex and notoriously unreliable without full-time support staffs (staves?) and backup servers up the wazoo.  This is to say nothing of the <a href="http://www.microsoft.com/licensing/programs/isv/default.mspx">tens of thousands of dollars</a> routinely shelled out for outrageous per-user licensing fees for these products.  And it&#8217;s not just lost money, it&#8217;s lost time; in my current workplace, we don&#8217;t even have the &#8220;luxury&#8221; of all of our computers being from one brand, so all of them need different drivers to run and different keystrokes to enter the BIOS, which, as you may be able to imagine, wastes. a. lot. of. time.  Bottom line:  Windows is expensive and unreliable; the very bane of IT.  The sooner it&#8217;s replaced by something—anything—easier to maintain, the better.</p>
]]></content:encoded>
			<wfw:commentRss>http://techpaladin.com/2008/06/20/the-standard-mac-it-rant/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>

