<?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"
	>
<channel>
	<title>Comments on: DOSBox, part II: standalone DOS apps on desktop</title>
	<atom:link href="http://polishlinux.org/apps/dosbox-part-ii-autonomous-dos-programs-for-windows-or-mac/feed/" rel="self" type="application/rss+xml" />
	<link>http://polishlinux.org/apps/dosbox-part-ii-autonomous-dos-programs-for-windows-or-mac/</link>
	<description>All About GNU/Linux and BSD - reviews, comparisons, articles</description>
	<pubDate>Thu, 18 Mar 2010 02:31:23 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: Peter</title>
		<link>http://polishlinux.org/apps/dosbox-part-ii-autonomous-dos-programs-for-windows-or-mac/#comment-128530</link>
		<dc:creator>Peter</dc:creator>
		<pubDate>Sat, 20 Jun 2009 06:14:24 +0000</pubDate>
		<guid isPermaLink="false">http://polishlinux.org/apps/dosbox-part-ii-autonomous-dos-programs-for-windows-or-mac/#comment-128530</guid>
		<description>YEAH UM WHY THE.. DIDN'T THEY USE P330 IN THE *.CONF FILE IT IS USED FOR CORRECT 16 BIT SOUND EMULATION WHY DIDN'T THE DOSBOX TEAM KNOW THIS

