<?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 on: DOS-Minix 2.04	</title>
	<atom:link href="https://virtuallyfun.com/2009/10/09/dos-minix-2-04/feed/" rel="self" type="application/rss+xml" />
	<link>https://virtuallyfun.com/2009/10/09/dos-minix-2-04/</link>
	<description>Fun with Virtualization</description>
	<lastBuildDate>Fri, 12 Jul 2024 12:34:52 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.0.1</generator>
	<item>
		<title>
		By: Neozeed		</title>
		<link>https://virtuallyfun.com/2009/10/09/dos-minix-2-04/comment-page-1/#comment-77</link>

		<dc:creator><![CDATA[Neozeed]]></dc:creator>
		<pubDate>Sat, 10 Oct 2009 00:17:01 +0000</pubDate>
		<guid isPermaLink="false">https://virtuallyfun.com/?p=168#comment-77</guid>

					<description><![CDATA[I should leave 2 notes here..&lt;br /&gt;&lt;br /&gt;First is that the &#039;easy&#039; way I&#039;ve found to move data in &#038; out of dosminix is to &#034;mount&#034; a tar file.  At the boot loader, you can specify&lt;br /&gt;&lt;br /&gt;dosfile-d1=x.tar&lt;br /&gt;&lt;br /&gt;This will &#039;mount&#039; x.tar onto disk #1.  Go ahead and &#039;boot&#039; minix, and then you can extract the x.tar file simply by running tar xf /dev/c0d1&lt;br /&gt;&lt;br /&gt;Likewise, you can tar cf /dev/c0d1 then extract x.tar from MS-DOS (NT whatever) to get data out of the minix setup.&lt;br /&gt;&lt;br /&gt;When compiling large c files, you&#039;ll find that the C compiler will freak because it&#039;s out of memory...&lt;br /&gt;&lt;br /&gt;The command:&lt;br /&gt;chmem +# /usr/lib/em_cemcom.ansi&lt;br /&gt;&lt;br /&gt;will show the maximum memory amount the C compiler can use.  You can give it an additional megabyte with:&lt;br /&gt;&lt;br /&gt;chmem +102400 /usr/lib/em_cemcom.ansi&lt;br /&gt;&lt;br /&gt;When building f2c and dungeon I had to do this a few times..&lt;br /&gt;&lt;br /&gt;For those less adventurous I&#039;ve built f2c, it&#039;s library &#038; adventure right here:&lt;br /&gt;&lt;br /&gt;http://vpsland.superglobalmegacorp.com/install/f2c/dungeon-2.5.6-i386-minix.zip]]></description>
			<content:encoded><![CDATA[<p>I should leave 2 notes here..</p>
<p>First is that the &#39;easy&#39; way I&#39;ve found to move data in &amp; out of dosminix is to &quot;mount&quot; a tar file.  At the boot loader, you can specify</p>
<p>dosfile-d1=x.tar</p>
<p>This will &#39;mount&#39; x.tar onto disk #1.  Go ahead and &#39;boot&#39; minix, and then you can extract the x.tar file simply by running tar xf /dev/c0d1</p>
<p>Likewise, you can tar cf /dev/c0d1 then extract x.tar from MS-DOS (NT whatever) to get data out of the minix setup.</p>
<p>When compiling large c files, you&#39;ll find that the C compiler will freak because it&#39;s out of memory&#8230;</p>
<p>The command:<br />chmem +# /usr/lib/em_cemcom.ansi</p>
<p>will show the maximum memory amount the C compiler can use.  You can give it an additional megabyte with:</p>
<p>chmem +102400 /usr/lib/em_cemcom.ansi</p>
<p>When building f2c and dungeon I had to do this a few times..</p>
<p>For those less adventurous I&#39;ve built f2c, it&#39;s library &amp; adventure right here:</p>
<p><a href="http://vpsland.superglobalmegacorp.com/install/f2c/dungeon-2.5.6-i386-minix.zip" rel="nofollow ugc">http://vpsland.superglobalmegacorp.com/install/f2c/dungeon-2.5.6-i386-minix.zip</a></p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
