[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: CP/M disk format question
- Subject: Re: CP/M disk format question
- From: jonnosan <jonnosan@gmail.com>
- Date: Fri, 11 Jul 2008 15:11:01 -0700 (PDT)
- Complaints-to: groups-abuse@google.com
- Injection-info: s50g2000hsb.googlegroups.com; posting-host=144.137.72.142; posting-account=XeaUgQoAAACn-Gws0Ssl9mrTmlxSVui3
- Newsgroups: comp.sys.apple2
- Organization: http://groups.google.com
- References: <48779f9e$0$17148$742ec2ed@news.sonic.net>
- User-agent: G2/1.0
- Xref: g2news1.google.com comp.sys.apple2:1570
On Jul 12, 3:59 am, Andy McFadden <fad...@fadden.com> wrote:
>
> I've been sent an apparently valid disk image that uses block numbers above
> 128. It appears that such values wrap around, storing data in track 0-2.
>
Andy,
By coincidence, I've recently been hacking cp/m handling into my
dsktool.rb library - is there any chance I could get a copy of the
problematic image (or any other particularly interesting specimens)?
BTW as part of that cp/m work, I put together code to parse
(unprotected) MBASIC / GBASIC tokenised files, it's pretty simple -
the format is exactly the same as the x86 BASICA/GWBASIC format
described at http://www.chebucto.ns.ca/~af380/GW-BASIC-tokens.html -
the only difference seems to be the mapping of bytes to keywords - I
can supply those values if you're interested in adding this to
CiderPress.