\\*.TO.ERT.*\\ UM.. ERT DO YOU HAVE THE TALK VERSIONS OF THIS GAME GET THE SCUMMVM EMULATOR AND DOWNLOAD THE LARGER GAMEFILE PACK OF THE GAME YOU'VE GOT THAT HAS THE SPEECH FILES IN IT IT WILL BE ABOUT 200 to 600 MEGS LARGER BECAUSE OF THE SPEECH FILES INCLUDED!!</description>
		<content:encoded><![CDATA[<p>YEAH UM WHY THE.. DIDN&#8217;T THEY USE P330 IN THE *.CONF FILE IT IS USED FOR CORRECT 16 BIT SOUND EMULATION WHY DIDN&#8217;T THE DOSBOX TEAM KNOW THIS</p>
<p>\\*.TO.ERT.*\\ UM.. ERT DO YOU HAVE THE TALK VERSIONS OF THIS GAME GET THE SCUMMVM EMULATOR AND DOWNLOAD THE LARGER GAMEFILE PACK OF THE GAME YOU&#8217;VE GOT THAT HAS THE SPEECH FILES IN IT IT WILL BE ABOUT 200 to 600 MEGS LARGER BECAUSE OF THE SPEECH FILES INCLUDED!!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ERT</title>
		<link>http://polishlinux.org/apps/dosbox-part-ii-autonomous-dos-programs-for-windows-or-mac/#comment-128435</link>
		<dc:creator>ERT</dc:creator>
		<pubDate>Thu, 28 May 2009 10:22:27 +0000</pubDate>
		<guid isPermaLink="false">http://polishlinux.org/apps/dosbox-part-ii-autonomous-dos-programs-for-windows-or-mac/#comment-128435</guid>
		<description>its possible to do this with ScummVM adventures?

DOSbox version of this cant open speech files</description>
		<content:encoded><![CDATA[<p>its possible to do this with ScummVM adventures?</p>
<p>DOSbox version of this cant open speech files</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Hugo Marien</title>
		<link>http://polishlinux.org/apps/dosbox-part-ii-autonomous-dos-programs-for-windows-or-mac/#comment-121947</link>
		<dc:creator>Hugo Marien</dc:creator>
		<pubDate>Wed, 02 Jul 2008 05:46:27 +0000</pubDate>
		<guid isPermaLink="false">http://polishlinux.org/apps/dosbox-part-ii-autonomous-dos-programs-for-windows-or-mac/#comment-121947</guid>
		<description>Some correction of typo's:

The supported grphics mode of one of the special versions is 1280*1024 and it is of course 3D acceleration.</description>
		<content:encoded><![CDATA[<p>Some correction of typo&#8217;s:</p>
<p>The supported grphics mode of one of the special versions is 1280*1024 and it is of course 3D acceleration.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Hugo Marien</title>
		<link>http://polishlinux.org/apps/dosbox-part-ii-autonomous-dos-programs-for-windows-or-mac/#comment-121946</link>
		<dc:creator>Hugo Marien</dc:creator>
		<pubDate>Wed, 02 Jul 2008 05:41:37 +0000</pubDate>
		<guid isPermaLink="false">http://polishlinux.org/apps/dosbox-part-ii-autonomous-dos-programs-for-windows-or-mac/#comment-121946</guid>
		<description>Hi,

Not only "old" games can run in DOSBox but also CAD-systems. I was (am) the developer of a powerful 2D CAD system programmed for DOS and VESA graphics cards, DOS is mostly forgotten and most modern Video cards doesn't support the whole VESA standard anymore. Oddly enough however, they respond on the VESA standard identification call "affirmative". I didn't find any time (or was it courage?) to port the system to Windows (mostly because the support of a mouse is limited in Windows) but in DOSBox the system runs very well on Windows XP and VISTA and I suppose it will also in Linux and all supported OS's.

There are compiled versions of DOSBox available that support graphics 1280*1240 (Hal9000) and even 3D acellaration.</description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>Not only &#8220;old&#8221; games can run in DOSBox but also CAD-systems. I was (am) the developer of a powerful 2D CAD system programmed for DOS and VESA graphics cards, DOS is mostly forgotten and most modern Video cards doesn&#8217;t support the whole VESA standard anymore. Oddly enough however, they respond on the VESA standard identification call &#8220;affirmative&#8221;. I didn&#8217;t find any time (or was it courage?) to port the system to Windows (mostly because the support of a mouse is limited in Windows) but in DOSBox the system runs very well on Windows XP and VISTA and I suppose it will also in Linux and all supported OS&#8217;s.</p>
<p>There are compiled versions of DOSBox available that support graphics 1280*1240 (Hal9000) and even 3D acellaration.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Raptou</title>
		<link>http://polishlinux.org/apps/dosbox-part-ii-autonomous-dos-programs-for-windows-or-mac/#comment-121822</link>
		<dc:creator>Raptou</dc:creator>
		<pubDate>Sat, 21 Jun 2008 23:29:18 +0000</pubDate>
		<guid isPermaLink="false">http://polishlinux.org/apps/dosbox-part-ii-autonomous-dos-programs-for-windows-or-mac/#comment-121822</guid>
		<description>@TD-Linux: In most of your comments you are probably correct as far as your machine is concerned. However, notice that in my examples I presented the way to produce universal packages. Thus, some restrictions had to be made.

Answering your questions:

1) Unfortuntaley they have to be reverse in DOS/Windows and other systems. In DOS "/" is for additional optionsand "\" for directories. The rest of the symbols are identical (" * "," . "," ? "). In dosbox.conf just like in MS DOS 5 you cannot use "\" to access paths in Linux/Mac OS and vice versa. And this is autoexec.bat that is being emulated in [autoexec] section.

2) Unfortunately in Windows "output=opengl" often doesn't work properly. This is not always true but it happens often enough to not use it in universal packages.

If you want to prepare special packages for different computers, here are some hints:

- For very old video cards "2D", with no 3d accelerator - use  output=surface. This is the slowest mode but works on ancient software
- Old video cards but of more recent generation (likek np. Ati Rage) - output=overlay
- 3D stare video cards that understand DirectDraw, Windows - output=ddraw 
- 3D stare video cards, other operating systems - output=opengl 

3) Frameskip.

Skipping frames in Dosbox is directly associated with CYCLE parameter. It serves the idea of "connecting" the speed of video graphics displayed in thevirtual Dosbox computerwith its emulated processor. Some very old games use real tacting and their speed depends on the processor clock. For these games the emulated PC processor needs to be drastically slowed down. This is why the manual regulation of those parameters was introduced. In order to adjust the params to some game we need to read the data displayed in the title windows of the game and then write them down in the config script.

4) You are correct here, this value can be the same in both configurations. For most applications even 4MB would be more than enough. The value 64MB for Mac is the remains of my trying to run GEOS Ensemble under Dosbox (it was hard, but I succeeded, the article about it will appear on PolishLinux.org soon, so stay tuned).</description>
		<content:encoded><![CDATA[<p>@TD-Linux: In most of your comments you are probably correct as far as your machine is concerned. However, notice that in my examples I presented the way to produce universal packages. Thus, some restrictions had to be made.</p>
<p>Answering your questions:</p>
<p>1) Unfortuntaley they have to be reverse in DOS/Windows and other systems. In DOS &#8220;/&#8221; is for additional optionsand &#8220;\&#8221; for directories. The rest of the symbols are identical (&#8221; * &#8220;,&#8221; . &#8220;,&#8221; ? &#8220;). In dosbox.conf just like in MS DOS 5 you cannot use &#8220;\&#8221; to access paths in Linux/Mac OS and vice versa. And this is autoexec.bat that is being emulated in [autoexec] section.</p>
<p>2) Unfortunately in Windows &#8220;output=opengl&#8221; often doesn&#8217;t work properly. This is not always true but it happens often enough to not use it in universal packages.</p>
<p>If you want to prepare special packages for different computers, here are some hints:</p>
<p>- For very old video cards &#8220;2D&#8221;, with no 3d accelerator - use  output=surface. This is the slowest mode but works on ancient software<br />
- Old video cards but of more recent generation (likek np. Ati Rage) - output=overlay<br />
- 3D stare video cards that understand DirectDraw, Windows - output=ddraw<br />
- 3D stare video cards, other operating systems - output=opengl </p>
<p>3) Frameskip.</p>
<p>Skipping frames in Dosbox is directly associated with CYCLE parameter. It serves the idea of &#8220;connecting&#8221; the speed of video graphics displayed in thevirtual Dosbox computerwith its emulated processor. Some very old games use real tacting and their speed depends on the processor clock. For these games the emulated PC processor needs to be drastically slowed down. This is why the manual regulation of those parameters was introduced. In order to adjust the params to some game we need to read the data displayed in the title windows of the game and then write them down in the config script.</p>
<p>4) You are correct here, this value can be the same in both configurations. For most applications even 4MB would be more than enough. The value 64MB for Mac is the remains of my trying to run GEOS Ensemble under Dosbox (it was hard, but I succeeded, the article about it will appear on PolishLinux.org soon, so stay tuned).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: TD-Linux</title>
		<link>http://polishlinux.org/apps/dosbox-part-ii-autonomous-dos-programs-for-windows-or-mac/#comment-121819</link>
		<dc:creator>TD-Linux</dc:creator>
		<pubDate>Sat, 21 Jun 2008 17:42:42 +0000</pubDate>
		<guid isPermaLink="false">http://polishlinux.org/apps/dosbox-part-ii-autonomous-dos-programs-for-windows-or-mac/#comment-121819</guid>
		<description>Several things in the first part (dosbox.conf) of this post worry me, though the packaging looks fairly sound.

