On 6/3/2006 at 7:54 AM Richard A. Cini wrote:
Going back to an original comment about using the
LABEL command in
the 22DISK definition, when producing the data for the LBL file, is that
data in straight track/sector order?
That all depends on the definition. If the sector ordering is given as
1,6,11,16,2,7...., that's the order that 22DISK writes the label record.
It only makes sense to do it that way. While there are a few systems that
adopt a different scheme to store the boot tracks, trying to accommodate
them leads to madness.
I've even mixed and matched tools on a PeeCee to create CBIOS and Boot
loader disk images. Good old DOS DEBUG understands the .HEX files produced
by ASM and gives you a lot more command and address flexibility than does,
say, DDT. And DEBUG will write a file for you.
If we're really missing the CP/M Alteration Guide from online archives, I
can scan one of my copies and email it to someone who's willing to host it,
as long as whomever owns the rights to the publication doesn't care.
With SS media, you're going to be restricted to about 80K of usable disk
space. The Xerox 820 XER2 definition should be fine for that.
I think (but I'd have to check) the Tarbell controller used a little 82S123
bipolar fuse-programmable ROM to hold the bootstrap code. A tight squeeze,
but it worked.
Cheers,
Chuck