Re: Building an Apple CP/M Disk

["Bill Buckels" <bbuckels@mts.net>]

"schmidtd" <schmidtd@my-deja.com> wrote in message 
64cff4fc-4556-4173-9a9e-97b963eebec3@k1g2000prb.googlegroups.com">news:64cff4fc-4556-4173-9a9e-97b963eebec3@k1g2000prb.googlegroups.com...
>What's interesting to me is that you're exposing and overcoming the 
>shortcoming that none of our image manipulation tools support writing to 
>CP/M disk images.  If they did, you could boil all of this down to "Ctrl-C 
>and Ctrl-V."  (Plus the header stripping, but that could be built into the 
>CP/M support of the image manipulator, I suppose.)

The whole CP/M retro-computing community (if such it can be called) indulges 
in a plethora of strange work-arounds and perhaps that is part of the 
attraction for me. The CP/M era in general was devoid of the mythical 
unifying standards that we profess today. So it seems fitting that a rugged 
workaround dovetailed by documentation spanning decades can be glued 
together and made to work without all the mouse-master cr*pola.

Yep, it is an interesting noodle-scratcher, and probably somebody twice as 
smart as me (likely a schmidt or a european dude) will show us a better way 
to do what I wrote about. If not today then give it a day or so... although 
there isn't much romantic about CP/M so maybe my tough-love approach is as 
good as it gets.

Elementary my dear fellow. What I am not saying is that I could write a 
utility that writes to an Apple CP/M diskimage, but for lazy reasons I don't 
plan to at the moment if ever.

Bill