<?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>DeckerD: Drew&#039;s Personal Corner of the Web &#187; Workaround</title>
	<atom:link href="http://www.deckerd.com/tag/workaround/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.deckerd.com</link>
	<description></description>
	<lastBuildDate>Fri, 01 Jan 2010 20:22:16 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>VMWare: Unable to load the BIOS due to the VMWare Splash screen not showing</title>
		<link>http://www.deckerd.com/core/vmware-unable-to-load-the-bios-due-to-the-vmware-splash-screen-not-showing/</link>
		<comments>http://www.deckerd.com/core/vmware-unable-to-load-the-bios-due-to-the-vmware-splash-screen-not-showing/#comments</comments>
		<pubDate>Tue, 06 Jan 2009 10:47:46 +0000</pubDate>
		<dc:creator>Drew</dc:creator>
				<category><![CDATA[Core]]></category>
		<category><![CDATA[The Notebook]]></category>
		<category><![CDATA[Tips]]></category>
		<category><![CDATA[Virtualization]]></category>
		<category><![CDATA[VMWare]]></category>
		<category><![CDATA[Workaround]]></category>

		<guid isPermaLink="false">http://www.deckerd.com/?p=192</guid>
		<description><![CDATA[<p class="prepend-1 append-1 featuredTitle">After upgrading my version of VMWare from VMWare 1.6 to VMWare 2.0, and then installing and updating the VMWare Infrastructure Client, I had a new issue; accessing the BIOS from the VMWare splash startup screen. Before the upgrade, VMWare would display the VMWare splash screen as it loaded the NVRAM (I believe), and had a section that said "Press F2 to enter setup"; it went by fast, but it was at least there. After fiddling around with VMWare for a few minutes, I found a way around this <a href="http://www.deckerd.com/core/vmware-unable-to-load-the-bios-due-to-the-vmware-splash-screen-not-showing/">Read More &#187;</a></p>]]></description>
		<wfw:commentRss>http://www.deckerd.com/core/vmware-unable-to-load-the-bios-due-to-the-vmware-splash-screen-not-showing/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Splunk Free: .htaccess Protection using Apache</title>
		<link>http://www.deckerd.com/core/splunk-free-htaccess-protection-using-apache/</link>
		<comments>http://www.deckerd.com/core/splunk-free-htaccess-protection-using-apache/#comments</comments>
		<pubDate>Wed, 12 Dec 2007 01:29:06 +0000</pubDate>
		<dc:creator>Drew</dc:creator>
				<category><![CDATA[Core]]></category>
		<category><![CDATA[Apache]]></category>
		<category><![CDATA[CentOS]]></category>
		<category><![CDATA[htaccess]]></category>
		<category><![CDATA[Sys Admin]]></category>
		<category><![CDATA[The Notebook]]></category>
		<category><![CDATA[UNIX/Linux]]></category>
		<category><![CDATA[Workaround]]></category>

		<guid isPermaLink="false">http://www.deckerd.com/splunk-free-htaccess-protection-using-apache/</guid>
		<description><![CDATA[<p class="prepend-1 append-1 featuredTitle">You ever hear of Splunk? Splunk enables you to search and navigate all your logs and IT data in real time; logs, configurations, messages, traps and alerts, scripts and metrics. It's an awesome tool to make it easier to monitor and watch your log files. Unfortunately, Splunk is expensive. How expensive? Try $5000 a year, for the cheapest license. Here's the main problem; the free version of Splunk does not come with any user authentication, not even Admin authentication. This means that <a href="http://www.deckerd.com/core/splunk-free-htaccess-protection-using-apache/">Read More &#187;</a></p>]]></description>
		<wfw:commentRss>http://www.deckerd.com/core/splunk-free-htaccess-protection-using-apache/feed/</wfw:commentRss>
		<slash:comments>32</slash:comments>
		</item>
		<item>
		<title>Windows Fix: &#8220;Insufficient system resources exist to complete the API&#8221;</title>
		<link>http://www.deckerd.com/core/windows-fix-insufficient-system-resources-exist-to-complete-the-api/</link>
		<comments>http://www.deckerd.com/core/windows-fix-insufficient-system-resources-exist-to-complete-the-api/#comments</comments>
		<pubDate>Sun, 22 Jul 2007 07:29:25 +0000</pubDate>
		<dc:creator>Drew</dc:creator>
				<category><![CDATA[Core]]></category>
		<category><![CDATA[Hardware]]></category>
		<category><![CDATA[Memory/RAM]]></category>
		<category><![CDATA[The Notebook]]></category>
		<category><![CDATA[Tips]]></category>
		<category><![CDATA[Windows]]></category>
		<category><![CDATA[Windows XP]]></category>
		<category><![CDATA[Workaround]]></category>

		<guid isPermaLink="false">http://www.deckerd.com/windows-fix-insufficient-system-resources-exist-to-complete-the-api/</guid>
		<description><![CDATA[<p class="prepend-1 append-1 featuredTitle">Ugh. Another Windows error. Another Windows error that really doesn't tell you what is really wrong; some (most) people aren't nerds. Don't worry, I've got your fix right here. This has to do with memory on your Windows XP system. Have you tried Hibernating or putting your system into standby after upgrading your RAM? If you have, keep on reading. Alright, while this isn't a very descriptive error message to the average computer user, a simple Google search can have your answer in no <a href="http://www.deckerd.com/core/windows-fix-insufficient-system-resources-exist-to-complete-the-api/">Read More &#187;</a></p>]]></description>
		<wfw:commentRss>http://www.deckerd.com/core/windows-fix-insufficient-system-resources-exist-to-complete-the-api/feed/</wfw:commentRss>
		<slash:comments>17</slash:comments>
		</item>
		<item>
		<title>Curing &#8216;Symbolic link not allowed&#8217; (Apache 2.0)</title>
		<link>http://www.deckerd.com/core/curing-symbolic-link-not-allowed-apache-20/</link>
		<comments>http://www.deckerd.com/core/curing-symbolic-link-not-allowed-apache-20/#comments</comments>
		<pubDate>Thu, 14 Jun 2007 20:19:39 +0000</pubDate>
		<dc:creator>Drew</dc:creator>
				<category><![CDATA[Core]]></category>
		<category><![CDATA[Apache]]></category>
		<category><![CDATA[CentOS]]></category>
		<category><![CDATA[Debian]]></category>
		<category><![CDATA[File Systems]]></category>
		<category><![CDATA[Red Hat]]></category>
		<category><![CDATA[Security]]></category>
		<category><![CDATA[Software]]></category>
		<category><![CDATA[Sys Admin]]></category>
		<category><![CDATA[The Notebook]]></category>
		<category><![CDATA[Ubuntu]]></category>
		<category><![CDATA[UNIX/Linux]]></category>
		<category><![CDATA[Workaround]]></category>

		<guid isPermaLink="false">http://www.deckerd.com/curing-symbolic-link-not-allowed-apache-20/</guid>
		<description><![CDATA[<p class="prepend-1 append-1 featuredTitle">Awhile back when trying to add a directory to Apache on my Ubuntu 6.06 LTS server, I ran into some issues. These issues, of course were the infamous 403 "Forbidden" error that your web barfs up when you try to access a server that is not publicly viewable, because of permission issues. I'm going to give you my scenario and explain how you can fix this issue, so that you don't have to go through an hour of throwing your hands up in disgust. The Scenario In our example, out DocumentRoot <a href="http://www.deckerd.com/core/curing-symbolic-link-not-allowed-apache-20/">Read More &#187;</a></p>]]></description>
		<wfw:commentRss>http://www.deckerd.com/core/curing-symbolic-link-not-allowed-apache-20/feed/</wfw:commentRss>
		<slash:comments>18</slash:comments>
		</item>
		<item>
		<title>VMWare: &#8220;Failed to create named-pipe directory&#8221; error</title>
		<link>http://www.deckerd.com/core/vmware-failed-to-create-named-pipe-directory-error/</link>
		<comments>http://www.deckerd.com/core/vmware-failed-to-create-named-pipe-directory-error/#comments</comments>
		<pubDate>Wed, 30 May 2007 08:09:31 +0000</pubDate>
		<dc:creator>Drew</dc:creator>
				<category><![CDATA[Core]]></category>
		<category><![CDATA[Applications]]></category>
		<category><![CDATA[Security]]></category>
		<category><![CDATA[Software]]></category>
		<category><![CDATA[Sys Admin]]></category>
		<category><![CDATA[The Notebook]]></category>
		<category><![CDATA[Tips]]></category>
		<category><![CDATA[UNIX/Linux]]></category>
		<category><![CDATA[Virtualization]]></category>
		<category><![CDATA[VMWare]]></category>
		<category><![CDATA[Workaround]]></category>

		<guid isPermaLink="false">http://www.deckerd.com/vmware-failed-to-create-named-pipe-directory-error/</guid>
		<description><![CDATA[<p class="prepend-1 append-1 featuredTitle">Have you ever received the Failed to create named-pipe directory error message via the vmware-mui error log files, and not able to access the VMWare Management Interface? If so, here's the fix. The error message at hand is the following: /var/log/vmware-mui/error_log ModVmdb load: Address of ModVmdb_InitCore: 0xb7c745a0 Failed to create named-pipe directory: /var/run/vmware//httpd/3854: No such file or directory VMWARE PANIC: \nNOT_IMPLEMENTED F(4023):707 Panic: Could not <a href="http://www.deckerd.com/core/vmware-failed-to-create-named-pipe-directory-error/">Read More &#187;</a></p>]]></description>
		<wfw:commentRss>http://www.deckerd.com/core/vmware-failed-to-create-named-pipe-directory-error/feed/</wfw:commentRss>
		<slash:comments>12</slash:comments>
		</item>
	</channel>
</rss>
