<?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: Compiling Microsoft Word 1.1a for Windows	</title>
	<atom:link href="https://virtuallyfun.com/2018/08/30/compiling-microsoft-word-1-1a-for-windows/feed/" rel="self" type="application/rss+xml" />
	<link>https://virtuallyfun.com/2018/08/30/compiling-microsoft-word-1-1a-for-windows/</link>
	<description>Fun with Virtualization</description>
	<lastBuildDate>Fri, 18 Mar 2022 03:15:27 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.0</generator>
	<item>
		<title>
		By: Anixx		</title>
		<link>https://virtuallyfun.com/2018/08/30/compiling-microsoft-word-1-1a-for-windows/comment-page-1/#comment-212763</link>

		<dc:creator><![CDATA[Anixx]]></dc:creator>
		<pubDate>Wed, 01 May 2019 16:18:04 +0000</pubDate>
		<guid isPermaLink="false">https://virtuallyfun.com/wordpress/?p=8798#comment-212763</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://virtuallyfun.com/2018/08/30/compiling-microsoft-word-1-1a-for-windows/comment-page-1/#comment-201385&quot;&gt;Roy&lt;/a&gt;.

Yes. And it has been fixed recently.]]></description>
			<content:encoded><![CDATA[<p>In reply to <a href="https://virtuallyfun.com/2018/08/30/compiling-microsoft-word-1-1a-for-windows/comment-page-1/#comment-201385">Roy</a>.</p>
<p>Yes. And it has been fixed recently.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: me		</title>
		<link>https://virtuallyfun.com/2018/08/30/compiling-microsoft-word-1-1a-for-windows/comment-page-1/#comment-210607</link>

		<dc:creator><![CDATA[me]]></dc:creator>
		<pubDate>Fri, 29 Mar 2019 14:03:04 +0000</pubDate>
		<guid isPermaLink="false">https://virtuallyfun.com/wordpress/?p=8798#comment-210607</guid>

					<description><![CDATA[Winword 1.0 works too if you prefer a Windows 2 look.
https://imgur.com/2YxDq87]]></description>
			<content:encoded><![CDATA[<p>Winword 1.0 works too if you prefer a Windows 2 look.<br />
<a href="https://imgur.com/2YxDq87" rel="nofollow ugc">https://imgur.com/2YxDq87</a></p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: neozeed		</title>
		<link>https://virtuallyfun.com/2018/08/30/compiling-microsoft-word-1-1a-for-windows/comment-page-1/#comment-201388</link>

		<dc:creator><![CDATA[neozeed]]></dc:creator>
		<pubDate>Sat, 01 Sep 2018 19:21:05 +0000</pubDate>
		<guid isPermaLink="false">https://virtuallyfun.com/wordpress/?p=8798#comment-201388</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://virtuallyfun.com/2018/08/30/compiling-microsoft-word-1-1a-for-windows/comment-page-1/#comment-201385&quot;&gt;Roy&lt;/a&gt;.

It&#039;s not rendering it exactly correct, but if you look @ the Windows 2 picture there is an icon there, and it lets you go between documents.  Word 1.1a has something very MDI like.]]></description>
			<content:encoded><![CDATA[<p>In reply to <a href="https://virtuallyfun.com/2018/08/30/compiling-microsoft-word-1-1a-for-windows/comment-page-1/#comment-201385">Roy</a>.</p>
<p>It&#8217;s not rendering it exactly correct, but if you look @ the Windows 2 picture there is an icon there, and it lets you go between documents.  Word 1.1a has something very MDI like.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Roy		</title>
		<link>https://virtuallyfun.com/2018/08/30/compiling-microsoft-word-1-1a-for-windows/comment-page-1/#comment-201385</link>

		<dc:creator><![CDATA[Roy]]></dc:creator>
		<pubDate>Sat, 01 Sep 2018 15:54:39 +0000</pubDate>
		<guid isPermaLink="false">https://virtuallyfun.com/wordpress/?p=8798#comment-201385</guid>

					<description><![CDATA[Is the gray block in the menu a bug of winevdm?]]></description>
			<content:encoded><![CDATA[<p>Is the gray block in the menu a bug of winevdm?</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: sdose		</title>
		<link>https://virtuallyfun.com/2018/08/30/compiling-microsoft-word-1-1a-for-windows/comment-page-1/#comment-201353</link>

		<dc:creator><![CDATA[sdose]]></dc:creator>
		<pubDate>Fri, 31 Aug 2018 09:16:39 +0000</pubDate>
		<guid isPermaLink="false">https://virtuallyfun.com/wordpress/?p=8798#comment-201353</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://virtuallyfun.com/2018/08/30/compiling-microsoft-word-1-1a-for-windows/comment-page-1/#comment-201348&quot;&gt;neozeed&lt;/a&gt;.

If you go for linux and almost ancient word processors, I recommend abiword.
I had it first time ~2000 on SuSE Linux and was very impressed, what I got for free, after learning/using MS-Office95 in school.

The ~2000-versions are still very small, but already powerful. They will work like a charm on a 486.]]></description>
			<content:encoded><![CDATA[<p>In reply to <a href="https://virtuallyfun.com/2018/08/30/compiling-microsoft-word-1-1a-for-windows/comment-page-1/#comment-201348">neozeed</a>.</p>
<p>If you go for linux and almost ancient word processors, I recommend abiword.<br />
I had it first time ~2000 on SuSE Linux and was very impressed, what I got for free, after learning/using MS-Office95 in school.</p>
<p>The ~2000-versions are still very small, but already powerful. They will work like a charm on a 486.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: neozeed		</title>
		<link>https://virtuallyfun.com/2018/08/30/compiling-microsoft-word-1-1a-for-windows/comment-page-1/#comment-201348</link>

		<dc:creator><![CDATA[neozeed]]></dc:creator>
		<pubDate>Fri, 31 Aug 2018 07:28:01 +0000</pubDate>
		<guid isPermaLink="false">https://virtuallyfun.com/wordpress/?p=8798#comment-201348</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://virtuallyfun.com/2018/08/30/compiling-microsoft-word-1-1a-for-windows/comment-page-1/#comment-201345&quot;&gt;Malcolm&lt;/a&gt;.

It&#039;d be like also adding in MIPS/Alpha/PowerPC/ARM support...  Or WineLib on X11 to make it a &quot;native&quot; Linux app.  But I&#039;d imagine there is so many more better options than Word 1.1a...]]></description>
			<content:encoded><![CDATA[<p>In reply to <a href="https://virtuallyfun.com/2018/08/30/compiling-microsoft-word-1-1a-for-windows/comment-page-1/#comment-201345">Malcolm</a>.</p>
<p>It&#8217;d be like also adding in MIPS/Alpha/PowerPC/ARM support&#8230;  Or WineLib on X11 to make it a &#8220;native&#8221; Linux app.  But I&#8217;d imagine there is so many more better options than Word 1.1a&#8230;</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Malcolm		</title>
		<link>https://virtuallyfun.com/2018/08/30/compiling-microsoft-word-1-1a-for-windows/comment-page-1/#comment-201345</link>

		<dc:creator><![CDATA[Malcolm]]></dc:creator>
		<pubDate>Fri, 31 Aug 2018 06:31:50 +0000</pubDate>
		<guid isPermaLink="false">https://virtuallyfun.com/wordpress/?p=8798#comment-201345</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://virtuallyfun.com/2018/08/30/compiling-microsoft-word-1-1a-for-windows/comment-page-1/#comment-201334&quot;&gt;neozeed&lt;/a&gt;.

Regarding Gorilla Word 1.1a - what I learned from winfile is that it&#039;s very hard to go anywhere without a small group of people with a clear direction in mind.  If everyone has their own direction, nothing happens.

What I&#039;d like to do to it is:
1. Continue removing Windows 2.x support;
2. Fix issues preventing it from working/working well on newer systems;
3. Move towards the more standard/later converter system (see GC1039.EXE.)  What&#039;s there now is a clear precursor but not close enough to load the Word 6/97 converters.

Beyond that though, I can&#039;t see it ever being functionally comparable to its newer peers.]]></description>
			<content:encoded><![CDATA[<p>In reply to <a href="https://virtuallyfun.com/2018/08/30/compiling-microsoft-word-1-1a-for-windows/comment-page-1/#comment-201334">neozeed</a>.</p>
<p>Regarding Gorilla Word 1.1a &#8211; what I learned from winfile is that it&#8217;s very hard to go anywhere without a small group of people with a clear direction in mind.  If everyone has their own direction, nothing happens.</p>
<p>What I&#8217;d like to do to it is:<br />
1. Continue removing Windows 2.x support;<br />
2. Fix issues preventing it from working/working well on newer systems;<br />
3. Move towards the more standard/later converter system (see GC1039.EXE.)  What&#8217;s there now is a clear precursor but not close enough to load the Word 6/97 converters.</p>
<p>Beyond that though, I can&#8217;t see it ever being functionally comparable to its newer peers.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: neozeed		</title>
		<link>https://virtuallyfun.com/2018/08/30/compiling-microsoft-word-1-1a-for-windows/comment-page-1/#comment-201344</link>

		<dc:creator><![CDATA[neozeed]]></dc:creator>
		<pubDate>Fri, 31 Aug 2018 05:37:12 +0000</pubDate>
		<guid isPermaLink="false">https://virtuallyfun.com/wordpress/?p=8798#comment-201344</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://virtuallyfun.com/2018/08/30/compiling-microsoft-word-1-1a-for-windows/comment-page-1/#comment-201339&quot;&gt;Chris M.&lt;/a&gt;.

I&#039;m going from memory but the #1 reason for the p-code thing was that it was much more smaller than using a traditional compiler.  I guess they saw the Infocom Z-Machine, and wanted more of that...  I mean it was great playing a PDP-10 game on a Commodore 64, but taking 10-15 seconds for the VM to page in/out and decompress between moves was... insanely slow.

What is kind of funny is that this compiler is *NOTHING* like their retail products.  I guess I shouldn&#039;t be too surprised.]]></description>
			<content:encoded><![CDATA[<p>In reply to <a href="https://virtuallyfun.com/2018/08/30/compiling-microsoft-word-1-1a-for-windows/comment-page-1/#comment-201339">Chris M.</a>.</p>
<p>I&#8217;m going from memory but the #1 reason for the p-code thing was that it was much more smaller than using a traditional compiler.  I guess they saw the Infocom Z-Machine, and wanted more of that&#8230;  I mean it was great playing a PDP-10 game on a Commodore 64, but taking 10-15 seconds for the VM to page in/out and decompress between moves was&#8230; insanely slow.</p>
<p>What is kind of funny is that this compiler is *NOTHING* like their retail products.  I guess I shouldn&#8217;t be too surprised.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Chris M.		</title>
		<link>https://virtuallyfun.com/2018/08/30/compiling-microsoft-word-1-1a-for-windows/comment-page-1/#comment-201339</link>

		<dc:creator><![CDATA[Chris M.]]></dc:creator>
		<pubDate>Fri, 31 Aug 2018 03:13:20 +0000</pubDate>
		<guid isPermaLink="false">https://virtuallyfun.com/wordpress/?p=8798#comment-201339</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://virtuallyfun.com/2018/08/30/compiling-microsoft-word-1-1a-for-windows/comment-page-1/#comment-201329&quot;&gt;Malcolm&lt;/a&gt;.

Microsoft had this weird obsession with p-code in the mid-80s (Multiplan was written in it) as a way to maintain portability. The downside is that it was pretty slow. It never really went away with them.... look at .NET!]]></description>
			<content:encoded><![CDATA[<p>In reply to <a href="https://virtuallyfun.com/2018/08/30/compiling-microsoft-word-1-1a-for-windows/comment-page-1/#comment-201329">Malcolm</a>.</p>
<p>Microsoft had this weird obsession with p-code in the mid-80s (Multiplan was written in it) as a way to maintain portability. The downside is that it was pretty slow. It never really went away with them&#8230;. look at .NET!</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: neozeed		</title>
		<link>https://virtuallyfun.com/2018/08/30/compiling-microsoft-word-1-1a-for-windows/comment-page-1/#comment-201334</link>

		<dc:creator><![CDATA[neozeed]]></dc:creator>
		<pubDate>Fri, 31 Aug 2018 01:30:11 +0000</pubDate>
		<guid isPermaLink="false">https://virtuallyfun.com/wordpress/?p=8798#comment-201334</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://virtuallyfun.com/2018/08/30/compiling-microsoft-word-1-1a-for-windows/comment-page-1/#comment-201325&quot;&gt;Jack&lt;/a&gt;.

In the &#039;opus\program&#039; directory of the source there should be a pre-compiled binary if I recall correctly.

I was trying to run it on PCem, on a 486SX-16 with an EGA adapter, and 8MB of RAM, and it&#039;d crash out Windows HARD.

I haven&#039;t looked at the ASM, but I think that Word does all kinds of weird things to the system state, like trying to take over for the OS itself, instead of just using the API&#039;s.  I guess all that kind of stuff could be decapitated, or made to be more like the OS/2 version, but the license doesn&#039;t really allow for online collaboration.... and I don&#039;t know about doing some kind of gorilla Word 1.1a, kind of like the &quot;OpenNT 4.5&quot; stuff.]]></description>
			<content:encoded><![CDATA[<p>In reply to <a href="https://virtuallyfun.com/2018/08/30/compiling-microsoft-word-1-1a-for-windows/comment-page-1/#comment-201325">Jack</a>.</p>
<p>In the &#8216;opus\program&#8217; directory of the source there should be a pre-compiled binary if I recall correctly.</p>
<p>I was trying to run it on PCem, on a 486SX-16 with an EGA adapter, and 8MB of RAM, and it&#8217;d crash out Windows HARD.</p>
<p>I haven&#8217;t looked at the ASM, but I think that Word does all kinds of weird things to the system state, like trying to take over for the OS itself, instead of just using the API&#8217;s.  I guess all that kind of stuff could be decapitated, or made to be more like the OS/2 version, but the license doesn&#8217;t really allow for online collaboration&#8230;. and I don&#8217;t know about doing some kind of gorilla Word 1.1a, kind of like the &#8220;OpenNT 4.5&#8221; stuff.</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
