<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments for Geekchef.com</title>
	<atom:link href="http://geekchef.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://geekchef.com</link>
	<description></description>
	<lastBuildDate>Tue, 24 Jan 2012 02:09:36 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>Comment on Running Doom under Linux by Greg</title>
		<link>http://geekchef.com/running-doom-under-linux/comment-page-1/#comment-3094</link>
		<dc:creator>Greg</dc:creator>
		<pubDate>Tue, 24 Jan 2012 02:09:36 +0000</pubDate>
		<guid isPermaLink="false">http://geekchef.com/?p=31#comment-3094</guid>
		<description>I got the original doom to work on Arch Linux with X server 1.11.3 and the vesa driver. I don&#039;t know if this is specific to my system but the colors were displaying incorrectly. Apparently the color map wasn&#039;t taking affect because it wasn&#039;t installed. The color map can be installed immediately after creation (i_video.c:794):

XInstallColormap(X_display, X_cmap);

This seems to be a necessary step and I don&#039;t know why it wasn&#039;t done originally. Maybe it&#039;s a requirement of more recent X servers.</description>
		<content:encoded><![CDATA[<p>I got the original doom to work on Arch Linux with X server 1.11.3 and the vesa driver. I don&#8217;t know if this is specific to my system but the colors were displaying incorrectly. Apparently the color map wasn&#8217;t taking affect because it wasn&#8217;t installed. The color map can be installed immediately after creation (i_video.c:794):</p>
<p>XInstallColormap(X_display, X_cmap);</p>
<p>This seems to be a necessary step and I don&#8217;t know why it wasn&#8217;t done originally. Maybe it&#8217;s a requirement of more recent X servers.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Running Doom under Linux by Steve</title>
		<link>http://geekchef.com/running-doom-under-linux/comment-page-1/#comment-2861</link>
		<dc:creator>Steve</dc:creator>
		<pubDate>Sat, 31 Dec 2011 23:51:00 +0000</pubDate>
		<guid isPermaLink="false">http://geekchef.com/?p=31#comment-2861</guid>
		<description>Some more fixes for you:

dstrings.h lines 46 &amp; 55 require commas at the end. This stops linuxdoom crapping out at the quit message. Also, add a space at the end of the string in line 50: ...at the dos prompt! &quot; - This makes sure the whole string is displayed.
doomdef.h line 34 should be 109 and not 110. This will make demos work.

Linuxdoom compiles fine under Debian Squeeze BTW.</description>
		<content:encoded><![CDATA[<p>Some more fixes for you:</p>
<p>dstrings.h lines 46 &amp; 55 require commas at the end. This stops linuxdoom crapping out at the quit message. Also, add a space at the end of the string in line 50: &#8230;at the dos prompt! &#8221; &#8211; This makes sure the whole string is displayed.<br />
doomdef.h line 34 should be 109 and not 110. This will make demos work.</p>
<p>Linuxdoom compiles fine under Debian Squeeze BTW.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Running Doom under Linux by Steve</title>
		<link>http://geekchef.com/running-doom-under-linux/comment-page-1/#comment-2821</link>
		<dc:creator>Steve</dc:creator>
		<pubDate>Mon, 26 Dec 2011 18:40:39 +0000</pubDate>
		<guid isPermaLink="false">http://geekchef.com/?p=31#comment-2821</guid>
		<description>Thanks. That&#039;s fixed it.

I&#039;m also working on making the code 64 bit compatible. That&#039;s a lot of work, but will be worth it. It&#039;s mainly fixing the pointers for wad loading, that is, according to Fraggle.

Wish me luck!</description>
		<content:encoded><![CDATA[<p>Thanks. That&#8217;s fixed it.</p>
<p>I&#8217;m also working on making the code 64 bit compatible. That&#8217;s a lot of work, but will be worth it. It&#8217;s mainly fixing the pointers for wad loading, that is, according to Fraggle.</p>
<p>Wish me luck!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Running Doom under Linux by narc</title>
		<link>http://geekchef.com/running-doom-under-linux/comment-page-1/#comment-2669</link>
		<dc:creator>narc</dc:creator>
		<pubDate>Tue, 13 Dec 2011 01:39:58 +0000</pubDate>
		<guid isPermaLink="false">http://geekchef.com/?p=31#comment-2669</guid>
		<description>Ugh!  Nearly 1½ year later and compiling the basic code under Ubuntu 64-bits is a hassle, to which I now have no solution.  (I used a 32-bits system back then). /me thinks the gcc compiler was updated to support stronger typing: I have a bunch of illegal casting of char * to int * that probably an old, more forgetful compiler would accept.

Fortunately, I could compile the sound server.  Your problem is similar to what I read in a different forum and which I was able to reproduce (with a different signal though).  I simply forgot to indicate a change in linux.c:56, to also eliminate the extern int errno in the same fashion as above and include &lt;errno.h&gt; somewhere at the top.

Hope this works.  And if you have some additional tips about my compilation problem, feel free to contribute.</description>
		<content:encoded><![CDATA[<p>Ugh!  Nearly 1½ year later and compiling the basic code under Ubuntu 64-bits is a hassle, to which I now have no solution.  (I used a 32-bits system back then). /me thinks the gcc compiler was updated to support stronger typing: I have a bunch of illegal casting of char * to int * that probably an old, more forgetful compiler would accept.</p>
<p>Fortunately, I could compile the sound server.  Your problem is similar to what I read in a different forum and which I was able to reproduce (with a different signal though).  I simply forgot to indicate a change in linux.c:56, to also eliminate the extern int errno in the same fashion as above and include &lt;errno.h&gt; somewhere at the top.</p>
<p>Hope this works.  And if you have some additional tips about my compilation problem, feel free to contribute.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Running Doom under Linux by Steve</title>
		<link>http://geekchef.com/running-doom-under-linux/comment-page-1/#comment-2651</link>
		<dc:creator>Steve</dc:creator>
		<pubDate>Sun, 11 Dec 2011 19:37:02 +0000</pubDate>
		<guid isPermaLink="false">http://geekchef.com/?p=31#comment-2651</guid>
		<description>I cannot get the soundserver to compile. Trouble with linking. No errors or warnings, just:
collect2: ld terminated with signal 11</description>
		<content:encoded><![CDATA[<p>I cannot get the soundserver to compile. Trouble with linking. No errors or warnings, just:<br />
collect2: ld terminated with signal 11</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Arduino: a board and a philosophy by SolarBear</title>
		<link>http://geekchef.com/arduino-a-board-and-a-philosophy/comment-page-1/#comment-704</link>
		<dc:creator>SolarBear</dc:creator>
		<pubDate>Sat, 12 Mar 2011 15:37:00 +0000</pubDate>
		<guid isPermaLink="false">http://geekchef.com/?p=172#comment-704</guid>
		<description>Oh why THANK YOU VERY MUCH, SIR. Now I have to get myself a kit. It&#039;s not like these people are PASSIONATE about their stuff, right ? Really uninspiring.

*sigh* Sarcasm is SO 2010... Okay, gonna shop for one, see ya.</description>
		<content:encoded><![CDATA[<p>Oh why THANK YOU VERY MUCH, SIR. Now I have to get myself a kit. It&#8217;s not like these people are PASSIONATE about their stuff, right ? Really uninspiring.</p>
<p>*sigh* Sarcasm is SO 2010&#8230; Okay, gonna shop for one, see ya.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Souvenir from Japan by Jos</title>
		<link>http://geekchef.com/souvenir-from-japan/comment-page-1/#comment-492</link>
		<dc:creator>Jos</dc:creator>
		<pubDate>Wed, 16 Feb 2011 21:12:41 +0000</pubDate>
		<guid isPermaLink="false">http://geekchef.com/?p=99#comment-492</guid>
		<description>C un souvenir pas comme un autre. 
Il se situe mieux que tout autre dans  l&#039;espace temps.</description>
		<content:encoded><![CDATA[<p>C un souvenir pas comme un autre.<br />
Il se situe mieux que tout autre dans  l&#8217;espace temps.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on I challenge you (as well) by SolarBear</title>
		<link>http://geekchef.com/i-challenge-you-as-well/comment-page-1/#comment-443</link>
		<dc:creator>SolarBear</dc:creator>
		<pubDate>Fri, 04 Feb 2011 01:23:51 +0000</pubDate>
		<guid isPermaLink="false">http://geekchef.com/?p=158#comment-443</guid>
		<description>AWESOME. Srsly.</description>
		<content:encoded><![CDATA[<p>AWESOME. Srsly.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on I challenge you (as well) by narc</title>
		<link>http://geekchef.com/i-challenge-you-as-well/comment-page-1/#comment-441</link>
		<dc:creator>narc</dc:creator>
		<pubDate>Thu, 03 Feb 2011 23:48:59 +0000</pubDate>
		<guid isPermaLink="false">http://geekchef.com/?p=158#comment-441</guid>
		<description>Absolutely.  All other entries I saw had some relationship between picture and title, obvious or subtle.  A great challenge, mrcory.  Thanks.</description>
		<content:encoded><![CDATA[<p>Absolutely.  All other entries I saw had some relationship between picture and title, obvious or subtle.  A great challenge, mrcory.  Thanks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on I challenge you (as well) by MrCorey</title>
		<link>http://geekchef.com/i-challenge-you-as-well/comment-page-1/#comment-440</link>
		<dc:creator>MrCorey</dc:creator>
		<pubDate>Thu, 03 Feb 2011 23:43:40 +0000</pubDate>
		<guid isPermaLink="false">http://geekchef.com/?p=158#comment-440</guid>
		<description>That&#039;s awesome. Strange how fitting the quote or the name can match to a random picture.</description>
		<content:encoded><![CDATA[<p>That&#8217;s awesome. Strange how fitting the quote or the name can match to a random picture.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

