<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title><![CDATA[esxDOS BBS — Full auto boot]]></title>
		<link>https://board.esxdos.org/viewtopic.php?id=731</link>
		<atom:link href="https://board.esxdos.org/extern.php?action=feed&amp;tid=731&amp;type=rss" rel="self" type="application/rss+xml" />
		<description><![CDATA[The most recent posts in Full auto boot.]]></description>
		<lastBuildDate>Tue, 30 Jun 2020 16:28:57 +0000</lastBuildDate>
		<generator>PunBB</generator>
		<item>
			<title><![CDATA[Re: Full auto boot]]></title>
			<link>https://board.esxdos.org/viewtopic.php?pid=1658#p1658</link>
			<description><![CDATA[<p>Distributing a Spectrum game on SD media now is like if games that shipped on floppies back in the day had shipped on large hard disks. It just doesn&#039;t make any sense. The internet is ubiquitous and no-one has any problem copying media to their SD card. The problem of not having a convenient way of running the apps (because they all use different methods) has already been solved by the application package format I came up with. It&#039;s not tied to a specific esxDOS version. It makes it easy to see what apps you have installed (<span style="color: blue">.ls /programs</span>). All you have to do is install the <span style="color: blue">.run</span> command in the <span style="color: blue">bin</span> folder and then install the apps in the <span style="color: blue">programs</span> folder. And application names can be any length (truncated to 11 characters). To open an app you type <span style="color: blue">.run <em>&lt;appname&gt;</em></span>. If you wanted to go the extra mile you could create an installer as a <span style="color: blue">.tap</span> file that would write all the app files to the correct folders and then delete itself.</p><p>There is no license as such. esxDOS is copyright Papya Design. The only reference to the permitted use of the copyright is &quot;All rights perversed&quot;, which is typically included in permissive licenses. Typically it means the software is not public domain, but you can use it however you see fit so long as you don&#039;t blame the author.</p>]]></description>
			<author><![CDATA[null@example.com (aowen)]]></author>
			<pubDate>Tue, 30 Jun 2020 16:28:57 +0000</pubDate>
			<guid>https://board.esxdos.org/viewtopic.php?pid=1658#p1658</guid>
		</item>
		<item>
			<title><![CDATA[Full auto boot]]></title>
			<link>https://board.esxdos.org/viewtopic.php?pid=1657#p1657</link>
			<description><![CDATA[<p>Hi All,</p><p>I&#039;ve been wondering what would be needed to be able to distribute physical copies of homebrew games made for ESXDOS, and I found there are two main problems:</p><p>1) ESXDOS version segmentation. <br />2) License</p><p>First problem makes people unable to create a bootable SD card, that you can just insert in your DivMMc and get it working out of the box, as you don&#039;t know which version of the files at SYS and BIN folders to add. I honestly don&#039;t know the reason behind that, but I wonder if there may be a set of SYS files that can be &quot;wildcard sys files&quot;, so ESXDOS accepts them as valid, always. Otherwise, there may be an option to have some AUTOEXEC.BIN file in SYS folder, that if present, is loaded as ESXDOS.BIN temporarily (not flashed), in which case authors will just to make sure the usual ESXDOS.BIN file is bundle with the SYS and BIN foldes in the SD card, and just rename it AUTOEXEC.BIN</p><p>Second problem is that as far as I have found, it&#039;s unclear if ESXDOS can be bundled with a game.</p><p>Of course I understand first problem will persist even if a new version supporting some of the features I suggested is created, casue that would not change the current segmentation, but in the long term it may be a solution.</p>]]></description>
			<author><![CDATA[null@example.com (Uto)]]></author>
			<pubDate>Mon, 29 Jun 2020 16:26:09 +0000</pubDate>
			<guid>https://board.esxdos.org/viewtopic.php?pid=1657#p1657</guid>
		</item>
	</channel>
</rss>
