<?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 for DevBlog</title>
	<atom:link href="http://simonowen.com/blog/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://simonowen.com/blog</link>
	<description>Stuff and nonsense</description>
	<pubDate>Sat, 22 Nov 2008 08:10:56 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
		<item>
		<title>Comment on fdrawcmd.sys license update by Peace</title>
		<link>http://simonowen.com/blog/2007/02/11/fdrawcmdsys-license-update/#comment-276</link>
		<dc:creator>Peace</dc:creator>
		<pubDate>Mon, 04 Aug 2008 18:30:20 +0000</pubDate>
		<guid isPermaLink="false">http://blog.simonowen.com/2007/02/11/fdrawcmdsys-license-update/#comment-276</guid>
		<description>I only want to say thanks for your very well driver!!!

Regards, Peace</description>
		<content:encoded><![CDATA[<p>I only want to say thanks for your very well driver!!!</p>
<p>Regards, Peace</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on SAM/IP by Simon</title>
		<link>http://simonowen.com/blog/2007/12/11/samip/#comment-222</link>
		<dc:creator>Simon</dc:creator>
		<pubDate>Tue, 15 Jan 2008 19:49:06 +0000</pubDate>
		<guid isPermaLink="false">http://simonowen.com/blog/2007/12/11/samip/#comment-222</guid>
		<description>Excellent! Please let me know when you do...</description>
		<content:encoded><![CDATA[<p>Excellent! Please let me know when you do&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on SAM/IP by Adrian Brown</title>
		<link>http://simonowen.com/blog/2007/12/11/samip/#comment-221</link>
		<dc:creator>Adrian Brown</dc:creator>
		<pubDate>Tue, 15 Jan 2008 18:58:30 +0000</pubDate>
		<guid isPermaLink="false">http://simonowen.com/blog/2007/12/11/samip/#comment-221</guid>
		<description>Well, ive just finished a major deadline so im just typing up my z80 article then ill start on uip again :)</description>
		<content:encoded><![CDATA[<p>Well, ive just finished a major deadline so im just typing up my z80 article then ill start on uip again <img src='http://simonowen.com/blog/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on SAM/IP by Simon</title>
		<link>http://simonowen.com/blog/2007/12/11/samip/#comment-196</link>
		<dc:creator>Simon</dc:creator>
		<pubDate>Tue, 11 Dec 2007 23:54:37 +0000</pubDate>
		<guid isPermaLink="false">http://simonowen.com/blog/2007/12/11/samip/#comment-196</guid>
		<description>I've finished converting all I need for cpc/ip, and it didn't take more than about an hour.

It's just a minor limitation of the original Comet syntax, and not a problem that pyz80 is faithful to it!

That said, if I run into anything similar I'll be sure to check with you first next time - thanks!</description>
		<content:encoded><![CDATA[<p>I&#8217;ve finished converting all I need for cpc/ip, and it didn&#8217;t take more than about an hour.</p>
<p>It&#8217;s just a minor limitation of the original Comet syntax, and not a problem that pyz80 is faithful to it!</p>
<p>That said, if I run into anything similar I&#8217;ll be sure to check with you first next time - thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on SAM/IP by Andrew Collier</title>
		<link>http://simonowen.com/blog/2007/12/11/samip/#comment-194</link>
		<dc:creator>Andrew Collier</dc:creator>
		<pubDate>Tue, 11 Dec 2007 23:43:43 +0000</pubDate>
		<guid isPermaLink="false">http://simonowen.com/blog/2007/12/11/samip/#comment-194</guid>
		<description>You should have said! I doubt it would be too much work to extend pyz80 to accept strings inside DEFB. If you're porting a lot of this source it may be worthwhile for me to extend the source parsing to accept unmodified files in this other format. Would that be useful, or have you passed that point by now?</description>
		<content:encoded><![CDATA[<p>You should have said! I doubt it would be too much work to extend pyz80 to accept strings inside DEFB. If you&#8217;re porting a lot of this source it may be worthwhile for me to extend the source parsing to accept unmodified files in this other format. Would that be useful, or have you passed that point by now?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on fdrawcmd.sys license update by Simon</title>
		<link>http://simonowen.com/blog/2007/02/11/fdrawcmdsys-license-update/#comment-57</link>
		<dc:creator>Simon</dc:creator>
		<pubDate>Thu, 06 Sep 2007 14:02:01 +0000</pubDate>
		<guid isPermaLink="false">http://blog.simonowen.com/2007/02/11/fdrawcmdsys-license-update/#comment-57</guid>
		<description>GNU GPL seems like a better option for allowing 3rd party changes to be fed back into the main project.  If I'm going to open it up, I'd prefer it to stay open for everyone - and BSD doesn't /require/ that.

What makes you think BSD would be a better option?</description>
		<content:encoded><![CDATA[<p>GNU GPL seems like a better option for allowing 3rd party changes to be fed back into the main project.  If I&#8217;m going to open it up, I&#8217;d prefer it to stay open for everyone - and BSD doesn&#8217;t /require/ that.</p>
<p>What makes you think BSD would be a better option?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on fdrawcmd.sys license update by Luchezar Georgiev</title>
		<link>http://simonowen.com/blog/2007/02/11/fdrawcmdsys-license-update/#comment-17</link>
		<dc:creator>Luchezar Georgiev</dc:creator>
		<pubDate>Sat, 25 Aug 2007 08:13:54 +0000</pubDate>
		<guid isPermaLink="false">http://blog.simonowen.com/2007/02/11/fdrawcmdsys-license-update/#comment-17</guid>
		<description>Why exactly the GNU GPL? The "modified" BSD licence is much less restrictive and still GPL-compatible.</description>
		<content:encoded><![CDATA[<p>Why exactly the GNU GPL? The &#8220;modified&#8221; BSD licence is much less restrictive and still GPL-compatible.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Atom Lite CF support by Simon</title>
		<link>http://simonowen.com/blog/2007/06/25/atom-lite-cf-support/#comment-15</link>
		<dc:creator>Simon</dc:creator>
		<pubDate>Mon, 13 Aug 2007 14:25:51 +0000</pubDate>
		<guid isPermaLink="false">http://simonowen.com/blog/2007/06/25/atom-lite-cf-support/#comment-15</guid>
		<description>It wouldn't be much work to do it, though it'll never be as fully functional as the Windows version.  The FDRAWCMD interface support in the Linux kernel lacks the flexibility to terminate write commands early, since it's not something people would normally need to do.  That prevents writing CRC errors, short sectors, mixed density tracks, and a few other quirks required by copy protected disks.

That said, if you only want to read/write regular SAM and CP/M formats then you'll be fine with the standard support:

To read from SAM disk to raw image:
dd if=/dev/fd0u800 of=image.mgt

To write the image back to a formatted disk:
dd if=image.mgt of=/dev/fd0u800

To format a new SAM disk:
fdformat /dev/fd0u800

If the /dev/fd0u800 device doesn't exist, try /dev/.static/dev/fd0u800 instead.  Or for CP/M disks change the last part of the name to fd0u720.

You'll only be able to use .mgt (old-style 819200 byte .dsk images) with that method, but it might be better than nothing for now!</description>
		<content:encoded><![CDATA[<p>It wouldn&#8217;t be much work to do it, though it&#8217;ll never be as fully functional as the Windows version.  The FDRAWCMD interface support in the Linux kernel lacks the flexibility to terminate write commands early, since it&#8217;s not something people would normally need to do.  That prevents writing CRC errors, short sectors, mixed density tracks, and a few other quirks required by copy protected disks.</p>
<p>That said, if you only want to read/write regular SAM and CP/M formats then you&#8217;ll be fine with the standard support:</p>
<p>To read from SAM disk to raw image:<br />
dd if=/dev/fd0u800 of=image.mgt</p>
<p>To write the image back to a formatted disk:<br />
dd if=image.mgt of=/dev/fd0u800</p>
<p>To format a new SAM disk:<br />
fdformat /dev/fd0u800</p>
<p>If the /dev/fd0u800 device doesn&#8217;t exist, try /dev/.static/dev/fd0u800 instead.  Or for CP/M disks change the last part of the name to fd0u720.</p>
<p>You&#8217;ll only be able to use .mgt (old-style 819200 byte .dsk images) with that method, but it might be better than nothing for now!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Atom Lite CF support by Steve(spt)</title>
		<link>http://simonowen.com/blog/2007/06/25/atom-lite-cf-support/#comment-14</link>
		<dc:creator>Steve(spt)</dc:creator>
		<pubDate>Mon, 13 Aug 2007 11:30:29 +0000</pubDate>
		<guid isPermaLink="false">http://simonowen.com/blog/2007/06/25/atom-lite-cf-support/#comment-14</guid>
		<description>Is there any chance of a version of 
Samdisk for Linux?</description>
		<content:encoded><![CDATA[<p>Is there any chance of a version of<br />
Samdisk for Linux?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Atom Lite CF support by Simon</title>
		<link>http://simonowen.com/blog/2007/06/25/atom-lite-cf-support/#comment-11</link>
		<dc:creator>Simon</dc:creator>
		<pubDate>Mon, 16 Jul 2007 13:42:30 +0000</pubDate>
		<guid isPermaLink="false">http://simonowen.com/blog/2007/06/25/atom-lite-cf-support/#comment-11</guid>
		<description>Yes - AL+ DALLAS clock support was added last week, and confirmed over the weekend with Edwin's updated BDOS.

I implemented DALLAS RAM saving to the .cfg file for the normal clock, but that wasn't very convenient to view/edit.  I'll move that to an external file instead, with the AL clock saved to a different file.

SimCoupe currently emulates the DS1687, which has only 256 bytes of RAM.  Once I get my AL+ I'll implement the DS17887, which has a spacious 8K of RAM.  That should give much more room to play with for state saving!</description>
		<content:encoded><![CDATA[<p>Yes - AL+ DALLAS clock support was added last week, and confirmed over the weekend with Edwin&#8217;s updated BDOS.</p>
<p>I implemented DALLAS RAM saving to the .cfg file for the normal clock, but that wasn&#8217;t very convenient to view/edit.  I&#8217;ll move that to an external file instead, with the AL clock saved to a different file.</p>
<p>SimCoupe currently emulates the DS1687, which has only 256 bytes of RAM.  Once I get my AL+ I&#8217;ll implement the DS17887, which has a spacious 8K of RAM.  That should give much more room to play with for state saving!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
