Re: nibtools, GCR, G64

From: silverdr_at_wfmh.org.pl
Date: Thu, 30 May 2013 19:55:51 +0200
Message-Id: <53CFFCD2-59E9-4DA5-8B43-908AE16597FC@wfmh.org.pl>
On 2013-05-30, at 19:09, Nate Lawson wrote:

>> Maybe we think of different things / use cases. I mean I am still /looking/ for the SYNC mark here. Actually in a G64 file. And being compliant with the said documentation caused me to write eight "else if" blocks (which I am afraid may never be needed) rather than one or two lines.
> 
> 
> May I suggest you check out nibedit?

Nate! Nice to see you joining the thread too! :-)

> I posted it on my web page, both in Python script and Windows exe forms.

So you have a Python compiler for Windows?

> http://root.org/~nate/c64/
> 
> Note that it's a beta and more testing/fixing is needed, but it does decode G64 files, including emulating drive behavior of aligning bits on sync.

Ha - I still need to collect all modules you import there to check that out in practice (windows exe is not much of a use here) but I already see that you delegate all the heavy-weight bit lifting to a "BistStream" lib. Something I have to do myself here without any crane..

Like: trk_stream.split(SYNC_SYMBOL) and there you are, right? Kinda c00l! But.. I discussed few minutes ago with Pete that "SYNC_SYMBOL" can theoretically also wrap around the track data of a G64. I suspect the "split" doesn't take this into account, does it?

-- 
SD!


       Message was sent through the cbm-hackers mailing list
Received on 2013-05-30 18:03:15

Archive generated by hypermail 2.2.0.