<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Lallafa's Blog &#187; Commodore 64</title>
	<atom:link href="http://lallafa.de/blog/category/commodore-64/feed/" rel="self" type="application/rss+xml" />
	<link>http://lallafa.de/blog</link>
	<description>Personal Musings about the Commodore64, Macs and my other Hobby Projects</description>
	<lastBuildDate>Fri, 06 Apr 2012 12:50:59 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.3</generator>
		<item>
		<title>Updated OpenCBM and Nibtools Portfiles</title>
		<link>http://lallafa.de/blog/2011/07/updated-opencbm-and-nibtools-portfiles/</link>
		<comments>http://lallafa.de/blog/2011/07/updated-opencbm-and-nibtools-portfiles/#comments</comments>
		<pubDate>Fri, 01 Jul 2011 18:10:36 +0000</pubDate>
		<dc:creator>lallafa</dc:creator>
				<category><![CDATA[Commodore 64]]></category>
		<category><![CDATA[Mac Stuff]]></category>
		<category><![CDATA[Software]]></category>

		<guid isPermaLink="false">http://lallafa.de/blog/?p=299</guid>
		<description><![CDATA[<p>If you are using OpenCBM or Nibtools with the MacPort Portfiles I offer here on my site then you can now find an update of both Portfiles on the following pages:</p> OpenCBM on Mac Nibtools on Mac <p>What has changed? Until now I had Portfiles that pick the source from a Snapshot tarball I have <span style="color:#777"> . . . &#8594; Read More: <a href="http://lallafa.de/blog/2011/07/updated-opencbm-and-nibtools-portfiles/">Updated OpenCBM and Nibtools Portfiles</a></span>]]></description>
			<content:encoded><![CDATA[<p>If you are using OpenCBM or Nibtools with the MacPort Portfiles I  offer here on my site then you can now find an update of both Portfiles  on the following pages:</p>
<ul>
<li><a title="OpenCBM on Mac" href="http://lallafa.de/blog/opencbm-on-mac/">OpenCBM on Mac</a></li>
<li><a title="Nibtools on Mac" href="http://lallafa.de/blog/opencbm-on-mac/nibtools-on-mac/">Nibtools on Mac</a></li>
</ul>
<p>What  has changed? Until now I had Portfiles that pick the source from a  Snapshot tarball I have stored on my site. This was the release version  that made it to the public in January 2011. Now I added Portfiles that  directly build the HEAD revision of the associated Source Repositories.  With these ports you are always up to date,but they are development  snapshots that might not work sometimes…You have been warned <img src="../wp-includes/images/smilies/icon_wink.gif" alt=";)" /></p>
]]></content:encoded>
			<wfw:commentRss>http://lallafa.de/blog/2011/07/updated-opencbm-and-nibtools-portfiles/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>What I&#8217;ve done lately&#8230;</title>
		<link>http://lallafa.de/blog/2011/06/what-ive-done-lately/</link>
		<comments>http://lallafa.de/blog/2011/06/what-ive-done-lately/#comments</comments>
		<pubDate>Sun, 05 Jun 2011 17:30:59 +0000</pubDate>
		<dc:creator>lallafa</dc:creator>
				<category><![CDATA[Commodore 64]]></category>
		<category><![CDATA[Hardware]]></category>
		<category><![CDATA[Mac Stuff]]></category>
		<category><![CDATA[Misc]]></category>
		<category><![CDATA[My Site]]></category>
		<category><![CDATA[Software]]></category>
		<category><![CDATA[VICE]]></category>
		<category><![CDATA[VICE on Mac]]></category>

		<guid isPermaLink="false">http://lallafa.de/blog/?p=260</guid>
		<description><![CDATA[<p>So many month passed by and no update here&#8230; I wasn&#8217;t lazy (at least not all the time and so I&#8217;ll give you a short summary what retro projects I&#8217;ve been involved with lately:</p> DiskFreeezerX &#8211; My pet project that aims to build a standalone disk capture device&#8230; Should come very handy for partys or <span style="color:#777"> . . . &#8594; Read More: <a href="http://lallafa.de/blog/2011/06/what-ive-done-lately/">What I&#8217;ve done lately&#8230;</a></span>]]></description>
			<content:encoded><![CDATA[<p>So many month passed by and no update here&#8230; I wasn&#8217;t lazy (at least not all the time <img src='http://lallafa.de/blog/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' />  and so I&#8217;ll give you a short summary what retro projects I&#8217;ve been involved with lately:</p>
<ul>
<li><a title="DiskFreezerX" href="http://lallafa.de/blog/diskfreezerx/">DiskFreeezerX</a> &#8211; My pet project that aims to build a standalone disk capture device&#8230; Should come very handy for partys or meeting people that don&#8217;t want to leave their precious disks&#8230; Take the device with you, slip in a disk, press a button and some time later you have a shiny exact clone of the disk on your SD card&#8230; That&#8217;s the goal!<br />
The current state here is: The device is built and functional as a prototype and as a first Rev A PCB&#8230; See my shiny new <a title="dfx Hardware" href="http://lallafa.de/blog/diskfreezerx/dfx-hardware/">dfx hardware</a> page for all the glory details and lots of photos&#8230;<br />
<a href="http://lallafa.de/blog/wp-content/uploads/2011/06/dfx-board1.jpg"><img class="aligncenter size-medium wp-image-226" title="dfx-board1" src="http://lallafa.de/blog/wp-content/uploads/2011/06/dfx-board1-300x150.jpg" alt="" width="300" height="150" /></a></li>
<li><a title="MacVICE" href="http://lallafa.de/blog/macvice/">MacVICE</a> &#8211; Not much own contribs done here lately. But always following the flow of new features and busy building current snapshots. And before I forget it: With MagerValp&#8217;s help I finally fixed the dreaded &#8220;black-screen&#8221; display problem when the fine blended display is enabled&#8230; So enjoy temporal filtering with no more black outs!</li>
<li><a href="https://github.com/GnoStiC/PUAE">PUAE</a> &#8211; I am really happy that GnoStiC is now bringing together the current WinUAE and the already dated E-UAE code base to create finally a greate Amiga emualator for all *nix, Linux and Mac users&#8230; I really appreciate that and help by submitting small patches. I&#8217;ve created my own little fork/clone of the repository at GitHub: You can check this out if you want to have a look what I am patching lately: <a href="https://github.com/cnvogelg/PUAE">PUAE/cnvogelg</a></li>
<li><a href="https://www.gitorious.org/amitools/amitools">amitools</a> &#8211; Another little crazy project started by me. Its a python library that allows you to read and parse Amiga&#8217;s Hunk-based binary format. With all the memory on the good ol&#8217; times fading away and with UAE refreshing my old desire for the Amiga I wrote this lib to refresh and to store the old knowledge in readable python code. Currently, there is not much docs there. But a real hacker will find his/her way&#8230; I wrote a small sample that scans your harddrive for amiga files (even in adf, lha containers) and tries to parse the exe with the lib&#8230; The lib got a new push with the introduction of the <a href="http://en.wikibooks.org/wiki/Aros/Platforms/68k_support">AROS m68k Port</a> (yay!!).. This port uses a decent gcc compiler to generate m68k-elf binaries. So I added ELF parsing to amitools. The only thing still missing is now the converter elf to hunk and back again in python (similar to <a href="http://www.evillabs.net/wiki/index.php/AROS_m68k-amiga">elf2hunk</a>)&#8230;</li>
</ul>
<p>That&#8217;s it! See you soon with more updates&#8230;</p>
]]></content:encoded>
			<wfw:commentRss>http://lallafa.de/blog/2011/06/what-ive-done-lately/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Nibtools on Mac added and OpenCBM on Mac updated</title>
		<link>http://lallafa.de/blog/2011/02/nibtools-on-mac-added-and-opencbm-on-mac-updated/</link>
		<comments>http://lallafa.de/blog/2011/02/nibtools-on-mac-added-and-opencbm-on-mac-updated/#comments</comments>
		<pubDate>Tue, 01 Feb 2011 18:50:16 +0000</pubDate>
		<dc:creator>lallafa</dc:creator>
				<category><![CDATA[Commodore 64]]></category>
		<category><![CDATA[Hardware]]></category>
		<category><![CDATA[Mac Stuff]]></category>
		<category><![CDATA[Software]]></category>

		<guid isPermaLink="false">http://lallafa.de/blog/?p=218</guid>
		<description><![CDATA[<p>Now with ZoomFloppy device hitting the streets and a growing number of Mac users that own this device its about time to give them decent software packages to work with. I already started the OpenCBM on Mac page quite some time ago when I started to help porting the code for Macs. I reworked the <span style="color:#777"> . . . &#8594; Read More: <a href="http://lallafa.de/blog/2011/02/nibtools-on-mac-added-and-opencbm-on-mac-updated/">Nibtools on Mac added and OpenCBM on Mac updated</a></span>]]></description>
			<content:encoded><![CDATA[<p>Now with ZoomFloppy device hitting the streets and a growing number of Mac users that own this device its about time to give them decent software packages to work with. I already started the OpenCBM on Mac page quite some time ago when I started to help porting the code for Macs. I reworked the full page and simplified a lot of things. Here it is the shiny new <a title="OpenCBM on Mac" href="http://lallafa.de/blog/opencbm-on-mac/">OpenCBM on Mac</a> page with special attention for easy setup of ZoomFloppy users!</p>
<p>The OpenCBM tools are really useful for day-to-day normal disk transfers. But when it comes to copy-protected disks the only tool there is Nibtools from <a href="http://c64preservation.com/">C64Preservation</a>. These tools use the OpenCBM libraries and I soon got them to compile on my machine. The only thing missing there was writing a Portfile and setting up a page similar to the OpenCBM on Mac one. Here we go: I added a shiny new Portfile for Nibtools and described its installation on the <a title="Nibtools on Mac" href="http://lallafa.de/blog/opencbm-on-mac/nibtools-on-mac/">Nibtools on Mac</a> page.</p>
<p>Enjoy installing all the nice tools on your Mac and have lots of fun capturing your old treasures to disk images&#8230;</p>
]]></content:encoded>
			<wfw:commentRss>http://lallafa.de/blog/2011/02/nibtools-on-mac-added-and-opencbm-on-mac-updated/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>dtv2ser 0.5 released</title>
		<link>http://lallafa.de/blog/2010/12/dtv2ser-0-5-released/</link>
		<comments>http://lallafa.de/blog/2010/12/dtv2ser-0-5-released/#comments</comments>
		<pubDate>Sat, 11 Dec 2010 21:20:25 +0000</pubDate>
		<dc:creator>lallafa</dc:creator>
				<category><![CDATA[DTV64]]></category>
		<category><![CDATA[Hardware]]></category>

		<guid isPermaLink="false">http://lallafa.de/blog/?p=200</guid>
		<description><![CDATA[<p>From time to time I get requests of users who want to buy or build their own dtv2ser device from the schematics I published in previous dtv2ser versions. Unfortunately, I only ordered a small number of prototype boards and those boards are already all sold out. For most users the schematic is too difficult to <span style="color:#777"> . . . &#8594; Read More: <a href="http://lallafa.de/blog/2010/12/dtv2ser-0-5-released/">dtv2ser 0.5 released</a></span>]]></description>
			<content:encoded><![CDATA[<p>From time to time I get requests of users who want to buy or build their own dtv2ser device from the schematics I published in previous dtv2ser versions. Unfortunately, I only ordered a small number of prototype boards and those boards are already all sold out. For most users the schematic is too difficult to build from scratch and so they couldn&#8217;t use dtv2ser at all <img src='http://lallafa.de/blog/wp-includes/images/smilies/icon_sad.gif' alt=':(' class='wp-smiley' /> </p>
<p>With the growing popularity of the Arduino platform I soon had the idea to &#8220;port&#8221; the dtv2ser firmware to this common and easy available boards. I managed to get the firmware running in about a day and the good thing is: only three tiny HW modifications are required to transform a Arduino 2009 board into a fully functional dtv2ser device&#8230; So time to pack all the new stuff together and make a new release&#8230;</p>
<p>..here it is: <a title="dtv2ser" href="http://lallafa.de/blog/dtv2ser/">dtv2ser 0.5 with Arduino 2009 support</a> is available. The release mainly contains the new board support and some minor bug fixes.<a href="http://lallafa.de/blog/wp-content/uploads/2010/12/dtv2ardu-side.jpg"><img class="aligncenter size-medium wp-image-193" title="dtv2ardu-side" src="http://lallafa.de/blog/wp-content/uploads/2010/12/dtv2ardu-side-300x199.jpg" alt="" width="300" height="199" /></a></p>
<p>Enjoy and have fun building your own dtv2ser <img src='http://lallafa.de/blog/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /> </p>
]]></content:encoded>
			<wfw:commentRss>http://lallafa.de/blog/2010/12/dtv2ser-0-5-released/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>MacVICE News: Introducing IO Tree</title>
		<link>http://lallafa.de/blog/2010/11/macvice-news-introducing-io-tree/</link>
		<comments>http://lallafa.de/blog/2010/11/macvice-news-introducing-io-tree/#comments</comments>
		<pubDate>Sun, 14 Nov 2010 12:37:44 +0000</pubDate>
		<dc:creator>lallafa</dc:creator>
				<category><![CDATA[Commodore 64]]></category>
		<category><![CDATA[Mac Stuff]]></category>
		<category><![CDATA[VICE]]></category>
		<category><![CDATA[VICE on Mac]]></category>

		<guid isPermaLink="false">http://lallafa.de/blog/?p=170</guid>
		<description><![CDATA[<p>While the last added debugging features to MacVICE are all well-known and mostly ported from WinVICE this one is a new and currently mac-only debugging feature: The IO Tree. &#8220;What&#8217;s this?&#8221;, you might ask.</p> <p>The IO Tree is actually an anotated dump of the memory-mapped IO registers from your beloved cbm platform. All is packed <span style="color:#777"> . . . &#8594; Read More: <a href="http://lallafa.de/blog/2010/11/macvice-news-introducing-io-tree/">MacVICE News: Introducing IO Tree</a></span>]]></description>
			<content:encoded><![CDATA[<p>While the last added debugging features to MacVICE are all well-known and mostly ported from WinVICE this one is a new and currently <em>mac-only debugging feature</em>: The IO Tree. &#8220;What&#8217;s this?&#8221;, you might ask.</p>
<p>The IO Tree is actually an anotated dump of the memory-mapped IO registers from your beloved cbm platform. All is packed into a GUI Tree to make it hierarchical and let you control the vast amount of information that is kept there. But IO Tree is not only a register dump with descriptions, it also allows to combine and format the register values to make most sense and to reflect the actual function they represent. So the IO Tree can combine LO-/HI-Addr registers to show a 16 Bit address, can mask out a bit flag and show its state, maps a masked value set to a set of string descriptions or even do very special things like decoding VIC II color values&#8230;</p>
<p>The nice thing about the IO Tree is, that it is actually not stored in the MacVICE binary but in a text PList called <strong>IOTree.plist</strong>. This allows to extend the tree with new custom registers for every user. Currently, I have typed in all VIC II, SID, CIA 1, CIA 2 and 6510 On-Chip registers right out of <a href="http://unusedino.de/ec64/technical/aay/c64/">AYY64</a> (Thanks Ninja/The Dreams for this great resource!). If you find errors or have something to add then drop me a comment&#8230; Currently the syntax of the plist is not documented but simply have a look at the existing tree and you&#8217;ll find out how it works&#8230;</p>
<p>If you want to try out IO Tree then have a look at the latest MacVICE snapshot (at least revision 23154 is required). While waiting for its upload/download enjoy a screenshot:</p>
<p><a href="http://lallafa.de/blog/wp-content/uploads/2010/11/macvice_iotree.png"><img class="aligncenter size-full wp-image-171" title="macvice_iotree" src="http://lallafa.de/blog/wp-content/uploads/2010/11/macvice_iotree.png" alt="" width="596" height="579" /></a></p>
]]></content:encoded>
			<wfw:commentRss>http://lallafa.de/blog/2010/11/macvice-news-introducing-io-tree/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>MacVICE News: New Debug Windows</title>
		<link>http://lallafa.de/blog/2010/11/macvice-news-new-debug-windows/</link>
		<comments>http://lallafa.de/blog/2010/11/macvice-news-new-debug-windows/#comments</comments>
		<pubDate>Sun, 14 Nov 2010 12:03:50 +0000</pubDate>
		<dc:creator>lallafa</dc:creator>
				<category><![CDATA[Commodore 64]]></category>
		<category><![CDATA[Mac Stuff]]></category>
		<category><![CDATA[VICE]]></category>
		<category><![CDATA[VICE on Mac]]></category>

		<guid isPermaLink="false">http://lallafa.de/blog/?p=162</guid>
		<description><![CDATA[<p>I am currently working on extending MacVICE with some fancy debugging features. Users of WinVICE already know the memory, register and disassemlby windows that exist besides the monitor view.</p> <p>I adopted all of these window types with a slight make-it-the-mac-way style attached My debug windows are tied to the main or drive CPU and need <span style="color:#777"> . . . &#8594; Read More: <a href="http://lallafa.de/blog/2010/11/macvice-news-new-debug-windows/">MacVICE News: New Debug Windows</a></span>]]></description>
			<content:encoded><![CDATA[<p>I am currently working on extending MacVICE with some fancy debugging features. Users of WinVICE already know the memory, register and disassemlby windows that exist besides the monitor view.</p>
<p>I adopted all of these window types with a slight make-it-the-mac-way style attached <img src='http://lallafa.de/blog/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' />  My debug windows are tied to the main or drive CPU and need no switching. Currently, only the CPU windows are available.</p>
<p>The windows are available in the current MacVICE snapshots:</p>
<p style="text-align: center;"><a href="http://lallafa.de/blog/wp-content/uploads/2010/11/macvice_disas.png"><img class="size-medium wp-image-163 aligncenter" title="macvice_disas" src="http://lallafa.de/blog/wp-content/uploads/2010/11/macvice_disas-215x300.png" alt="" width="215" height="300" /></a><a href="http://lallafa.de/blog/wp-content/uploads/2010/11/macvice_mem.png"><img class="aligncenter size-medium wp-image-164" title="macvice_mem" src="http://lallafa.de/blog/wp-content/uploads/2010/11/macvice_mem-300x173.png" alt="" width="300" height="173" /></a><a href="http://lallafa.de/blog/wp-content/uploads/2010/11/macvice_reg.png"><img class="aligncenter size-full wp-image-165" title="macvice_reg" src="http://lallafa.de/blog/wp-content/uploads/2010/11/macvice_reg.png" alt="" width="192" height="223" /></a></p>
<p>I hope you like them&#8230;</p>
<p>BTW: If you don&#8217;t find this feature have a look in the &#8220;Window/Debugger Windows&#8221; menu <img src='http://lallafa.de/blog/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /> </p>
]]></content:encoded>
			<wfw:commentRss>http://lallafa.de/blog/2010/11/macvice-news-new-debug-windows/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>XUM1541 and OpenCBM for Mac</title>
		<link>http://lallafa.de/blog/2009/12/xum1541-and-opencbm-for-mac/</link>
		<comments>http://lallafa.de/blog/2009/12/xum1541-and-opencbm-for-mac/#comments</comments>
		<pubDate>Sat, 19 Dec 2009 20:18:33 +0000</pubDate>
		<dc:creator>lallafa</dc:creator>
				<category><![CDATA[Commodore 64]]></category>
		<category><![CDATA[Hardware]]></category>
		<category><![CDATA[Mac Stuff]]></category>

		<guid isPermaLink="false">http://lallafa.de/blog/?p=128</guid>
		<description><![CDATA[<p>With christmas time the presents arrive&#8230; Nate Lawson presented the beta of his incredible XUM1541 USB to IEC/parallel adapter for OpenCBM. I was immediately amazed by this project and built my own version of the XUM1541. I had the chance to help out testing the software on Macs even in its early stages, so everything <span style="color:#777"> . . . &#8594; Read More: <a href="http://lallafa.de/blog/2009/12/xum1541-and-opencbm-for-mac/">XUM1541 and OpenCBM for Mac</a></span>]]></description>
			<content:encoded><![CDATA[<p>With christmas time the presents arrive&#8230; Nate Lawson presented the beta of his incredible <a href="http://www.root.org/~nate/c64/xum1541/">XUM1541</a> USB to IEC/parallel adapter for <a href="http://sourceforge.net/projects/opencbm/">OpenCBM</a>. I was immediately amazed by this project and built my own version of the XUM1541. I had the chance to help out testing the software on Macs even in its early stages, so everything will work smoothly on our favorite platform&#8230;</p>
<p style="text-align: left;">
<div id="attachment_125" class="wp-caption aligncenter" style="width: 330px"><a href="http://lallafa.de/blog/wp-content/uploads/2009/12/XUM1541.jpg"><img class="size-full wp-image-125 " title="XUM1541" src="http://lallafa.de/blog/wp-content/uploads/2009/12/XUM1541.jpg" alt="" width="320" height="219" /></a><p class="wp-caption-text">Lallafa&#39;s XUM1541 Prototype</p></div>
<p>Now with the beta of <a href="http://rdist.root.org/2009/12/11/xum1541-beta-now-available/">XUM1541 online</a>, I have another present for you: The <a title="OpenCBM on Mac" href="http://lallafa.de/blog/opencbm-on-mac/">OpenCBM on Mac </a>page on my site. This page describes how to compile and set up the OpenCBM software yourself and how to get your device running on your Mac. Have fun!</p>
]]></content:encoded>
			<wfw:commentRss>http://lallafa.de/blog/2009/12/xum1541-and-opencbm-for-mac/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>dtv2ser 0.4 released!</title>
		<link>http://lallafa.de/blog/2008/09/dtv2ser-04-released/</link>
		<comments>http://lallafa.de/blog/2008/09/dtv2ser-04-released/#comments</comments>
		<pubDate>Sun, 28 Sep 2008 16:58:41 +0000</pubDate>
		<dc:creator>lallafa</dc:creator>
				<category><![CDATA[DTV64]]></category>
		<category><![CDATA[Hardware]]></category>
		<category><![CDATA[Mac Stuff]]></category>
		<category><![CDATA[Software]]></category>

		<guid isPermaLink="false">http://lallafa.de/blog/?p=88</guid>
		<description><![CDATA[<p>LTNS! Yes, indeed&#8230; it took quite a while to finish this new version, but its really worth the wait!</p> <p>dtv2ser 0.4 now supports all new features of dtvtrans 1.0 including init after reset, BASIC loading, saving and RUN. Furthermore, full flash support was added!</p> <p>If you are impatient then just head over to the dtv2ser <span style="color:#777"> . . . &#8594; Read More: <a href="http://lallafa.de/blog/2008/09/dtv2ser-04-released/">dtv2ser 0.4 released!</a></span>]]></description>
			<content:encoded><![CDATA[<p>LTNS! Yes, indeed&#8230; it took quite a while to finish this new version, but its really worth the wait!</p>
<p>dtv2ser 0.4 now supports all new features of <b>dtvtrans 1.0</b> including init after reset, BASIC loading, saving and RUN. Furthermore, full <b>flash</b> support was added!</p>
<p>If you are impatient then just head over to the <a href="http://www.lallafa.de/blog/dtv2ser">dtv2ser homepage</a> and download your copy.</p>
<p><span id="more-88"></span></p>
<p>What&#8217;s new in this version? Let me explain it with a short walk through:</p>
<h3>Basics</h3>
<p>After flashing the new 0.4 firmware, you launch the dtv2sertrans client as usual. On Macs you can see some kind of auto-detection of the serial port:</p>
<pre>
> dtv2sertrans
dtv2sertrans version 0.4, dtv2ser device version 0.4
dtvtrans server NOT responding!!
</pre>
<p>Ah&#8230; no dtvtrans server is running on my DTV. So let&#8217;s reset the DTV (and enter dtvtrans via dtvboot):</p>
<pre>
> dtv2sertrans reset
dtv2sertrans version 0.4, dtv2ser device version 0.4
  resetting dtv... enter dtvtrans
  initializing full BASIC
</pre>
<p>That&#8217;s new: BASIC and KERNAL is fully initialized after a reset, so BASIC commands like load, save, run will work. Querying dtv2sertrans again:</p>
<pre>
> dtv2sertrans
dtv2sertrans version 0.4, dtv2ser device version 0.4
dtvtrans server version 1.0 (DTVBOOT 1.2 via joy2 in ROM)
</pre>
<p>Now the server is detected and reports the version, the port and if it resides in RAM or ROM.<br />
You can query more info with:</p>
<pre>
> dtv2sertrans server info
  dtvtrans revision: 1.0
    implementation:  DTVBOOT 1.2
    port:            joy2
    mode:            ROM
    range:           0x1f8000-0x1fb3db
</pre>
<h3>dtvtrans 1.0 Features</h3>
<p>Let&#8217;s check out the new dtvtrans 1.0 features that support BASIC commands and simplify loading, running programs:</p>
<pre>
> dtv2sertrans reset + load mygame.prg + run
</pre>
<p>Reset + init BASIC, load a program via dtv2ser and run it&#8230; That&#8217;s easy!</p>
<pre>
> dtv2sertrans save myprog.prg
</pre>
<p>This call saves the current program like the BASIC SAVE does only via dtv2ser&#8230;</p>
<p>Whats quite handy is a fill commando to simple write a value (e.g. 0) to a range of memory:</p>
<pre>
> dtv2sertrans fill 0x18000-0x20000 0
</pre>
<h3>Flash Commands</h3>
<p>And now flashing! But first a <b>Warning:</b> Flashing operation can destroy your DTV. So you have to be sure what you are doing. In this guide I&#8217;ll warn you, if something dangerous will happen. So you can decide if you dare it <img src='http://lallafa.de/blog/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /> </p>
<p>First let&#8217;s see if your dtv2ser device can handle sys calls:</p>
<pre>
> dtv2sertrans diag sys
dtv2sertrans version 0.4, dtv2ser device version 0.4
  loading servlet '/Users/chris/Projects/svn/dtv2ser/servlet/diag_srv.prg'
  testing 25 sys calls with wait and return value fetch
  * 0/25: testing sys call with 84 frames duration
  duration: 00:01.823
...
  * 24/25: testing sys call with 51 frames duration
  duration: 00:01.219
  * 25/25: all calls passed OK!
</pre>
<p>Ok, sys call test passed without errors&#8230; So the flash commands that are called via sys should work.<br />
Now let&#8217;s ensure that the dtvtrans server program is runnning from RAM and not from ROM!</p>
<pre>
> dtv2sertrans server ram
dtv2sertrans version 0.4, dtv2ser device version 0.4
  resetting...
  is alive?
  initializing BASIC
  query dtvtrans server
  dtvtrans running in ROM. loading RAM version
  loading prg file '/Users/chris/Projects/svn/dtv2ser/contrib/dtvtrans_joy2.prg': 2548/0x0009f4 bytes, start: 0x0801
  sending program to DTV
    speed:  client=16.48 server=16.59 (kbyte/s)
    time:   00:00.191 for 2548/0x0009f4 bytes
  run program
  query dtvtrans server
  dtvtrans is now in RAM. Good!
    implementation: DTVTRANS 1.0
</pre>
<p>Fine, server now running from RAM&#8230; We are ready for flashing!<br />
Let&#8217;s check the type of the flash ROM found in the DTV:</p>
<pre>
> dtv2sertrans flash id
dtv2sertrans version 0.4, dtv2ser device version 0.4
  flash type: SST39VF1681
</pre>
<p>Now let&#8217;s have a look a the flash usage:</p>
<pre>
> dtv2sertrans flash map
dtv2sertrans version 0.4, dtv2ser device version 0.4
  generating flash map on DTV
  duration: 00:04.731
          flash ROM map ('.'=empty '*'=filled)
          0xxx 1xxx 2xxx 3xxx 4xxx 5xxx 6xxx 7xxx 8xxx 9xxx Axxx Bxxx Cxxx Dxxx Exxx Fxxx
  000000: .... **** .... .... .... .... .... .... .... **** **** **** .... **** **** ****
  010000: **** ***. .... .... **** **** **** **** **** **** **** **** **** **** **** ****
  020000: **** **** **** **** **** **** **** **** **** **** **** **** **** **** **** ****
  030000: **** **** **** **** **** **** **** **** **** **** **** **** **** **** **** ****
  040000: **** **** **** **** **** **** **** **** **** **** **** **** **** **** **** ****
  050000: **** **** **** **** **** **** **** **** **** **** **** **** **** **** **** ****
  060000: **** **** **** **** **** **** **** **** **** **** **** **** **** **** **** ****
  070000: **** **** **** **** **** **** **** **** **** **** **** **** **** **** **** ****
  080000: **** **** **** **** **** **** **** **** **** **** **** **** **** **** **** ****
  090000: **** **** **** **** **** **** **** **** **** **** **** **** **** **** **** ****
  0a0000: **** **** **** **** **** **** **** **** **** **** **** **** **** **** **** ****
  0b0000: **** **** **** **** **** **** **** **** **** **** **** **** **** **** **** ****
  0c0000: **** **** **** **** **** **** **** **** **** **** **** **** **** **** **** ****
  0d0000: **** **** **** **** **** **** **** **** **** **** **** **** **** **** **** ****
  0e0000: **** **** **** **** **** **** **** **** **** **** **** **** **** **** **** ****
  0f0000: **** **** **** **** **** **** **** **** **** **** **** **** **** **** **** ****
  100000: **** **** **** **** **** **** **** **** **** **** **** **** **** **** **** ****
  110000: **** **** **** **** **** **** **** **** **** **** **** **** **** **** **** ****
  120000: **** **** **** **** **** **** **** **** **** **** **** **** **** **** **** ****
  130000: **** **** **** **** **** **** **** **** **** **** **** **** **** **** **** ****
  140000: **** **** **** **** **** **** **** **** **** **** **** **** **** **** **** ****
  150000: **** **** **** **** **** **** **** **** **** **** **** **** **** **** **** ****
  160000: **** **** **** **** **** **** **** **** **** **** **** **** **** **** **** ****
  170000: **** **** **** **** **** **** **** **** **** **** **** **** **** **** **** ****
  180000: **** **** **** **** **** **** **** **** **** **** **** **** **** **** **** ****
  190000: **** **** **** **** **** **** **** **** **** **** **** **** **** **** **** ****
  1a0000: **** **** **** **** **** **** **** **** **** **** **** **** **** **** **** ****
  1b0000: **** **** **** **** **** **** **** **** **** **** **** **** **** **** **** ****
  1c0000: **** **** **** **** **** **** **** **** **** **** **** **** **** **.. .... ....
  1d0000: .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... ....
  1e0000: .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... ....
  1f0000: .... .... .... .... .... .... .... .... **** **** **** **** **** **** **** ****
</pre>
<p>The first step in flashing is to store the current contents of the flash ROM in a file:</p>
<pre>
> dtv2sertrans flash dump orig_rom.bin
dtv2sertrans version 0.4, dtv2ser device version 0.4
  dumping flash ROM to file 'orig_rom.bin'
    speed:  client=17.95 server=17.96 (kbyte/s)
    time:   01:54.116 for 2097152/0x200000 bytes
  saving raw file 'orig_rom.bin': 2097152/0x200000 bytes
</pre>
<p>Now, create or alter the ROM file (e.g. use tools like <a href="http://picobay.com/dtv_wiki/index.php?title=DTVFSEdit">DTVFSEdit</a>).<br />
If the new ROM is ready, you can flash it back to your DTV with (first in dummy mode w/o flashing):</p>
<pre>
> dtv2sertrans flash sync new_rom.bin
dtv2sertrans version 0.4, dtv2ser device version 0.4
  loading raw file 'new_rom.bin': 2097152/0x200000 bytes
  syncing flash ROM
          flash ROM map ('*'=flash '#'=erase+flash)
          0xxx 1xxx 2xxx 3xxx 4xxx 5xxx 6xxx 7xxx 8xxx 9xxx Axxx Bxxx Cxxx Dxxx Exxx Fxxx
  010000: #... ..#. .... .... .... .... .... .... .... .... .... .... .... .... .... ....
  020000: .... .... .... .... .... .... .... .... .... .... .... .... .... .... .... ....
...
</pre>
<p>If you add the -f switch then a real flash operation is performed. This will alter your DTV! So make sure the image is correct:</p>
<pre>
> dtv2sertrans flash sync -f new_rom.img
...
</pre>
<p>Ok, that&#8217;s it! This was a short walk through for all the new dtv2ser 0.4 features. But there are many more things to discover. Just run dtv2sertrans -h to see more options&#8230;</p>
<p>Have Fun,<br />
-chris</p>
]]></content:encoded>
			<wfw:commentRss>http://lallafa.de/blog/2008/09/dtv2ser-04-released/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Finished my DIY 1541U Cartridge Case</title>
		<link>http://lallafa.de/blog/2008/06/finished-my-diy-1541u-cartridge-case/</link>
		<comments>http://lallafa.de/blog/2008/06/finished-my-diy-1541u-cartridge-case/#comments</comments>
		<pubDate>Sun, 01 Jun 2008 10:34:23 +0000</pubDate>
		<dc:creator>lallafa</dc:creator>
				<category><![CDATA[DTV64]]></category>
		<category><![CDATA[Hardware]]></category>
		<category><![CDATA[Misc]]></category>

		<guid isPermaLink="false">http://lallafa.de/blog/index.php/2008/06/01/finished-my-diy-1541u-cartridge-case/</guid>
		<description><![CDATA[ <p>Puh, finally my 1541U cartridge has a decent case! I created one myself starting with a generic case at the price of about one EUR&#8230;</p> <p>Have a look at my Lallafa&#8217;s 1541U DIY Cartridge Case Page for more details!</p> ]]></description>
			<content:encoded><![CDATA[
<a href="http://lallafa.de/blog/wp-content/gallery/u1541cart/1541UCart1.jpg" title="" class="shutterset_singlepic14" >
	<img class="ngg-singlepic" src="http://lallafa.de/blog/wp-content/gallery/cache/14__320x240_1541UCart1.jpg" alt="1541UCart1" title="1541UCart1" />
</a>

<p>Puh, finally my 1541U cartridge has a decent case!<br />
I created one myself starting with a generic case at the price of about one EUR&#8230;</p>
<p>Have a look at my <a href="http://lallafa.de/blog/index.php/u1541-diy-cartridge-case">Lallafa&#8217;s 1541U DIY Cartridge Case Page</a> for more details!</p>
]]></content:encoded>
			<wfw:commentRss>http://lallafa.de/blog/2008/06/finished-my-diy-1541u-cartridge-case/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>sd2iec in DTV Joystick</title>
		<link>http://lallafa.de/blog/2008/04/sd2iec-in-dtv-joystick/</link>
		<comments>http://lallafa.de/blog/2008/04/sd2iec-in-dtv-joystick/#comments</comments>
		<pubDate>Sun, 06 Apr 2008 13:25:44 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[DTV64]]></category>
		<category><![CDATA[Hardware]]></category>

		<guid isPermaLink="false">http://lallafa.de/blog/index.php/2008/04/06/sd2iec-in-dtv-joystick/</guid>
		<description><![CDATA[ <p>I just built my sd2iec device board from Shadowolf. Its really small and compact so I thought why not integrate it into my modded DTV with the original joystick case. I don&#8217;t wanted to sacrificy the battery case so I knew there is not much place left&#8230;</p> <p>With a lot of cramming and fiddling <span style="color:#777"> . . . &#8594; Read More: <a href="http://lallafa.de/blog/2008/04/sd2iec-in-dtv-joystick/">sd2iec in DTV Joystick</a></span>]]></description>
			<content:encoded><![CDATA[
<a href="http://lallafa.de/blog/wp-content/gallery/dtvmod/dtvmod02.jpg" title="" class="shutterset_singlepic9" >
	<img class="ngg-singlepic" src="http://lallafa.de/blog/wp-content/gallery/cache/9__320x240_dtvmod02.jpg" alt="dtvmod02" title="dtvmod02" />
</a>

<p>I just built my <a href="http://http://www.forum64.de/wbb3/index.php?page=Board&amp;boardID=194">sd2iec device</a> board from Shadowolf. Its really small and compact so I thought why not integrate it into my modded DTV with the original joystick case. I don&#8217;t wanted to sacrificy the battery case so I knew there is not much place left&#8230;</p>
<p>With a lot of cramming and fiddling around I finally managed to insert the sd2iec inside my DTV Mod. Phew! Now the case is filled up to the limit &#8211; but its cool to have a sd2iec right inside the joystick;)</p>

<a href="http://lallafa.de/blog/wp-content/gallery/dtvjoy/dtvjoy07.jpg" title="" class="shutterset_singlepic7" >
	<img class="ngg-singlepic" src="http://lallafa.de/blog/wp-content/gallery/cache/7__320x240_dtvjoy07.jpg" alt="dtvjoy07" title="dtvjoy07" />
</a>

<p>Have a look here at <a href="http://lallafa.de/blog/index.php/modded-dtv-joystick-gallery/">my gallery</a> for more pictures!</p>
]]></content:encoded>
			<wfw:commentRss>http://lallafa.de/blog/2008/04/sd2iec-in-dtv-joystick/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
	</channel>
</rss>