Here are my concerns:

1) In Windows, you can use either forward or back slashes for directories, while still using forward slashes in arguments, in much the same way you can use forward slashes in arguments for programs in Linux. So, this argument is void - use forward slashes everywhere.

2) You say that OpenGL will hide some parts on Windows... not true, at least from my experience. All it is doing is drawing a framebuffer on a quad, why would some parts of your DOS program not work correctly?

3) Frameskip=1? I suppose, most dos games didn't get that many frames per second anyway, but some explanation would have been nice...

4) Why is the emulated memory twice as large for Mac? It has nothing to do with the OS... I'll call it a typo.

P.S. I spot another typo - there are 3 rogue lines in the top of the [render] section for Quake.

I did like the packaging section, however :)</description>
		<content:encoded><![CDATA[<p>Several things in the first part (dosbox.conf) of this post worry me, though the packaging looks fairly sound.</p>
<p>Here are my concerns:</p>
<p>1) In Windows, you can use either forward or back slashes for directories, while still using forward slashes in arguments, in much the same way you can use forward slashes in arguments for programs in Linux. So, this argument is void - use forward slashes everywhere.</p>
<p>2) You say that OpenGL will hide some parts on Windows&#8230; not true, at least from my experience. All it is doing is drawing a framebuffer on a quad, why would some parts of your DOS program not work correctly?</p>
<p>3) Frameskip=1? I suppose, most dos games didn&#8217;t get that many frames per second anyway, but some explanation would have been nice&#8230;</p>
<p>4) Why is the emulated memory twice as large for Mac? It has nothing to do with the OS&#8230; I&#8217;ll call it a typo.</p>
<p>P.S. I spot another typo - there are 3 rogue lines in the top of the [render] section for Quake.</p>
<p>I did like the packaging section, however <img src='http://polishlinux.org/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: JotaEle</title>
		<link>http://polishlinux.org/apps/dosbox-part-ii-autonomous-dos-programs-for-windows-or-mac/#comment-121807</link>
		<dc:creator>JotaEle</dc:creator>
		<pubDate>Fri, 20 Jun 2008 13:08:45 +0000</pubDate>
		<guid isPermaLink="false">http://polishlinux.org/apps/dosbox-part-ii-autonomous-dos-programs-for-windows-or-mac/#comment-121807</guid>
		<description>Why don't you build a static dosbox binary for Linux?
Thus you can reduce the dependencies problem when you install a program in different distros.</description>
		<content:encoded><![CDATA[<p>Why don&#8217;t you build a static dosbox binary for Linux?<br />
Thus you can reduce the dependencies problem when you install a program in different distros.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
