<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title><![CDATA[esxDOS BBS — DivMMC Future Flash Fail]]></title>
		<link>https://board.esxdos.org/viewtopic.php?id=268</link>
		<atom:link href="https://board.esxdos.org/extern.php?action=feed&amp;tid=268&amp;type=rss" rel="self" type="application/rss+xml" />
		<description><![CDATA[The most recent posts in DivMMC Future Flash Fail.]]></description>
		<lastBuildDate>Thu, 30 Aug 2018 13:59:56 +0000</lastBuildDate>
		<generator>PunBB</generator>
		<item>
			<title><![CDATA[Re: DivMMC Future Flash Fail]]></title>
			<link>https://board.esxdos.org/viewtopic.php?pid=1008#p1008</link>
			<description><![CDATA[<p>Ok, I would like to withdraw my &quot;bug report&quot;! ;-) In the meantime I were able to flash my DivMMC Furture with the new esxDOS version 0.8.6.</p><p>The problem was that I obeyed to the three steps from the official &quot;Readme.txt&quot; from esxDOS and did not realize that flashing a DivMMC Future has an extra step. This has to be done before hitting &quot;Enter&quot; after loading the &quot;esxmmc.tap&quot;: EJECT the SD card! ;-)</p><p>As this is mentioned in the DivMMC Future guide ... it was of course my fault!</p>]]></description>
			<author><![CDATA[null@example.com (cha05e90)]]></author>
			<pubDate>Thu, 30 Aug 2018 13:59:56 +0000</pubDate>
			<guid>https://board.esxdos.org/viewtopic.php?pid=1008#p1008</guid>
		</item>
		<item>
			<title><![CDATA[Re: DivMMC Future Flash Fail]]></title>
			<link>https://board.esxdos.org/viewtopic.php?pid=881#p881</link>
			<description><![CDATA[<p>Ok, thanks for the info.</p>]]></description>
			<author><![CDATA[null@example.com (cha05e90)]]></author>
			<pubDate>Tue, 05 Jun 2018 11:25:25 +0000</pubDate>
			<guid>https://board.esxdos.org/viewtopic.php?pid=881#p881</guid>
		</item>
		<item>
			<title><![CDATA[Re: DivMMC Future Flash Fail]]></title>
			<link>https://board.esxdos.org/viewtopic.php?pid=879#p879</link>
			<description><![CDATA[<p>Hi,</p><p>There should be no difference between RC2 and final in that regard. Sadly I do not have a DivMMC Future to test this.</p>]]></description>
			<author><![CDATA[null@example.com (lordcoxis)]]></author>
			<pubDate>Tue, 05 Jun 2018 09:04:23 +0000</pubDate>
			<guid>https://board.esxdos.org/viewtopic.php?pid=879#p879</guid>
		</item>
		<item>
			<title><![CDATA[DivMMC Future Flash Fail]]></title>
			<link>https://board.esxdos.org/viewtopic.php?pid=878#p878</link>
			<description><![CDATA[<p>Hello!</p><p>I own a DivMMC Future, which has been flashed with the Release Candidate 2 of esxDOS 0.8.6. So far this setup worked just fine. The flashing itself were done some weeks ago and went flawless by doing all the steps described in the Readme file (except the &quot;Jumper&quot; part of course!). </p><p>After the release of the final version I tried to update this by the same procedure - but this time it fails with a rather generic error &quot;CANNOT FLASH&quot; after pressing &quot;Any key&quot;. Afterwards the RC2 is still in charge (and works just like before), so the flashing really did not happen.</p><p>Did someone else a successful update of his DivMMC Future?<br />And what might cause the difference in behavior of RC2 and Final?</p><p>Any hints and help would be appreciated!</p><p>Thanks,<br />Frank</p>]]></description>
			<author><![CDATA[null@example.com (cha05e90)]]></author>
			<pubDate>Mon, 04 Jun 2018 15:20:40 +0000</pubDate>
			<guid>https://board.esxdos.org/viewtopic.php?pid=878#p878</guid>
		</item>
	</channel>
</rss>
